CPE Weekly Update – Week 47 2022

Originally published at: https://communityblog.fedoraproject.org/cpe-weekly-update-week-47-2022/

This is a weekly report from the CPE (Community Platform Engineering) Team. If you have any questions or feedback, please respond to this report or contact us on #redhat-cpe channel on libera.chat.

We provide you with both infographics and text versions of the weekly report. If you just want to quickly look at what we did, just look at the infographic. If you are interested in more in-depth details look at the text version.

Week: 21st to 25th November 2022

Highlights of the week

Infrastructure & Release Engineering

Goal of this Initiative

The purpose of this team is to take care of day-to-day business regarding CentOS and Fedora Infrastructure and Fedora release engineering work.
It’s responsible for services running in Fedora and CentOS infrastructure and preparing things for the new Fedora release (mirrors, mass branching, new namespaces etc.).
The ARC (a subset of this team) investigates possible initiatives that CPE might take.
Planning board
Docs

Update

Fedora Infra

CentOS Infra including CentOS CI

Release Engineering

  • Catch up debt in repos, fedora-comps, pungi …
  • F38 changes reviews
  • Rewrite of SOP in progress
  • Business as usual

CentOS Stream

Goal of this Initiative

This initiative is working on CentOS Stream/Emerging RHEL to make this new distribution a reality. The goal of this initiative is to prepare the ecosystem for the new CentOS Stream.

Updates

  • Sync of Stream 8 modules into the new infra done.
  • Now syncing the other RPM packages. We want to do a test compose in the new system next week.

EPEL

Goal of this initiative

Extra Packages for Enterprise Linux (or EPEL) is a Fedora Special Interest Group that creates, maintains, and manages a high-quality set of additional packages for Enterprise Linux, including, but not limited to, Red Hat Enterprise Linux (RHEL), CentOS and Scientific Linux (SL), Oracle Linux (OL).

EPEL packages are usually based on their Fedora counterparts and will never conflict with or replace packages in the base Enterprise Linux distributions. EPEL uses much of the same infrastructure as Fedora, including a build system, Bugzilla instance, updates manager, mirror manager and more.

Updates

  • EPEL 9 is up to 11,526 (+174) packages from 4,404 (+49) source packages
  • We now have a retirement policy for EPEL packages
  • Proposal for a new workflow and branching structure for EPEL 10
  • Carl attended Supercomputing 22 conference last week and had good conversations about EPEL, CentOS, and RHEL. Already sponsored a new packager as a result.

FMN replacement

Goal of this initiative

FMN (Fedora-Messaging-Notification) is a web application allowing users to create filters on messages sent to (currently) fedmsg and forward these as notifications on to email or IRC.
The goal of the initiative is mainly to add fedora-messaging schemas, create a new UI for a better user experience and create a new service to triage incoming messages to reduce the current message delivery lag problem. Community will profit from speedier notifications based on own preferences (IRC, Matrix, Email), unified fedora project to one message service and human-readable results in Datagrepper.
Also, CPE tech debt will be significantly reduced by dropping the maintenance of fedmsg altogether.

More information on the project can be found here.

Updates