March 6, 2026
Proxy Wars: License Edition
GPL upgrades via section 14 proxy delegation
Pick a license boss: devs cheer, skeptics cry power grab
TLDR: A dev proposes naming a “proxy” to approve future license upgrades under GPL’s section 14, avoiding both lock-in and blind trust. The comments explode: some praise the veto-friendly control, others fear single-person gatekeeping or FSF influence, pushing for maintainer votes or CLAs—open-source power politics in action.
Open-source devs are buzzing over a new licensing move: instead of locking a project to one version of the GPL (a popular free software license) or trusting future versions blindly, a maintainer can name a “proxy” who publicly approves upgrades later. That’s straight from section 14 of GPLv3, and one dev even named themselves as the proxy. The crowd split fast: some love the control, others smell drama.
Fans say it’s basically “use newer license, but with a veto switch”—clean, clever, and fair to contributors. Skeptics clap back with “what if the proxy disappears?” and push for a group vote via a MAINTAINERS file, while the anti-FSF (Free Software Foundation) crowd grumbles this still hands too much power to license writers. The corporate-leaning crew dropped a spicy “use a CLA,” meaning a Contributor License Agreement that lets maintainers relicense more freely—cue boos from folks who prefer community rights. Meanwhile, KDE slid in with the flex: they already do a membership vote for future upgrades, complete with paperwork you can peek at here.
Memes flew: “license gatekeeper,” “FSF final boss,” and “family meeting in MAINTAINERS.” It’s open-source governance meets reality TV, and everyone’s arguing about who gets the rose—and the right to change the rules.
Key Points
- •GPL-3.0-only requires consent from all copyright holders to change the license, which can be impractical.
- •GPL-3.0-or-later permits use under future versions published by the FSF, but delegates control over updates.
- •Section 14 of GPLv3/AGPLv3 allows designating a proxy to publicly accept future license versions for the program.
- •The article provides sample license text that keeps AGPLv3-only while empowering a named proxy to authorize upgrades.
- •The approach is integrated with the Developer Certificate of Origin, with contributors retaining their copyrights.