Background: At the Open Source Summit North America, a group of around 8-12 people each agreed on the metrics important in the following scenarios. For now, we will focus our conversation around these outcomes to further the conversation. The two-hour session sparked great conversations but could not address all aspects. We thank everyone who participated.
Below is the metric->signal->action chain for Growth-Maturity-Decline.
How to contribute:
- To advance the document, fork the rep, make your changes, create a pull request see CONTRIBUTING.md
- To ask questions or make comments, post to our mailing list, join our weekly Hangout call, or open an issue on GitHub.
(Not yet written up)
We thank everyone who participated in the workshop at the Open Source Summit North America. The below picture is the flip chart figure that came out of the Growth-Maturity-Decline group.
Some possible definitions
Patch speed: There can be two different data. One is "review efficiency", which is the number of merged/abandoned changes out of all submitted patches over a given period. The other is "time-to-merge", which is the time since a patch is submitted until this is merged/abandoned.
Bug resolution: Somewhat simlar to the patch speed above. We could look at the total number of tickets closed out of all the tickets opened over a given time period. We can also look at the "time-to-close", which is time since a bug is opened until it is closed.
Number of new developers: Number of new contributors (using appropriate userid) over a period (e.g. monthly, quarterly, etc.)