Websites/WebifyMe/Meeting May 11

From New wiki
Jump to navigation Jump to search

Wed May 11th 1pm PST

x474 Get to the Choppa

Follow Up

Picking up from our Apr 20th meeting

  • Claudia: Estimate amount of time TBG will be away until they can return to development on Webifyme.
  • Claudia: Estimate amount of time L10n blockers will take to fix
  • ozten: Update schedule based on this estimate
    • Unable to update schedule :(
  • Claudia: Write up admin screen requirements bug 654857
  • ozten: Give Krupa access to admin account on stage
    • No admin app, yet
  • William: Update copy bugs to be L10n blocker dependencies
  • Claudia: Will ask brez if Webifyme use Responsys for email address collection?

Status Update

Projects been largely frozen while TBG worked on Markup... 29 Open bugs

Dev/Stage/Prod - Operations Status Update

Top priority bug 650033 String Freeze and Extract blockers:

Copy Freeze

Stas asked if we in copy freeze

Williamr: yes, except maybe legal

Critical Path Timeline

TBD - String freeze

TBD - Webifyme-dev.allizom.org staged

TBD - WebQA starts

TBD - WebQA finishes

TBD - Go / No Go Decision

TBD - Prod launch

In Parallel Timeline

TBD

New Topics

  • Django 1.2.5, locale detection, other Playdoh like platform requirements

New Schedule Details

  • QA needs 2-3 days to certify stage is worth testing
  • UTest needs 2-3 days notice to schedule resources
  • L10n needs 3 weekends

Next Actions

  • Ops: New Person Starting May 12, will work on bug 656085, finishing stage and prod
    • Celery next
    • Jake or oremj probably
  • ozten: Will check with brez and Flux to see who will hookup Responsys
  • William: Will check on legal bug to make sure they are string frozen (privacy checkbox, etc)
  • ozten: Check with brez on # of Ajax calls (CSRF Django 1.2.5 work)
  • Tiffany - Will fix Typekit hostname issues bug 656085

Next Meeting is probably May 18th