Confirmed users
330
edits
| Line 42: | Line 42: | ||
# See the task completion reflected in profile statistics. | # See the task completion reflected in profile statistics. | ||
# Earn reputation and badges. | # Earn reputation and badges. | ||
# Participate in community discussion to make "One and Done" better (similar to [http://meta.stackoverflow.com/ Meta Stack Overflow] | # Participate in community discussion to make "One and Done" better (similar to [http://meta.stackoverflow.com/ Meta Stack Overflow]) | ||
A Mozilla QA team member should be able to: | |||
# Define areas of interest within Mozilla QA in which Mozilla Community Contributors may participate (e.g. WebQA, B2G, etc). | |||
# Define test environment needed for completing tasks in each area of interest. | |||
# Define common tasks for contributors (e.g. bug reporting, bug triage, bug verification, etc.) | |||
# Define clear workflows for each common task (similar to [https://wiki.ubuntu.com/Bugs/HowToTriage/Charts Ubuntu's 5-a-day]) | |||
# Create tasks with clear instructions, a defined time box and other attributes (e.g. priority for Mozilla QA, difficulty level, area of interest, etc.). | |||
# Internally discuss a particular task by sharing the task's URL. | |||
# Identify and associate Mozilla QA Mentors for each task. | |||
# Schedule each task for when Mozilla QA Mentors are available to support contributor. | |||
# Save the task in an "unpublished" state and make it "go live" as needed. | |||
# Get notified when a contributor picks up the task. | |||
# Mentor contributor in case help is requested or encouragement is needed. | |||
# Get notified when contributor updates progress on the task, and marks it complete or abandoned. | |||
# Send thanks to the contributor. | |||
== Product Version 2.0 == | == Product Version 2.0 == | ||
(Features that are nice-to-have but do not fit into Version 1.0 above can be listed here.) | (Features that are nice-to-have but do not fit into Version 1.0 above can be listed here.) | ||