2023 Year in Review: Community Platform Engineering (CPE)

Originally published at: https://communityblog.fedoraproject.org/2023-year-in-review-cpe/

This is a summary of the work done on initiatives by the Community Platform Engineering (CPE) Team. Every quarter, the CPE team works together with CentOS Project and Fedora Project community leaders and representatives to choose projects that will be being worked upon in that quarter. The CPE team is then split into multiple smaller sub-teams that will work on the chosen initiatives and day-to-day work that needs to be done. Some of the sub-teams are dedicated to the continuous efforts in the team whilst some are created only for the initiative purposes.

This update is made from infographics and detailed updates. If you want to just see what’s new, check the infographics. If you want more details, continue reading.

About

The Community Platform Engineering Team is a Red Hat team that is working exclusively on community projects. Its members are part of Fedora Infrastructure, Fedora Release Engineering and CentOS Infrastructure teams. This team works on initiatives, which are projects with larger scope related to community work that needs to be done. It also investigates possible initiatives with the ARC (The Advance Reconnaissance Crew), which is formed from a subset of the Infrastructure & Release Engineering sub-team members based on the initiative that is being investigated.

Issue trackers

Initiatives

PDC Retirement

PDC is the Product Definition Center, running at: https://pdc.fedoraproject.org/.

However, this application which was developed internally, is no longer maintained. This codebase has been “orphaned” for a few years now and we need to find a solution for it.

We are reviewing and having a critical look on what we store in there, see what is really needed and then find a solution for its replacement.

Status: In Progress

Issue trackers

Documentation

Application URLs

Matrix Native Zodbot

With ongoing stability issues with the Matrix <-> IRC bridge and many contributors switching over to Matrix, Zodbot has become increasingly unreliable. The bridge is currently shut off completely. This initiative aims to provide a future-proof solution and allow us to conduct meetings without wasting time troubleshooting the Matrix <-> IRC bridge and Zodbot.

Status: In Progress

Issue trackers

Documentation

FMN Replacement

FMN is a project that allows people in our community to get notified when messages that interest them fire on the message-bus, making the message-bus more useful to people that are not directly developing or troubleshooting applications running in our infra.

The previous solution had plenty of tech debt which caused lag times between an event happening and the subscriber to be notified, so this initiative rewrote the service from scratch and is now live! Users are recommended to migrate their rules to the new service and notifications can also now be configured to email, IRC and Matrix.

Status: Done

Issue trackers

Documentation

Application URLs

DNF-Countme Update

DNF Mirrors Countme scripts are used to gain statistics data about the downloads of Fedora. Purpose of this initiative is to optimize the current solution by adding more comprehensive testing, removing unnecessary code and reducing storage consumption of the data.

Status: Done

Issue trackers

Documentation

ARC Investigations

Investigate moving registry.fp.o to quay.io

Traditionally, registry.fedoraproject.org was needed as quay.io did not support multiarch which it now does. The purpose of this ticket is to carry out some investigation work to confirm all the above is true as well as finding any other potential blockers to the move.

Status: Done

Documentation

Spam fighting

We had plenty of spam on pagure.io this year. To fight it more effectively, the ARC team tried a few different approaches to recognize and delete spam. It’s now much easier to delete the spam user with all the spam it created.

Status: Done

ARC investigation/planning for FCAS

In order to have a quantitative understanding of how the contributor activity has changed over the years and to provide the foundational support to the Fedora Project strategy 2028’s guiding star about doubling the number of active contributors every week, it is important to have a service that tracks their statistics. This measurement would help make the strategy goal meaningful as well as assist the Fedora Council and the related bodies understand how far they have progressed into making this happen and identify the underlying particular problems that act as a barrier in realizing this objective.

Status: Done

Documentation

Badges backend for new Service

Fedora Badges is a service that grants virtual accolades for milestones and completing tasks within the Fedora Project community. For example, a community member may collect badges for testing package updates on Bodhi when they test 1, 5, 10, 20, 40, 80, 125, 250, 500 and 1000 updates.

Status: Done

Documentation

Pagure to GitLab importer

With Fedora and CentOS now having an official namespace on GitLab, multiple projects want to migrate their repositories from Pagure to GitLab. This initiative is aimed to provide an easy way to migrate those projects.

Status: Done

Documentation

DNF-countme

The purpose of this work was about investigating the current solution and it’s bottlenecks to identify what needs to be done to solve the following problems:

  • Storage bottleneck when creating the intermediate database file
  • Operations efficiency for the infrastructure team

Status: Done

Documentation

Dist-Git decoupling & ecosystem mapping

The objective of the potential initiative is to move repository contents (including but not limited to source codes, Packit configurations, RPM specfiles) from Pagure Dist-Git to another platform and confirm that the associated tooling and services (including but not limited to FMN, Datanommer, COPR, Toddlers, FMN, CI, Monitor-Gating, Packit, Bodhi, Fedpkg) work well with the newer platform. The investigation aims to be as agnostic as it can be regarding the destination platform to help ideate a general solution for the compatibility of the associated tooling and services.

Status: Done

Documentation

Epilogue

If you get here, thank you for reading this. If you want to contact us, feel free to do it on matrix.

As CPE members are part of Fedora Infrastructure, Fedora Release Engineering and CentOS Infrastructure, see also the Fedora Infra & Releng update and CentOS Infrastructure update.

1 Like

Re: FMN
The service itself might be “done”, but it seems that various services are not hooked up yet to the new FMN (e.g. koschei, copr). I don’t mean to complain. It’s just that I’ve seen “FMN done” so often already that whenever something didn’t work I tried to fix my FMN settings (which, e.g., include koschei and copr in selection lists) only to find out (by asking around) that it’s not even supposed to work yet. Stating that clearly helps everyone.

Thanks for pointing that out. Yes the FMN initiative we worked on is done, but it doesn’t mean that the work on FMN is finished and we don’t touch it again. We are still trying to resolve remaining issues as they are coming.