Across the Fedora Project, several common themes emerged this week. A major focus was the ongoing migration from Pagure to the new Forgejo platform, with the Infrastructure, Releng, Quality, and Packaging Committee groups all actively discussing the technical migration, adapting their workflows, and updating tooling. Preparation for the upcoming Fedora 44 release was another key activity, involving mass rebuilds, change proposal submissions, release testing, and planning for the mass branching event. Finally, the upcoming FOSDEM 2026 conference is having a significant impact, influencing meeting schedules, reducing team capacity, and serving as a key venue for community presentations and engagement.
Design Team
The team focused on finalizing two posters. For the Fedora Council Strategy Summit poster (#127), a minor logo transparency issue was identified, and niknikovsky was tasked with fixing it before closing the ticket. The poster for getting involved with Fedora (#121) received more extensive feedback on layout, alignment, and spacing issues, which niknikovsky will also address. The text content for this poster is still awaiting final approval, which madelinepeck will coordinate.
EPEL
The EPEL group discussed the planned migration from Pagure to Forgejo, scheduled for the first week of February. A major decision was made to merge a policy change that restricts the use of the -epel suffix in package names. The group also agreed that the "epel" name should be reserved more broadly as a Fedora-wide policy and tasked conan_kudo with filing an issue with the Fedora Packaging Committee (FPC). Due to travel for FOSDEM, the meeting for Jan 28 was canceled.
FESCO
The Fedora Engineering Steering Committee made several key decisions on change proposals for upcoming releases.
* Decisions:
* The proposal to restrict ptrace (#3520) was rejected due to being confusing and lacking consensus; a new proposal for Fedora 45 was requested.
* The proposal for the early removal of Java 21 (#3526) was approved, but the final decision on using RPM scriptlets for user notification was deferred to the FPC.
* The Podman 6 upgrade (#3530) was approved with strict conditions requiring that incompatible changes are in testing by the Beta Freeze and that upgrades from Fedora 42 are fully supported.
* The owners of the Common Licenses package proposal (#3541) decided to withdraw it, opting to create the package first and propose a policy change for Fedora 45.
* Due to the upcoming FOSDEM conference, the next meeting may be postponed if a quorum is not present.
Go SIG
The group is preparing for the Go 1.26 release. alexsaezm is running a mass rebuild of packages in COPR to test the Go 1.26 release candidate after a previous attempt failed. Upstream fixes have been submitted for packages like gh and rclone to make them compatible with new vet rules in the upcoming release. Action items were assigned to alexsaezm to review a Bugzilla ticket, investigate a node-exporter issue, and check his own packages for compatibility.
Image Mode Initiative
The initiative made a key decision on naming, with a poll resulting in the bootc project being renamed "Fedora Atomic". The group is now seeking Fedora Council approval to officially rename the initiative to the "Atomic Initiative". A change proposal for Fedora 44, "Konflux Atomic," is now live for community feedback. Progress on organizing Konflux training has been delayed due to team vacations.
Infra & Releng
In a joint sprint planning meeting, the teams focused on their upcoming work and the use of the new Forgejo platform.
* Important Subjects: Both teams gave positive feedback on using Forgejo for project management and agreed to scope project boards at the organization level to include tickets from all their repositories. They also established a process for tracking unplanned work with a day-to-day label.
* Decisions/Goals:
* The Infrastructure team's sprint will focus on "Forge migration and cleanup" and handling day-to-day tasks, with lower capacity due to FOSDEM travel.
* The Releng team's primary goal is the complex mass branching for the next Fedora release, scheduled for February 3rd. A secondary goal is migrating more repositories to Forgejo.
Infrastructure
The team had a very busy week dominated by the migration of their issue tracker from Pagure to Forgejo. * Important Subjects: The successful migration was the central topic. The team established a new triage process for Forgejo, where new tickets will be assigned points and priority labels. They also coordinated a "Mass upgrade+reboot week" to prepare systems before the Fedora branching. Network saturation caused by bots and AI scrapers was an ongoing issue that required intervention. * Decisions: Tickets were successfully migrated, though private tickets will remain on Pagure for now. They decided to explore holding planning meetings in Matrix to increase community involvement. Several bots and meeting templates need to be updated to point to the new Forgejo repository URLs.
Internationalization
The group reviewed progress for the Fedora 44 release cycle. Two i18n-related changes have been submitted, and the ongoing mass rebuild has not shown an unexpectedly high number of failures. The team is still waiting for feedback from native Arabic speakers to decide on making Cascadia the default monospace font. A reminder was issued for bug owners to address the 55 open bugs targeted for the Fedora 42 release.
IoT Working Group
The group reviewed the OpenQA test status for Fedora 43 (Stable) and Fedora 44 (Rawhide). For both releases, known test failures related to console issues are being ignored. Rawhide is showing five additional soft failures due to an expected "Pre-release warning," and a change will be made in OpenQA to prevent this in the future. Internal testing for Rawhide is failing due to a suspected upstream bug in greenboot-rs, which is under investigation.
Packaging Committee
The committee reached consensus on two policy proposals and planned for their migration to Forgejo.
* Decisions:
* A pull request was approved to clarify that scriptlet output is not a reliable method for communicating with users.
* The committee agreed to recommend, via a "SHOULD" guideline, that library packagers use versioned symbols to improve dependency accuracy, but stopped short of making it a strict requirement.
* It was decided that the packaging-committee project should be migrated from Pagure to forge.fp.o.
Quality
The Quality team's work is currently focused on Fedora 44 readiness and the migration to Forgejo.
* Important Subjects: Fedora 44 testing is blocked by a significant bug (BZ#2429501) that breaks Server installs with an XFS /boot partition, causing over 150 test failures. The migration of QA repositories to Forgejo is nearly complete, and the team has successfully implemented CI/CD using Forgejo Actions.
* Decisions & Events: A call for Fedora 44 Test Days has been sent, and a GNOME 50 Test Day is planned for February 11. adamw will document his findings on using Forgejo Actions.
RISC-V SIG
The group's main discussion was a critical debugedit/binutils issue that is blocking the build of ~1400 packages for the Fedora 43 release.
* Decisions: After the debugedit maintainer joined the meeting and promised a patch within 1-2 days, the group decided to wait for the fix before proceeding with the F43 release or the F44 mass rebuild. This avoids releasing with missing packages and prevents the same failures in the next cycle.
* Other Subjects: The group discussed F44 planning, with a goal of creating a unified kernel image. Several members are also attending FOSDEM 2026, where a talk on "Fedora on RISC-V" will be presented.
Releng
The Releng team focused on process improvement and planning for major release cycle events.
* Important Subjects: The team discussed the aftermath of the F44 mass rebuild, which left many packages unsigned due to a deployment issue on the signing server. They also began tackling the complex task of migrating fedpkg to integrate with the new Forgejo platform.
* Decisions: The team decided to refine their backlog by using part of their weekly meeting for ticket grooming. A FESCo ticket will be filed to request a postponement of the mass branching due to key personnel traveling for FOSDEM. The mass branching work itself will be broken down into smaller, more manageable tickets in Forgejo.
Server SIG
The Server SIG planned its focus for the upcoming year and for future community events.
* Decisions: The group decided on four main projects for the year: creating a home server spin, improving backup documentation and tooling, developing net-boot (PXE) documentation, and working on Ansible/NFS projects.
* Action Items: pboy will create project trackers for these initiatives in Forgejo. The group will also collaborate on a proposal for a Birds of a Feather (BoF) session at the Flock 2026 conference. Several members plan to attend both FOSDEM and Flock.
This summary has been AI-generated. If you see errors, please email aurelien@bompard.org or reach out to @abompard:fedora.im on Matrix, and they will be corrected.