Why Is My Community In Danger?
summary
Project Chaos metrics guide actionable checks: measure growth/maturity/decline, diversity and inclusion numbers, and bus factor (aim for >10) using examples like OpenSSL’s single-maintainer risk and a fictional Firefox infighting to show product success ≠ health. Track PR review times and compare corporate vs external merge latency, enforce make processes transparent, and document what is the project how do you use it how do you get it to improve onboarding and reduce volunteer dropout.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:55What It Means To Be a Healthy Community
- 2:25Defining Community Health
- 6:10Diversity Inclusion
- 6:23Risk
- 7:43The Bus Factor
- 8:02Lottery Factor
- 31:59In the Red Hat Development Model Which Contribution Is More Valued Is It the Outside Contributor or the Corporate Contributor
- 33:41Do External Country Contributors Have Access to the Code
related talks
30mMeasuring Security Risk: Community Engagement Is the Best Mitigation
46mMeasuring Community Health
41mBuilding and Supporting Open Source Communities Through Metri...
43mBuilding and Supporting Open Source Communities Through Metrics
36mPanel Discussion: OSS Viability and Project...
26mBuilding & Supporting Open Source Communities Through Metrics
25mDefining the Limits of Risk
27mMeasuring the Health of Your CNCF Project: Going Beyond Stars and Forks