Changes

Jump to: navigation, search

Contribute/Coding

1,751 bytes added, 22:32, 17 January 2012
no edit summary
===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://developer.mozilla.org(which pages)
* http://www.mozilla.org/contribute
 
* http://bugzilla.mozilla.org
* http://hg.mozilla.org (and other repositories?)
* 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 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.
 
* 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]'
====Curate List of Opportunities====
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====
 
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).
 
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 [contribution trends] Mercurial patch dashboards. For instance, have a plan to reach out to anyone 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 coding modules. Identify process for recognizing new contributors and creating new owners/peers.
=Background Information=
Canmove, confirm
7,088
edits

Navigation menu