Book management 2014/Mentor's notes

Timeline

• Comunity bonding period: April 22 - May 18(27 days)
• Code time: May 19 - August 10(84 days)
  • Feature 1(8 days)
  • Test/doc/bugs 1(8 days)
  • Feature 2(8 days)
  • Test/doc/bugs 1(8 days)
  • Feature 3(8 days)
  • Test/doc/bugs 1(8 days)
  • Feature 4(8 days)
  • Test/doc/bugs 1(8 days)
  • Extra time(16 days)
• Final time: 11-24 August(12 days)
  • Extra time (Do not want to need to use this time to code): 11-17 August (7 days).
  • Final evaluation: 18-21 - August(4 days)
  • Send code to google: 22-24 August(3 days).

Test plan

• • Design (review)(in progress?)
  • Basic tests(in progress)
  • Debug(in progress)
  • Conventions(in progress)
  • Localisation(in progress)
  • Performace(in progress)
  • Security (checklist)(?)
  • Accessibility(?)
  • Compatibility(?)
• Documentation
  • Basic documentation in extension page Done(partial)
  • Make a screencast showing the fun
• Review queue
  • Create Extension: mediawiki.org page for the extension Done(extension page)
  • Request a component in the WMF Bugzilla instance Done(request - component)
  • Get the extension code in git/gerrit Done(request - git)
  • Ensure your extension is properly translatable.
  • Make a screencast showing the fun
  • Request a design review (especially needed if the extension affects any user facing functionality)
  • Request a performance and security reviews
  • Show community support/desire for the extension to be deployed (most likely applicable)
  • Create a tracking bug (see above) for the extensions deployment to WMF servers
    • This bug should only concern that issue, any sub-issues should be separate bugs that are marked as "blocking" this bug