Carl George

do not care about contributing, do not care about getting their bugs answered. They just want to get the product for free. They're like, oh, no, I'm going to go to these other guys that give me the same thing.

do not care about contributing, do not care about getting their bugs answered. They just want to get the product for free. They're like, oh, no, I'm going to go to these other guys that give me the same thing.

The big change is that because it got actually harder on CentOS and Red Hat once the AquaHire thing happened and they were paying the CentOS maintainers because customers would come in and say, well, you're making both of these things, so why should I pay you for one and not the other? Or why should I pay you for the one when this other one's free?

The big change is that because it got actually harder on CentOS and Red Hat once the AquaHire thing happened and they were paying the CentOS maintainers because customers would come in and say, well, you're making both of these things, so why should I pay you for one and not the other? Or why should I pay you for the one when this other one's free?

And that conflation of having Red Hat sponsorship, it helped the project not fail and collapse, but it also made it harder to have those conversations, to draw that line between the product and the project. And so now the new rebuilds, like I heard one guy inside Red Hat described it as these changes are Red Hat getting out of the rebuild business.

And that conflation of having Red Hat sponsorship, it helped the project not fail and collapse, but it also made it harder to have those conversations, to draw that line between the product and the project. And so now the new rebuilds, like I heard one guy inside Red Hat described it as these changes are Red Hat getting out of the rebuild business.

Like we decided that's not where we want to spend our time. Here's the way that building an operating system works in our pipeline holistically to make a better product. And it's still really close to RHEL and you can still use it for whatever you want to, but it's not going to be trying to match RHEL identically anymore. It's getting six months ahead of RHEL on features and fixes.

Like we decided that's not where we want to spend our time. Here's the way that building an operating system works in our pipeline holistically to make a better product. And it's still really close to RHEL and you can still use it for whatever you want to, but it's not going to be trying to match RHEL identically anymore. It's getting six months ahead of RHEL on features and fixes.

But like you said, a lot of those people that are going to different alternatives now, they're in that latter group, the five plus year usage where they just want the same thing. They don't want anything to change ever. And they don't want to think about being able to contribute being a benefit.

But like you said, a lot of those people that are going to different alternatives now, they're in that latter group, the five plus year usage where they just want the same thing. They don't want anything to change ever. And they don't want to think about being able to contribute being a benefit.

They're self-supporting. They're active in the projects. They're contributing. They identify a feature that they want or something that's broken that they want to fix, a bug. and they're contributing that into CentOS Stream. They're active contributors there. They're contributing to upstream projects. I know they're heavily involved in SystemD. They participate there.

They're self-supporting. They're active in the projects. They're contributing. They identify a feature that they want or something that's broken that they want to fix, a bug. and they're contributing that into CentOS Stream. They're active contributors there. They're contributing to upstream projects. I know they're heavily involved in SystemD. They participate there.

A lot of times you'll find talks from them at conferences like Scale where they're talking about the internals of SystemD because they employ a lot of SystemD developers. They have kernel developers, ButterFS developers, all kinds of stuff. So they have a lot of that expertise in-house. Gotcha.

A lot of times you'll find talks from them at conferences like Scale where they're talking about the internals of SystemD because they employ a lot of SystemD developers. They have kernel developers, ButterFS developers, all kinds of stuff. So they have a lot of that expertise in-house. Gotcha.

So they're not really, they don't really need to leverage that support any more than just interacting with those communities already. All right. So the future stuff. Juicy future. Juicy. So the major version right now of RHEL is 9. Everyone knows that. Same for all these RHEL-likes and CentOS Stream, which is still RHEL-like. It's all major version 9.

So they're not really, they don't really need to leverage that support any more than just interacting with those communities already. All right. So the future stuff. Juicy future. Juicy. So the major version right now of RHEL is 9. Everyone knows that. Same for all these RHEL-likes and CentOS Stream, which is still RHEL-like. It's all major version 9.

Everyone can count and knows that the next number after that is 10. Is it 10? Yes. Was it eight, nine? I'm making this joke. Go ahead. It's a little silly because there was actually a time before I got hired where there's some weird marketing thing around it where they were telling engineers that they couldn't say that the next version was eight. And I don't know where it originated or why.

Everyone can count and knows that the next number after that is 10. Is it 10? Yes. Was it eight, nine? I'm making this joke. Go ahead. It's a little silly because there was actually a time before I got hired where there's some weird marketing thing around it where they were telling engineers that they couldn't say that the next version was eight. And I don't know where it originated or why.

Oh, wow. But then, like, some real marketing folks showed up at the, I think it was the Fedora Flock Conference, with stickers with the rocket ship and the number 8 on it. And after, you know, all the messaging to the engineers was like, don't say the number 8. Just say, oh, whatever, you know, whatever the next version is. And so the engineers were all mad.

Oh, wow. But then, like, some real marketing folks showed up at the, I think it was the Fedora Flock Conference, with stickers with the rocket ship and the number 8 on it. And after, you know, all the messaging to the engineers was like, don't say the number 8. Just say, oh, whatever, you know, whatever the next version is. And so the engineers were all mad.