What Makes a Good or Bad Open Source Experience
summary
Summarizes findings from a podcast of practitioner interviews that tie concrete numbers to problems: the claim that 80% of a product’s codebase is open source; Rackspace’s OpenStack moved from 86% to 57% vendor authorship as a deliberate community goal; ElasticSearch’s license shifts spawn OpenSearch and OpenTofu forks; regulators push the Cyber Resilience Act with ~2 years lead time; maintainers face fatigue and a missing 5% maintenance gap that breaks supply-chain reliability.
AI-written summary · about
chapters (12)
- 0:00Open source ecosystem intro
- 10:26Open source community experiences
- 15:04Single vendor challenges
- 20:24License changes impact
- 23:16License misconceptions
- 25:24Beyond license type
- 26:30Government regulations
- 28:16Paid work & security
- 33:19Non-code contributors
- 35:04Corporate open source
- 40:18Supply chain challenges
- 41:44Q&A
related talks
36mState of Open Source in 2024
39mSOS: Sustainable Open Source
57mThe Dramatic Consequences of the Open Source Revolution (...)
01h 01mWe're Building On Hollowed Foundations (...)
36mSOS Sustainable Open Source
47mGame of Open Source: A Tale of Hype & Mire
40mOpen Source Is Not the Same Anymore
25mWhat Makes Open Source Work: Licensing and Beyond