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 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: 09 January – 13 January 2023

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
Docs

Update

Fedora Infra

  • Got container pipeline all working before the break in Dec (many thanks to cverna and others who worked on it)
  • Finally fixed proxy09’s ipv6 issues, it’s fully operational now.
  • Pushed fix for collectd selinux denial thats been around for a while.
  • Catching up on requests, etc from break

CentOS Infra including CentOS CI

Release Engineering

  • SCM Request Processor is now live in production, this automates SCM (Source Code Management) requests
  • butane 0.17.0 release signed
  • Pagure-dist-git release is in f36,f37,f38 and epel7 stable epel8 build is incoming

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

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

    Updates

    • EPEL 9 is up to 13,004 (+763) packages from 4,828 (+256) source packages
      • EPEL 9 has officially passed EPEL 8 for number of source packages
    • Filed tickets and patches for uninstallable packages (blosc-bench, poezio)

      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.

      Updates

      • Planning Call completed yesterday, 10/1
        • 2 priorities identified
          • Caching 
          • Message schemas for any and all apps that interact with FMN standardized

      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.

      Updates