The Role of Open Source Management Talent in Ensuring Software...
summary
An applied claim: using CHAOSS metrics and OSS Scorecard plus dependency analysis uncovers 131 high‑risk Go components among Kubernetes dependencies driven mainly by poor community regeneration; dashboards surface metrics like backlog management index, review efficiency and the pony factor to quantify risk. A Cloud‑ecosystem database defines thresholds, a use case with a European bank validates the model, and recommended actions are targeted engagement, sponsored fellowships and contributing developer time.
AI-written summary · about
chapters (12)
- 0:00Open Source management intro
- 1:10Open Source as software foundation
- 3:21Risk management in supply chains
- 7:20Open Source partnership model
- 9:08Identifying Open Source risks
- 13:10Four-step risk process
- 17:30Treating Open Source risks
- 21:11Kubernetes case study
- 26:48Measuring community risks
- 28:56Action with internal experts
- 31:41Integrating Open Source processes
- 32:25Q&A
related talks
31mThe Value of OSS Management for Risk Mitigation
32mA Complex Web of Open Source Software Dependencies Risk
27mThe OSS-ential Understanding of Community Health and Metrics
36mPanel Discussion: OSS Viability and Project...
25mDefining the Limits of Risk
41mManaging the risk and growth of using Open Source Software
41mBuilding and Supporting Open Source Communities Through Metri...
34mAssessing Project Risk Using CHAOSS Metrics