Who Signs the Deed? Relicensing and the Contributors Who Have to Live With It
Photo: Randolph.hollingsworth, CC BY-SA 4.0, via Wikimedia Commons
Few events in an open-source project's life expose its actual power structure as efficiently as a relicensing. The code may belong to "the community" in every README and conference talk, but the moment a maintainer announces a move from MIT to a source-available arrangement — or from permissive to copyleft — the community discovers precisely how much of that ownership was rhetorical.
A license change is not a legal footnote. It is a property transaction, and the interesting question is always the same: who had the authority to sign, and who had to be persuaded?
The Two Paths, and What Each Assumes
Projects handle this in one of two ways. The first requires no prior planning: copyright law itself. If contributors never transferred their rights, every one of them technically holds a stake in the combined work, and a wholesale relicensing requires their consent — a logistical nightmare that has stalled more than one high-profile transition.
The second path is contractual foresight. A Contributor License Agreement, signed at first pull request, grants the project (or more often, the corporate steward behind it) the standing to relicense unilaterally. The DCO, by contrast, is a lighter-weight certification of origin that grants no such power. This is the quiet battleground: CLAs concentrate flexibility in the maintainer's hands, DCOs distribute it to every contributor. Neither is neutral. Each encodes a prediction about whether the project will one day want to change the deal.
What the Reaction Patterns Teach
When major relicensing events have played out publicly, the community response has followed a predictable choreography: an announcement framed as sustainability, a wave of forks within days, and a bruised argument about betrayal. The forks matter less than the rhetoric. Contributors who object rarely claim legal standing — the CLA settled that. They claim a broken promise, which tells you the social contract was always operating one layer above the license file.
The lesson for governance-minded maintainers is blunt. If your project's legitimacy rests on community goodwill, a CLA converts that goodwill into a contingent liability. The day you exercise the option, you spend it.
An Honest Position
There are legitimate reasons to relicense. Sustainability is real, venture funding is real, and sometimes copyleft is the right defensive posture. The position worth defending is not that relicensing is wrong — it is that it should be priced honestly. If a project intends to preserve the option to commercialize, say so in the contribution docs before the first outside patch arrives, not after. Contributors deserve to know whether they are donating to a commons or extending a line of credit.
Open source belongs to whoever the paperwork says it does. The rest — the belonging that actually sustains a project — has to be earned before the announcement, not apologized for after the fork.
