Playing fair in the Open Source World
summary
Describes Google’s concrete lessons from donating Apache Beam: mismatched tooling and release cadence caused friction, so Google builds an Apache Google program with program managers, training, issue triage and an internal summit to align teams. Gives hard numbers: 47,000 GitHub repos, ~1 billion Googler interactions, ~20 million lines contributed and ~5,500 Googlers contributing. Recommends integrating open source work into performance reviews, adopting compatible tooling, and prioritizing project goals over corporate timelines.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 2:16Talk overview and speaker background
- 5:10Who I am and my open source journey
- 7:18Google’s role in open source
- 9:51Apache Beam origin story
- 12:03Four lessons from Apache Beam
- 17:18Commercial vendor participation models
- 20:52Recommendations for fair participation
- 26:58Building open source citizenship at Google
- 30:52Shoutouts and closing remarks
- 31:16Q&A session
related talks
43mFostering an Open Source Culture
01h 01mKeynote - Open source is just about the source, isn't it?
14mOpen Source Licenses at the Center
13mHow can we truly arrive at "open-source everywhere"?
20mHow Google Fostered Open Source Community During the Pandemic
09mKeynote: But Why?
21mGoogle's Chris DiBona at OSCON
41mHow Your Company Can Help Sustain Open Source