Open Source Licensing: Use Versus Abuse
summary
Covers concrete license switches and their effects: MongoDB moves to SSPL and restricts contribution model, Elastic shifts from Apache to the Elastic License to block hosted forks, Redis and HashiCorp relicense to business‑source patterns to protect cloud revenue while risking contributor churn. Lists consequences—reduced adoption, legal uncertainty, ecosystem fragmentation and higher maintenance costs—and notes there is no single auto‑solver for final artifact licensing though SBOM/SPDX inventories help and BSL/USL variants are becoming common.
AI-written summary · about
chapters (13)
- 0:00Open source licensing intro
- 1:45Fairness in licensing changes
- 5:18MongoDB’s SSPL shift
- 8:07Elastic’s license change
- 10:22HashiCorp’s license impact
- 13:22Public domain vs proprietary
- 16:12Permissive licenses
- 19:28Copyleft licenses and GPL
- 21:19Business Source License
- 22:23Key licensing terms
- 24:55Docker licensing issues
- 27:26Security and compliance
- 28:11Q&A
related talks
14mOpen Source Licensing in a Business World
01h 38mOpen Source Licensing: Types, Strategies and Compliance
51mThe Impact of Leveraging Open Source
25mLicensing Tradeoffs in Open Source Startups
31mUpdate on licensing - "not really" open source licenses
34mWhen Your Open Source Turns to the Dark Side
01h 26mOpen Source Software Licenses and Business Models Explained
32mSOS: Sustainable Open Source
