7 ms·
Understanding the “GPL is a Contract” court case
- daurnimator 9y ago> Another interesting point in the case is that the court found Artifex’s claim of damages to be admissible because of their use of dual-licensing. An economic structure for remuneration of the developer by users who did not wish to comply with the GPL terms, and thus acquired a commercial license, was clearly present. Interesting development. This makes me want to dual-license my software so that violations have more teeth to them.
- likelynew 9y agoWell, why? If someone uses GPL only, it means they are not looking for money, but is more of a choice to not use more permissive licences. Dual licensing does not solves anything for them.
- rwmj 9y agoWait what? I write GPL only software for a living and I certainly am looking for money from it. It's just that I don't get the money by selling you the software itself.
- icebraining 9y agoIt's just that I don't get the money by selling you the software itself. Even that is perfectly fine. The company I previously worked for did exactly that: sell AGPL-licensed software to other businesses.
- daurnimator 9y agoBecause when I choose a GPL license, I do it because I want anyone that uses that code to share their changes back with me. If all I get out of a long court case is finally seeing their code, then it's not worth it for me to sue, and it's not worth it for them to comply with the license. Instead: if I dual license it: when they don't comply with the GPL license, I can sue them for damages: which makes things a hell of a lot more appealing for a lawyer to take my case, and not as much as a waste of my time.
- eeZah7Ux 9y ago"dual-licensed" is normally used to describe 2 Open Source licenses that user can choose from. [Edited for clarity]
- rmccue 9y agoI believe here that the use of "dual license" here is about open source + paid proprietary, not two open source licenses. The idea being that you can claim damages.
- quadrangle 9y agonormally is a stretch. The term applies to all forms of dual licensing, and dual free and proprietary might be more common, just maybe not in your particular experience.
- quadrangle 9y ago> I do it because I want anyone that uses that code to share their changes back with me You should be clear that the GPL has no such upstream requirement. Changes only need to be passed on downstream. It's pass-it-on, not give-back. It often works out that upstream gets access to the same channel that receives the changes, but that's not necessarily the case, strictly.
- vilhelm_s 9y agoAlthough Jacobsen v. Katzer (2008) seems to give teeth even without dual licensing. Katzer argued that the open-source conditions are "non-economic", and therefore not enforcable as a copyright infringement case, but the Court of Appeals, Federal Circuit wrote > Traditionally, copyright owners sold their copyrighted material in exchange for money. The lack of money changing hands in open source licensing should not be presumed to mean that there is no economic consideration, however. There are substantial benefits, including economic benefits, to the creation and distribution of copyrighted works under public licenses that range far beyond traditional license royalties. For example, program creators may generate market share for their programs by providing certain components free of charge. Similarly, a programmer or company may increase its national or international reputation by incubating open source projects. Improvement to a product can come rapidly and free of charge from an expert not even known to the copyright holder. The Eleventh Circuit has recognized the economic motives inherent in public licenses, even where profit is not immediate. [---] The clear language of the Artistic License creates conditions to protect the economic rights at issue in the granting of a public license. These conditions govern the rights to modify and distribute the computer programs and files included in the downloadable software package. The attribution and modification transparency requirements directly serve to drive traffic to the open source incubation page and to inform downstream users of the project, which is a significant economic goal of the copyright holder that the law will enforce. Through this controlled spread of information, the copyright holder gains creative collaborators to the open source project; by requiring that changes made by downstream users be visible to the copyright holder and others, the copyright holder learns about the uses for his software and gains others' knowledge that can be used to advance future software releases. The parties later settled, so we don't know what damages could have been awarded, but this affirms the basic principle of the GPL.
- notzorbo3 9y agoWhat Perens doesn't explain, and what I'm curious about is if the GPL is considered a contract in just this specific case, or in general. As far as I understand, a contract requires agreement from the contractor (is that the right term? Contractee?). The finding says: > Defendant used Ghostscript, did not obtain a commercial license, and represented publicly that its use of Ghostscript was licensed under the GNL GPU. These allegations sufficiently plead the existence of a contract. I read that as: Since the defendent publically aknowledged their use of the software under the GPL, they indirectly "agreed" to it, hence it's considered a contract. If a company doesn't publically state that, is it then not considered a contract, and only a license?
- vertex-four 9y agoThe issue, of course, is that if they didn't agree to it, then they're (probably) redistributing a copyrighted work without a license to do so. So it's likely expedient for a court to assume that redistribution of a GPLed work constitutes acceptance of the GPL, as the alternative makes no sense.
- notzorbo3 9y agoThe issue here is not about acceptance of the license, but whether it is just copyright infringement or also breach of contract.
- delinka 9y agoIANAL, but it makes sense to me that A) you've agreed to the GPL and thus have willingly entered a contract, or B) not agreed to the GPL and are committing copyright infringement. You can then only be in breach of contract if you're operating under A.
- notzorbo3 9y agoI'm also not a lawyer. I assumed that since they're making such a big deal about the GPL being considered a contract in this case, that in other cases it wasn't considered a contract. It feels like they're saying a breach of contract is somehow different than just violating a license / copyright law, but I'm not sure.
- Nokinside 9y agoI hope single-vendor commercial open source business model would be more common. http://dirkriehle.com/publications/2009-2/the-commercial-open-source-business-model/ http://dirkriehle.com/publications/2009-2/the-commercial-ope... GPL + Commercial dual licensing seems to be really good option for small and midsize business where ake the code and take the business is real possibility. GPL is widely known and quite clear. GPL establishes open source genealogy, not just one point in time event like BSD licenses do. Ghostscript, MySql, Qt etc. followed this path successfully. Qt is now a public company with open source product.
- vog 9y agoWhy not AGPL + Commercial? To me this sounds like an even better option, as it closes some GPL loopholes such as "hiding" modified GPL code behind a service.
- k__ 9y agoI thought they closed the loopholes with v3?
- vog 9y agoThey closed all loopholes regarding software that runs on the user's computer. For software that is used over the network (such as web applications), the GPLv3 grants the rights only to the server admins, because in the spirit of the GPLv3 these are the users of the software. In contrast, AGPLv3 states that in this case the real end users are those receiving the granted rights.
- belorn 9y agoDifferent loopholes. V3 closes the idea of pretending to give someone permission to modify and share software, but then using encryption or patents to make it impossible in practice. Like selling a car but then withholding the ignition key. AGPL closes the idea that someone just ship a thin client and have everything running on a server, which is an experience that can be almost indistinguishable from receiving a copy. Since GPL explicitly do not treat the transmission of a copy and using a service as identical, AGPL go as far as copyright allows and tries to fix that.
- tzs 9y ago> There’s been a lot of confusion about the recent Artifex v. Hancom case, in which the court found that the GPL was an enforceable contract. The author is reading too much into this. This was just a ruling on a motion by the defendant, Hancom, to dismiss under Rule 12(b)(6) of the Federal Rules of Civil Procedure, the "failure to state a claim upon which relief can be granted" rule. A 12(b)(6) motion essentially says "Let's assume for the sake of argument that every allegation of fact that the plaintiff made in their complaint is true. Under that set of facts, there is no way that a court could find that we are liable under whatever law plaintiff claims we have violated". When a court rules against such a motion, it is not saying that the alleged facts ARE true, or that when those facts are applied to the laws in question the plaintiff will win. All it is saying is that they plaintiff has alleged everything that is necessary in order for it to be possible for the plaintiff to win. So in this case all the court really found was that it is possible that GPL is an enforceable contract in the circumstances alleged by plaintiff, Artifex.
- microcolonel 9y agoRight, at best the case can provide analogy for a future case under substantially identical circumstances. It does say, though, that a court considered some provisions of the GPL, in the fashion that Artifex could be considered to have agreed, to be binding. That alone is no small thing.
- belorn 9y agoThis is true for every decision by a court except for the final judgment. A typical example would be a bail hearing, where they are not supposed to establish guilt. But like with many human system it tend to leak. Its not uncommon to hear lawyers say that the outcome of a motion will imply where the final decision will land.
- monochromatic 9y agoSometimes a motion is dispositive of the whole case (or nearly so). Failing to dismiss on 12(b)(6) isn't like that at all.
- 9y ago
- inian 9y agoHow is Linux immune to wannacry like attacks?
- deleted 9y ago[deleted]
- ryanlol 9y agoNot sure why this got downvoted. The claim the author makes sounds ridiculous at best. >My computer running the GNU and Linux software isn’t entirely virus-proof, but it’s immune to “Wannacry” and a lot of the garbage that most of you tolerate. Essentially any Linux desktop install is going to be an absolute security nightmare when compared to a fully patched windows install. While Microsoft has been pushing trustworthy computing for 15 years, on Linux desktops we only recently started to get ASLR/PIE. Wannacry wasn't even exploiting any 0days and therefore "Windows" was also immune to it from the beginning.
- vetinari 9y ago"Trustworthy" computing is not about security, but about platform control. You can still exploit a computer, whether it has TPM & accessories or not. If the Windows was immune to Wannacry, we would not hear about it in the first place. You might argue, that it was the operators who failed to update, but there was already a discussion, that due to Microsoft abusing the Windows Update in the past, many people had many good reasons to disable it.
- ryanlol 9y ago>"Trustworthy" computing is not about security, but about platform control. You can still exploit a computer, whether it has TPM & accessories or not. I'm sorry, but this is just tinfoil nonsense. Trustworthy computing has nothing to do with TPM & accessories. Stuff like this is what Trustworthy computing is about: https://www.blackhat.com/docs/us-16/materials/us-16-Weston-Windows-10-Mitigation-Improvements.pdf https://www.blackhat.com/docs/us-16/materials/us-16-Weston-W... The above PDF is also a good reference guide to mitigations that are not present on desktop linuxes. >If the Windows was immune to Wannacry, we would not hear about it in the first place. You might argue, that it was the operators who failed to update, but there was already a discussion, that due to Microsoft abusing the Windows Update in the past, many people had many good reasons to disable it. Choosing not to install security updates also leaves you vulnerable to such attacks on Linux, and they do happen. Are you seriously trying to imply that you've never had an issue with a package manager on Linux?
- unlmtd 9y agoI never signed a GPL contract.