Is this Open Source Project Healthy or Lifeless?
summary
Look for concrete thresholds and evidence: respond within two business days on issues and PRs, run metrics only on projects with 60 commits over six months, expect roughly one release per month for active projects, check for a security.md, Dependabot use, and proper open source licensing and a code of conduct. Watch for contributor concentration and bus‑factor risk (openssl/Heartbleed revealing ~$2,000 yearly funding), foundation ownership (CNCF, Linux Foundation) and whether governance lets others join leadership.
AI-written summary · about
chapters (13)
- 0:00Intro
- 3:19Active, engaged, helpful, and welcoming
- 4:45Keeping up with contributions
- 9:39Active contributors and organizational diversity
- 15:49Regular releases and Security updates
- 19:59Code of conduct, events, leadership, and community
- 24:32Lower risk: participate as equals
- 25:41Higher risk: single company in control
- 26:55Ongoing commitment to collaborate with others
- 29:30Processes for how people collaborate and make decisions
- 31:30Licensing, code of conduct contribution, and communication process
- 34:23Opportunities and responsibilities for leaders
- 39:23CNCF Contributor Strategy SIG contributor-strategy
related talks
30mA Strategic Approach to Assessing Viability of OSS Projects
55mRunning an open source project like a professional
01h 01mWe're Building On Hollowed Foundations (...)
38mSimple Steps for a Calm “Sunset”
24mNavigating Open Source Project Risk
36mOpen-Source: Open Choice - A DevOps Guide for OSS Adoption
14mWhat can we do to make Open Source more sustainable?
16mKeynote: Back to Security Basics: Evaluating, Consuming, and Contributing Open Source Software