Open Source Corporate Sustainability – Models to Consider
summary
Corporate OSPOs must treat code as product and plan for human capital: target a 30-minute ramp so a developer can start a repo or contribute quickly, allocate bench strength 1–5 per 1,000 engineers (example: 33,000 engineers vs ~150 OSPO staff), and expect a median of ~10 contributions/year while outliers hit 100. Sustainability models include open-20% / sabbatical incentives, freemium/open-core/support-for-fee, and partnerships — embed OSPO with HR, security, CSR (example: a maternal health data hackathon building free datasets) to secure funding and measurable ROI.
AI-written summary · about
chapters (11)
- 0:00Start
- 0:49How Many Open Source Contributions You Made in the Past Year
- 2:43Why Does Sustainability Matter
- 4:23Innovation Progress
- 7:25The Oxymoronic Balancing Act
- 8:22Product Roadmap
- 11:39Do You Have To Do 100 Contributions in a Year
- 19:59Freemium Pyramid
- 20:37Foundation Partnership
- 20:59Sponsorship
- 23:03Questions
related talks
28mSustainability beyond funds: Extrospective OSPOs
32mOSPOs: Key Lever for Open Source Sustainability
46mOSPOs: Key Lever for Open Source Sustainability
01h 39mWorkshop: Building and Managing an Open Source Program Office
41mHow Your Company Can Help Sustain Open Source
21mScaling Internal Collaboration with Open Source Operating Models
45mCulture Change: Building an OSPO in a Proprietary Software Company
42mThe Power of "AND": A New Template for Open Source Sustainability