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

Jump to navigation Jump to search
no edit summary
No edit summary
Line 4: Line 4:


= Who Is In The Web QA Community =
= Who Is In The Web QA Community =
==[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.
==[https://wiki.mozilla.org/QA/Execution/Web_Testing/Community/Casual_Contributor Casual Contributor]==
 
A casual contributor is someone who has volunteered small amounts of time in an activity.
 
* Examples: Someone who has earned one of our [https://badges.mozilla.org/en-US/profiles/profile/webqa.badges WebQA Badges], joined our [https://mail.mozilla.org/listinfo/mozwebqa Web QA Mailing list], commented on one of our GitHub repos, submitted a pull request, attended a test day, joined our [https://mozillians.org/en-US/group/webqa/ Mozillians group].
 
* Estimated size: Thousands of people


* 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.
* Mission impact: In aggregate, casual contributors create real value for the improvement of Web QA projects and Mozilla, spreading the word, providing decision-informing data and more.


* Goal size: 8 - 10 people


* Mission impact: Core contributors make major impacts on Web QA projects through their contributions of time, skill and leadership.


==[https://wiki.mozilla.org/QA/Execution/Web_Testing/Community/Active_Contributor Active Contributor]==
==[https://wiki.mozilla.org/QA/Execution/Web_Testing/Community/Active_Contributor Active Contributor]==
Line 24: Line 27:
* Mission impact: Active contributors directly support Web QA through their contributions of time and skill and provide the team with the ability to move forward with a wide range projects.
* Mission impact: Active contributors directly support Web QA through their contributions of time and skill and provide the team with the ability to move forward with a wide range projects.


==[https://wiki.mozilla.org/QA/Execution/Web_Testing/Community/Casual_Contributor Casual Contributor]==


A casual contributor is someone who has volunteered small amounts of time in an activity.
==[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.


* Examples: Someone who has earned one of our [https://badges.mozilla.org/en-US/profiles/profile/webqa.badges WebQA Badges], joined our [https://mail.mozilla.org/listinfo/mozwebqa Web QA Mailing list], commented on one of our GitHub repos, submitted a pull request, attended a test day, joined our [https://mozillians.org/en-US/group/webqa/ Mozillians group].
* 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.


* Estimated size: Thousands of people
* Goal size: 8 - 10 people  


* Mission impact: In aggregate, casual contributors create real value for the improvement of Web QA projects and Mozilla, spreading the word, providing decision-informing data and more.
* Mission impact: Core contributors make major impacts on Web QA projects through their contributions of time, skill and leadership.
Confirmed users
1,504

edits

Navigation menu