Community Metrics What to Measure and Why?
summary
Concrete claim: community metrics become useful when they answer specific operational questions — not broad vanity stats — by using repository timestamps and contributor fingerprints to measure repeat vs flyby contributors, conversion rates from first‑time to active contributors, and area‑dependency of code. Implementation uses Auger + GitHub relational DB plus dashboards and an "eight‑knot questions" workflow to turn hypotheses into visuals. Applied to Fedora’s goal of doubling Fedora contributors by 2028 and other projects, the metrics surface actionable gaps (documentation, onboarding, bus‑factor hotspots) and succeed at turning disagreement into measurable initiatives.
AI-written summary · about
chapters (9)
- 0:00Community metrics intro
- 0:20Why measure metrics
- 2:07Choosing actionable metrics
- 5:18Codifying problems and metrics
- 8:48Campaign impact measurement
- 10:11Community analysis method
- 15:31New contributor behavior
- 20:49Analysis lessons learned
- 23:58Closing thoughts on data
related talks
34mCommunity Data: What to Measure and Why?
46mMeasuring Community Health
26mBuilding & Supporting Open Source Communities Through Metrics
43mBuilding and Supporting Open Source Communities Through Metrics
30mMeasuring the Impact of Community Events
41mBuilding and Supporting Open Source Communities Through Metri...
43mIf You Can’t Measure It, You Can’t Improve It
39mMeasuring the Impact of Community Events