~/talk

Community Data: What to Measure and Why?

linkedin:calidolfi
slides:none on file

Argues that useful community metrics come from concrete questions, not vanity counts, and shows a repeatable workflow: pick a magic 8-ball question, map available sources (e.g. GitHub API or chat logs), then convert subquestions into metrics. Gives specific measures — 150 contributors, months with 100 vs 40 commits, distinguish active vs drifting contributors and repeat vs flyby (<4 contributions) — and demonstrates a dashboard that aggregates repos, lets thresholds be tuned, and drives hypothesis-led community experiments (examples used successfully with Fedora and internal dashboards).

AI-written summary · about

  1. 0:00Start
  2. 0:51What Can Strong Community Metrics Enable
  3. 2:41Expose Areas of Improvement or Highlighting Strengths
  4. 3:30Community Impact or Business Impact
  5. 5:06Codifying Problems and Metrics
  6. 5:32Analysis Angles
  7. 5:58Number of Contributors
  8. 6:23Active versus Drifting Contributors
  9. 6:52Repeat versus Flyby Contributors of the Time
  10. 7:21Commits Overtime
  11. 7:36The Depth of Commit over Time
  12. 8:08Commits by a Subset of Contributors
  13. 8:35Community Campaign Impact Measurement
  14. 10:24Scenario Three
  15. 10:59Breaking Down Your Focus Area
  16. 13:17Select the Specific Data Points Needed
  17. 14:56Analysis in Action
  18. 23:45Data Analysis
  19. 25:14Closing Thoughts
  20. 34:05What Are the Things That We Should Keep an Eye on Initially To Build Out a Healthy Community Measuring Program
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.