Adopting open source in your organization
summary
Company shifts from “Linux is a cancer” to becoming the largest contributor on GitHub by choosing a concrete business need: put Git into Team Foundation Server / Visual Studio Team Services. Team integrates libgit2, implements a missing merge routine (published under GPL), uses legal compliance tools (WhiteSource), avoids long‑term forks, and adopts inner‑source workflows. Outcome: hosts the world’s largest git repository — about 300 GB and 4 million files — and gains customer traction and faster pull‑request handling.
AI-written summary · about
chapters (26)
- 0:00Introduction
- 4:50Bill Gates and open source
- 6:30Business need for open source
- 8:00Team Foundation Server
- 11:40Version Control
- 14:10Competitive Advantage
- 21:02Convince your boss
- 24:55Your bosses know whats coming
- 25:40They care about closing deals
- 26:04Talk to your management
- 29:50Talk to your lawyers
- 32:20One person in a company
- 35:28Keep it legal
- 35:44Types of opensource licenses
- 37:27Educate your legal team
- 40:28Compliance scanning
- 43:48Embrace the community
- 44:55Dont fork
- 45:35Create abstract mechanisms
- 46:34Contribution funnel
- 47:13Microsoft
- 47:47Have fun
- 49:04Shipping your code
- 52:18The inner source
- 52:54Working in silos
- 53:21Windows and Visual Studio
related talks
44mFrom the Cathedral to the Bizarre: Microsoft’s Open Source Journey
13mHow can we truly arrive at "open-source everywhere"?
57mOpen Source at commercial organisations
15mAdopting Open Source Practices To Build More Inclusive Products and Services
44mBringing Open-Source Brilliance to Scrum Teams: A Guide to Enhanced Collaboration
23mThe Open Source Journey of the Most Unlikely Participant
44m7 Things you can Learn from Microsoft's Open Source Experience
30mMaximizing Open Source Investment to Drive Business Innovation