Keynote - Leading in Open Source, a Strategic Approach
summary
Company contributions come from individuals whose leadership travels with them, so strategic alignment with business goals prevents churn and preserves institutional influence; measure outcomes using dashboards and the chaos metrics project rather than raw commit counts; prefer upstreaming patches over internal forks to avoid long-term technical debt and security drift; hire or allocate full‑time engineers for strategic projects (example: dedicated engineers on Cluster API and Kubernetes) and budget conference travel and maintenance plans so contributions actually get merged and sustained.
AI-written summary · about
chapters (17)
- 0:00Start
- 2:02Individuals
- 3:04Companies
- 4:06Community = People
- 5:03Balance
- 7:07Contribution Strategy and Plans
- 9:34Risk and Strategy
- 11:22Build/Contribute
- 13:46Guidelines
- 14:40Measure Success
- 16:42Upstream Your Patches
- 18:15Work with the Community
- 18:53Leadership
- 19:52Relationships
- 21:42Maintenance Expectations
- 22:18Open Sourcing Your Software
- 24:02Final Thoughts
related talks
01h 01mKeynote - Open source is just about the source, isn't it?
06mKeynote: Supporting the Community – So Open Source Projects Can Grow and Thrive
53mKeynote - Embracing Openness as a Competitive Advantage
09mKeynote: What Winning Open Source Looks Like
10mKeynote: Embracing Open Source to Beat the Great Reshuffle
10mKeynote: Embracing Open Source to Beat the Great Reshuffle
20mKeynote: Open Open Source and Making Great Places for Col...
11mKeynote: How to Craft Open Source Contributions