A brainstorm of metrics that we may wish to track.

Once the work is complete on moving the repositories and other build/test/release infrastructure out of Juniper, the Linux Foundation will be able to add Tungsten Fabric to the LF installation of Grimoire for collecting and monitoring community metrics.

In advance of that, the community should consider what sort of metrics it would like to track.

Criteria:

1. Must be able to automate the collection of the metric
2. Metric must directly support one or more of the 2019 TSC Priorities
3. Vanity metrics (number of commits, lines of code, etc) are not welcome

Guideline:

• Fewer metrics are better for now. It's best to keep it simple then iterate on the metrics later as we get a better grasp on what we need.

Metric ideas:

These are in no particular order. Addition to the list does not mean we will definitely track that metric, only that we'll consider it.

• Number of contributing companies
• Number of overall contributors (all types of contributions)
• Mailing list participation: number of messages and diversity of participants (not simply the same voices all the time)
• Chat tool participation: number of messages and diversity of participants (not simply the same voices all the time)
• JIRA participation (bugs & blueprints): diversity of participants (not simply the same voices all the time)
• Gerrit review participation: diversity of participants (not simply the same voices all the time)
• Quality of participation: pull requests/gerrit changes accepted/merged vs submitted, average time for a change to be reviewed and submitted (proposals from all voices are considered and have a good experience), average time for an issue to receive a reply, issues opened vs closed (all voices feel they can contribute to the community).