Changes

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.

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.

Audit and update the existing [[Modules|module ownership]] information for coding modules. Identify process for recognizing new contributors and creating new owners/peers.