QA/QMO/QMO 4.0/Meeting Notes
From MozillaWiki
1-14-2011
Bugzilla+QMO:Stats
Automation
- bugs opened/filed
- patches attached
- bugs resolved
- bug comments
Places to look: Mozilla QA/All
Browser Tech
- qawanted
- bug comments
- bugs filed
- bug verifications
- nominations that are +'d
- in-litmus+
- jetpack: in-testsuite+
- sync: [qa+]
Places to look
- Mobile: Fennec/All, Core/Widget:Android, Core/Widget:Maemo
- Sync: Mozilla Services/All
- Jetpack:
- Test Pilot: Mozilla Labs/
Desktop
- bugs filed
- Bugs verified: branch keywords
- bugs confirmed
- bug comments
- qawanted: resolved, regression range, steps to reproduce
Places to Look: Firefox/All, Core/All, Toolkit/All
Services
- bugs filed w/ keywords: crash
- whiteboarded "testday"
Places to Look: same as "Desktop"
WebQA
- bugs filed
- bugs confirmed
- bugs verified
- "regression" keyworded
- bug comments w/ diff's from SVN
- qawanted
- [qa+] -> could be higher priority since its a need
- in-litmus+
- in-testsuite+
Places to Look: AMO/All, Webtools/Input, SUMO/Website, ....
1-12-2011
Main Focus Areas
- 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
- Needs:
- 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
5-05-2011
Agenda:
- Discuss initial technical requirements, deliverables and timelines
https://wiki.mozilla.org/QA/QMO/QMO_4.0
https://bugzilla.mozilla.org/show_bug.cgi?id=617399
Attendees:
- Al Billings
- Craig Cook
- Ryan Snyder
- Chris More
- Mike Alexis
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