Good for Alma, I say. Why base your business model on RedHat not finding a way to kill it? RedHat is a de facto enterprise standard in part because of the existence of free source-rebuild distributions allowing for small FOSS developers to ensure compatibility. They said so themselves, they want users to either switch to another distribution or pay for RedHat. So let’s give them what they want and abandon RHEL compatibility.
I don’t think that “let’s all abandon RHEL so it becomes irrelevant” is the appropriate response here. It’s a matter of freedom and principles. If RHEL exists, a compatible, free and unencumbered alternative should be allowed to exist as well.
RedHat thinks they shouldn’t exist, and is trying to maneuver within legal limits to ensure they don’t exist. It’s not that I agree with RedHat that the compatible clones shouldn’t exist. It’s that I think RedHat’s actions are duplicitous enough that we should no longer see RHEL compatibility as a goal to care about. Much the same way Google has taken actions to distance itself from a dependence on Java after Oracle went all APIs-are-patentable rampage. Why engage with an entity who has a stated goal of ending your existence?
Also, Alma doesn’t have a business model in the same way that Debian doesn’t have a business model. The Alma Linux OS Foundation is a non-profit organization.
I knew there was a foundation behind Alma but hadn’t looked into them too much, as I was already thinking of continuing to target RHEL compatibility may have poor business continuity after they killed CentOS as a free RHEL clone.
That depends on which “we” you talk about. Personally, yes, I have moved everything that I had away from RHEL-derivatives towards Debian after the CentOS debacle 2 years ago, and I would recommend anyone else to do the same.
So we’re in “violent” agreement.
it’s also a matter of principle: “we”, as in the community as a whole, can’t let this stand.
Right. We just have a difference of opinion on how to stand against RedHat’s actions here.
Rocky has announced their plan to continue as a 1:1 source rebuild. They’re looking at using sources from RedHat’s Universal Base Image Docker images, and also using cloud instances with consumption based pricing. With the latter option you spin up an instance on AWS/Azure/DigitalOcean/etc and it has a license for that instance, so you get the sources for the package versions on that instance. But since the license was temporary, then there’s nothing for RHEL to terminate when you redistribute the sources.
RedHat says they don’t want clones of RHEL. I say give it to them, lets have a landscape where they’re no longer the de facto standard because there are no other distributions targeting RHEL compatibility.
deleted by creator
Good for Alma, I say. Why base your business model on RedHat not finding a way to kill it? RedHat is a de facto enterprise standard in part because of the existence of free source-rebuild distributions allowing for small FOSS developers to ensure compatibility. They said so themselves, they want users to either switch to another distribution or pay for RedHat. So let’s give them what they want and abandon RHEL compatibility.
Removed by mod
RedHat thinks they shouldn’t exist, and is trying to maneuver within legal limits to ensure they don’t exist. It’s not that I agree with RedHat that the compatible clones shouldn’t exist. It’s that I think RedHat’s actions are duplicitous enough that we should no longer see RHEL compatibility as a goal to care about. Much the same way Google has taken actions to distance itself from a dependence on Java after Oracle went all APIs-are-patentable rampage. Why engage with an entity who has a stated goal of ending your existence?
I knew there was a foundation behind Alma but hadn’t looked into them too much, as I was already thinking of continuing to target RHEL compatibility may have poor business continuity after they killed CentOS as a free RHEL clone.
Removed by mod
So we’re in “violent” agreement.
Right. We just have a difference of opinion on how to stand against RedHat’s actions here.
Won’t Rocky have the same issue as Alma? RedHat has made RHEL closed source, so how can they maintain compatibility?
I suspect Rocky and other source rebuilds just haven’t made the announcement yet. Alma was merely the first to make an official statement.
Rocky has announced their plan to continue as a 1:1 source rebuild. They’re looking at using sources from RedHat’s Universal Base Image Docker images, and also using cloud instances with consumption based pricing. With the latter option you spin up an instance on AWS/Azure/DigitalOcean/etc and it has a license for that instance, so you get the sources for the package versions on that instance. But since the license was temporary, then there’s nothing for RHEL to terminate when you redistribute the sources.
RedHat says they don’t want clones of RHEL. I say give it to them, lets have a landscape where they’re no longer the de facto standard because there are no other distributions targeting RHEL compatibility.
You’ve said the words, corpo-apologists will start haunting you now, good luck fending them off.