From Feb 02 to Feb 08

Many groups are coordinating efforts for the upcoming Fedora 44 release, with discussions centered on branching, mass rebuilds, and Change Proposals. A significant cross-team effort is the ongoing migration from Pagure to the new Forgejo instance, impacting infrastructure, release engineering, quality assurance, and steering committees, all of whom are planning and executing the move for their respective repositories and documentation. Additionally, there is a focus on updating key software stacks and policies, including NodeJS, MariaDB, and considering new security defaults like restricting ptrace.

CoreOS

The team focused on the Fedora 44 release schedule and the migration to the Konflux build system. While concerns about Konflux's stability were raised, the group decided to proceed with the migration for F44 while keeping the old system as a fallback. They also discussed a proposal for new container image labels, noting that FCOS images are currently missing some required labels. The chunkah project was officially moved to the coreos GitHub organization to foster better collaboration.

  • The decision was made to proceed with migrating the FCOS build process to Konflux for F44, but to maintain the old build system as an easy fallback, with a final decision to potentially postpone to F45 to be made later.
  • The jlebon/chunkah project will be moved to the coreos GitHub organization.

Design Team

The team discussed procedural improvements, including the potential use of Google Meet and Gemini for better meeting notes and adding their meeting back to the Fedora Calendar. The inspiration for the Fedora 45 wallpaper was decided to be Alan Turing. A significant portion of the meeting was dedicated to the possibility of bringing back supplemental wallpapers. The old process and tools are defunct, so a new, low-overhead process, potentially using a Fedora Discussion thread for submissions, would need to be established.

  • A ticket will be opened to discuss using Google Meet and Gemini for future meetings.
  • The Design team meeting will be added back to the Fedora Calendar.
  • The old, outdated supplemental wallpaper wiki page will be taken down.
  • Merge Request #4 for the Fedora Project Logos was approved for merging.

EPEL

The Steering Committee meeting focused on the migration from Pagure to Forgejo, with testing of migration scripts currently underway. A recent update to distribution-gpg-keys was discussed, which resolved an issue affecting builds against RHEL 10. The committee also began planning for the EPEL 11 bringup, aiming to leverage ELN Extras to bootstrap the process and have a concrete plan finalized by the Flock conference.

  • The decision on the new Forgejo repository name for the steering committee was deferred until more members are present.

FESCO

