When Your Open Source Turns to the Dark Side
summary
Relicensing and sabotage are real risks: Terraform → BSL and HashiCorp’s fork ecosystem lead to OpenTofu (Linux Foundation) uptake; Elasticsearch → SSPL → OpenSearch forces line‑by‑line rewrites and adoption by Dow Jones, Goldman Sachs, Pinterest, Rackspace and Zoom; Grafana switches Loki/Tempo to AGPLv3; a single npm maintainer breaks colors and faker and causes widespread outages. Practical takeaways: manage license exposure like security, prefer foundation governance, use plugins not downstream forks, add license checks to CI, and remember open source is not a business model.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 3:09Open source dark side
- 8:50Elasticsearch relicensing
- 12:00Elasticsearch breaking changes
- 16:58Grafana AGPL risks
- 21:15Colors and Faker controversy
- 24:05Sustainable open source
- 26:16Using open source wisely
- 28:21Selecting open source projects
- 31:29Summary and ratchet model
- 32:53Closing advice
related talks
34mRelicensing: When Your Open Source Tool Turns to the Dark Side
25mWhat Makes Open Source Work: Licensing and Beyond
32mSOS: Sustainable Open Source
42mWhen Your Open Source Tool Turns to the Dark Side
30mOpen Source Licensing: Use Versus Abuse
40mOpen Source Is Not the Same Anymore
44mOpen-Source Exploitation
36mState of Open Source in 2024