Panel Discussion: OSS Viability and Project...
summary
CHAOSS builds concrete metric collections — e.g., viability metric model (governance, community, compliance, security) and smaller six-metric starters — using measures like age of issue, number of maintainers, bus/elephant factor and dependency-tree checks (a “Nebraska” metric). Organizations deploy dashboards and a component intelligence service to flag AGPL or single-vendor risks and to guide when to contribute, fork, or replace (Elasticsearch→OpenSearch cited). Metrics improve apples-to-apples comparisons but struggle with hard-to-measure signals like active maintainer employer concentration.
AI-written summary · about
chapters (10)
- 0:00OSS viability panel
- 3:30Assessing project viability
- 9:07Non-viable projects impact
- 12:58Viability metrics start
- 17:39Project red flags
- 21:54Scaling viability education
- 26:13Vendor dominance vs health
- 30:21Tracking project viability
- 34:16Project vitality beyond survival
- 35:18Closing remarks
related talks
27mThe OSS-ential Understanding of Community Health and Metrics
30mA Strategic Approach to Assessing Viability of OSS Projects
43mBuilding and Supporting Open Source Communities Through Metrics
33mData to Action: Build Healthy & Sustainable OSS Communities
41mBuilding and Supporting Open Source Communities Through Metri...
46mPanel Discussion: What Our OSPOs Have...
26mBuilding & Supporting Open Source Communities Through Metrics
35mThe Benefits and Pitfalls of OSS Project Metrics: Measuring Health and Risk in Open Source Communities