The Fedora Community Blog is the official Fedora Project blog, with announcements on releases, policies, tooling decisions, and community news.
HN links it for Fedora's choice of Forgejo as its git forge, its AI-assisted contribution policy, and updates on Modularity.
While it's true that a good number of RHEL users don't use EPEL due to the lack of vendor escalation, there are many that do use it. In fact, they tell Red Hat that specific EPEL packages being available in the next version of EPEL block them from migrating to the next major version of RHEL. The feedback finally got loud enough that Red Hat decided to provide headcount to the Community Platform Engineering (CPE) group to create an EPEL team focused on improving EPEL (this is my team at work).
https://communityblog.fedoraproject.org/cpe-to-staff-epel-work/
That said, the "vendor escalate-able only" group is large enough that RHEL is significantly underrepresented in EPEL stats. My guess is that somewhere around 40-60% of RHEL customers use EPEL. For RHEL rebuilds, I would guess that it's probably in the high 90% range, so their numbers in EPEL countme stats are probably fairly accurate. CentOS Stream on the other hand is also underrepresented, as we have countme data for both EPEL 9 and CentOS Stream 9, which shows there are over twice as many instances without EPEL as instances with EPEL.
Keep in mind that the countme data only includes systems connecting directly to Fedora's MirrorManager. Sites that run their own local mirrors are not included. We will never have a complete picture of popularity between these distros. For example, Facebook runs "millions" (a direct quote from their engineers' conference talks, they don't publish exact numbers) of CentOS Stream…
And if you just need a great forge for your company's dev teams you are all good to go. OTOH if you self-host a popular FOSS project then all of the network effects of hosting your repo on Github are gone. If you are a quite large project, such as Fedora who chose Forgejo [0] then it is fine to have a dedicated forge. If your small library repositories are hosted on single-person or small community self-hosted instances, then there is a lot of benefit if the forges hooked into this larger software development social network.
[0] https://communityblog.fedoraproject.org/fedora-chooses-forgejo/
https://www.debian.org/legal/debian-community-site
Statements of other communities about this guy:
https://fsfe.org/about/legal/minutes/minutes-2019-10-12.en.pdf#page=17
https://openlabs.cc/en/statement-we-have-been-a-target-of-disinformation-efforts-our-initial-reaction/
https://communityblog.fedoraproject.org/statement-on-we-make-fedora/
He also have been banned in other communities, like FSFE, FOSDEM, Fedora, Openlabs, GSoC…
I don’t believe this page has been updated to note that it won’t be released in F27 as hoped due to systemic problems in the beta: https://communityblog.fedoraproject.org/modularity-dead-long-live-modularity/
I’m looking forward to seeing what they’re going to do with it next; this is a super tough problem to get right in a supportable way. I have a lot of faith in the Fedora team to put together something awesome.
The Fedora policy on AI-assisted contributions seems very reasonable: https://communityblog.fedoraproject.org/council-policy-proposal-policy-on-ai-assisted-contributions/
https://communityblog.fedoraproject.org/mel-chua/