For some definition of community.
Adoption by many large organizations / businesses was also quite fast. And may have even caused us some trouble, I suspect the attention garnered by NASA's use of Rocky Linux had something to do with instigating Red Hat's recent antics.
Fascinating. No wonder why Red Hat got a little irritated.
And that I think I am finally understanding the differences between Alma and Rocky.
And what exactly do you mean by "builders' community", do you actually mean "Red Hat"?
By "not participate in" do you mean "not pay your employer"? Which we do, actually. Just wired a good chunk of money to Red Hat the other day, ostensibly earmarked for supporting the Fedora project.
> ostensibly earmarked for supporting the Fedora project.
Thanks for that. I never said you don't support the rpm-/Fedora-based ecosystem as a whole, and I appreciate that you also do so monetarily.
> I never said you don't support the rpm-/Fedora-based ecosystem as a whole,
Er. Really?
Maybe this dichotomy prompted the whole "hackers and hobbyists" imagined threat.
In the case of EL, Fedora and CentOS Stream are communities that office both users and builders, but the two groups congregate in different places. For example EPEL is targeted at the user community but it is outside the focus of the builder community. ELN is of interest to builders but it is outside the focus of the user community.
All users can choose to contribute (with bug reports, code, whatever) at either the upstream or the distro level; or they can just be users. Builders are a (very small) subset of the people who consume a distro, and like all users they can choose how much to participate in the community and whether to be contributors or not.
But that ship sailed, the good of the downstream users' contributions are not enough to cancel out the negative net value of the builders' bad behavior.
However: unfortunately part of what you said is true. Red Hat apparently took this decision because of some new facts that caused the negative from the "rebuilders" to increase, and the decision had the potential of hurting the users of the rebuilds.
Fortunately it's clear now that there are multiple ways for the downstreams to adapt[1]. Users will be able to keep their distros and—if they wish—contribute in a number of ways to the community. And builders and Red Hat will be able to collaborate in a shared place which is ELN for major released and Stream for minor releases. In a sense this removes excuses from Red Hat and should make everyone feel safer.
[1] you could say despite Red Hat's change, and I accept that. But it's also thanks to Red Hat going overall beyond the requirements of the open source licenses, with things such as Stream and the UBI source container.
Rocky Linux, as it is, will always be 1:1 with RHEL. We are dedicated to providing 1:1 "bug for bug" Rocky Linux, for both 8 and 9, for the full duration of their life cycles. Broken promises from CentOS are the reason we started Rocky Linux in the first place, we're not going back on anything we've already committed to.
I believe we (Rocky Linux) were pretty specific about how we're getting source in the announcement at <https://rockylinux.org/news/keeping-open-source-open/>. SRPMs from UBIs, cloud instances, etc. The only intentional omission are the additional legal loopholes we've discovered to get source, that we're keeping in our back pocket. We want to keep those backup methods to ourselves so that Red Hat doesn't close off too many at once, should they choose to try to screw over our community again in the future.