Values-based OSS Open Discussion
summary
Argues that the real issue is concrete: cloud vendors relicense or slot their APIs under familiar names (example: TensorFlow reworking NumPy APIs, Amazon/Redis licensing disputes), which risks losing stable open APIs as a Commons. Shows tools and projects involved: NumPy pandas matplotlib TensorFlow, plus Anaconda and PyData ecosystems. Gives a startling size claim — the core maintainer community once fits in a minivan of maintainers adding billions of daily value — and names the pattern: extend-and-extinguish by platform players.
AI-written summary · about
chapters (14)
- 0:00Values-based open source intro
- 1:54What open source means
- 7:10Open APIs as commons
- 13:09Innovation vs commoditization
- 17:45Businesses value in OSS
- 20:37Software as community
- 23:01Software as property
- 26:50Conway’s law
- 28:54Four collaboration stages
- 33:14Trust in open source
- 34:59Goal vs value thinking
- 38:28Preserving values in cloud
- 40:58Leadership through values
- 44:29Defend open source values
related talks
42mOpen Source at a Crossroads
47mGame of Open Source: A Tale of Hype & Mire
36mState of Open Source in 2024
44mTranslating Open Source Value to the Cloud
31mUpdate on licensing - "not really" open source licenses
46mPower Dynamics, Rug Pulls, and Other Corporate Impacts on OSS Sustainability
32mSOS: Sustainable Open Source
32mOpen Source: The Engine of Innovation in the Digital Age