Confirmed users
4,072
edits
QA/Sync/Community/Action Plan: Difference between revisions
m
→Casual Contributor
| (5 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
A high level guide on how to contribute to Firefox Sync Quality Assurance. Each level of contribution is generally outlined at [https://wiki.mozilla.org/QA/Sync/Community Sync QA Community]. Read on if you are a Sync user and interested in becoming at least a Casual Contributor if not an Active or Core Contributor. | A high level guide on how to contribute to Firefox Sync Quality Assurance. Each level of contribution is generally outlined at [https://wiki.mozilla.org/QA/Sync/Community Sync QA Community]. Read on if you are a Sync user and interested in becoming at least a Casual Contributor if not an Active or Core Contributor. | ||
= | = What is there to do? = | ||
There is prolific growth in and production from the Mozilla Development Community. Mozilla QA needs your help to keep up with that growth and production. Firefox Sync QA is one area where you can make an impact. What follows are | There is prolific growth in and production from the Mozilla Development Community. Mozilla QA needs your help to keep up with that growth and production. Firefox Sync QA is one area where you can make an impact. What follows are ways to take action and make an impact at each of the higher levels of the Sync QA Community. | ||
''note: each item will eventually link to detailed instructions for that action item. If you are interested in something that isn't linked to details, please hunt me down and I'll make it priority to complete'' | |||
== [https://wiki.mozilla.org/QA/Sync/Community#Casual_Contributor Casual Contributor] == | == [https://wiki.mozilla.org/QA/Sync/Community#Casual_Contributor Casual Contributor] == | ||
The easiest | The easiest ways to contribute to the Firefox Sync Community are to take a few moments to do one or more of the following. | ||
* | * Always submit any Firefox crash reports, especially if they happen around a Sync. | ||
* | ** What is [https://developer.mozilla.org/en-US/docs/Crash_reporting Crash Reporting]? | ||
* | ** By submitting crash data, our analyst will identify trends and get a workable bug on file for the developers to fix. | ||
* Share your thoughts on Sync at [http://input.mozilla.org/en-US/feedback input.mozilla.org]. Understanding what our users enjoy using or not helps Mozilla make their products better. | |||
* Look up or file a support ticket on an issue you have with Sync at [http://support.mozilla.org/en-US/home SUMO]. By observing how support issues are trending, Mozilla can identify top issues and correct them in our products or services. | |||
Yes, it is that easy | Yes, it is that easy! Nothing too complicated or time consuming. Just take a moment to get involved. | ||
== [https://wiki.mozilla.org/QA/Sync/Community#Active_Contributor Active Contributor] == | == [https://wiki.mozilla.org/QA/Sync/Community#Active_Contributor Active Contributor] == | ||
| Line 40: | Line 44: | ||
* Responsible for final Sync client sign-offs | * Responsible for final Sync client sign-offs | ||
* Determine and drive test case writing needs. | * Determine and drive test case writing needs. | ||
A core Contributor can expect to put 20 - 40 hours per week towards Sync QA. This work is often, but not exclusively, done by Mozilla employees. | |||
= What's Next? = | |||
Becoming a Casual Contributor is fairly self explanatory. However, if you want get more deeply involved in Firefox Sync QA by becoming an Active Contributor, you'll need some guidance from a Core Contributor to get you going. | |||