75
Canonical changes the license of LXD to AGPL
(discourse.ubuntu.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Dec 2023
75 points (100.0% liked)
Linux
48335 readers
1111 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
They would have used a license like SSPL or the newer BSL for that. AGPL keeps it open. They got that going for them and about nothing else.
No, the copyright owner can sell proprietary versions however they like. Outside contributions are required to sign Canonical's CLA. Read https://github.com/canonical/lxd/blob/main/CONTRIBUTING.md#license-and-copyright before making claims.
I don’t understand how AGPL allows Canonical to make and sell proprietary copies of this software without violating their license. That’s the only way your scenario could happen. If you’re aware of a situation where a company can do this, I’d love to learn.
The FSF made an FAQ page for a reason: https://www.gnu.org/licenses/gpl-faq.html#ReleaseUnderGPLAndNF
"To release a nonfree program is always ethically tainted, but legally there is no obstacle to your doing this. If you are the copyright holder for the code, you can release it under various different non-exclusive licenses at various times. [...] the GPL is a license from the developer for others to use, distribute and change the program. The developer itself is not bound by it, so no matter what the developer does, this is not a “violation” of the GPL."
Canonical read the FAQ, many people here didn't.
Wow! I learned something. To return the favor, life would be better for you if you were less rude in the way you convey information.
People making unsubstantiated claims are the rude ones, not the ones making factually correct statements without fluff.