Open Source Is Not the Same Anymore
summary
Open source projects now change licenses, lock APIs, or stay controlled by one vendor; curl ends a $86,000 bug‑bounty after AI‑generated noise; Synadia tries to reclaim NATS despite supplying ~97% of commits; Terraform’s BS L move spawns OpenTofu; Redis fork Valkey grows to ~50,000 contributors and ~20,000 stars with ~75% of users exploring alternatives. CodeRabbit finds AI PRs (470 samples) have 1.7× more issues and ~3× more vulnerabilities; Cortex shows PR volume +20% and incidents +23.5%. Follow a five-question checklist: read three lines of the license, check the elephant/bus factor, verify governance, newcomer treatment, and trademark ownership.
AI-written summary · about
chapters (21)
- 0:00Changing open source landscape
- 1:42Open source a decade ago
- 2:24Open source transformation stories
- 8:44Licenses and communities unreliable
- 11:54Licenses as negotiation tools
- 13:19Open source communities breakdown
- 16:07Economic impact and AI slop
- 17:53Critical problems in open source
- 18:39Evaluating open source projects
- 22:30Reading licenses and agreements
- 24:16Who writes the code matters
- 26:25Project governance and maintainership
- 28:11Newcomer treatment in projects
- 30:59Contributor docs and responsiveness
- 32:44Trademark ownership importance
- 34:54Successful open source models
- 35:59Kubernetes mentorship programs
- 37:01Linux Foundation mentorship
- 38:47Verifying claims and resources
- 39:10Open washing and single-vendor risks
- 39:52Key takeaways and advice
related talks
34mWhen Your Open Source Turns to the Dark Side
36mState of Open Source in 2024
43mWhat Makes a Good or Bad Open Source Experience
39mSOS: Sustainable Open Source
25mWhat Makes Open Source Work: Licensing and Beyond
42mOpen Source at a Crossroads
36mSOS Sustainable Open Source
49mTrustworthy Open Source: The Consequences of Success