Community Update - Week 6

News & Announcements Community Blog
1

Originally published at: Community Update - Week 6 – Fedora Community Blog

This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project.

Week: 02 Feb – 05 Feb 2026

Fedora Infrastructure

This team is taking care of day to day business regarding Fedora Infrastructure.
It’s responsible for services running in Fedora infrastructure.
Ticket tracker

CentOS Infra including CentOS CI

This team is taking care of day to day business regarding CentOS Infrastructure and CentOS Stream Infrastructure.
It’s responsible for services running in CentOS Infratrusture and CentOS Stream.
CentOS ticket tracker
CentOS Stream ticket tracker

Release Engineering

This team is taking care of day to day business regarding Fedora releases.
It’s responsible for releases, retirement process of packages and package builds.
Ticket tracker

  • Fedora 44 mass branching preparation [ticket]
  • Mass resigning [ticket]
  • Creating Bugzilla component [ticket]
  • Day to day tickets [ticket]

RISC-V

This is the summary of the work done regarding the RISC-V architecture in Fedora.

  • Fedora RISC-V kernel situation: work on a unified kernel is in-progress for F44 that will work across different boards.
    • Copr RISC-V chroots are being used for kernel builds
  • In the RISC-V SIG meeting, agreed to work on a formal “community initiative” for RISC-V
    • Much of the real work has already been going on w/o a “formal” process — Koji server running on Fedora Infra, FAS integration, RISC-V in Copr, etc.
  • State of RISC-V on Fedora talk at FOSDEM was well received. Slides [PDF] and video are available.
  • F43: the difference between the packages in primary Koji and the RISC-V Koji is very little now (i.e. the gap is being closed).

QE

This team is taking care of quality of Fedora. Maintaining CI, organizing test days
and keeping an eye on overall quality of Fedora releases.

Forgejo

This team is working on introduction of https://forge.fedoraproject.org to Fedora
and migration of repositories from pagure.io.

  • [Forgejo] Create a localization-docs namespace and group mapping for specific requirements [Followup] [Resolved]
  • [Forgejo] Migrate Weblate translations/internationalization tooling from Pagure/GitLab/GitHub to Forgejo [Followup] [Resolved]
  • [Forgejo] Verify if the milestone dates are set correctly in the production deployment of Fedora Forge [Followup] [Resolved]
  • [Forgejo] Create and present Fedora -> Forgejo efforts during FOSDEM 2026 Distributions Devroom [Followup] [Followup] [Resolved]
  • Image build automation pull request
  • Fedora-based runner image built, tested and deployed to staging for further testing (under the playground org), definition
  • Private Issues: Debug failing tests, tidy up accrued changes and cope with nullable public/private issue ID fields

UX

This team is working on improving User experience. Providing artwork, user experience,
usability, and general design services to the Fedora project

If you have any questions or feedback, please respond to this report or contact us on #admin:fedoraproject.org channel on matrix.

3 Likes