Strategic Alignment of Open Source Contributions with Corporate Strategies
summary
VMware builds a centralized open source program office wiki that lists a curated set of strategic projects table (chosen by three criteria: flagship components, future importance, and active employee commits), maps who contributes from which product teams, and mandates regular reviews of project maturity, governance, releases and company contributor counts. The process prevents duplicate upstream work (one real incident caused public confusion), drives consistent contribution behavior, and flags projects at risk so resources shift before availability or reputation problems emerge.
AI-written summary · about
chapters (9)
- 0:00Introduction and speaker intro
- 2:54Why companies contribute to open source
- 5:20Aligning contributions with business strategies
- 7:46Identifying strategic open source projects
- 11:01Benefits of centralized project tracking
- 12:29Building company reputation in communities
- 14:14Assessing project viability and engagement
- 16:22Four key steps to strategic alignment
- 17:28Final thoughts and conclusion
related talks
22mStrategic Alignment of Open Source Contributions with Corporate Product Strategies
32mHow to Be a Good Corporate Citizen in Open Source
25mHow to Be a Good Corporate Citizen in Open Source
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..
55mStrategic Benefits of Contributing to Open Source: For businesses and individuals
28mKeynote - Leading in Open Source, a Strategic Approach