OSPOs: Key Lever for Open Source Sustainability
summary
Organizations that frequently contribute upstream formally create an OSPO 65% of the time, and internal programs report 80% positive impact on software best practices. Practical levers: set funding via contributor funds and GitHub Sponsors, build Minimal Viable OSPOs focused on four roles—enabler, counselor, advocate, environmentalist—and run working groups (metrics, employee engagement, community health like osmometers). Proven wins: clearer policy, more upstream contributions and measurable health signals; common failures are siloing, legal‑only focus, poor alignment and one‑size‑fits‑all setups.
AI-written summary · about
chapters (8)
- 0:00Introduction to OSPOs
- 1:07Organizations addressing open source sustainability
- 5:02OSPOs as a role and its responsibilities
- 10:45Assessing open source readiness
- 16:10Common OSPO anti-patterns
- 18:38Community learnings and best practices
- 26:07Key takeaways and resources
- 30:28About the speaker and Q&A
related talks
46mOSPOs: Key Lever for Open Source Sustainability
30mDemystifying OSPOs
37mOSPO is a Key Element for your Company, but also for the OS Ecosystem
46mOSS Management & OSPO Ask Anything
42mDoes Your OSPO Help or Hinder Contributions?
26mOpen Source Program Offices
39mHow Can Your OSPO Maximize Open Source Business Value for the Organization?
25mOpen Source Corporate Sustainability – Models to Consider