Canmove, confirm
7,088
edits
Changes
no edit summary
===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.
Notes: get traffic stats for each to prioritize?
For an area of the project that has been active for so long, such as coding, there will be many old pages with out of date information on them. For instance, a search of 'mozilla coding' brings up [http://www-archive.mozilla.org/contribute/hacking/first-bugs/ this page on the www-archive.mozilla.org site] as the third result and a [https://developer.mozilla.org/en/Mozilla_Source_Code_Via_CVS guide for using CVS] as the fourth.
* Retire and redirect any legacy pages in top results for a Google search of '[https://www.google.com/search?q=mozilla+coding&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a mozilla coding]'
We can also look for volunteers beyond our Mozilla channels. Ideas for that include:
* http://www.volunteermatch.org
How can we use events as offline channels to help people get involved?
===Potential Contributors===
* Create and maintain a curated list of 50 mentored bugs that can be handed out to promising new contributors as they arrive through the various channels.
===Active Contributors===
'''First Patch'''
The creation of someone's first patch is a key moment in the coding contributor lifecycle and there are a number of things we can do to make this a better experience for people and to amplify the signal of first-time patches.
* Have an tool that takes the [https://bugzilla.mozilla.org/show_bug.cgi?id=719526 email headers from Bugzilla about first patches] and use a Pulse feed to announce that in relevant IRC channels
* Have an [https://bugzilla.mozilla.org/show_bug.cgi?id=721206 email sent out to people who have just had their first patch approved] encouraging them and giving them key information such as the way to get added to credits, how to make sure the patch is landed, how to find other bugs, etc.
'''Recognition'''
Take the current ad hoc process of recognizing active contributors with swag, invitations to events, etc and create a scalable process for identifying and recognize key active contributors. For example, Josh maintains a manual list of people he is encouraging but that isn't very scalable.
'''Phonebook'''
Have a plan for getting newly active contributors into the phonebook and use relevant tags (ex, firefox, javascript, mobile, 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 'javascript' tag if you were looking for help with a complicated javascript engine bug that wouldn't be a good fit for new contributors). We may want to document a set of tags we'd like people to use.
'''Dashboards'''
Create a process for using the [https://metrics.mozilla.com/data/content/pentaho-cdf-dd/Render?solution=community&path=%2Fdashboards&file=contributorMap.wcdf contributor map] and [https://metrics.mozilla.com/data/content/pentaho-cdf-dd/Render?solution=community&path=%2Fdashboards&file=contributionTrends.wcdf contribution trends] Mercurial patch dashboards. 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===
