Until someone gives legal notice to IBM lawyers forcing Red Hat source code to be released pulicly, all of this debating over it means jack nothing.
If nobody takes IBM to court, the matter is settled and all developers must accept Red Hat’s choices.
If they dismiss the online talk, ignore all criticisms, and nobody pays for a lawsuit, the case is done and finished.
I’m not trying skip over your points, as I said from my first first, everybody can talk all they want, who has the power of persuasion or legal force to change IBM’s decision?
I may be wrong, but I believe only the Linux Foundation is a position to call IBM CTO, President, whoever, and say “We heard about the changes to with holding Red Hat’s source code, you will not be doing that, it shall remain public. If you want to discuss this further, please send your most expensive lawyers to our offices and we will explain in detail why you won’t be doing that.”
Until someone gives legal notice to IBM lawyers forcing Red Hat source code to be released pulicly, all of this debating over it means jack nothing.
That’s a misunderstanding. Even according to the GPL Red Hat doesn’t have to release their source publicly (though it would have been nice if they had kept doing that), they only have to give it to those who they give the binaries to (i.e. RHEL customers). The big issue is that they are trying to restrict their users from redistributing the sources that they are legally entitled to, which is a freedom they should have according to the GPL.
Section 6 of the GPL v2.0 says:
Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients’ exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.
If nobody takes IBM to court, the matter is settled and all developers must accept Red Hat’s choices.
I believe it’s the other way around. IBM needs to take someone to court over this to enforce their rules. For example, a customer who re-distributes RHEL sources or the Rocky Linux developers if (according to IBM) they “illegitimately” acquire RHEL sources.
I may be wrong, but I believe only the Linux Foundation is a position to call IBM CTO, President, whoever
You would be wrong indeed. Technically, anyone who holds a copyright on any part of a GPL licensed program that is included in RHEL could sue IBM for GPL violations. So even a developer of something silly like for example, cowsay, could do this.
The likely retaliation RH/IBM would take is simply banning the account, not starting a lawsuit immediately. However, rights holders may attempt sue before or after such an event, but likely after.
RH thinks they have the right to distribute code in this manner, and they can keep doing so until challenged in court. You can do actions in general without asking the court every time, I think the same applies here as well.
I personally think it is a violation in a strict sense, but at the same time I don’t think it really matters too much realistically. Stream is upstream RHEL, and they are very similar, and at some points in time, should be identical. It’s also not clear what you get exactly by suing RH/IBM. The likely case is that they settle or rule to have that section removed from the ToS.
Until someone gives legal notice to IBM lawyers forcing Red Hat source code to be released pulicly, all of this debating over it means jack nothing.
If nobody takes IBM to court, the matter is settled and all developers must accept Red Hat’s choices.
If they dismiss the online talk, ignore all criticisms, and nobody pays for a lawsuit, the case is done and finished.
I’m not trying skip over your points, as I said from my first first, everybody can talk all they want, who has the power of persuasion or legal force to change IBM’s decision?
I may be wrong, but I believe only the Linux Foundation is a position to call IBM CTO, President, whoever, and say “We heard about the changes to with holding Red Hat’s source code, you will not be doing that, it shall remain public. If you want to discuss this further, please send your most expensive lawyers to our offices and we will explain in detail why you won’t be doing that.”
That’s a misunderstanding. Even according to the GPL Red Hat doesn’t have to release their source publicly (though it would have been nice if they had kept doing that), they only have to give it to those who they give the binaries to (i.e. RHEL customers). The big issue is that they are trying to restrict their users from redistributing the sources that they are legally entitled to, which is a freedom they should have according to the GPL.
Section 6 of the GPL v2.0 says:
I believe it’s the other way around. IBM needs to take someone to court over this to enforce their rules. For example, a customer who re-distributes RHEL sources or the Rocky Linux developers if (according to IBM) they “illegitimately” acquire RHEL sources.
You would be wrong indeed. Technically, anyone who holds a copyright on any part of a GPL licensed program that is included in RHEL could sue IBM for GPL violations. So even a developer of something silly like for example, cowsay, could do this.
The likely retaliation RH/IBM would take is simply banning the account, not starting a lawsuit immediately. However, rights holders may attempt sue before or after such an event, but likely after.
RH thinks they have the right to distribute code in this manner, and they can keep doing so until challenged in court. You can do actions in general without asking the court every time, I think the same applies here as well.
I personally think it is a violation in a strict sense, but at the same time I don’t think it really matters too much realistically. Stream is upstream RHEL, and they are very similar, and at some points in time, should be identical. It’s also not clear what you get exactly by suing RH/IBM. The likely case is that they settle or rule to have that section removed from the ToS.