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: September 12th – 16th 2022

CPE infographic

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

  • F37Beta release seems to have gone pretty smoothly.
  • Bunch of certs expiring (vpn, messaging, etc). Will be renewing them this week.
  • Business as usual

CentOS Infra including CentOS CI

Release Engineering

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.


  • Actively working on resolving centpkg issues
    • New version of centpkg in testing so it works with the new rpkg
  • Last CentOS Stream 8 release tracking 8.7 is out. Next week we’re switching to 8.8. Also generated new cloud images.
  • IDM modules, SSSD, IPA, all updated and working in CentOS Stream 8.


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 8639 (+75) packages from 3640 (+39) source packages
  • qt6 package rebased from 6.2 to 6.3 in EPEL 9 testing
  • Initial ipython package in EPEL 9 testing
  • fedpkg in EPEL9 testing
  • nagios-plugins-check-updates package backported support for Alma and Rocky in EPEL 8 testing
  • Early observations from the EPEL survey:
    • On a scale of 1 to 5, average happiness is 4.5
    • Many people suggested a website to look up EPEL packages, so we added a link to to our docs
    • 41% of people who don’t contribute don’t know where to get started
    • 30% of people who don’t contribute don’t want to contribute
    • 19% of people who don’t contribute want training

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.


  • Database connection and models
  • Frontend mockups
  • Work on the consumer and the sender modules