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

We provide you both infographics and text version 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 below the infographic.

Week: 05 September – 09 September 2022

CPE Infographics

Highlights of the week

Infrastructure & Release Engineering

Goal of this Initiative

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 (which is a subset of the team) investigates possible initiatives that CPE might take on.
Planning board


Fedora Infra

  • Updated pesign and put in nspawn workaround and secure-boot signing is all working again.
  • Got our power9 machine that had been down back up after a full power reset.
  • Resigned all of eln with fedora-38 key

CentOS Infra including CentOS CI

Release Engineering

  • Up to RC 1.5 for f37 beta (go/nogo tomorrow)
  • fedora-minimal container images are not automatically synced to quay, did manual sync investigation in progress

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.


  • We’re able to build all modules for c8s with the new c9s-like workflow.
  • Content Resolver minor feature: new package count graph in views
  • Working on a new Content Resolver feature: calculating repository split for views (BaseOS, AppStream, etc.) to be used with Fedora ELN.


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 buildsystem, bugzilla instance, updates manager, mirror manager and more.


  • EPEL 9 is up to 8564 (+910) packages from 3601 (+224) source packages
  • Initial haskell stack landed in EPEL 9, including common blocker pandoc
  • fence-agents-epel added to EPEL 9 to provide agent subpackages excluded from RHEL fence-agents package
    • Current workflow, wording and timing causes confusion and possible package removal before it’s time.
    • Currently getting input for a new workflow.
  • EPEL Survey closed and reviewing the results
  • Proposal to drop EPEL 8 Modular

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.


  • Frontend Mock
  • Notification Sender
  • Foundational Database Bits
  • Declutter Dependency PRs and other CI improvements