FESCo approved a policy exception for a soname bump for qtkeychain, qxmpp, and kaidan on stable releases, pending successful COPR rebuilds. A change proposal for ibus-speech-to-text was deferred due to concerns about its reliance on third-party model downloads. This sparked a broader conversation about the need for a formal policy regarding packages that download external content post-installation, which will be taken to the mailing lists. The committee also decided to delay the F44 branching by about 24 hours to accommodate ongoing mass rebuilds and a critical bug fix. Lastly, they discussed process improvements for handling Change Proposals and began planning the migration of FESCo documentation to Forgejo.

  • An exception to the updates policy was approved to allow a soname bump for qtkeychain, qxmpp, and kaidan on stable Fedora releases, conditional on COPR rebuilds showing no new issues.
  • The decision on the ibus-speech-to-text change proposal (#3556) was deferred pending more information from the change owner.
  • The F44 branching was delayed by approximately 24 hours.

Discussions

There are new posts in several existing discussions and one new topic. FESCo approved the Change Proposals for switching the default MariaDB to 11.8, updating IBus to 1.5.34, replacing nwg-shell with DankFedoraMiracleWM in the MiracleWM spin, updating TagLib to version 2, dropping LibreOffice's KF5 integration, updating Rust Coreutils and Nushell, updating Django to 6.x, and adjusting container image labels to align with OCI specifications. A change to drop FUSE 2 libraries from Atomic Desktops was also approved after discussion confirmed that major AppImage build tools have a path to migrate away from the old runtime. For Fedora 45, FESCo approved changes to update Lua to 5.5 and to build Atomic Desktop disk images with Image Builder. The NodeJS metapackage change was deferred to F45. A new proposal for F45 was introduced to restrict ptrace by default, which would be disabled when developer tools like gdb are installed; initial feedback questioned the system-wide nature of the proposed override. Finally, an update on the Haskell GHC 9.10 change was posted, noting it is now in Rawhide for testing.

Go SIG

The meeting was held via text chat and had very low attendance. The primary discussion was a status update on Go versions across Fedora releases: Go 1.26rc3 is in Rawhide and F44, while updates for Go 1.25 and 1.24 are in testing for F43 and F42. A question about the QGIS project was deemed off-topic.

  • No decisions were taken.

Infra & Releng

During their sprint planning, the teams clarified that future meetings need a clear format, as there was confusion between text-based and video call options. Both teams identified the migration of their repositories to the new Forgejo instance as the main priority for the upcoming sprint. The Infrastructure team reported successes in system updates and the smooth migration of registry.fp.o, but noted that anubis on the staging Pagure instance has been broken. The Release Engineering team reported that the mass branching for the new Fedora release went well, though some work was blocked by the non-functional Pagure staging instance.

  • The primary focus for the next sprint for both teams will be migrating repositories to Forge.
  • The format for future meetings will be clarified to avoid confusion.

Discussions

A new discussion topic was started requesting feedback on a proposal to create daily, incremental database exports for Datanommer. This would supplement the current full nightly dump, significantly reducing bandwidth usage and restore times for data analysts who need to keep local replicas of the database up-to-date. The proposed script has been tested and shows negligible load impact on the production server.

Infrastructure

Across several daily standups and a weekly meeting, the team focused on ticket triage, the ongoing Fedora 44 mass branching event, and migrating applications in OpenShift from deploymentconfig to deployment. A significant blocker for migrating the main Ansible repository to Forgejo was resolved, though the work is more complex than anticipated. Monitoring alerts for high CPU on proxy11 and a growing distrobuild queue (expected due to the branching pause) were addressed. The team also reviewed a pull request to reorganize infrastructure documentation to be more newcomer-friendly and welcomed back a returning contributor.

  • Outdated links in meeting bots (abompard, zodbot) must be updated to point to the new Forgejo instance.
  • The sync configuration on batcave01 needs to be updated to listen for forgejo messages for the infra/ansible repository.
  • CPU resources for proxy11 will be increased to address high load alerts.
  • App owners must review pull requests from phsmoura to migrate applications to the deployment configuration in OpenShift.

Discussions

A new discussion topic was started requesting feedback on a proposal to create daily, incremental database exports for Datanommer. This would supplement the current full nightly dump, significantly reducing bandwidth usage and restore times for data analysts who need to keep local replicas of the database up-to-date. The proposed script has been tested and shows negligible load impact on the production server.

Internationalization

The team is waiting for FESCo approval on their Fedora 44 changes and is working through a backlog of 48 bugs for Fedora 42. A key discussion point was scheduling the Fedora 44 i18n test week. To better align with the GNOME 50 release candidate, the date was moved from March 2nd to March 9th. This alignment with the GNOME RC schedule will be a consideration for planning future test weeks.

  • The Fedora 44 i18n test week was moved to start on March 9th.

IoT Working Group

The group's main focus was on the failing Fedora 44 (Rawhide) composes, which are in a DOOMED status, blocking all new builds and testing. The failure is suspected to be caused by the ssh-key-dir package, and the team is prepared to drop this package if necessary to resolve the issue. The group also discussed the possibility of packaging a real-time (RT) kernel for Fedora IoT, with an initial goal of making it available and a longer-term goal of potentially making it the default kernel if it proves stable.

  • The team is prepared to drop the ssh-key-dir package to fix Rawhide composes.
  • An issue will be created to start the discussion for packaging an RT-kernel for Fedora IoT.

Packaging Committee

The committee reviewed and discussed several pull requests. A proposal for NodeJS packaging guidelines was approved pending minor formatting changes. A PR to add guidelines for versioned symbols was also approved, with a consensus to merge it now and reorganize the shared library documentation later. The committee also approved an exception request to allow for parallel installable versions of MariaDB. Due to the chair's upcoming PTO, the next two meetings were canceled.

  • The exception for parallel installable MariaDB packaging was approved.
  • The PR for versioned symbols guidelines (FPC PR#1520) will be merged.
  • The PR for NodeJS packaging guidelines (FPC PR#1521) will be merged after the author provides semantic line breaks.
  • The next two meetings (Feb 19th and 26th) are canceled.

Quality

The team is preparing for the Fedora 44 release, which was scheduled to branch on February 3rd. They are investigating multiple failures in openQA compose tests and noted that several recently approved FESCo changes were missing their Bugzilla tracking bugs, which is a process issue that needs to be addressed. The migration of QA repositories to Forgejo is nearly complete, with the team now using Forgejo Projects for sprint planning. A follow-up task is to standardize labels across all migrated repositories. Test Days for KDE 6.6 and GNOME 50 have been announced, and a sequel to the GRUB OOM test day is being planned.

  • Labels will be standardized across all repositories in the quality Forgejo organization, starting with priority labels.

Discussions

A new topic was started to announce the KDE Plasma 6.6 Test Day, which will run from February 2nd to 9th. The announcement invites the community to help test the Fedora Rawhide KDE ISO image to improve quality and stability before the next release.

There's a new discussion about systemd on Fedora being compiled without support for forward secure sealing (FSS) for the journal. The discussion revealed this is intentional because FSS requires libgcrypt, a dependency that has been actively removed from systemd's build to simplify its dependency tree. The consensus is that reintroducing libgcrypt is not desirable, and the feature will likely remain disabled in Fedora until it is ported to use OpenSSL upstream.

RISC-V SIG

The team noted that the package difference between the primary and RISC-V Koji instances for Fedora 43 is at a record low. With F44 branching, development for that release is now underway. A new F43 container image is planned for release soon, following the resolution of a DWARF corruption issue. For F44, the group will initially use kernel v6.18 with plans to switch to v6.19, and a new unified kernel is in development. The group also shared that their FOSDEM 2026 talk on the state of Fedora on RISC-V is now available online. A major initiative is to create a formal proposal to the Fedora Council to officially integrate RISC-V into Fedora.

  • A new F43 container image will be built and published to the Quay registry.
  • An Etherpad has been started to draft a proposal for the Fedora Council to officially integrate RISC-V into Fedora.

Discussions

A new discussion was created to share the presentation from FOSDEM 2026. The talk, titled "State of the Arch: Fedora on RISC-V," covered the current status and progress of the RISC-V architecture within the Fedora ecosystem. Links to the video recording and the slides were provided for those who could not attend.

Releng

In two meetings, the team's primary focus was the F44 mass branching event. They reviewed and clarified several points in the Standard Operating Procedure (SOP) to ensure a smooth process. A new Ansible playbook will be used to automate the dist-git portion of the branching. The team also discussed the "Post-branch Freeze" process, where updates are held until a valid compose is ready. To improve this, a feature was proposed for Bodhi to temporarily restrict update creation on a new branch to administrators, preventing issues caused by delaying build signing.

  • status.fedoraproject.org will be used to communicate the status of the mass branching process.
  • The mass branching SOP will be updated with clarifications identified during the F44 branching.
  • An investigation will be done into the complexity of adding a feature to Bodhi to temporarily restrict update creation on a new branch to admins only.

Docs SIG

Discussions

A new discussion topic was started requesting feedback on a proposal to create daily, incremental database exports for Datanommer. This would supplement the current full nightly dump, significantly reducing bandwidth usage and restore times for data analysts who need to keep local replicas of the database up-to-date. The proposed script has been tested and shows negligible load impact on the production server.

Fedora Atomic Initiative

Discussions

There are new posts in an existing discussion about customizing SDDM themes in Kinoite. One user shared a detailed, step-by-step guide on how to create a custom theme in a writable location (/etc/sddm/themes), copy the default theme into it, and then modify the sddm.conf file to use the new custom theme directory. This allows for modifications like changing the background, which is normally not possible on an immutable system.

There is a new discussion about providing a "Fedora-hardened" configuration for those who want it. The poster proposed a script for immutable desktops like Kinoite and Silverblue that would apply a set of security enhancements, such as restricting cockpit access, hardening kernel parameters via sysctl, and separating SELinux user contexts. The goal is to make these reproducible changes easily accessible to users, and feedback was requested on whether this should be a script, a package, or another form of distribution.

There is a new discussion about systemd on Fedora being compiled without support for forward secure sealing (FSS) for the journal. The discussion revealed this is intentional because FSS requires libgcrypt, a dependency that has been actively removed from systemd's build to simplify its dependency tree. The consensus is that reintroducing libgcrypt is not desirable, and the feature will likely remain disabled in Fedora until it is ported to use OpenSSL upstream.

There are new posts in an existing discussion about replacing the Fedora Flatpak remote with Flathub. A user shared a method for making Flathub the default software source in GNOME Software by creating a dconf override file in /etc/dconf/db/local.d/ to adjust the packaging-format-preference key.

Security SIG

Discussions

There is a new discussion about providing a "Fedora-hardened" configuration for those who want it. The poster proposed a script for immutable desktops like Kinoite and Silverblue that would apply a set of security enhancements, such as restricting cockpit access, hardening kernel parameters via sysctl, and separating SELinux user contexts. The goal is to make these reproducible changes easily accessible to users, and feedback was requested on whether this should be a script, a package, or another form of distribution.

There is a new discussion about systemd on Fedora being compiled without support for forward secure sealing (FSS) for the journal. The discussion revealed this is intentional because FSS requires libgcrypt, a dependency that has been actively removed from systemd's build to simplify its dependency tree. The consensus is that reintroducing libgcrypt is not desirable, and the feature will likely remain disabled in Fedora until it is ported to use OpenSSL upstream.

Ambassadors

Discussions

A new discussion was started to organize an in-person Fedora Project presence at the FOSSASIA 2026 summit. The post calls for interested contributors to add their names to the event's Fedora Wiki page and submit proposals for budgeting and sponsorship. In a follow-up post, a contributor who worked on the Fedora Badges Revamp Project expressed their interest in attending to help represent the project and meet other FOSS enthusiasts.

Mindshare Committee

Discussions

A new discussion was started to organize an in-person Fedora Project presence at the FOSSASIA 2026 summit. The post calls for interested contributors to add their names to the event's Fedora Wiki page and submit proposals for budgeting and sponsorship. In a follow-up post, a contributor who worked on the Fedora Badges Revamp Project expressed their interest in attending to help represent the project and meet other FOSS enthusiasts.

Workstation Team

Discussions

There is a new discussion about systemd on Fedora being compiled without support for forward secure sealing (FSS) for the journal. The discussion revealed this is intentional because FSS requires libgcrypt, a dependency that has been actively removed from systemd's build to simplify its dependency tree. The consensus is that reintroducing libgcrypt is not desirable, and the feature will likely remain disabled in Fedora until it is ported to use OpenSSL upstream.

KDE

Discussions

There is a new discussion about systemd on Fedora being compiled without support for forward secure sealing (FSS) for the journal. The discussion revealed this is intentional because FSS requires libgcrypt, a dependency that has been actively removed from systemd's build to simplify its dependency tree. The consensus is that reintroducing libgcrypt is not desirable, and the feature will likely remain disabled in Fedora until it is ported to use OpenSSL upstream.

Other Discussions

In new posts on a topic about packaging ProtonVPN, a user shared a link to a GitHub issue they created to request a package for a third-party repository, demonstrating continued interest in making the client more accessible.

There are new posts in the discussion about the Go compiler disabling the DWARF5 format by default. A user requested an update, noting that a related readelf bug has been fixed upstream. They also suggested that optional Go and Delve packages could be provided without the nodwarf5 flag as a temporary workaround for users who need the newer debugging format.

There are new posts on the topic of Forgejo versions and packaging. In response to a user's questions, it was clarified that the forge.fedoraproject.org instance is deployed via a container and not from the Fedora RPM, so its version may not align with what is in the repositories. It was suggested that the user contact the package maintainer to offer help with maintaining the EPEL 9 version.

In new posts about a login failure on Pagure, the original poster stated that the issue appears to be resolved for them. Another user suggested that the issue might be reproducible if the user's forked repository is deleted.

This summary has been AI-generated and then manually edited. If you see errors, please email aurelien@bompard.org or reach out to @abompard:fedora.im on Matrix, and they will be corrected. The original meeting logs are available here (make sure you select the right week). The original discussion topics are available here. The original mailing-list messages are available here.

links

social