The Commons Clause was announced recently, along with several projects moving portions of their codebase under it. It’s an additional restriction intended to be applied to existing open source licenses with the effect of preventing the work from being sold, where the definition of being sold includes being used as a component of an online pay-for service. As described in the FAQ, this changes the effective license of the work from an open source license to a source-available license. However, the site doesn’t go into a great deal of detail as to why you’d want to do that.
Fortunately one of the VCs behind this move wrote an opinion article that goes into more detail. The central argument is that Amazon make use of a great deal of open source software and integrate it into commercial products that are incredibly lucrative, but give little back to the community in return. By adopting the commons clause, Amazon will be forced to negotiate with the projects before being able to use covered versions of the software. This will, apparently, prevent behaviour that is
not conducive to sustainable open-source communities.
But this is where things get somewhat confusing. The author continues:
Our view is that open-source software was never intended for cloud infrastructure companies to take and sell. That is not the original ethos of open source.
which is a pretty astonishingly unsupported argument. Open source code has been incorporated into proprietary applications without giving back to the originating community since before the term open source even existed. MIT-licensed X11 became part of not only multiple Unixes, but also a variety of proprietary commercial products for non-Unix platforms. Large portions of BSD ended up in a whole range of proprietary operating systems (including older versions of Windows). The only argument in favour of this assertion is that cloud infrastructure companies didn’t exist at that point in time, so they weren’t taken into consideration – but no argument is made as to why cloud infrastructure companies are fundamentally different to proprietary operating system companies in this respect. Both took open source code, incorporated it into other products and sold them on without (in most cases) giving anything back.
There’s one counter-argument. When companies sold products based on open source code, they distributed it. Copyleft licenses like the GPL trigger on distribution, and as a result selling products based on copyleft code meant that the community would gain access to any modifications the vendor had made – improvements could be incorporated back into the original work, and everyone benefited. Incorporating open source code into a cloud product generally doesn’t count as distribution, and so the source code disclosure requirements don’t trigger. So perhaps that’s the distinction being made?
Well, no. The GNU Affero GPL has a clause that covers this case – if you provide a network service based on AGPLed code then you must provide the source code in a similar way to if you distributed it under a more traditional copyleft license. But the article’s author goes on to say:
AGPL makes it inconvenient but does not prevent cloud infrastructure providers from engaging in the abusive behavior described above. It simply says that they must release any modifications they make while engaging in such behavior.
IE, the problem isn’t that cloud providers aren’t giving back code, it’s that they’re using the code without contributing financially. There’s no difference between what cloud providers are doing now and what proprietary operating system vendors were doing 30 years ago. The argument that “open source” was never intended to permit this sort of behaviour is simply untrue. The use of permissive licenses has always allowed large companies to benefit disproportionately when compared to the authors of said code. There’s nothing new to see here.
But that doesn’t mean that the status quo is good – the argument for why the commons clause is required may be specious, but that doesn’t mean it’s bad. We’ve seen multiple cases of open source projects struggling to obtain the resources required to make a project sustainable, even as many large companies make significant amounts of money off that work. Does the commons clause help us here?
As hinted at in the title, the answer’s no. The commons clause attempts to change the power dynamic of the author/user role, but it does so in a way that’s fundamentally tied to a business model and in a way that prevents many of the things that make open source software interesting to begin with. Let’s talk about some problems.
The power dynamic still doesn’t favour contributors
The commons clause only really works if there’s a single copyright holder – if not, selling the code requires you to get permission from multiple people. But the clause does nothing to guarantee that the people who actually write the code benefit, merely that whoever holds the copyright does. If I rewrite a large part of a covered work and that code is merged (presumably after I’ve signed a CLA that assigns a copyright grant to the project owners), I have no power in any negotiations with any cloud providers. There’s no guarantee that the project stewards will choose to reward me in any way. I contribute to them but get nothing back in return – instead, my improved code allows the project owners to charge more and provide stronger returns for the VCs. The inequity has shifted, but individual contributors still lose out.
It discourages use of covered projects
One of the benefits of being able to use open source software is that you don’t need to fill out purchase orders or start commercial negotiations before you’re able to deploy. Turns out the project doesn’t actually fill your needs? Revert it, and all you’ve lost is some development time. Adding additional barriers is going to reduce uptake of covered projects, and that does nothing to benefit the contributors.
You can no longer meaningfully fork a project
One of the strengths of open source projects is that if the original project stewards turn out to violate the trust of their community, someone can fork it and provide a reasonable alternative. But if the project is released with the commons clause, it’s impossible to sell any forked versions – anyone who wishes to do so would still need the permission of the original copyright holder, and they can refuse that in order to prevent a fork from gaining any significant uptake.
It doesn’t inherently benefit the commons
The entire argument here is that the cloud providers are exploiting the commons, and by forcing them to pay for a license that allows them to make use of that software the commons will benefit. But there’s no obvious link between these things. Maybe extra money will result in more development work being done and the commons benefiting, but maybe extra money will instead just result in greater payout to shareholders. Forcing cloud providers to release their modifications to the wider world would be of benefit to the commons, but this is explicitly ruled out as a goal. The clause isn’t inherently incompatible with this – the negotiations between a vendor and a project to obtain a license to be permitted to sell the code could include a commitment to provide patches rather money, for instance, but the focus on money makes it clear that this wasn’t the authors’ priority.
What we’re left with is a license condition that does nothing to benefit individual contributors or other users, and costs us the opportunity to fork projects in response to disagreements over design decisions or governance. What it does is ensure that a range of VC-backed projects are in a better position to improve their returns, without any guarantee that the commons will be left better off. It’s an attempt to solve a problem that’s existed since before the term “open source” was even coined, by simply layering on a business model that’s also existed since before the term “open source” was even coined. It’s not anything new, and open source derives from an explicit rejection of this sort of business model.
That’s not to say we’re in a good place at the moment. It’s clear that there is a giant level of power disparity between many projects and the consumers of those projects. But we’re not going to fix that by simply discarding many of the benefits of open source and going back to an older way of doing things. Companies like Tidelift are trying to identify ways of making this sustainable without losing the things that make open source a better way of doing software development in the first place, and that’s what we should be focusing on rather than just admitting defeat to satisfy a small number of VC-backed firms that have otherwise failed to develop a sustainable business model.
 It is unclear how this interacts with licenses that include clauses that assert you can remove any additional restrictions that have been applied
 Although companies like Hotmail were making money from running open source software before the open source definition existed, so this still seems like a reach
 “Source available” predates my existence, let alone any existing open source licenses
 Disclosure: I know several people involved in Tidelift, but have no financial involvement in the company
Source From: fedoraplanet.org.
Original article title: Matthew Garrett: The Commons Clause doesn’t help the commons.
This full article can be read at: Matthew Garrett: The Commons Clause doesn’t help the commons.