Community Health Reporting 101
summary
Demo of Apache Kibble shows a live dashboard that pulls daily from 4,199 sources and aggregates code repos, issue trackers and mailing lists; it surfaces a composite community health G‑score (example 9.19), a pony factor that flags projects reliant on ~2–3 people (Beam shows ~6), and contributor retention charts (Beam: ~42 newcomers <1 year, distribution across 1–5+ years). It also runs mailing‑list mood analysis, visualizes commit timing, and exposes stale issue age so projects can act on concrete signals.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 0:47About me
- 2:43What is community health
- 4:42Why report community health
- 7:15Github activity
- 9:20Health score
- 12:31Apache Kibble
- 14:37Kibble Demo
- 16:25Kibble Orientation
- 18:00Sources
- 19:19Views
- 21:10Kibble
- 24:41Issues
- 26:23Mailing List
- 28:07Retention
- 32:28Community Growth
- 36:31Summary
related talks
27mCommunity Data is Not Community Metrics
36mCommunity Data: What to Measure and Why?
48mGraphing Zephyr Development and Project Health and How Visualizing Data Help with Gr...
40mDiscovering Emerging Open Source Communities Through...
48mGraphing Zephyr Development and Project Health and How Visualizing Data Help with Gro...
19mOSPO Data Pyramid
35mWho What How: Understanding Kubernetes Development through DevStats - Josh Berkus & Łukasz Gryglicki
31mConfessions of a Data Junkie: Fetching, Parsing, and Visualization