Changes

Jump to: navigation, search

Contribute/Coding

5 bytes added, 18:51, 23 January 2012
Action Plan
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.
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 anyone 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 coding modules. Identify process for recognizing new contributors and creating new modules/owners/peers.
=Background Information=
Canmove, confirm
7,088
edits

Navigation menu