Talking with management about open source
summary
Explains how to translate open source into management terms by showing ROI, supply-chain risk and concrete remediation costs (e.g., replacing a tiny project could mean hiring six more people or rebuilding from scratch), uses Log4Shell as a supply-chain case that got fixed faster because it was open source, highlights the elephant factor (how many companies contribute) and single-maintainer risk (what happens if the maintainer wins the lottery), and argues open source is a long‑term investment that takes years to yield influence.
AI-written summary · about
chapters (20)
- 0:00Intro
- 0:35Why open source is important
- 1:35Meta reason why open source is important
- 2:53Think about your motivations
- 4:06Survey
- 5:15Why open source
- 6:32Translation not lying
- 7:11Profits
- 8:04Dont lead with philosophy
- 9:22Your business is not a charity
- 10:45ES bombs on the supply chain
- 11:22Marketing genius
- 12:27Trust
- 13:22Use data
- 14:31Sustainability
- 15:23Elephant Factor
- 17:02Reputation
- 18:55Fun
- 20:50Resume Building
- 24:18Question for Rich
related talks
37mTalking with management about open source
39mTalking with Management About Open Source
23mInvesting in Open-Source
27mHow to Explain the Impact of Your Open Source Work
27mHow open source companies win
23mMaking the Business Case for Contributing to Open Source
41mBridging the Gap: Incorporate OpenSource In Product Managers Toolbox
29mOpen Source and IP Departments: Risk Containment and Portfolio Management
