this post was submitted on 02 Apr 2024
499 points (98.1% liked)
Privacy
31942 readers
790 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
gpl prevents you from doing that fyi
gpl does not prevent the owner from changing the licence later. (Unless it is also making use of someone else's gpl components.)
For example, Qt has a free version which is under the GPL; and a paid version which is not. So if you were making software with Qt, if you were using the free version, you'd be compelled to also release your product under GPL. But you could then later switch to a paid subscription and rerelease under some other licience if you wanted to.
Actually it doesn't
doesnt it require any modified versions of the code be shared, preventing a change to a non-copyleft liscence?
Not if the copyright owner changes the license. When you are the creator you can do what you please. With that being said you can not do that if the public writes code. That's why you see CLAs (contributor license agreement)
Important to note that this only applies to future releases by the legal copyright owner. If the community doesn't like it (and they often don't), someone else can fork it from the last time it was GPL, and contributors can abandon the original codebase in favor of the GPL fork. As a result, it is extremely unwise to try to de-GPL software with a lot of contributors, as the copyright holder doesn't have a great chance at competing with a fork if contributors jump ship.
Linus Torvalds could legally pivot Linux to a proprietary license if he wanted to, but we'd probably see it replaced with a fork called "Binix" or something within a few months, and he'd be in charge of abandonware at that point.
Agreed although Linux would be really hard to relicense. You would need to get approval from every single person who every contributed
oh ok, thanks for telling me!