QA/COG
< QA
Jump to navigation
Jump to search
QA Community Outreach Guide [DRAFT]
Purpose
- To help provide direction to new Mozilla QA community members via a simple and concise guide for QA Community Leaders
FYI on Communication
- Actively engage with community members in a positive way
- Always ask questions if there is the slightest bit of uncertainty
- If they don't answer back after a certain amount of time, ask if they're confused about something
- Always answer questions promptly and concisely
Initial Introduction for New Community Members
- If they have a specific interest in a specific area
- Give them an e-mail address for one of the following mappings:
- If WebDev: stephend
- Community Involvement: aakashd, juanb
- Data Analysis: murali
- Localization: tchung, juanb
- Mobile: jmaher
- OS Testing: marcia
- Triaging, take part in Bug Days and/or contact tracy
- Unit Testing/Automation/Tool Development: ctalbert
- Website Testing: whimboo
- Give them an e-mail address for one of the following mappings:
- If no specific interest, ask them to go through QMO's Projects page and see if there is something they are interested in
- If nothing interests them from the list of Projects on QMO, suggest Litmus BFTs via QAC and tell them to e-mail you the BFT they are interested in
- Once they have determined a subgroup, forward their e-mail to tracy
- If nothing interests them from the list of Projects on QMO, suggest Litmus BFTs via QAC and tell them to e-mail you the BFT they are interested in
- In general, Offer the following reading material:
Determining the Next Step
- In the beginning
- Offer a simple assignment to determine their level of competency and reading material about the subject in QMO's Doc Tree
- After enough initial competency
- Continue to give them more authority and responsibility when they are ready for it
- Don't be afraid to let them make mistakes