About 100 potential new contributors a day are contacting us through the Get Involved page. We know what they’re interested in, but we don’t have a lot of visibility about who goes on to contribute.
If we can identify different steps people take to contribute to a project, we can look at each of those and see how many people take that step and move on to the next one. As an example, at the Coding Contribute Group we came up with this path for coding contributors.
I think this could be really powerful in a number of ways.
You can fix roadblocks. The Coding Stewards recently had Bugzilla send out email to anyone who had their first patch approved to help them figure out what to do next. We felt this might be a hurdle and with a conversion report we can see if this made moving to the next step easier.
You can identify superstar volunteers. I’ve color-coded this path to match with casual, active and core contributor levels. If you could identify every core volunteer in your project, you could invite them to work weeks, send them swag or ask them to help with new opportunities they may be interested in.
I imagine there would be many other ways to make use of this information to help us grow Mozilla. What would a contribution path look like for your project? What would you do to make contributing to your project easier with this information?
Hat tip to Jessilyn Davis for the idea for the Superstar Radar name.