QA/Execution/Web Testing/Contributor levels: Difference between revisions

Line 3: Line 3:
An overview of the Web QA Community based on the larger [https://wiki.mozilla.org/Community Mozilla Community].   
An overview of the Web QA Community based on the larger [https://wiki.mozilla.org/Community Mozilla Community].   


= Who Is In The Desktop Firefox QA Community =
= Who Is In The Web QA Community =
==[https://wiki.mozilla.org/QA/Execution/Web_Testing/Community/Core_Contributor Core Contributor] ==
==[https://wiki.mozilla.org/QA/Execution/Web_Testing/Community/Core_Contributor Core Contributor] ==


A core contributor is someone who has a leadership position on the Web QA team.
A core contributor is someone who has a leadership position on the Web QA team.


* Examples: Web QA project lead, someone who can be the primary tester on one of our projects, and can coordinate release testing. Web QA community mentor, someone who rallies our community and actively works with new contributors. Web QA Automation core contributor, someone who regularly makes pull requests and comments on one or many of our GitHub project repos.
* Examples: Web QA project lead, someone who can be the primary tester on one of our projects, and can coordinate release testing. Web QA community builder, someone who rallies our community and actively works with new contributors. Web QA Automation core contributor, someone who regularly makes pull requests and comments on one or many of our GitHub project repos.


* Goal size: 8 - 10 people  
* Goal size: 8 - 10 people  
Line 18: Line 18:
An active contributor is someone who has volunteered substantial time performing  Web QA  activities that involves interactions with others within the last 1 or 2 months.
An active contributor is someone who has volunteered substantial time performing  Web QA  activities that involves interactions with others within the last 1 or 2 months.


* Examples: Active participation in Web QA Test Days, someone who files bugs against our websites, someone who does manual testing on a project, someone who submits occasional pull requests on a Web QA Automation repo.
* Examples: Active participation in Web QA Test Days, someone who files bugs against our websites, someone who leads manual testing on a project, someone who submits occasional pull requests on a Web QA Automation repo.


* Goal size: 25 - 30 people
* Goal size: 25 - 30 people
Confirmed users
1,504

edits