4 ms·
http://llvm.org/docs/DeveloperPolicy.html#copyright http://llvm.org/docs/DeveloperPolicy.html#copyright: "The LLVM project does not require copyright assignmen
by Someone 10y ago
http://llvm.org/docs/DeveloperPolicy.html#copyright http://llvm.org/docs/DeveloperPolicy.html#copyright:
"The LLVM project does not require copyright assignments, which means that the copyright for the code in the project is held by its respective contributors who have each agreed to release their contributed code under the terms of the LLVM License.
An implication of this is that the LLVM license is unlikely to ever change: changing it would require tracking down all the contributors to LLVM and getting them to agree that a license change is acceptable for their contribution. Since there are no plans to change the license, this is not a cause for concern.
As a contributor to the project, this means that you (or your company) retain ownership of the code you contribute, that it cannot be used in a way that contradicts the license (which is a liberal BSD-style license), and that the license for your contributions won’t change without your approval in the future."
OOPS.
- JoshTriplett 10y agoThe LLVM license (the UofI/NCSA license) is permissive, and thus compatible with just about everything, including the Apache 2.0 license. All the existing code can stay under the old license unless someone agrees to the new one. New contributions can go under the new license. The effective license of the codebase will become Apache 2.0, with some pieces still available under the previous permissive license.
- notaplumber 10y agoThis is considered a dick move for a project to make, often this means any non-trivial changes to existing code will be under the more restrictive licence, with no backward compatibility, preventing such changes from being incorporated by the original authors or anyone perusing a fork of the originally permissive codebase. A common example of this kind of behaviour is GPL proponents forking BSD or other similiarly licensed software, and exclusively wrapping their contributions to it under the GPLv3.
- JoshTriplett 10y agoA license change certainly shouldn't happen lightly, or without consulting the community. In this case, it looks like an extensively considered decision with substantial community feedback. And patent lawsuits hurt, so as reasons to change licenses go, that seems like a pretty good one.
- petertodd 10y agoWhy is this a dick move? It only applies to further work done on the project. By licensing your work under a BSD/MIT/etc. style license you explicitly gave anyone permission to use the work in nearly any way they wanted, including as part of a Apache, GPL3, or even completely proprietary closed-source project. If everyone else on a project decides to use a different license than you picked for their future hard work, that's their choice, not yours.
- notaplumber 10y agoI said it was a dick move, not an invalid one. The person is choosing to licence their contributions with an arbitrary set of additional restrictions.
- icebraining 10y agoAnd like any other choice, it's not inherently free from criticism.
- cyphar 10y ago> A common example of this kind of behaviour is GPL proponents forking BSD or other similiarly licensed software, and exclusively wrapping their contributions to it under the GPLv3. A much more common example is a proprietary software vendor taking a lax licensed project and creating a proprietary fork of it. Of course, BSD proponents don't mention the far more common case (because it wouldn't help the narrative that GPL proponents only spend their time relicensing code). Why you don't have a problem with proprietary forks but do have a problem with copyleft forks is beyond me. Especially since sometimes copyleft forks are created because the developers made so many changes that it stands in its own right as a separate project (and the developers feel that user freedom trumps upstreamability).
- johncolanduoni 10y agoThe whole point of the switch to Apache 2.0 was the patent grant. The old code will not be effectively under the Apache 2.0 license as far as this clause is concerned because the patent grant is a restriction on the copyright holder, not the user. You can't just take the fact that the authors of some parts of the code agreed not to sue you for patents they implemented in their respective contributions and then force everybody else not to sue you for their own patents.
- JoshTriplett 10y agoI'm not suggesting that it's perfect. I'm just suggesting that from a legal point of view, the current license grants enough permissions that they don't have to have unanimous agreement from every copyright holder; the scenario painted in the linked email couldn't happen as written. (They may still want unanimous agreement, either to have more code under the new license or to confirm community consensus.)
- DannyBee 10y agoNothing this says is wrong. Nobody is changing the license without approval. Random openbsd developers who don't work on the project opining otherwise is just random internet kibitzing