When the Open Source Program Office is Responsible for Innovation
summary
An internal program tracks 140 ideas through three stages — idea → PoC → impact — and reports 30+ initiatives that reached measurable value: RISC‑V support became a product feature, a TensorFlow demo moved to the CNCF/Octo project, Zephyr originated internally, and a cryptography scanner became a company‑wide inner‑source tool. The portal is open‑sourced (Apache) with a Vue.js frontend, Firestore now, planned Go + Postgres backend; staffing scales from interns to about one full‑time coordinator per ~200–500 projects.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:49Samuel Langley
- 1:18Wright Brothers
- 3:00The Scratch Image Principle
- 8:15Mastery
- 10:07Open Source Principles That Drive Open Source Projects
- 11:13Workflow
- 16:47There's Zero Mandate To Participate
- 17:10The Process Should Be Frictionless
- 21:13Recognition
- 22:28Tensorflow
- 27:52Kind of Data Are We Gathering and How Do We Use that Data To Measure Success
- 28:46Summary
- 31:39Staffing and Capacity
related talks
43mFostering an Open Source Culture
40mThree Cs to an Open Source Program Office
23mHow Open Source is Leading Open Innovation at Scale
20mThe Open Source Program Office: If It's Such a Good Idea, Why Haven't We Been Doing It?
19mFrom InnerSource To Open Source: Building a Dual-Focused OSPO in a Tradition...
45mFostering an Open Environment for Developers in a Regulated Industry
28mBuilding Open Source Culture in an Enterprise: The Infosys OSPO Story
40mPartnerships in Open Source - the friends you didn't know you had