QA/COG

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

• 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
  • 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:
      • Litmus Tutorial
      • A Bug's Life Walkthrough
    • Once they have determined a subgroup, give them tracy's contact info to vet 1-2 test reports

Determining the Next Step

• Continue to give them more authority and responsibility when they are ready for it
  • Don't be afraid to let them make mistakes