QA/Community/Growth

Goals

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

Brainstorming

• How to improve Bug Days
  • Feedback from developers - Triona
  • occasional developer attendance corresponding to the topic at hand
  • better attendance in general - need ~5 people for a successful bug day.
    • 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
  • 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 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.
• "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.

Ideas in Action

• QMO (in progress)
• Develop strong relationship with mozillaZine.org (contacted Alex Bishop at mZ)