Websites/WebifyMe/Meeting Apr 20

From MozillaWiki
Jump to: navigation, search

Wed April 20th 1pm PST

Follow Up

Picking up from our Apr 13th meeting

Grace

  • Stas or Gandalf - L10n time estimates, list of locales
    • Targeted locales: en-US, de, fr, it, es, pl, ja, ar, ru, pt-BR (other locales welcome as well)
    • L10n needs two weekends
  • Estimate peak and average traffic to the site
  • Estimate conversion rate for people finishing the quiz (image generated)

Stephen

  • Contact Accessibility community for testing
    • Accessibility bug will be filed when the staging is ready for QA
  • 15 QA engineers will start testing it from Monday (04/25)
  • Will work on the test plan once we have the site staged.

Ozten

Status Update

Critical Path Timeline

We're looking good here, TBG finished staging bugs and IT is staging the site.

Apr 15th - TBG Staging bugs Fixed

Apr 21th string freeze - 15th Slipped, new strings discovered in DB

Apr 22nd (1 week approx, 2 weeks would be Apr 29th worse case) Webifyme.allizom.org staged

Apr 25th - WebQA starts

May 6th - WebQA finishes

May 9th - Go / No Go Decision

May 10th - Prod launch

In Parallel Timeline

Apr 18th - May 6th - L10n Two weekends (Apr 30th and May 7th)

Apr 22nd - May 6th - Operations builds out prod environment (1 week approx)

Apr 24 - May 6th - Infrasec testing (4 days approx)

Triage as needed - TBG, Grace, Krupa, ozten

Apr 15th - May 6th - TBG fixing bugs which have been reported

New Topics

  • Couple new L10n bugs
  • What key success metrics are we measuring? How?
    • What percentage of people do we expect to finish the quiz?
      • 70 - 80%
    • What does it mean to finish the quiz
      • Answering at least 10 questions, generating an image
    • William to revisit bug 642348
    • Two reason 1) Measuring success of campaign 2) Estimating traffic and usage for Operations
  • Scope of L10n work is actually larger than previously thought. Any extra time (3 weekends) would be appreciated
    • Code staged so localizers can preview their work, we should wait to extract the strings until after the site is staged as this shakes out a lot of bugs
  • testers scheduled to start Monday.
    • They will cover locale testing
    • They will test locale detection first, even before localization is finished

Next Actions

[] Grace or William: Get exact peak numbers for TwitterParty to estimate peak load

[] William: Update Goals and Metrics bug

[] Stas: Will try a dry run at extracting strings, may file a bug to use Tower in the project

Next Meeting is Apr 27th

Retrieved from "https://wiki.mozilla.org/index.php?title=Websites/WebifyMe/Meeting_Apr_20&oldid=303441"