QA/Community/Growth: Difference between revisions

From MozillaWiki
< QA‎ | Community
Jump to navigation Jump to search
No edit summary
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
'''[[Mozilla_QA_Community|&laquo; back to Mozilla_QA_Community]]'''
<small>[[QA/Community|&laquo; QA/Community]]</small>


== '''Goals''' ==
== '''Goals''' ==
Line 8: Line 8:


'''Community Action Plans'''
'''Community Action Plans'''
* [[Mozilla_QA_Community:Growing_the_Mozilla_QA_Community:Q42007Strategy | Q42007 Community Strategy Doc]]
* [[QA/Community/Growth/Q42007Strategy|Q42007 Community Strategy Doc]]
* [[QA/Community/Growth/Q12008Strategy|Q12008 Community Strategy Doc]]


== '''Brainstorming''' ==
== '''Brainstorming''' ==
Line 21: Line 22:
*** promotion via blogs
*** promotion via blogs
*** promotion via news sites
*** promotion via news sites
** better bugday documentation for planners and participants: '''Done [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day:Planner here]''' Feel free to make any changes that would make it and the [http://wiki.mozilla.org/Mozilla_QA_Community:Bug_Day Bug Day page] better.
** better bugday documentation for planners and participants: '''Done [[QA/Community/Bug_Day/Planner|here]]''' Feel free to make any changes that would make it and the [[QA/Community/Bug_Day|Bug Day page]] better.
** careful selection of topics that are interesting, fun, and able to benefit from working as a team.
** careful selection of topics that are interesting, fun, and able to benefit from working as a team.


* How to expand Test Days to other aspects of QA
* How to expand Test Days to other aspects of QA
* "Mozilla University" - collection of docs and tutorials on how new people can get involved in Mozilla (based on experience with Seneca and other college outreach)
* "Mozilla QAC" (QA Community) - Create a presence at major social networking sites (MySpace, Hi5, Facebook, etc).  Some groups already exist for Firefox, but need to figure out whether to tap into that or start a QA specific group.
* "Mozilla QAC" (QA Community) - Create a presence at major social networking sites (MySpace, Hi5, Facebook, etc).  Some groups already exist for Firefox, but need to figure out whether to tap into that or start a QA specific group.
* "Mini-Projects" - Small, short-term projects that will either help the QA team get work done or allow the community to try out new things and create through learning.
* "Mini-Projects" - Small, short-term projects that will either help the QA team get work done or allow the community to try out new things and create through learning.
Line 32: Line 32:
== '''Ideas in Action''' ==
== '''Ideas in Action''' ==
* QMO (in progress)
* QMO (in progress)
* "Mozilla University" - collection of docs and tutorials on how new people can get involved in Mozilla (based on experience with Seneca and other college outreach)
** Created Mozilla University page https://www.mozilla.com/en-US/university/
** Over 500 flyers distributed to Campus Reps around the country linking to Mozilla Unversity
* Develop strong relationship with mozillaZine.org (contacted Alex Bishop at mZ)
* Develop strong relationship with mozillaZine.org (contacted Alex Bishop at mZ)
** Find ways to work together on Mozilla Support project
** Engage the community more in the mZ forums
* Promoting to OS groups and International communities
* Promoting to OS groups and International communities
** Mac user test group
** Mozilla Japan localizing QMO and Litmus


== Sources we use currently on Testdays ==
== Sources we use currently on Testdays ==

Latest revision as of 21:32, 15 February 2008

« QA/Community

Goals

General Goals:

  • Organize successful community events and projects
  • Improve documentation, processes, and tools
  • Get more people involved through outreach

Community Action Plans

Brainstorming

  • How to improve Bug Days
    • Feedback from developers
    • occasional developer attendance corresponding to the topic at hand
    • improve attendance in general - need ~5-10 active people.
      • promotion via irc
      • promotion via wiki
      • promotion via qmo
      • word of mouth
      • promotion via blogs
      • promotion via news sites
    • better bugday documentation for planners and participants: Done here Feel free to make any changes that would make it and the Bug Day page better.
    • careful selection of topics that are interesting, fun, and able to benefit from working as a team.
  • How to expand Test Days to other aspects of QA
  • "Mozilla QAC" (QA Community) - Create a presence at major social networking sites (MySpace, Hi5, Facebook, etc). Some groups already exist for Firefox, but need to figure out whether to tap into that or start a QA specific group.
  • "Mini-Projects" - Small, short-term projects that will either help the QA team get work done or allow the community to try out new things and create through learning.
  • Action items page that is closely related to everyday QA tasks for community members to hit anytime

Ideas in Action

  • QMO (in progress)
  • "Mozilla University" - collection of docs and tutorials on how new people can get involved in Mozilla (based on experience with Seneca and other college outreach)
  • Develop strong relationship with mozillaZine.org (contacted Alex Bishop at mZ)
    • Find ways to work together on Mozilla Support project
    • Engage the community more in the mZ forums
  • Promoting to OS groups and International communities
    • Mac user test group
    • Mozilla Japan localizing QMO and Litmus

Sources we use currently on Testdays

  • When we have a Testday we communicate to the following sources currently
    • vistaqa@mozilla.org Vista Community QA Mailinglist
    • communityQA@mozilla.org General Community QA Mailing List
    • mozilla.dev.quality Newsgroup
    • Mozillazine Forum (section Build)
    • www.firefox-browser.de (German Community, see Tomcat to get posts on this forum)
    • QA weblog (weblogs.mozillazine.org\qa)