[CentOS] Current RHEL fragmentation landscape

Tue Jul 25 00:24:12 UTC 2023
Gordon Messmer <gordon.messmer at gmail.com>

On 2023-07-24 13:47, frank saporito wrote:
> Let me know if you disagree with any of these statements:
>
> 1. Red Hat is no longer posting source code to git.centos.org.


Correct.  Red Hat used to publish a de-branded subset of RHEL source 
code there, and they've discontinued that process.  The current code for 
RHEL is now published to the CentOS Stream repos.


> 2. Red Hat will release source code to partners and customers via the 
> Red Hat Customer Portal. (ref: Red Hat announcement)


Also correct.  This is the only channel through which Red Hat ever 
posted complete code for RHEL.  It hasn't been changed.


> 3. Per Red Hat EULA, customers can not freely distribute the source 
> code. (ref: Red Hat EULA)


It's a little more complex than that, but probably close enough for now.


> 4. Red Hat's policy decision has made it difficult (maybe impossible) 
> for "clone" distributions to continue existing. (ref: Google "red hat 
> source code")


This is the point at which I think we start to wade out into the 
territory of myth.  It has never been possible to create a clone of RHEL 
from the code that Red Hat published.  First, because Red Hat doesn't 
publish the information that would be required to create reproducible 
builds.  But more importantly, because RHEL has one life cycle per minor 
release, and distributions built from the old git.centos.org 
repositories had *at best* one life cycle per major release.

CentOS Stream also has one life cycle per major release, and conforms to 
the interface compatibility guide for the matching RHEL major release.

Distributions derived from CentOS Stream can have either lifecycles per 
minor release *or* one lifecycle per major release.  Unlike the old 
source publication process, they can have continuous or overlapping life 
cycles.

Yes, this involves more steps than the old process.  The next natural 
question is whether the additional work is justified by the improvement 
in the outcome.  And from my point of view, that is a very easy "yes".

I understand that it's confusing, but CentOS was never a substitute for 
RHEL, and never provided the benefits of RHEL's model.  It is not the 
"free RHEL" that many users tend to think it was:

https://fosstodon.org/@gordonmessmer/110648143030974242

https://www.youtube.com/watch?v=tf_EkU3x2G0

... and conversely, CentOS Stream is a much better stable LTS for 
self-supported systems than you might believe:

https://medium.com/@gordon.messmer/in-favor-of-centos-stream-e5a8a43bdcf8


> 5. Red Hat's policy change contradicts the GPL's spirit.


As you acknowledge, that's a subjective question.  I would say "no."

I think the entire history of the free-as-in-speech vs free-as-in-beer 
clarification is proof that we wanted to ensure the right to improve 
software if you didn't like its limitations, not the right to give away 
software if you didn't like its price.

But I also think it's important to acknowledge that the thing that 
rebuilders are asking for (the RPM source repositories) aren't GPL 
licensed, they're MIT licensed, which makes the question something of a 
non-sequitur.