How to Be a Good Corporate Citizen in Open Source
summary
Explains concrete practices for company participation: maintain a curated list of 18 VMware projects plus 14 third‑party strategic projects, dedicate engineers full time to Spring RabbitMQ Kubernetes work, use CHAOSS metrics to measure influence not just commit counts, prefer hiring existing contributors cautiously, implement lightweight approval and clear licensing guidance, submit patches upstream to avoid long‑term maintenance debt, and refuse to dump unmaintained code into communities without a maintenance plan.
AI-written summary · about
chapters (9)
- 0:00Start
- 0:11Dynamics of Collaboration
- 1:27How Collaboration Works
- 5:59How To Build a Contribution Strategy and Plans for Participating in Open Source Projects
- 7:53Which Open Source Projects Are Strategic
- 12:32Measuring Open Source Project Success
- 12:46Decide What To Measure
- 20:28Upstreaming Your Patches
- 21:20Understanding Maintenance Expectations
related talks
32mHow to Be a Good Corporate Citizen in Open Source
25mHow to be a Corporate Open Source Citizen
18mStrategic Alignment of Open Source Contributions with Corporate Strategies
38mHow To Be a Responsible Open Source Citizen
41mHow Your Company Can Help Sustain Open Source
22mStrategic Alignment of Open Source Contributions with Corporate Product Strategies
42mOpen Source Citizenship
43mLeadership in Open Source and Why Companies Care