QA/QMO/QMO 4.0/Meeting Notes

Team hierarchy
- Needed for browser technologies
- Each sub-team will have its own page, forum, members
- Need coordination with Buddypress possibly
Bugzilla Stats
- Needs:
  - store data using bugzilla rest api's
  - admin menu to add stats: primary pref menu of states per load, secondary menu of adding/deleting stats
  - show stats on user profile within a new tab
  - leave some flexibility to re-purpose data taken from bugzilla
Achievements
- Need a badging system from marcia/anthony on feb 11th
- designs for badges thereafter
- admin work will be necessary post-release of QMO
- achievements are their own tab based on the plugin

Agenda:

Attendees:

Notes:

Craig: He is a front end programmer and doesn't understand on how to build the plugin to bugzilla
Craig: If wordpress is going to be updated, we need to do regression testing
Al: There will be no authentication for pull of info from bugzilla
Al: There is a weekly DB backup and this site is completely separate from everything else.
Al: We are 2 months behind because of Firefox launch, re-org, and priorities have shifted.

To do:

Chris/Mike: Find a webdev resource for wordpress plugin creation
Chris: Find out if the website should be more branding toward Mozilla (ask Aakash)
IT: Get plugins updated to the current spec and have QA test
Al: Chris bi-weekly meeting for QMO
Craig: Start the basic theme work changes

Contents