canmove, Confirmed users
7,088
edits
Contribute/QA: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
=Action Plan= | =Action Plan= | ||
Ideas | ===Goals=== | ||
Pull together key goals from Anthony's metrics discussion with team. | |||
===Potential Contributors=== | |||
====Optimize Existing Channels==== | |||
Audit existing channels where potential contributors find information (or should be able to find information) about how to get involved and then optimize to make sure the channels are effective. | |||
* https://quality.mozilla.org | |||
* http://nightly.mozilla.org and http://www.mozilla.org/projects/firefox/prerelease.html | |||
* http://www.mozilla.org/firefox/aurora/ and Aurora First Run page? | |||
* http://www.mozilla.org/firefox/beta/ and Beta First Run page? | |||
* http://bugzilla.mozilla.org | |||
* irc://irc.mozilla.org | |||
* others??? | |||
Notes: get traffic stats for each to prioritize? | |||
====Retire Legacy Channels==== | |||
For an area of the project that has been active for so long, such as QA, there will be many old pages with out of date information on them. For instance, a search for both '[https://www.google.com/search?q=mozilla+testing&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a mozilla testing]' and '[https://www.google.com/search?q=mozilla+qa&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a mozilla qa]' on Google brings up [http://www-archive.mozilla.org/quality/ this page on the www-archive.mozilla.org site] as the first result and QMO is not in the top set of results. | |||
* Retire and redirect any legacy pages in top results for a Google search of '[https://www.google.com/search?q=mozilla+testing&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a mozilla testing]' and '[https://www.google.com/search?q=mozilla+qa&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a mozilla qa]' | |||
====Match Volunteers with Opportunities==== | |||
* Create a list of role descriptions so people can easily understand what is expected of them? This might be something that is more appropriate for already active contributors looking to get more involved than for people just starting out. | |||
* Create processes for manually connecting people with opportunities (eg, helping someone in a Test Day make a contribution) and for giving people a self-service way to get startted (eg, by installing the Nightly and following steps that show up on the first run page). | |||
===Active Contributors=== | |||
Have a plan for getting newly active contributors into the phonebook and use relevant tags (ex, qa, automation, aurora, etc). This will allow us to reach out to experienced contributors with specific opportunities as they come up (for instance, you could email everyone with a 'aurora' tag if you were looking for help with a crasher that needs to be looked into by an experienced community member). We may want to document a set of tags we'd like people to use. | |||
Have a process for taking someone who has come in through a QA entry point, such as installing the nightly, and introducing them to the full range of QA opportunities (desktop, web, automation, etc). It probably makes sense to hold off on presenting the full range of information until people are somewhat familiar with things instead of having this be something people see right away. | |||
Create a dashboard that tracks relevant metrics and create a process for using those metrics. For instance, have a plan to reach out to any previously active contributor that hasn't been involved in the last two months to learn why they left or help them get involved again. | |||
===Core Contributors=== | |||
Audit and update the existing [[Modules|module ownership]] information for QA modules. Identify process for recognizing new contributors and creating new modules/owners/peers. | |||
===Other Ideas To Consider=== | |||
* membership drive to get contributors into phonebook -- can use qa-branded swag for incentive (for instance, marcia knows that gabby is a contributor in argentina but where else are contributors?) | * membership drive to get contributors into phonebook -- can use qa-branded swag for incentive (for instance, marcia knows that gabby is a contributor in argentina but where else are contributors?) | ||