Power Dynamics, Rug Pulls, and Other Corporate Impacts on OSS Sustainability
summary
Covers data on relicensing and hard forks with concrete cases — Elasticsearch → OpenSearch, Terraform → OpenTofu, Redis → Valky, Puppet → Openbox — showing patterns: 95–97% employee contributions at Elastic, 52 contributors from 13 companies in Valky’s first year with 22 prior Redis contributors, and a clear spike then decline in forks/stars around relicensing. Uses CHAOSS metrics and Jupyter notebooks for analysis, highlights CLAs as a red flag, and recommends preferring neutral foundations and the project viability/practitioner guides to reduce risk.
AI-written summary · about
chapters (15)
- 0:00Open source power imbalances
- 1:46Cloud providers and feudalism
- 5:17Rug pulls in open source
- 9:08Hard forks vs social forks
- 11:38Relicensing as rug pull
- 13:02Puppet’s rug pull and OpenBao
- 17:14ElasticSearch relicensing and OpenSearch
- 21:27Terraform relicensing and OpenTofu
- 23:11Redis relicensing and Valky
- 25:36Measuring OSS usage with stars/forks
- 28:04Warning signs and rug pull prevention
- 30:09Neutral foundations and governance
- 32:38Supporting OSS sustainability
- 34:44Shifting power in OSS ecosystems
- 35:46Q&A
related talks
36mState of Open Source in 2024
34mWhen Your Open Source Turns to the Dark Side
50mOpen Source as a Business: Strategy, Struggle & Success
33mThe Cathedral, the Bazaar, and the Coffee House
36mPanel Discussion: OSS Viability and Project...
39mSOS: Sustainable Open Source
43mWhat Makes a Good or Bad Open Source Experience
47mGame of Open Source: A Tale of Hype & Mire