Strategic Alignment of Open Source Contributions with Corporate Product Strategies
summary
Company maintains an OSPO wiki table listing a handful of strategic open source projects chosen by three criteria (key flagship components, active commits/releases, significant employee contributions) and reviews them on a quarterly cadence; assessment uses concrete signals — commit/release frequency, number of maintainers and contributing companies, governance neutrality, security policies and community health — to avoid duplicate efforts and reputational damage after a prior internal double-open-source incident.
AI-written summary · about
chapters (12)
- 0:00Introduction
- 1:22Agenda
- 2:00Benefits of Open Source
- 4:01Why Alignment
- 5:10Alignment
- 6:32Strategic Projects
- 7:00Strategic Projects Table
- 8:54Benefits
- 9:37Building Trust
- 10:58Continuous Improvement
- 13:03Where to Start
- 14:16Questions
related talks
18mStrategic Alignment of Open Source Contributions with Corporate Strategies
38mStrategic Alignment Between Community Contributions and Corporate Product Strategies
42mAlignment of Community Contributions and Business Goals - How Can Your OSPO Help?
35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..
21mHow Can Your OSPO Ensure Viability of the Open Source Projects That Your Product Reli...
39mHow Can Your OSPO Maximize Open Source Business Value for the Organization?
28mGoverning Open Source in the Enterprise: OSPO Strategies for Innovation and Compliance- 35mOpen Source as a Product: Strategies for Building and Scaling Successful Open Source..