QMO has always had a lot of potential, but its always been a little bit lacking. We have always understood it is a community site that allowed our new and old community members to get more information about opportunities within our sphere of work, but nothing much past that. There were ideas, but no real cohesive strategy or vision about what it should have been and how it made Mozilla’s products better. It’s a whole lot cleaner and simpler than what it was previous, it’s also a very static site that doesn’t get updated as much as it should, provide a low bar to join our community and identify the people within the QA community that are really doing some good for the Mozilla project (and the Internet as a whole). So, Al Billings and I have been churning through ideas and plans on how to fix this and make it something that our community is really proud to be a part of. Here’s the mission and roadmap we’ve come up with and plan to execute:
Mission
* To become the source of updates and activity within QA’s teams and community members
* To identify and elevate the level of involvement of QA community members
How We’ll Get There
QMO 3.0
Purpose: Lower the bar for users to interact with the QA community and offer a method to better identify themselves within it.
Desired Results:
* Team Forums
* User accounts
QMO 3.5
Purpose: Add support for a reward system onto quality.mozilla.org that will help build growth and strengthen retention of community.
Desired Results:
* Reward system for users
* Team blogs
QMO 4.0
Purpose: Integrate statistics from Bugzilla on a per-user basis to better identify community member involvement around quality-related tasks.
Desired Results:
* Relevant Bugzilla statistics related to users and teams are exposed on their home pages
* Support for surveys within blogposts
* Users can join events
* Localization of static content
QMO 4.1
Purpose: Integrate statistics from automation efforts on per-user basis to better identify community member involvement around “pushes” for the Automation team.
Desired Results:
* Relevant Mercurial/GitHub statistics related to users and teams are exposed on their home pages
* Community moderation support
QMO 4.2
Purpose: Integrate statistics from our next-generation Test Case Manager to identify community member involvement around testcases ran, failed and invalidated.
Desired Results:
* Relevant TCM statistics related to users and teams are exposed on their home pages