QA/COG: Difference between revisions
< QA
Jump to navigation
Jump to search
Line 14: | Line 14: | ||
*** Give them the contact information of the mozQA member who is in charge of that area | *** Give them the contact information of the mozQA member who is in charge of that area | ||
**** If WebDev, have them read the [https://wiki.mozilla.org/QA/Execution/Web_Testing/Volunteer WebDev Volunteer Guide] and contact '''stephend''' via e-mail | **** If WebDev, have them read the [https://wiki.mozilla.org/QA/Execution/Web_Testing/Volunteer WebDev Volunteer Guide] and contact '''stephend''' via e-mail | ||
**** If Community Involvement, contact '''aakashd''' via e-mail | **** If Community Involvement, contact '''aakashd''', '''juanb''' via e-mail | ||
**** If Data Analysis, contact '''murali''' via e-mail | **** If Data Analysis, contact '''murali''' via e-mail | ||
**** If Localization, contact '''tchung''' via e-mail | **** If Localization, contact '''tchung''', '''juanb''' via e-mail | ||
**** If Mobile, contact '''jmaher''' via e-mail | **** If Mobile, contact '''jmaher''' via e-mail | ||
**** If OS Testing, contact '''marcia''' via e-mail | **** If OS Testing, contact '''marcia''' via e-mail |
Revision as of 16:52, 24 August 2009
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 as if it was your first priority
- Always ask questions if there is the slightest bit of uncertainty
- If they don't answer back after a certain length of time, ask if they're confused about something
- Always answer questions promptly and concisely
Initial Introduction for New Community Members
- After the end of the first conversation, either one of two things should happen
- If they have a specific interest in a specific area
- Give them the contact information of the mozQA member who is in charge of that area
- If WebDev, have them read the WebDev Volunteer Guide and contact stephend via e-mail
- If Community Involvement, contact aakashd, juanb via e-mail
- If Data Analysis, contact murali via e-mail
- If Localization, contact tchung, juanb via e-mail
- If Mobile, contact jmaher via e-mail
- If OS Testing, contact marcia via e-mail
- If Triaging, take part in Bug Days and/or contact tracy via e-mail
- If Unit Testing/Automation/Tool Development, contact ctalbert via e-mail
- If Website Testing, contact whimboo via e-mail
- Offer a simple assignment to determine their level of competency
- Offer reading material about the subject in QMO's Doc Tree
- Give them the contact information of the mozQA member who is in charge of that area
- If no specific interest, ask them to run through Litmus BFTs via QAC and find a subgroup they are interested in testing more
- Offer links to the following reading material:
- Once they have determined a subgroup, give them tracy's contact info to vet 1-2 test reports
- If they have a specific interest in a specific area
Determining the Next Step
- Once they have incubated in their beginning tasks and have confidence that they are ready to assist further, make sure to promote them by giving them more authority and responsibility.
- Once this authority is offered, you need to treat them as a valued member of the community who should be depended on from then on.
- If they ask for authority, give them a chance to deliver (and make some mistakes)