Understanding Corporate Open Source Strategy
summary
Companies behave around open source for money and legal risk, so expect decisions driven by finance and lawyers rather than altruism. Three concrete interaction modes are invisible open source (hidden libs like libxml under proprietary stacks), visible open source (obvious components like Grafana, MariaDB/Postgres) and homegrown forks or releases. Common motives: abandonware drops, “field of dreams” repos, competing SDKs, security auditing, or publicity. Problems include multi-headed orgs, governance refusal, culture and lawyer bottlenecks, and empty foundation money.
AI-written summary · about
chapters (16)
- 0:00Introduction and background
- 1:51Why companies exist and act
- 6:25How companies interact with open source
- 7:06Invisible open source explained
- 9:31Visible open source explained
- 10:54Homegrown open source explained
- 11:35Open core model critique
- 13:18Reasons companies release code
- 15:06Misconceptions about maintenance
- 15:27Field of dreams open source
- 17:34Open source to compete
- 18:37Security and open source
- 20:05Publicity as open source motivation
- 21:08Challenges companies face
- 25:43Culture clash and governance
- 27:27Being a professional open source user
related talks
25mHow to be a Corporate Open Source Citizen
04mThe role of open source in a company
24mNavigating Open Source Project Risk
54mWho Pays for Open Source? A Case for Open Governance & Enterprise Contributions
44mOpen Source in Financial Services: The Good, The Bad and the Ugly
42mOpen Source at a Crossroads
37mTalking with management about open source
35mWho Pays for Open Source? A Case for Open Governance & Enterprise Contributions