3 ms·
Open source is hosed because a bare license is revocable at any time by the licensor. If your business depends on an NPM library written by some schlub on the i
by bitwize 6y ago
Open source is hosed because a bare license is revocable at any time by the licensor. If your business depends on an NPM library written by some schlub on the internet, and that schlub decides they don't like you, then they can revoke your license and sue for copyright infringement, not to mention preventing you from operating legally as long as you depend on their software.
It gets even worse if the "schlub" is an entity like Google -- and you appear on their radar and they decide you're a competitor.
- CameronNemo 6y agoI have never heard of this phenomenon actually working. Some Linux contributors threatened it after the CoC was instituted, but nothing came of it. Do you have an example of somebody actually revoking copyright and successfully suing or settling?
- bitwize 6y agoMore like "one guy engaged in saber rattling and nobody listened", and he didn't even make any substantive Linux contributions. This same guy actually did try revoking the license to his open source slot machine game from the GeekFeminism contributors, and the GF people were like "okay, yeah, sure, whatever, we promise not to touch your shitty game again". So this remains untested in court. But if you actually look at the relevant bits of contract law, you'll see... he actually has stopped-clock syndrome on this, and it really has dire consequences for how we do open source. At least in the USA, and admittedly, different views on copyrights and licensing prevail outside the USA, where much of the work on Linux is done.
- frenchy 6y ago> Open source is hosed because a bare license is revocable at any time by the licensor. I haven't the slightest clue what you're taking about. You can change your license on future versions, but you can't retroactively change the conditions of an offer that's already been accepted. If you're talking about the ability to delete published packages from NPM, that's entirely unrelated to licensing.
- CameronNemo 6y agoThis is what is being referred to. I have never seen an actual case of it occurring, only threats. https://lulz.com/linux-devs-threaten-killswitch-coc-controversy-1252/ https://lulz.com/linux-devs-threaten-killswitch-coc-controve...
- bitwize 6y agoMikeeUSA may be an odious little prick, but he is 100% correct in his legal analysis, and cites actual legal experts to support his case.
- bitwize 6y ago> I haven't the slightest clue what you're taking about. You can change your license on future versions, but you can't retroactively change the conditions of an offer that's already been accepted. Yes, you can. In order to be a legally binding contract, three things are required: an offer, acceptance, and consideration. Consideration is the value gained by entrants into a contract. In short, if you did not pay to license some piece of open source software, there is no consideration for the author of that software. Hence, the license attached to the software is NOT a contract binding on the author. It is a bare license -- simply the terms under which you are permitted to use the author's IP -- and the author is legally entitled to revoke it at any time. You may not like it, and it has unfortunate implications for open source, but that's how contract law in common law jurisdictions like the USA works.
- detaro 6y agoSince you seem to know a bit about this: When that question came up I've frequently seen references to https://www.law.cornell.edu/uscode/text/17/203 https://www.law.cornell.edu/uscode/text/17/203, which puts multi-decade limits on that - why would that not apply?