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 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 infographic.

Week: 13th – 17th February 2023

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


Fedora Infra

  • More progress on fas2discourse operator (this will allow us to sync groups between fas and discource)
  • Setup some s3 buckets for discourse folks to replicate our backups to
  • Rolled out alerting for all openshift applications
  • Got everything (eln, f39,f38) signed (including stupid typo that took me hours to find)
  • Got rawhide/branched composes all back on track and working
  • Brought s390x builders back after outage
  • Gathered more info on an ansible-freeipa bug and got a workaround.
  • Fixed some stg openshift apps that were failing (fedocal, resultsdb-ci-listener)
  • Re-arranged ppc64le compose vm’s to spread the load over different vmhosts instead of all being on one.
  • Reinstalled more hosts with rhel9 (37 done / ~116 left)

CentOS Infra including CentOS CI

  • Koji Stream migration to 1.31.0 (need fix for 1.31.1)
  • Storage clean up for work/scratch jobs for stream koji
  • Implemented koji-gc policy for stream koji
  • Worked with AltImages SIG to create tags+test kiwi builds and dedicated namespace
  • Multiple tags on for SIGs
  • Started a migration script for centos 7 to rhel 9

Release Engineering

  • Improvement of mass branching documentation

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.



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.


  • Pulled bind9-next from EPEL 9 testing per Steering Committee vote
  • Backported CVE-2022-0699 fix for shapelib in EPEL 7/8/9
  • Prep for adding fasjson-client to epel9 (see request):
    • Multiple upstream pull requests (bravado-core, bravado, swagger_spec_validator, fasjson-client)
    • Multiple packaging pull requests (bravado-core, bravado, jsonref, swagger-spec-validator, rfc3987, strict-rfc3339, webcolors, requests-futures, requests-mock, fasjson-client)
  • WIP builds available for testing in copr pending official builds

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.


  • Caching is mostly done (in review: cache pulling all the rules from the DB)
  • Implement Matrix sender
  • Statistics about generated notifications
  • Tests in staging (ongoing)

Community Design

Goal of this initiative

CPE has few members that are working as part of Community Design Team. This team is working on anything related to design in Fedora Community.