Leveraging the Open Source Development Model Inside Your Company
summary
Wind River runs a 12‑month pilot called code swap that uses a private internal GitHub and a landing page to share and preserve code, yielding about 15% developer registration, seven active projects and three slated for open source release. Projects include an encryption detection script that replaces four independent tools, a connected foosball table and a LEM lander demo. The program emphasizes autonomy/mastery/purpose, three simple enablement tools, and clear pathways to open source.
AI-written summary · about
chapters (9)
- 0:00Introduction and motivation
- 1:52Defining strategic objectives
- 4:50Why open models work
- 7:23Key ingredients of open systems
- 9:52Technical enablement factors
- 13:31Implementing the code swap
- 17:26Program structure and pathways
- 22:58Refining and scaling the model
- 25:41Q&A and closing thoughts
related talks
19mFrom InnerSource To Open Source: Building a Dual-Focused OSPO in a Tradition...
45mFostering an Open Environment for Developers in a Regulated Industry
23mThe Open Source Journey of the Most Unlikely Participant
38mWhen the Open Source Program Office is Responsible for Innovation
13mHow can we truly arrive at "open-source everywhere"?
09mThe InnerSource Flywheel
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
24mAnother Session on "Why Going Open Source?”