News for hackers. Stuff that matters.
Re:LLVM relicensing update and call for help by WastingMyTime89 on Sunday November 21, 2021 @09:21AM (#29296350)
Not being able to relicense code provided by other people without their agreement is definitely a feature of any license.

Let’s not kid ourself: the main reason companies don’t like the GPL is because they don’t want to share the code they actually use in their products. Making that impossible is an intended consequence of the license not some unforeseen flaw. If you are fine with companies profiteering from your work then choosing the MIT or BSD license definitely make sense.

The whole discussion really is about commercial interest in the end.

Re:LLVM relicensing update and call for help by the_mitsuhiko on Sunday November 21, 2021 @10:45AM (#29297013)
The biggest risk of the GPL is in fact not companies but to you as a creator. If you plan on commercializing your work in any capacity, accepting contributions under the GPL will be the end of that. Given the murky laws around copyright reassignment getting contributions in under a more liberal license so you retain extra rights yourself is tricky.

There are many projects which learned after a few years that their choice of license backfired on them.

Re:LLVM relicensing update and call for help by WastingMyTime89 on Sunday November 21, 2021 @11:52AM (#29297678)
> The biggest risk of the GPL is in fact not companies but to you as a creator. If you plan on commercializing your work in any capacity, accepting contributions under the GPL will be the end of that.

If you accept contributions, that’s not your work anymore. That’s your work and your contributors work. You are still perfectly free of removing said work and commercialise your own. You just can’t profite from the work of others without asking them. That’s a feature of the license not a risk.

> Given the murky laws around copyright reassignment getting contributions in under a more liberal license so you retain extra rights yourself is tricky.

You are misrepresenting the situation once again. It is not about retaining your own right. The whole issue is on the work of others.

Re:LLVM relicensing update and call for help by the_mitsuhiko on Sunday November 21, 2021 @01:26PM (#29298457)
Something does not stop being my work when it hat contributions from others but generally that’s besides the point. The main issue of GPL comes from the risk to the original creator itself. Others not using the software is less the concern.
Re:LLVM relicensing update and call for help by WastingMyTime89 on Monday November 22, 2021 @04:20AM (#29304461)
> Something does not stop being my work when it hat contributions from others

Of course it does both from a legal and moral point of view. Composite work is the product of their authors plural. You are perfectly free to strip it from the contributions of others and relicense your actual work.

> The main issue of GPL comes from the risk to the original creator itself

You keep coming back to that but still have to explain what they are. Yes, the GPL prevents you from relicensing the work of your contributors. That's not a risk to the original creator itself.

Re:LLVM relicensing update and call for help by sangnoir on Sunday November 21, 2021 @11:42PM (#29302833)
> The main issue of GPL comes from the risk to the original creator itself

The risk of abiding by the license? The GPL ensures user have access to source code provided under the license, so I'm assuming by "commercializing" you mean hiding away source code that used to be public? The calculus is simple: if you want to make money by doing an open-source bait-and-switch, do not license your code under GPL.

Re:LLVM relicensing update and call for help by the_mitsuhiko on Monday November 22, 2021 @02:28AM (#29303784)
Commercializing can happen in many ways. GPL code in itself can’t even be published on the app store without violating the license. If you are not the complete copyright holder you can run into issues very quickly.
Re:LLVM relicensing update and call for help by sangnoir on Friday November 26, 2021 @12:12PM (#29352003)
> GPL code in itself can’t even be published on the app store without violating the license

Did you mean without violating the app store EULA? Because the GPL places no restrictions on how generated binaries are distrubuted, only that the source be transmitted to any user upon request.

Re:LLVM relicensing update and call for help by pests on Monday November 22, 2021 @12:41AM (#29303174)
If a single line was written and contributed without copyright assignment, than line is theirs. The project can be yours, but you no longer own 100% rights to it.
Re:LLVM relicensing update and call for help by the_mitsuhiko on Monday November 22, 2021 @02:25AM (#29303761)
Precisely. Which is why releasing code under the GPL requires a lot of up front consideration.