QA/Community/QMO Design/Goals: Difference between revisions
< QA | Community | QMO Design
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[Mozilla_QA_Community:QMO_Design | Back to QMO Design]] | [[Mozilla_QA_Community:QMO_Design | Back to QMO Design]] | ||
== What we want to accomplish with QMO: == | |||
* Create a home for the Mozilla QA Community of testers and volunteers | |||
** Provide a place for them to communicate, create, and share tasks and projects | |||
** Support various Mozilla projects' QA efforts by allowing their communities to coexist in one place and share resources | |||
* More focus on Firefox testing, test development, and QA outreach | |||
** Organize and track community events | |||
** Host community projects for data analysis, new tools, and test automation. | |||
** Create a program to attract more users to the Mozilla project and groom them into testers and qa engineers. | |||
== What we don't want to do: == | |||
* Don't become a support center (JT is already working on a customer service strategy that will be focusing on providing support for our users) | |||
* Don't step on any toes or reinvent the wheel | |||
** Don't compete with mozillaZine, but work with that community and share ideas/content. | |||
** Don't disrupt regular communication channels like IRC and newsgroups, but utilize them as much as possible to expand QMO's reach and influence. | |||
** Don't replace the wiki, only migrate static content from the wiki to QMO and continue to use the wiki when appropriate and link to it instead. | |||
Revision as of 18:47, 3 April 2007
What we want to accomplish with QMO:
- Create a home for the Mozilla QA Community of testers and volunteers
- Provide a place for them to communicate, create, and share tasks and projects
- Support various Mozilla projects' QA efforts by allowing their communities to coexist in one place and share resources
- More focus on Firefox testing, test development, and QA outreach
- Organize and track community events
- Host community projects for data analysis, new tools, and test automation.
- Create a program to attract more users to the Mozilla project and groom them into testers and qa engineers.
What we don't want to do:
- Don't become a support center (JT is already working on a customer service strategy that will be focusing on providing support for our users)
- Don't step on any toes or reinvent the wheel
- Don't compete with mozillaZine, but work with that community and share ideas/content.
- Don't disrupt regular communication channels like IRC and newsgroups, but utilize them as much as possible to expand QMO's reach and influence.
- Don't replace the wiki, only migrate static content from the wiki to QMO and continue to use the wiki when appropriate and link to it instead.