The concern is that Red Hat terminates your account if you redistribute the source to another party. This feels like an additional restriction placed on the source code, which if it is, would indeed violate the GPL.
Serious concern and asshole move? Yes. Gpl violation? Not sure. You could argue you are not restricted to do whatever you want with the code you receive with a subscription. But if you share the code, they don’t want you as a customer anymore and won’t give you new code. I don’t know if the GPL allows that.
Terminating a support contract, in itself, is not a GPL violation. The restrictions only affects the ability to receive future updates.
Edit: Red Hat indeed claims that no GPL violation is happening, yet they inform their customers that sharing updates leads to contract termination, which clearly breaches the GPL at least in spirit: https://sfconservancy.org/blog/2023/jun/23/rhel-gpl-analysis/
Context is important. It’s possible that the software is distributed without any warning like that and that the termination of the support contract is done without citing the redistribution of previous versions as a reason.
OTOH if the customers could prove that there’s widespread knowledge of the retaliatory termination that could be equivalent to a (non-written) restriction that is indeed incompatible with the GPL
“the way we understand it today, Red Hat’s user interface agreements indicate that re-publishing sources acquired through the customer portal would be a violation of those agreements.”
The warning is in the agreement every customer (and free developer account) signs to obtain access. They also mention they could sue you, although I think it is unrealistic they would do so just for redistribution.
I haven’t seen this in person so I can only speculate, but I bet they’ll only provide the sources as a tarball or something instead of a git repo, which will make it a PITA for anyone do actually do anything useful with it. I mean, you could potentially still build a full distro from it, but you wouldn’t be able to feasibly maintain it without the ability to do a sync and merge from upstream. So this way, Red Hat achieves their goal of being able to kill any spinoff distro, whilst still remaining compliant with the GPL.
It’s not a “they will.” Red Hat customers are able to download source rpms from the repository or the site, this has been the case for a very long time. It is possible to clone / sync the repository, this is how airgapped networks can still host their own.
I don’t suppose they’re modifying much of the GPL’d kernel necessarily. That’s the part protected by GPL.
Their own actual distro is not exactly a modification of GPL software. And if they modify GPL software, they wouldn’t have issues providing source code to that.
How is this supposed to work with GPL ? Because anyone owning a copy is free to redistribute sources
The plan is to give the source Code to paying customers. This is gpl-compliant.
The concern is that Red Hat terminates your account if you redistribute the source to another party. This feels like an additional restriction placed on the source code, which if it is, would indeed violate the GPL.
Now THIS is a GPL-violation or at least a serious concern and asshole move.
Serious concern and asshole move? Yes. Gpl violation? Not sure. You could argue you are not restricted to do whatever you want with the code you receive with a subscription. But if you share the code, they don’t want you as a customer anymore and won’t give you new code. I don’t know if the GPL allows that.
This clearly goes against the intention of the GPL. Maybe not illegal.
That I agree with. Maybe this will cause the FSF to create a 4th version.
Terminating a support contract, in itself, is not a GPL violation. The restrictions only affects the ability to receive future updates.
Edit: Red Hat indeed claims that no GPL violation is happening, yet they inform their customers that sharing updates leads to contract termination, which clearly breaches the GPL at least in spirit: https://sfconservancy.org/blog/2023/jun/23/rhel-gpl-analysis/
I think it depends on whether it’s considered an additional restriction on the recipient’s right to redistribute the software.
Saying, “you can redistribute the software but you will face _____ penalty” seems like a gray area to me.
Context is important. It’s possible that the software is distributed without any warning like that and that the termination of the support contract is done without citing the redistribution of previous versions as a reason. OTOH if the customers could prove that there’s widespread knowledge of the retaliatory termination that could be equivalent to a (non-written) restriction that is indeed incompatible with the GPL
Yes more details would be good.
According to Alma Linux
The warning is in the agreement every customer (and free developer account) signs to obtain access. They also mention they could sue you, although I think it is unrealistic they would do so just for redistribution.
Yeah, it’s a big myth that GPL prevents corporate profiteering.
I haven’t seen this in person so I can only speculate, but I bet they’ll only provide the sources as a tarball or something instead of a git repo, which will make it a PITA for anyone do actually do anything useful with it. I mean, you could potentially still build a full distro from it, but you wouldn’t be able to feasibly maintain it without the ability to do a sync and merge from upstream. So this way, Red Hat achieves their goal of being able to kill any spinoff distro, whilst still remaining compliant with the GPL.
Additionally, they have to release sources for the projects but not necessarily for things like the spec files or the rpms.
Here’s the source for the kernel . . . .
Thanks I can get that from kernel.org
It’s the part that’s not GPL that’s the value add here.
Build scripts are absolutely required by the GPL
It’s not a “they will.” Red Hat customers are able to download source rpms from the repository or the site, this has been the case for a very long time. It is possible to clone / sync the repository, this is how airgapped networks can still host their own.
I don’t suppose they’re modifying much of the GPL’d kernel necessarily. That’s the part protected by GPL.
Their own actual distro is not exactly a modification of GPL software. And if they modify GPL software, they wouldn’t have issues providing source code to that.
exactly, why isn’t this a gpl violation