Panel Discussion: What Our OSPOs Have...
summary
Practical playbook for measuring project health: how to pick one or two metrics tied to business strategy, run experiments, and retire misleading measures (commits, raw activity, lines of code) when automation skews results. Covers concrete tools—OSSF Scorecard, license and vuln tooling, and community-driven practices from CHAOSS—how license and CI checks trigger a business review, how lines added/removed get repurposed into churn, and examples of dashboards that failed versus ones that produced actionable questions.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 6:20Project health definition
- 11:39Collecting project metrics
- 17:41Evaluating open source metrics
- 23:40Metrics usage advice
- 28:56Q&A
- 35:25Failed metrics examples
- 41:09Advice for maintainers
- 46:04Closing remarks
related talks
28mThe Many Faces of Measuring OSPO Success
36mPanel Discussion: OSS Viability and Project...
42mPractical wisdom to build your OSPO: The Good Governance Initiative
37mYour OSPO’s Role in Ensuring Long-Term Business Viability
42mDoes Your OSPO Help or Hinder Contributions?
40mTODO Steering Committee - Management & OSPO Ask Anything
46mOSS Management & OSPO Ask Anything
39mHow Can Your OSPO Maximize Open Source Business Value for the Organization?