- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or # to comment.
Idk, I’d say it brought us together (against RedHat) pretty quickly.
Yes, and made many of us realise just how important it is to use and support Community distros and projects, and ditch the Corps.
No more Ubuntu, no more Fedora (Red Hat in disguise). Use Debian and any other community distro.
I’ve settled on Linux Mint Debian Edition, personally.
As a former RedHat advocate it sucks honestly, I have to find companies like Rancher and Suse that off truly FOSS products now. Like I want opensource devs to get paid if they are being depended on, but the RedHat paywall makes avoiding the vendor lock or trying to be cost flexible a legal land mine. They also offer more and more proprietary rebrands of FOSS projects that I fear will get EEEd as well.
How can they use GPL’ed code and then close it? I thought this was specifically forbidden?
Eh. Not sure why people would go with red hat over debian these days.
Thought the GPL theoretically forbade this. No? Licensing is not a strong suit of mine…
The code is available as git, you just don’t have access to src.rpm.
Not what they did on the surface (limiting source to only customers). That’s allowed by the GPL. But they went beyond that which imo makes them non-compliant.
-
RH will cancel your access/agreement if you share the GPL’d source with others. That’s directly forbidden by section 6 of the GPLv2. RH is free to cancel your agreement when they want, but not because you exercised your rights under the GPL.
-
Once your agreement is canceled, you also lose access to the matching source for other GPL’d packages installed on your system. RH could offer other methods to be in compliance, but as far as I know, they have not.
-
