QA/Community/QMO Design

What is QMO?

Why?

• With so many different channels of communication, new (and sometime veteran) mozilla contributors can sometimes get lost. Developers hang out in #developers, testers use litmus.mozilla.org, everyday users submit Talkback reports and browse the mozillaZine forums...there are just so many places to be.
• Since QA is often the entry point for people interested in the mozilla project, it is critical to provide them with a place to go to get started. In the early days, http://www.mozilla.org/quality/ was that place, but over the years it has become outdated as people migrated over to the forums, newsgroups, and wikis. So most of the information there, although still useful (and mostly relevant), is no longer enough to help someone get started with the mozilla project as a tester.
• QMO will fix both problems mentioned above by providing a central portal for everything related to software quality, Mozilla QA, and the mozilla community.

How?

• Start with pretty UI and a blog. The website will be blog based so that we can post regularly as we have been doing with the QA blog, but also will provide us with a URL that will be easy for people to remember and get to... and from there, we plan to design that site such that every type of user and contributor will be able to find what they are looking for. By customizing the design of the site, we hope to create a unique identity for the QA team and community so we all have our own place in the mozilla project community. We have decided to go with Joomla! CMS for QMO and work has begun on building the basic site. It will be made public as soon as we have enough content there for it to be useful. :-)
• Consolidate and update old documents. By finding and cleaning up pages from mozilla.org and the wiki, we hope to convert important docs into static pages, and provide links to certain wiki pages.
• Make things quick and easy. Whether you want to look up a crash incident with your Talkback ID, find a list of bugs the need to be verified for Firefox 2.0, or see photos of some of our QA volunteers, you will be able to do so quickly and easily from QMO.
• Create a launch pad for various QA tools/projects. With a portal like QMO, we will be able to promote important events and tools that will help everyone. By providing access to Talkback, Reporter, Hendrix, and Litmus, we hope new people will be able to find what they're interested in and start helping out.

Site Layout

Documentation

• Guides & Howtos
• Testing Tips
• Tech Docs
• Mozilla.org Archive

Community

• Get Involved
  • Buzilla Triage
  • Testing
  • Crash/Feedback Analysis
  • Writing Test Cases
  • QMO Design and Maintenance

• Events
  • Bug Days
  • Test Days
  • MUGs (Mozilla User Groups)

• People
  • MoCo QA
  • Testers/Members
  • Users/Fans

• Connect
  • IRC
  • mozillaZine Forums
  • Newsgroups
  • QMO/QA Blog

Tools

• Bugzilla
• Litmus
• Talkback
• Reporter

Projects

• Litmus Extension
• Talkback Tools & Reporting
• Airbag
• Test Harness

Blogroll

Feedback

mozilla.org and mozilla wiki Archives

Sites that would be helpful to integrate into QMO

• http://www.mozilla.org/newlayout/bugathon.html (sample of what a good bug day page should look like... with plenty of help, bugzilla queries, etc)
• http://www.mozilla.org/quality/help/ (nice list of general info about how to get involved, should be updated and organized for easier browsing)
• http://www.mozilla.org/support/firefox/tips (might be a nice way to get regular users to try "hacking" Firefox and learn more about how things work... for advanced users only)
• http://wiki.flock.com/index.php?title=Verifying_a_bug (needs to be updated to reflect Mozilla community, contributed/maintained by Eli Goldberg)
• http://www.mozilla.org/support/firefox/keyboard (one of many support docs we should probably link to in a general usage FAQ)
• http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day (most of the links in the FAQ section, as well as a general "Bug Day" page)
• http://wiki.mozilla.org/Mozilla_QA (Lots of general information about QA activities, could be updated and organized better)
• http://developer.mozilla.org/en/docs/Bug_Writing_Guidelines (Easy to follow guidelines to make effective bug reports, could link to in a testing FAQ)
• http://wiki.mozilla.org/MozillaQualityAssurance:Triage (work in progress for a newer guide to triaging bugs on BMO)
• http://www.gerv.net/hacking/before-you-mail-gerv.html (need to convert it to before mailing qa doc)
• http://www.mozilla.org/quality/help/unconfirmed.html (older bug triager's guide)
• http://www.mozilla.org/newlayout/bugathon.html (bugathon/reduced test cases)
• http://bugzilla.mozilla.org/page.cgi?id=etiquette.html (bugzilla guidelines)
• http://www.mozilla.org/quality/help/bugzilla-privilege-guide.html (what to do and not to do in bugzilla (permission's guide)
• http://www.mozilla.org/quality/help/beginning-duplicate-finding.html (duplicate finding guide)

Sites that need updating and should be added to QMO

Sites that are obsolete and need to be removed from mozilla.org and not added to QMO