As a community manager on a project that wants to increase the number of contributors, I want to know where new contributors are dropping out. I need:
- To know how I am doing as a whole
- To track how well I am doing at each stage
- To identify the most impactful places to improve
- New Contributors
- Overall success rate. A blend of all the detail-level metrics.
- Clones
- Popularity (like downloads, stars, and clones) shows how many potential contributors are using the project2
- Issue Response Time and Issue Age
- Slow response time discourages new contributors
- Bus Factor
- More-widely distributed work reflects contributor growth
- Review Cycle Duration within a Change Request, Change Request Acceptance Ratio, Change Requests Duration
- Ease of getting a change request accepted influences whether contributors stick around for subsequent work
The metrics fall into different categories and distinct places in a workflow.
First, the overall rate of contributor growth is measured. This enables the user to understand the baseline health of contributor growth.
Second, the success or failure of new contributors moving through each stage of the process - from user to bug reporter to contributor - is measured.
Last, factors that influence the success rate for each stage are measured.
https://gist.github.com/lucasgonze/343a8eb31644a0eb47f94b10a1635f5d
- Lucas Gonze
I wasn't able to find metrics on some types of contributions:
- Creating an issue or a substantive comment
- Improving documentation
- Triaging issues
Types of Contributions covers those, but only in a very general way.
Cool! Thanks!
At that high level, I think a triage metric may be very difficult to define. I am wondering if the issue response metric already covers this or at least part of it (maybe minus the cleaning up and creating boards bit).