News for hackers. Stuff that matters.
Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by thesuperbigfrog on Friday January 05, 2024 @11:20AM (#38880769)
>> Red Hat’s official stance is that downstream distros like Rocky or AlmaLinux should be basing off of CentOS Stream — that would allow all the EL distributions to contribute and use the same OS base

That stance goes contrary to the "everyone benefits" nature of free and open source software. It turns "everyone benefits" into "Red Hat / IBM profits". Why should the community contribute to Red Hat's bottom line if Red Hat refuses to contribute back to the community?

Rocky Linux's "going around Red Hat's back" is only necessary because of Red Hat's choice to not contribute back to the community.

If IBM wants to expand its AIX (https://en.wikipedia.org/wiki/IBM_AIX) business, it can do so without tainting Red Hat.

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by dralley on Friday January 05, 2024 @11:32AM (#38880942)
Your analysis seems to be ignoring all of the work required to create and maintain the CentOS Stream / RHEL distribution in the first place, which is substantial.

Prior to CentOS Stream, if you were a CentOS user or maintainer who experienced a bug, your only option was to file a bug on the RHEL bug tracker and wait for a Red Hat employee to fix it for you. It was the Android-esque "throw the code over the wall" model of open source.

Post CentOS Stream, a CentOS user or maintainer files the bug in the CentOS Stream bug tracker, can write a patch and have it reviewed by other users/maintainers/Red Hat employees tracking the issue, and then benefit from Red Hat QA'ing the fix.

So counter to your claim, I would argue that the CentOS Stream model provides more bidirectional / mutual benefits.

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by thesuperbigfrog on Friday January 05, 2024 @12:00PM (#38881370)
>> Your analysis seems to be ignoring all of the work required to create and maintain the CentOS Stream / RHEL distribution in the first place, which is substantial.

Substantial enough to effectively "close source" RHEL?

Red Hat's changes (https://www.redhat.com/en/blog/red-hats-commitment-open-sour...) effectively converted RHEL from a fully open source Linux distribution to "source available to paying customers only" proprietary product.

The changes are effectively a violation of the GPL by prohibiting customers from distributing RHEL sources through Red Hat's Terms of Service and EULAs:

https://rockylinux.org/news/keeping-open-source-open/

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by dralley on Friday January 05, 2024 @12:06PM (#38881459)
RHEL is not "effectively closed source" by any stretch of the imagination. The sources are available as CentOS Stream -- from which RHEL is built in the first place!! It is true that, in order to put together an exact copy of RHEL, you would need to do a bit of work to figure out exactly what versions RHEL uses, and specifically pick those versions out of CentOS Stream. It isn't as simple as downloading the entire tree of sources from a single git repository anymore. But that's not the same as "effectively closed source", either.
Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by orthoxerox on Friday January 05, 2024 @03:47PM (#38884710)
If you provide GPL software to your customers, you have to provide everything they need to build this exact version yourself, not point them at a repo and tell them to figure it out.
Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by dralley on Friday January 05, 2024 @04:07PM (#38884947)
Red Hat does provide all of that to RHEL customers. This is a discussion about what non-RHEL customers get.

Even non-customers are provided with all of the sources they they could use to build RHEL, given some additional effort. It's less trivial than it used to be, but not particularly difficult.

Alma takes the approach of reconstructing RHEL using these public sources, Rocky takes the approach of buying AWS VMs running RHEL for a few minutes at a time so that they can download RHEL sources as a "customer" while only paying a few dollars a month to do so.

The point is, even non-customers can rebuild RHEL using sources made publicly available by Red Hat if they so desire. It's not "effectively closed source", even to them.

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by josephcsible on Friday January 05, 2024 @04:13PM (#38885021)
Prior to CentOS Stream, couldn't you file the bug in the upstream project's bug tracker instead, and then still do all of the other stuff you said?
Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by dralley on Friday January 05, 2024 @04:20PM (#38885111)
You'd still have to wait for someone at Red Hat to backport the fix themselves. There wasn't really a way to actually participate in the engineering of CentOS itself.
Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by josephcsible on Friday January 05, 2024 @04:40PM (#38885346)
Won't you still have to wait for someone at Red Hat to move the change from Stream into RHEL?
Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by dralley on Friday January 05, 2024 @04:45PM (#38885394)
You'd have to wait on it to be QA'd before it would get into Stream officially, but once it's in Stream the process of it getting into RHEL is mostly automatic. It would just be a matter of waiting, since RHEL only does releases every 6 months whereas Stream releases constantly.

With CentOS you would have the same problem, except that there's no way to make the engineering part happen any faster than Red Hat's staffing and priorities allowed.

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by doublepg23 on Friday January 05, 2024 @11:24AM (#38880820)
Accusing Red Hat of not contributing to the wider free software community is so off-base I’m not sure how to respond.

Is there a single large FOSS project who’s git history isn’t filled with @redhat.com ?

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by thesuperbigfrog on Friday January 05, 2024 @11:32AM (#38880947)
Oh, so is it okay to share RHEL sources back with the original project communities or not?

If you share RHEL sources with the original project communities, what happens?

>> Is there a single large FOSS project who’s git history isn’t filled with @redhat.com ?

Does this give Red Hat the right to effectively "close source" the code for RHEL despite contributions from the rest of the community?

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by dralley on Friday January 05, 2024 @11:50AM (#38881203)
Yes, you can. This is something everyone gets mixed up.

RHEL is built from CentOS Stream sources. The changes Red Hat made to RHEL source distribution mostly just make it more challenging to reconstruct an entire build of RHEL from CentOS Stream - because you would have to map backwards from all of the different versions of sources available in CentOS Stream to the exact versions that a particular version of RHEL happens to use. But at the scale of any individual project, it's trivial for any upstream community to just look at the latest CentOS Stream sources for one particular package, if they want to look at which patches Red Hat is applying. There are no legal or contractual restrictions on this whatsoever.

This is setting aside the fact that most patches are backports from one upstream version to another, and bugfixes that get submitted "upstream first" to begin with, which makes the whole discussion kind of moot. The typical scenario for a net-new bugfix would be that a Red Hat employee submits the fix upstream and gets it reviewed and merged by said upstream months before it ever sees the light of day in RHEL, so upstream maintainers would never need to look at the RHEL sources in the first place.

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by heywoodlh on Friday January 05, 2024 @11:45AM (#38881126)
> Does this give Red Hat the right to effectively "close source" the code for RHEL despite contributions from the rest of the community?

Legally, yes. Not sure what the point is you're trying to make.

I'm not sure why anyone would want to use a downstream distribution of Red Hat if they don't like Red Hat's trajectory. If you don't like Red Hat's current objectives with RHEL, it should be as simple as: stop using something downstream of RHEL.

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by yjftsjthsd-h on Friday January 05, 2024 @12:04PM (#38881428)
> Legally, yes. Not sure what the point is you're trying to make.

Legally, no; unless RH is the only copyright holder, they get to follow the same rules as everybody else, and for GPL packages that means not imposing additional restrictions on redistribution of source code.

> If you don't like Red Hat's current objectives with RHEL, it should be as simple as: stop using something downstream of RHEL.

People are fine with being a downstream of RHEL. It's being upstream of RHEL that's the problem; Stream is RHEL Beta by another name.

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by dralley on Friday January 05, 2024 @12:22PM (#38881714)
>Legally, no; unless RH is the only copyright holder, they get to follow the same rules as everybody else, and for GPL packages that means not imposing additional restrictions on redistribution of source code.

And there aren't any. "RHEL Linux" isn't GPL licensed, the kernel is, and glibc is, and systemd is, etc. Individually.

The sources for all of those packages (and ones that aren't GPL licensed, for which there is not actually a legal requirement to distribute sources), individually, are available via CentOS Stream just as they ever were.

What Red Hat has stopped doing is providing a git repo containing the exact combination of package sources which collectively make up one particular version of RHEL. Instead, all of the sources are still available, but if you want to rebuild the entire distro you need to figure out which particular versions to use. And that's exactly what Alma Linux does.

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by yjftsjthsd-h on Friday January 05, 2024 @12:48PM (#38882061)
> "RHEL Linux" isn't GPL licensed, the kernel is, and glibc is, and systemd is, etc. Individually.

That is why I said "GPL packages", yes.

Okay, so if I buy RHEL, and I download the SRPM for the kernel, and I publish it - which I'm legally entitled to do, what with the kernel package being GPLv2 - is RH not going to terminate my RHEL license?

Re:June 30th, 2024, will bring the End of Life (EOL) of Cent... by dralley on Friday January 05, 2024 @01:02PM (#38882271)
Almost certainly not. I don't think that has even happened with Rocky, for whom they're not just downloading one package.