A Strategic Approach to Assessing Viability of OSS Projects
summary
Practical checklist for deciding tonight: evaluate governance, community, security and compliance with concrete metrics instead of buzzwords; run the Augur or GrimoireLab metric sets from the Chaos Project to measure change request closure ratio, issue age, release cadence and dependency update frequency; inspect organizational diversity and bus factor numbers, verify security processes with the OpenSSF scorecard and private vulnerability disclosure and embargo practices; prefer projects in neutral foundations (CNCF, Linux Foundation, Apache) or pay staff to contribute if you must rely on single-vendor code.
AI-written summary · about
chapters (10)
- 0:00Introduction and speaker background
- 3:37Why project ownership matters
- 7:11Assessing project viability overview
- 8:40Governance metrics and red flags
- 11:32Community health and culture
- 16:26Security and compliance checks
- 18:56Contributor sustainability risks
- 20:38Strategic risk assessment
- 22:46Long-term business implications
- 24:17Q&A session
related talks
36mPanel Discussion: OSS Viability and Project...
21mHow Can Your OSPO Ensure Viability of the Open Source Projects That Your Product Reli...
28mOpen Source: Open Choice – A DevOps Guide for OSS Adoption
31mOperationalizing Open Source Projects: When the Rubber Meets the Road
31mAssessing Open Source Software Projects in the Software Supply Chain
38mOpen-Source - Open Choice: A DevOps Guide for OSS Adoption
44mIs this Open Source Project Healthy or Lifeless?
35mThe Benefits and Pitfalls of OSS Project Metrics: Measuring Health and Risk in Open Source Communities