13 ms·
User beware: Modified AGPLv3 removes freedoms, adds legal headaches
- rectang 5y agoI can understand the trial court's rationale. Preventing a licensor from adding clauses may have been intent of the authors of the AGPL, but they aren't in a position to enforce that. The license in question is not being called "GNU Affero General Public License + Commons Clause", which could be fought on the grounds of trademark violation — it's being called the "Neo4j Sweden Software License". There's the theoretical possibility of a copyright claim for the text of the AGPL, where the AGPL's copyright holders disallow derivative works, but I'm pretty sure that won't fly for lots of reasons: not clear who has the copyright and therefore has standing, not original enough, functional rather than creative, etc. ETA: There may actually be a trademark problem here. https://sfconservancy.org/blog/2022/mar/30/neo4j-v-purethink-open-source-affero-gpl/ https://sfconservancy.org/blog/2022/mar/30/neo4j-v-purethink... > But Neo4j consciously chose not to do that. Instead, they license their software “subject to the terms of the GNU AFFERO GENERAL PUBLIC LICENSE Version 3, with the Commons Clause”. (The name “Neo4j Sweden Software License” only exists in the later Court papers, BTW, not with “The Program” in question.)
- phkahler 5y ago>> I can understand the trial court's rationale. Agreed, there is no point or value in adding terms that can be immediately removed by the person receiving it. IMHO the FSF also went a little too far trying to dictate how people go about handling violations in GPLv3, but it's still a good license.
- rectang 5y agoI think we have to accept that people will reuse and modify the texts of various open source licenses in all sorts of ways which cause downstream confusion. What the FOSS community needs to ensure is that users can always differentiate between a FOSS license and a modified version which has subtle but profound changes. Our best defenses there would seem to be trademarks and social pressure. "That's not actually the AGPL, and calling it the AGPL causes confusion in the marketplace."
- itsabug 5y agoIn fact, modifying and updating licenses falls under what I'd consider free speech. The answer to bad license edits is not to shut them down, it's just to write better ones and convince others to use them. I may not agree with bad license edits, but I'll defend them under the right to the free speech of the developer who is shipping the code.
- miffy900 5y agoWhat you're talking about falls under Fair Use. Free speech protections don't provide any such right.
- michaelmrose 5y agoIt's never been acceptable free speech to sell a fake Rolex watch or a fake Samsung TV and its not a violation of free speech to insist they call it something else. This is a really weird hill to die on.
- api 5y agoAll of these headaches stem from the OSI's refusal to address the problems posed by SaaS to the open source model. Their thinking is stuck in the 1980s and 1990s. SaaS is effectively a loophole. You can use 100% open source software to create something that is actually far more proprietary and that offers less user freedom than old school closed source applications. Yes the user can theoretically get the code but it's painful to operate and meanwhile the SaaS application has all the user's data. Open source is rapidly becoming free labor for closed SaaS and a tool to accelerate the lock-down of user data in the cloud rather than a tool to expand user freedom. People are trying to roll their own licenses to deal with these problems since the OSI is providing no leadership.
- jamestanderson 5y agoWasn't the AGPL created to address exactly this loophole?
- 5y ago
- lakecresva 5y ago> There's the theoretical possibility of a copyright claim for the text of the AGPL, where the AGPL's copyright holders disallow derivative works There's also a pretty clear case for promissory estoppel since their FAQ (which is "maintained by the Free Software Foundation's Licensing and Compliance Lab") says "we will not raise legal objections to your making a modified license": https://www.gnu.org/licenses/gpl-faq.en.html#ModifyGPL https://www.gnu.org/licenses/gpl-faq.en.html#ModifyGPL
- rectang 5y agoBut Neo4J didn't fulfill the conditions of that FAQ, particularly this: > provided that you call your license by another name
- bombcar 5y agoGiven that the AGPL itself uses qualifiers to be a different license from the GPL arguably adding the “with commons clause” is a different name.
- rectang 5y agoThat's the argument that the Commons Clause authors made — that they should be able to sponge off of the goodwill of FOSS community. It's outrageous, offensive, and I strongly suspect a losing legal argument so long as the original license name is a defensible trademark. Consider the Apache Software License version 2.0. "Apache" is a registered trademark held by the Apache Software Foundation in the US and other jurisdictions. The Commons Clause is not additive, it is antithetical to the values of the ASF and directly undermines the ASF's mission. Calling something the "Apache License with the Commons Clause" damages the interests of the ASF by introducing a confusingly named product into the market. What I have more questions about are other licenses where there's not necessarily an obvious trademark held by a willing defender. Can you call your deceptive fake FOSS license the "Common Development and Distribution License"? I'm not so sure about trademark defense there — the only option might be social pressure.
- itsabug 5y agoI... Think this ruling is good, even if you disagree with the Commons clause? I'm not sure I'm thrilled with limiting the speech of developers by saying they cannot ever place any restrictions whatsoever on how their code is used.
- jamestanderson 5y agoDevelopers certainly can place restrictions on how their code is used. In my view, if developers want to add those restrictions, via the Commons Clause or otherwise, they should not license their work under the AGPLv3 (or other Open Source licenses). It appears the courts do not agree though, at least in this case.
- Dylan16807 5y agoWell it's not AGPLv3, it's a modified version.
- djur 5y agoYeah, I don't see any reason to think it's wrong. Neo4j is in the wrong in that they represented their corrupted AGPL as "free and open source", and they should not have used the original name and text of the AGPL. But I don't see any good argument that the FSF's interpretation of the corrupted AGPL should supersede that of the copyright holders.
- wtallis 5y ago> But I don't see any good argument that the FSF's interpretation of the corrupted AGPL should supersede that of the copyright holders. It seems like the copyright holders assembled a chimera license that is in conflict with itself. The resulting ambiguity should be construed against the copyright holders and in favor of the users.
- deleted 5y ago[deleted]
- 5y ago
- em-bee 5y agobasically all the court is saying is that a clause that says: you may remove any additional clauses is meaningless. maybe it needs to be written differently: any additional clauses are optional or even: this is the complete license, any additional text is not part of the license this clause is essentially a trap for anyone who wants to use this license with modifications. and if i wanted to do that i'd just remove this very clause to avoid misunderstandings. the question that remains is: how does one add optional clauses that actually remain optional
- rectang 5y agoIt's not meaningless. Licensees can remove clauses introduced by other licensees, but cannot remove clauses introduced by the original licensor. In this case, the original licensor introduced the Commons Clause, and licensees can't remove it. (Notwithstanding whether it was legitimate for Neo4J to present their modified text under a deceptive name.)
- michaelmrose 5y agoIf you distribute software that includes software that includes software that includes software who is the original licensor. Do you have to track who wrote which text and added which restrictions to track what restrictions apply to which portion of the text. When modified version of deps result in interleaved restrictions how do you decide what you can or cannot do? The only logical thing to do is to treat such additional restrictions as poison.
- rectang 5y ago> If you distribute software that includes software that includes software that includes software who is the original licensor. In this case, the original licensor is clear: it's Neo4J, who holds the copyright on the whole thing, who have made it available under a source-available license of their choice, and who can make it available under additional license if they like — such as a proprietary license which they will sell to you. In community open source projects which publish "software that includes software that includes software", you have to keep track of where every last line of code came from. That's called "provenance", and if you don't pay attention to it and improperly introduce code which belongs to somebody else without their permission, you're opening up both yourself and your users to legal liability. Tracking provenance is work, but the concepts at issue are not vague.
- mardifoufs 5y ago> As a consequence, using any software under a non-OSI-approved licensing combination requires professional advice on the scope of rights being granted. [...] Sticking to OSI-approved licenses is the way to ensure that everyone’s expectations are met. I have absolutely no strong opinion on either the OSI or the FSF, and I don't really care about licenses in general. Yet it seems like the OSI really likes to add these sorts of "conclusions" even if they don't really add anything to the article? This post isn't that bad since it's just misplaced and bland marketing. But they also recently posted a pretty misleading article about the same court case where they made a lot of weird assumptions to again conclude that they are the only true path (tm). [0] This wouldn't surprise me if it came from a corporation but why would a non profit be so militant and uncompromising w.r.t licensing philosophy? I get advocacy but I guess I'm not used to non-profits being so... competitive? [0] https://writing.kemitchell.com/2022/03/17/OSI-Neo4j-PureThink https://writing.kemitchell.com/2022/03/17/OSI-Neo4j-PureThin...
- thayne 5y ago> why would a non profit be so militant and compromising w.r.t licensing philosophy? Well, when open source licenses is the purpose of the non-profit, then it shouldn't be surprising that they are militant and uncompromising (I'm guessing that's what you meant).
- aaron695 5y ago
- hardwaresofton 5y ago> Affero General Public License version 3 with the addition of the Commons Clause (referred to in the case as the “Neo4j Sweden Software License”) was “free and open source” software. Unfortunately that case contains one more decision that is already raising concerns among the open source community. I still think AGPLv3 is the future for open source[0], but not like this, this is pretty egregious as adding the commons clause removes freedoms. This article contains the biggest confirmations I've seen of my long-held stance that the AGPL was never meant to prevent commercial use: > That conclusion goes against the intent of the drafters of the AGPLv3. The GPLv3 Second Discussion Draft Rationale says in footnote 73 that the restriction was aimed at the copyright owners themselves: “Here we are particularly concerned about the practice of program authors who purport to license their works under the GPL with an additional requirement that contradicts the terms of the GPL, such as a prohibition on commercial use.” I do wonder if a bunch of projects need to start considering a move to BSL or SSPL or something else. [EDIT] clarify that the commons clause is causing freedom removal. [0]: https://news.ycombinator.com/item?id=30866724 https://news.ycombinator.com/item?id=30866724
- thayne 5y ago> As Plaintiffs point out, however, the AGPLv3 defines “you” as the licensee, not the licensor. AGPL § 0 (“Each licensee is addressed as ‘you’”). Thus, read correctly, Sections 7 and 10 prohibit a licensee from imposing further restrictions, but do not prohibit a licensor from doing so. I don't understand this argument at all. Section 7 states > All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. And since "you" means the licensee, wouldn't that mean the licensee can remove the additional terms added by the commons clause?
- rectang 5y ago> And since "you" means the licensee, wouldn't that mean the licensee can remove the additional terms added by the commons clause? No (the trial court has reasoned), because the Commons Clause was introduced by the licensor. Thanks to that provision in the license, licensees can remove clauses introduced by other licensees, but cannot remove clauses introduced by the original licensor. The original licensor is Neo4J, the copyright holder for the software, which has made it available under the license in question.
- aspenmayer 5y agoWouldn't the pre-Commons Clause software still be soley GPL v3? I thought that software cannot be retroactively re-licensed, so I'm not following your (or maybe the court's) reasoning. I think you and OP can both be right, but in the context of this case, OP's point is not relevant, if I'm understanding correctly?
- pabs3 5y agoThat part of the license doesn't say only restrictions added by licensees can be removed, just that any added restrictions can be removed.
- aspenmayer 5y ago> And since "you" means the licensee, wouldn't that mean the licensee can remove the additional terms added by the commons clause? That logically follows to me. I think that's why they call it the AGPL v3 "with Commons Clause," as if it's not a modifier to the original agreement, AGPL v3, but rather an additional agreement that you also must agree to in order to use the software. This seems contrary to AGPL v3, which says you should be able to remove any additional clauses. I don't see why the Commons Clause folks did it at all, but in any case, they failed in court, which is technically all that matters at this point.
- saagarjha 5y agoA slight tangent, but perhaps relevant to the discussion: the clause mentioned in this article is not singular to AGPLv3; it's present in GPLv3 as well.
- cameldrv 5y ago“ Indeed, it would be contrary to principles of contract and copyright law to interpret these provisions as limiting Neo4J Sweden’s exclusive right to license its copyrighted software under terms of its choosing.” This makes no sense. Neo4j were the ones that picked AGPLv3 as the license. If they didn’t like the clause that allows the licensor to delete further terms, they should have picked a different license or written their own.
- jeremyjh 5y agoEssentially, by adding the commons clause to it, they did write their own license. If there is a complaint here it seems it would have to be about trademark infringement for calling it the AGPL. Not sure why SP calls this surprising. The AGPL itself is NOT licensed! There is no contract between FSF and Neo4J.
- wtallis 5y ago> The AGPL itself is NOT licensed! There is no contract between FSF and Neo4J. The AGPL begins with a copyright notice, followed by the statement: > Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. That looks to me like the license terms for using the AGPL itself. Modification isn't permitted, so if you want to construct a new license with the AGPL as the starting point, you have to use the AGPL verbatim followed by exceptions, because modifying the AGPL itself to delete the bits you don't want would be copyright infringement. Part of what's at issue here is whether Neo4J can append exceptions that effectively delete arbitrary portions of the AGPL even though Neo4J is required to keep the dead code in their license text. But Neo4J only seems to have done that implicitly, because the Commons Clause doesn't explicitly override the portions of the AGPL that talk about exceptions (and includes the problematic statement "Without limiting other conditions in the License").
- zaarn 5y agoYou don't have to modify the AGPL to impose additional restrictions. All you have to do is put your additional restrictions in the LICENSE.txt file and then at the end include "All further licensing conditions, rights and clauses are specified in LICENSE_AGPL.txt. Any such conditions, rights and clauses specified in LICENSE_AGPL.txt do not override, replace, nullify, void or otherwise affect conditions of this document unless specified in the very same document. This document takes precedence over any text in LICENSE_AGPL.txt" And now you have an unmodified AGPL with additional restrictions as much as you want to.
- thescriptkiddie 5y agoAnyone know if the Free Software Foundation has done a piece on this?
- smlavine 5y agoI just really, really, really, really hope that we don't have to go through a GPLv4 because of this.
- jupp0r 5y agoIANAL, but I feel like it’s vastly preferable to hire one and have some written agreement with the license holder to be using AGPL software in any commercial product.
- pengaru 5y agoThis echoes of the kind of v3 fuckery Linus Torvalds complained about in his GPLv3 objection recorded at DebConf '14. [0] I'm a long-time Free/Libre software user and advocate, but "if the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term." strikes me as a very strange thing for the license to include. The copyright holder clearly has the authority to use whatever licensing terms they wish. If they added restrictions, this clause is in direct conflict with their intentions. Of course the court sided with the plaintiff. I don't understand what the FSF was trying to do here, it seems obviously underhanded like Torvalds touches upon in[0]. [0] https://www.youtube.com/watch?v=PaKIZ7gJlRU&t=147s https://www.youtube.com/watch?v=PaKIZ7gJlRU&t=147s
- pabs3 5y agoThe intent of that part is explained by the Conservancy post linked from the OSI article.
- didibus 5y ago> 73 [...] Here we are particularly concerned about the practice of program authors who purport to license their works under the GPL with an additional requirement that contradicts the terms of the GPL, such as a prohibition on commercial use. Such terms can make the program non-free, and thus contradict the basic purpose of the GNU GPL; but even when the conditions are not fundamentally unethical, adding them in this way invariably makes the rights and obligations of licensees uncertain. It still doesn't sit right with me. Like the program authors should be allowed to license things however they want. A clause to contradict the program authors so as to not have them contradict the GPL is kind of strange to me. I get the possibly "false advertisement" angle, like hey we're AGPL "caugh but not really". As a scheme to fool users into thinking they can use it freely. But still, I feel that be better to be on a user to read the additional terms and decide for themselves. At least the court recognized you can't call a modified AGPL free and open source, so I guess the court established that and now this clause is no longer needed on the AGPL maybe?
- pabs3 5y agoAnother post on this case from Software Freedom Conservancy: https://sfconservancy.org/blog/2022/mar/30/neo4j-v-purethink-open-source-affero-gpl/ https://sfconservancy.org/blog/2022/mar/30/neo4j-v-purethink...
- didibus 5y ago> The trial court held that this provision in the AGPLv3 applies only to downstream licensees, not when the original licensor adds them I honestly feel this rationale makes sense, so I kind of agree with the courts. If I'm choosing a license and I'm adding clause, it be weird that by accident one of my clause somehow invalidates my others, I'd be kind of angered if that happened without me realizing. I don't think the intent of the writers of AGPL matters here, more so the intent of the licensors matters. > It was the intention of the FSF (footnote 73) that if the licensor added more restrictions, the downstream users could remove them This just doesn't doesn't make sense to me lol. If that's the case, why would the licensors add more clause? They're basically irrelevant. It's almost like the FSF intended to trick the authors who choose AGPL into not realizing what terms they were licensing their work under. I get that FSF cares more about the users of a library than the authors of the library, so I understand the branding aspect. A user might have wrongly thought that AGPL meant they could resell it, and ignored reading the added clause. And I get that the combination of AGPL and the added clause would definitely be confusing to a user in the wording of AGPL with regards to removing them. But in the end, I feel I like this ruling. They said you can't call it free and open source if you don't allow for free and open source use as part of your license. But they also said that the intended clause from the authors mattered, not the interpretation of the user, and I think that's just to the authors.
- peeters 5y ago> It's almost like the FSF intended to trick the authors who choose AGPL into not realizing what terms they were licensing their work under. Yeah I don't really understand the logic here. It's almost like they're considering themselves the root licensor for all projects that use the AGPL. Which (despite their intention) comes across as pretty hostile towards software authors.
- timmb 5y agoIf you don’t want to offer the freedoms of a licence then pick a different one. To choose one with an established meaning and then remove those freedoms undermines the purpose of having standardised licences. The authors are potentially setting users up for unintended infringement. I see it as similar to organic food. Once you add non-organic ingredients then it’s not organic any more. You can do what you want but it’s fair enough if everyone else asks you to respect the labels they’ve built to let people make informed decisions.
- deleted 5y ago[deleted]
- peeters 5y agoNot a lawyer, have no law training...but I have a hard time seeing how any other interpretation than this court would be viable. At its heart, this is a matter of contradictory clauses in a contract. One clause says you can't do something, the other says you can. Why should one clause automatically trump the other? In cases like this, a court has to interpret what the parties intended the contract to mean. The licensor had full authority to set the terms, and willingly chose to modify the original license. It's unreasonable to conclude that they went out of their way to add a restriction that they intended everyone to be able to remove. At best each time this comes up a court is going to need to evaluate the circumstances objectively, which is itself a fatal flaw for a boilerplate license that tries to avoid these exact nuances.
- wtallis 5y ago> it's unreasonable to conclude that they went out of their way to add a restriction that they intended everyone to be able to remove. They added a restriction, but did not remove the portions of the original license that are in conflict with that restriction. So their actions paint at best a murky picture of what their intentions were; either their intentions were strange, or they were remarkably incompetent in crafting their license to fit their intentions. It seems to be a bit of a stretch to say the courts must interpret it as if it's the license they should have written, rather than the license they actually wrote.
- josefx 5y agoThe court documents at one point call that contradiction out as being nonsensical. A license cannot prevent the licensor from choosing restrictions, so interpreting the AGPL in a way that automatically nullifies those does not make sense in this context.
- dTal 5y ago>paint at best a murky picture Going out of your way to add something that you wrote is very clearly a more intentional and conscious act than failing to remove something that someone else wrote. The picture is crystal clear. >they were remarkably incompetent in crafting their license Perhaps. Irrelevant. >It seems to be a bit of a stretch to say the courts must interpret it as if it's the license they should have written That's the only possible resolution mechanism when someone writes a self-contradictory contract. Law is not code. Intention matters.
- jayp1418 5y agohttp://netbsd.org/about/redistribution.html#why-berkeley http://netbsd.org/about/redistribution.html#why-berkeley ;)
- milkllz 5y agoBefore people jumping into conclusion, maybe read this first? https://writing.kemitchell.com/2022/03/17/OSI-Neo4j-PureThink.html https://writing.kemitchell.com/2022/03/17/OSI-Neo4j-PureThin...
- chunsj 5y agoWhomever the legal expertise writes the license, the court can always invalidate it. Is this normal?
- milkllz 5y agoI think you are giving Neo4J too much credit on this. From what I read, they just basically slap Common Clause on APGLv3 and call it a day. The court just came in and adjudicate this is a (AND &&) clause instead or (OR ||) clause because assuming the latter would be kinda pointless because the Common Clause is more restrictive.
- arlcode 5y agoContracts cannot override the law (I can't sell myself into slavery even if I sign a contract saying so). Courts are there to decide how the law applies to a given situation when the parties do not agree. A judge makes a decision and that decision is in accordance with written law, precedence and legal tradition. If necessary it supersedes the intention of the original authors of the contract and the parties can appeal to a higher court. The law itself is pretty much what the government says it is.
- deleted 5y ago[deleted]
- MrStonedOne 5y agoCan the OSI stop trying justify their existence by finding any excuse to call out "non-osi approved" every chance they get. Only lawyers in corporations care about that distinction and I hate them more and more the more they try to authority signal using it. All of these excessive callouts to "OSI approved" or "Not OSI Approved" in every article like they are the gatekeepers to rather or not licenses can be called open source. Sorry, but you can't name your non-profit after a dictionary word or common usage phrase that existed before you even existed then become the all seeing gatekeeper over what qualifies for those terms. That's not how language works.
- philosophyquad 5y agoVery surprised by all the comments here critical of the OSI. Even if Neo4j was correct by the court's interpretation (which I agree with), it seems clear that they were indeed "open-washing" as the article says. It's changed now but it used to say on the Neo4j website "the Neo4j Enterprise Edition is dual licensed under Neo4j commercial license as well as under the free Affero General Public License (AGPL) v3" (neo4j.com/open-source-project on web.archive.org). Obviously this is misleading (because it is not in fact free). I think this is a big problem. Advertising products as open-source can drive adoption, but it should not come at the cost of diluting the meaning of the term itself.
- arlcode 5y agoIf I'm not mistaken the court agreed that you cannot call such a license free and open source anymore. This is a different matter.
- jart 5y agoThe AGPLv3 is the most terrifying open source license of them all so I fail to see how a creator having the intention of not wanting others to sell their code is any kind of divergence from that general feeling. Not a whole lot to sponge off.
- colonwqbang 5y agoWhy is it unexpected? It seems rather logical to me. The particular interaction between clauses on the license looks like a contract "bug". Why would Neo4j add such a clause to the license if they intended it to have no effect? The reasonable interpretation is that they did intend the added clause to mean what it says. What the writer of the original license template (the AGPL) wants is not relevant. Regardless, it's probably not very wise to take an established license like AGPL and amend it like this.
- squarefoot 5y agoPrevious discussion about the Commons Clause license. https://news.ycombinator.com/item?id=17818407 https://news.ycombinator.com/item?id=17818407
- nabla9 5y agoI don't understand the reasoning that called this ruling “erroneous." Whoever crafted the AGPLv3 license is not a party in the contract. AGPLv3 + modifier from the original licensor conveys the intention from the licensor more accurately than what AGPLv3 alone. Any contradictions between intent of the AGPLv3 and AGPLv3 + modifier must be resolved that in mind. Whatever FSF intended in the AGPLv3 or how it is interpreted in courts alone is meaningful only when there is no contradiction with AGPLv3 + modifier. Correct me if I'm wrong but I think this is pretty well established general principle. Added modifications override the original text without the need to alter the original.
- KingOfCoders 5y ago"Users beware, AGPLv3 removes freedoms, adds legal headaches" over MIT or PD.
- ttybird2 5y ago"In a prior post, we reported on a decision from a U.S. district court holding that it was false advertising for a company to claim that software licensed under the Affero General Public License version 3 with the addition of the Commons Clause (referred to in the case as the “Neo4j Sweden Software License”) was “free and open source” software" This part is false, also see https://news.ycombinator.com/item?id=30712215 https://news.ycombinator.com/item?id=30712215 and https://news.ycombinator.com/item?id=30726286 https://news.ycombinator.com/item?id=30726286 "That conclusion goes against the intent of the drafters of the AGPLv3" This is true, but I personally believe that the position held by the court (that it applies only to downstream licensees) makes much more sense. After all the original developer could have selected another license in the first place. "Any effort to change the terms of an open source license should be met with suspicion because they are likely designed to take away freedoms, or else an already OSI-approved license would have been suitable" I wonder when this start being true in their opinion (after the approval of GPLv3?). The threats to FOSS evolve and licenses must try to match them. It seems like an attempt to attack SSPL without explicitly mentioning it. "Sticking to OSI-approved licenses" There are also FSF-approved licenses which are not mentioned. The last part is pure advertisement.
- throwawayninja 5y agoAnd this is why my code is GPLv2 and nothing more, I even remove the auto-upgrade clause the FSF wants everyone using v2 to include.
- deleted 5y ago[deleted]