By analogy, it sounds like I give you the right to walk across a line, but I also have the right to shoot anyone that crosses the line. This has the net effect that you effectively are not allowed to cross the line.
You have the GPL rights for everything I've given you. I don't have to continue to convey the rights to new things to you if I don't like how you use them.
If Red Hat were selling GPL'ed software for navigation systems to a supplier in Country A and it turned out that they were re-distributing that software to Country B to bomb Country C, nobody would blink if Red Hat refused to stop doing business with that supplier. The imaginary obligations that people have invented around the GPL wouldn't allow Red Hat to discontinue that relationship.
My read is that Red Hat is probably not in compliance, although the second piece of contract law is recourse and damages. It's not clear it's worth anyone's time to prove Red Hat is not in compliance.
Note that there are hundreds of jurisdictions in the world. Red Hat is probably in compliance in most statutory law jurisdictions, at the edge in common law ones, and I can't speak for others.
That's an interesting line to walk. GPL is global, and Red Hat distributes software developed in hundreds of jurisdictions. Any of those software authors could sue in local courts. Most would lose. Some would win.
Let's be honest here: Red Hat is still distributing the software widely, but it's making it hard to make exact Xeroxes of RHEL. That's a business problem, not a software freedom problem. CentOS Stream is, at least in my opinion, from a software freedom perspective just as good as RHEL.
You can use it, study it, change it, and redistribute it. AFAIK everything in RHEL makes it into Stream, albeit out of order and hard to re-assemble as an exact copy. But it's not like Red Hat is adding great features to RHEL that it denies to users of Stream.
Compare that to the Open Core folks who are trying to gang up on Red Hat now. There's the core version that has most of the functionality, and then the enterprise features are held back under non-free conditions. You have no recourse if you're using an open core product and they get bought up and the software is discontinued. You can't exercise the four freedoms to hire someone to maintain it for you or DIY it if you don't have the code.
But someday when Red Hat stops making RHEL you can still exercise the four freedoms and ask somebody else to do it for you or DIY it. To me, that's the spirit of the GPL - not that I'm entitled to undermine somebody's business by making exact Xerox copies of their software indefinitely.
It doesn't. And this "loophole" is old.
In days of yore, GPL "compliance" could be "Fine, here's a magtape of the source."--with no build instructions.
This is effectively what RedHat just did.
Andy, you know, I'm kind of sympathetic. If you want "certified" Linux, then you should have to pay the company that went through the grief to go get the certifications.
You're allowed to use the service/software but not allowed to take away new business clients from us by re-sharing the source yourself.
That business is based on violating a license.
This is a judgement that you personally made, without explanation. The person who you replied to thought that it was a bad analogy, and explained themselves.
Make whatever judgement you like about how good the analogy was. Starting your answer with "no" might be appropriate if someone says "Fortran is a lisp" or "do you think cars can love", but it's not a cool thing to say if someone just states an opinion, regardless of whether or not you liked it.
It shouldn't hold up on court and hopefully it won't.
if some users are given access to future products based on good behavior, that doesn't mean anything legally
My imagination has no difficulty with that at all. US courts have a great deal of respect for legal contracts. Unless you can identify a conflict between subscription terms and GPL terms the former probably will survive a court challenge.