On behalf of the EPEL Steering Committee, I’m happy to announce the availability of EPEL 10.

https://communityblog.fedoraproject.org/epel-10-is-now-available/

#EPEL #CentOS #RHEL

@maxgot CentOS Stream is RHEL built in the open in collaboration with the community. Decisions are still made by Red Hat, so it's not community led, but it's more community oriented than classic CentOS ever was.

@maxgot This would be incredibly difficult to measure. The bulk of the dataset would come from GitLab merge requests. You would also have to go find bugzillas with patches attached, which was the workflow for CS8 before it was onboarded to the CS9 GitLab workflow.

@maxgot You'll have to identify the authors, not just as Hatters or not, but RHEL maintainers or not. I would argue that a MR from @Conan_Kudo working in a different department counts as community because working on RHEL is not his job. Or my submissions working in CPE to upstream debranding stuff for classic CentOS 8, or to resolve issues in support of EPEL. It gets even harder because I don't believe the maintainers are required to use their at-redhat-dot-com email addresses.

@killyourfm Was it worth it? I.e. should I do the same thing?

@vwbusguy @maxamillion It's going to be very close, because CentOS Stream is very close to RHEL itself. When I've measured it, it's typically 90-95% the same software versions depending on where in the cycle you are.

@vwbusguy @maxamillion It sounds like you're describing a shop that applies updates in prod without first testing them in non-prod. How do they explain when a regression or change in RHEL brings down prod? It's not really different. Testing updates before deploying them in prod is a best practice no matter what OS you're using.

Calckey looks like it has some pretty awesome features. However, using it as a primary account would mean migrating and changing my handle. This makes me think that Bluesky may be onto something regarding "account portability" in the AT protocol. Being able to keep the same handle when migrating between providers sounds really appealing.

#calckey #mastodon #fediverse #bluesky

If someone sends you a pull request, it's rude to close it in favor of your own commit that does the same thing with small adjustments. If changes are needed to the PR in order to merge it, ask for them. The person is literally asking to collaborate with you. Implementing their suggestion without their name attached is stealing credit. It also discourages them from collaborating with you in the future.