A primary focus across many groups was the upcoming Fedora 45 release cycle, which drove the submission and discussion of several key Change Proposals, including system-wide updates to LLVM 23 and a multi-widgetset Lazarus IDE. This release preparation was accompanied by significant package maintenance, highlighted by the major OpenSSL 4.0 update and its mass rebuild, compatibility work for Python 3.15, and security-driven package replacements in EPEL. Another common thread was the evolution of core infrastructure, with teams managing the migration from Pagure.io to Forgejo and the transition from Nagios to Zabbix for system monitoring. Community testing was also a crucial activity, with efforts centered on the new KDE Plasma 6.7 release and the restoration of Google Drive integration in GNOME. Finally, improving community processes was a recurring theme, with discussions on creating a new SIG for systemd-sysexts and enhancing security by mandating 2FA for packagers.

Announcements

This week's announcements focus on the upcoming Fedora 45 release cycle and evolving infrastructure. A reminder was sent out for the upcoming deadlines for F45 Changes, with two new proposals already submitted: a system-wide update to LLVM 23 and a plan to offer the Lazarus IDE with multiple widgetsets. On the infrastructure front, a post discusses the final steps for migrating from Pagure.io to the new Forgejo-based forge, while another provides a technical guide for onboarding Forgejo-hosted projects to Fedora Konflux. The Anaconda team is also seeking community input on a new web-based remote installation feature being built for headless systems.

In community news, a new Outreachy intern shared their experience working on the Fedora Release Schedule Planner API, highlighting a valuable contributor program. For the broader Linux community, a Fedora Magazine article details a practical method for how to sandbox AI coding agents with microVMs on Fedora Linux, addressing a modern security concern for developers.

FESCo

This week, discussions focused on several Change Proposals for the upcoming Fedora 45 release. New proposals were introduced to update the system-wide LLVM toolchain to version 23 and to offer the Lazarus IDE with multiple widgetset options (including GTK3 and various Qt versions), giving developers more choice beyond the current GTK2-only package. These proposals are now open for community feedback.

Discussions continued on previously submitted proposals. Regarding the Golang 1.27 update, it was noted that a fix for DWARF5 debugging issues is unlikely to be included in this release; developers needing this functionality are directed to a dedicated COPR repository. The libxml2 2.15 update, which will require a mass rebuild and deprecates the Python bindings, is awaiting consideration of feedback from the developer mailing list. A significant debate is ongoing around the proposal for a minimal GRUB EFI for Confidential Computing. While the proposal aims to create a smaller, more stable bootloader for Unified Kernel Images (UKIs), the discussion questions the rationale for not using systemd-boot, with conflicting information about the systemd maintainers' willingness to add necessary features.

Learn more about the FESCo team.

Workstation / GNOME

The main activity for the Workstation / GNOME group this week centered on the ongoing effort to restore Google Drive integration in GNOME. In the forum discussion "[Call for Testers] Restoring Google Drive integration in GNOME", a user inquired about installing the test packages on Fedora Silverblue. In response, instructions were provided on how to use rpm-ostree to replace the necessary system components from the testing COPR repository. This provides an opportunity for Silverblue users to contribute to testing this important feature.

Learn more about the Workstation / GNOME team.

KDE

This week's focus was the release and testing of KDE Plasma 6.7.0. The new version was made available for testing on Fedora 43 and Fedora 44, and the community was encouraged to help test and report bugs. In preparation for the final release, the COPR repository for the Plasma 6.7 beta was retired.

Discussions following the release highlighted several user-reported issues. Users on Kinoite noted that the network manager repeatedly asked for Wi-Fi passwords after rebooting; a workaround was discovered which involves entering the password in the main system settings instead of the connection pop-up. Other reported issues include a login loop for some users and desktop instability after clearing the Mesa shader cache. A dependency issue affecting kdevelop on Fedora 43 was also brought up, with the team noting it is a known problem related to a gpgme issue and is expected to be fixed after the Plasma update is pushed to stable.

Learn more about the KDE team.

Infrastructure

This week's activity was light as team members recovered from the Flock 2026 conference. The primary focus was on the monitoring system transition discussed in the main Infrastructure meeting. Nagios has now been officially decommissioned, and work is underway to remove its remaining components from all hosts. The team reviewed the current alerts in the new Zabbix monitoring system, identifying several noisy checks related to mail queues, file ages, and backups that will be tuned or investigated. The Daily Standup was a brief check-in, mostly acknowledging the post-conference recovery period.

Decisions

During the Infrastructure meeting, several actions were agreed upon to refine the new Zabbix monitoring setup:

• The alert threshold for the mail queue on smtp-mm will be increased to reduce noise caused by spam bounces.
• An alert for an out-of-date MySQL backup will be investigated.
• The threshold for countme file age checks will be raised to prevent intermittent alerts.
• The cause of unusually large log files on the dl03 mirror will be investigated.

Learn more about the Infrastructure team.

Release Engineering

This week, the Release Engineering group's activity centered on a community forum discussion. A user shared their detailed experience of successfully creating a customized Fedora 44 XFCE live ISO using the kiwi-ng tool. They described a multi-hour process of trial and error, highlighting solutions for common issues like user login configuration and providing practical advice, such as avoiding the /tmp directory for build outputs to prevent space-related failures. The user also sought help from the community on how to properly format and share their working config.xml file, presenting an opportunity for others to engage and assist.

Learn more about the Release Engineering team.

Quality

This week, the Quality team discussed several technical issues affecting development releases. A significant disruption occurred when a failing test, upgrade_server_domain_controller, blocked all Rawhide updates over the weekend. Other reported problems include broken Adwaita themes in XFCE on Rawhide due to the removal of gnome-themes-extra, a libvirtd service failure on Fedora 44 related to a ZFS module, and a temporary dependency issue preventing Thunderbird installation which was already being tracked. The team also welcomed a new contributor and announced the next QA meeting for June 22.

There are several opportunities for community involvement. Testers are needed for a new Synaptic-style GTK4 frontend for DNF5, which has received positive initial feedback. Additionally, the effort to restore Google Drive integration in GNOME continues, with instructions now available for testing on Fedora Silverblue. As always, volunteers are welcome to help with the validation of Fedora 45 Rawhide nightly composes.

Learn more about the Quality team.

Docs

This week, discussion continued on the long-running topic of a design proposal for Fedora's documentation. The conversation focused on the proposal's use of a tag-based system for organizing user documentation. Contributors expressed concerns about the reliability and consistency of manual tagging, suggesting it can indicate poor search functionality and structure. A preference was noted for traditional navigation methods like Tables of Contents for better topic discovery. As a modern alternative to manual tagging, it was suggested that Large Language Models (LLMs) could be employed for automated classification, which might prove more effective and less costly over a large set of documents.

Learn more about the Docs team.

Internationalization

This week, the Internationalization team announced a significant new collaboration: the MATE Desktop project has migrated its translation work to the Fedora Weblate platform. This move invites all translators to contribute to MATE applications and documentation directly within the Fedora infrastructure, strengthening the ties between the communities.

In other news, the community welcomed a new and proactive Norwegian translator, Arvind Frøiland, who introduced himself on the mailing list. Having already completed the Norwegian Bokmål translation for systemd, Arvind expressed a keen interest in contributing to other core components and requested reviewer permissions to help maintain and improve Norwegian translations more effectively.

Learn more about the Internationalization team.

EPEL

This week in EPEL was quiet, with a sparsely attended meeting due to the Flock conference. The main focus was on several significant package changes proposed on the mailing list. A key discussion is underway to replace the end-of-life p7zip package with the modern 7zip in EPEL 8 and 9 due to numerous unfixable security vulnerabilities in the older package. This is considered a slightly incompatible update, and an issue has been filed for community feedback and future discussion.

Other proposals seeking community input include the retirement of qt6-qtwebengine from EPEL 9 due to maintenance difficulties and a high number of CVEs, and a plan to update syncthing to v2 in EPEL 10 while retiring it from EPEL 8 and 9 because older dependencies prevent necessary security updates. Contributors, especially maintainers of packages that depend on these, are encouraged to participate in the discussions.

Learn more about the EPEL team.

Atomic

This week, discussion centered on a proposal to create a new Special Interest Group (SIG) focused on systemd system extensions (sysexts). The proposal, initiated by Jean-Baptiste Trystram, follows discussions at FLOCK 2026 and aims to formalize the building, documentation, and distribution of sysexts based on Fedora content. These extensions are seen as a key method for adding functionality to atomic systems, especially for software not well-suited for containers or Flatpaks. The primary goals for the proposed SIG would be to establish an official build process, potentially using Konflux, and to solve the open questions of distribution and discoverability. The idea has received positive engagement, with several contributors expressing interest in joining the effort.

Learn more about the Atomic team.

CoreOS

During the weekly meeting, the team reviewed upcoming system-wide changes for Fedora 45. A critical issue was discovered with the proposal to relocate RPM repository configurations to /usr. Because rpm-ostree relies on DNF4, this change is expected to break client-side package layering, a significant feature for users. This will be tracked closely. The team is also seeking a volunteer to investigate a bug related to another F45 change in fedora-coreos-tracker/issues/2160.

In the forums, a proposal was made to create a new Special Interest Group (SIG) for systemd-sysexts. The goal is to establish an official process for building and distributing system extensions, which offer a way to add functionality to atomic systems for software that isn't well-suited for containers. The proposal has received positive feedback and interest from several community members, presenting a new opportunity for contribution.

Learn more about the CoreOS team.

AI & ML

The AI & ML SIG met this week to discuss preparations for the upcoming Fedora 45 release, which is scheduled to branch on August 11, 2026. A key topic was the ongoing effort to update packages for the Python 3.15 release, which is causing the usual compatibility issues with torch and triton. The group plans for F45 to ship with ROCm 7.2, and work is underway on a compatibility package set to support this version on F46 when the next major ROCm release arrives. There is a strong interest in packaging local AI tools for F45, and contributors are needed to help review packages for the pi-coding-agent (Bugzilla #2464801) and the olla local AI proxy.

The idea of creating a dnf package group for AI/ML tools was briefly discussed but was ultimately deferred. The group felt it was too early to add this, given the complexity of handling different hardware backends (like ROCm) and the desire to avoid adding process overhead for the small number of active packagers. The meeting also touched on the status of OpenVINO, confirming that no one in the SIG is actively working on it at the moment.

Learn more about the AI & ML team.

Security

The Security SIG held its weekly meeting to discuss recent events and plan future work. Following the Flock conference, the group noted a new connection with Red Hat Product Security (RH ProdSec) and discussed concerns about documentation with security implications, which will be addressed soon. A major topic was the FESCo proposal to mandate two-factor authentication (2FA) for provenpackagers, prompted by recent security incidents in the wider open-source community. The SIG offered to support this initiative by helping with documentation and communications.

The team also triaged several issues, focusing on providing better support for package maintainers dealing with CVEs. This led to a decision to create a formal process for maintainers to request assistance. The group also briefly touched on tickets related to security-optimized sysctl settings and a protocol for skipping meetings. Contributors are encouraged to review and comment on the open tickets in the Security Forge and the Security Docs Forge.

Decisions

• The SIG approved the proposal in ticket #9 to create a formal support channel for package maintainers needing help with CVEs. The plan is to add a ticket template to the security/tickets repository and announce the new process on the devel mailing list.

Learn more about the Security team.

Perl

This week's activity for the Perl group focused on routine package maintenance and an enhancement to packaging tools. The perl-PPIx-Regexp package was updated to version 0.092 via several pull requests. The perl-Net-DNS package was also updated to version 1.55, which included an update to the upstream GPG signing key. A notable improvement was merged for perl-rpm-build-perl, which now supports the package NAME VERSION; syntax to improve automated dependency generation.

PHP

A discussion was initiated by Remi Collet regarding a build issue for PHP extensions on EPEL-10.2. It was noted that extensions were incorrectly being built against the newer PHP 8.4 stack instead of the default PHP 8.3. This occurred because the build system selected php8.4-devel as the best provider for the php-devel dependency. A workaround has been implemented to ensure packages are built against the correct version.

Decisions

• To resolve a build dependency conflict on EPEL-10.2, the BuildRequires for PHP extensions will be constrained to a specific version range (php-devel >= 8.3 with php-devel < 8.4). This ensures they build against the intended default PHP 8.3 stack. All affected extensions have already been rebuilt with this fix.

Learn more about the PHP team.

Other Discussions

• A discussion was initiated by FranciscoD about improving the packaging workflow by creating a separate git repository for up-to-date .spec file templates. This would allow rpmdev-newspec to use current templates and could be integrated into a new fedpkg new command. Following the discussion, a spec-templates repository was created, and a pull request for a fedpkg new-package command was opened to implement this functionality.
• Adam Williamson posted a heads-up that all Rawhide updates were being blocked by a failure in the upgrade_server_domain_controller test. He noted the bad timing post-Flock and devconf.cz and mentioned he was actively investigating to resolve the issue as soon as possible.
• Brad Smith announced upcoming changes for the containerd package. A FESCo exception now allows all Fedora releases to have the same containerd version, constrained only by the Go version. Additionally, starting with v2.3.x, the containerd-shim-runc-v2 will be provided as a static binary, matching upstream, which should be a transparent change for users.
• A change proposal for Fedora 45 was announced to update all LLVM sub-projects to version 23. This update will involve a soname version change for LLVM libraries and the addition of an llvm22 compatibility package. The plan is to push version 23.1.0 into F45 during the Beta Freeze, with release candidates being tested in COPR beforehand.
• A change proposal for Fedora 45 was announced to offer the Lazarus IDE built with multiple widgetsets (GTK2, GTK3, Qt5, Qt6) instead of just GTK2. The lazarus-ide package will be renamed to lazarus-ide-base, and new sub-packages for each widgetset will be introduced. This will allow users to choose their preferred interface and will facilitate the eventual retirement of gtk2.
• Aoife Moloney sent a reminder about the upcoming deadlines for Fedora 45 changes. The deadline for submitting System-Wide changes is June 30, 2026, and for Self-Contained changes is July 21, 2026. All changes must be in a testable state by August 11 and complete by August 25.
• Gordon Messmer initiated a discussion on both the nodejs and devel lists about the presence of pre-built binaries in the node_modules directories of bundled Node.JS packages in Fedora. The consensus was that this is an oversight and not permitted by packaging guidelines. The conversation highlighted the fundamental difficulty of adhering to Fedora's policies with the NPM ecosystem, where dependencies often include pre-compiled or minified assets, making review and maintenance impractical. It was suggested that bugs should be filed for affected packages and a FESCo ticket opened to address the systemic issue.
• Emanuele Petriglia inquired about the fx package, which was orphaned years ago due to issues with NodeJS packaging guidelines. Ben Beasley, the former maintainer, confirmed this was the reason and noted that since the tool has been rewritten in Go, the original packaging problems are no longer relevant, and it would be welcome back in Fedora.
• Kamil Paral called for new maintainers for the Packager Dashboard and Oraculum.
• C. S. Sushi proposed the creation of a Software Engineering SIG.
• Other topics discussed this week include a request for help with a List.remove() issue inside a for-loop in Java, comments on a spam email promoting a code editor that was also sent to openSUSE lists, and the continuation of a long discussion on AI-driven contributions which pivoted to requiring 2FA for packagers. Technical discussions covered packaging guidelines for distribution conditionals, how to handle autogenerated documentation in RPMs, and the implications of swapping fedora-release on COPR compatibility for Remixes. Announcements were made regarding the sunset of pagure.io, a change proposal for libxml2 2.15, and another for a minimal GRUB EFI for Confidential Computing. Users sought help with a mockbuild failure in rawhide and a Bodhi update issue. Finally, there was a check on a non-responsive maintainer and a question about the OpenSSL 4.0 mass rebuild.

New contributor introductions

• Benson Muite introduced himself to the 3dprinting SIG, expressing interest in using FOSS for making things and mentioning his work on reviewing FreeCAD to bring it back to Fedora.
• Kenny Glowner introduced himself, seeking sponsorship to become a Fedora packager. He aims to adopt and maintain the orphaned ccze and sslh packages, with a long-term goal of rewriting them in Rust.

Package Updates

• Ankur Sinha announced that highfive 3.3.0 is being prepared for Rawhide and listed the dependent packages that will be rebuilt.
• The upgrade to openbabel 3.2.0 was announced for Rawhide, which will require several dependent packages like IQmol and avogadro2 to be rebuilt or updated.
• Gwyn Ciesla announced an upcoming libupnp 2.0.2 build which includes a soname bump, and that all dependencies except the already-FTBFS eiskaltdcpp will be rebuilt.
• František Zatloukal announced upcoming upgrades to fmt 12.1.0 and spdlog 1.17.0 in Rawhide, which will involve a soname bump and a mass rebuild of dependent packages in a side tag.
• Gwyn Ciesla announced an update to QXlsx 1.5.1, which includes a soname bump. The dependent package LabPlot builds fine, while stellarium is already failing for other reasons.
• Ben Beasley gave a heads-up about the upcoming update of abseil-cpp to version 20260526.0 in F45/Rawhide, which breaks ABI compatibility and will require a rebuild of all dependent packages in a side tag.
• Mattia Verga announced an upgrade of libbox2d from version 2.x to 3.x in Rawhide, which includes a soname bump. The main consumer, libreoffice, will be upgraded at the same time.
• Mamoru TASAKA announced an update for libetpan to 1.10.1, which involves a soname bump. The dependent packages cairo-dock-plug-ins and claws-mail will be rebuilt, but this will be postponed until after the OpenSSL 4.0 changes are merged.
• Fabio Valentini announced that the libgit2 package has been retired in Rawhide as part of the Changes/Versioned_libgit2_packages implementation, and requested reviews for pending pull requests on packages that still need to be updated.
• Milan Crha announced an upcoming evolution-data-server 3.61.1 release which includes a soname bump for libcamel. He plans to rebuild all affected packages in a side tag.
• The OpenSSL 4.0.1 update has officially landed in Rawhide, along with 734 rebuilt packages. An openssl3 compatibility package is available for packages that have not yet been updated. Maintainers are urged to make their packages compatible before the F45 mass rebuild.
• José Expósito announced plans to update mesa to v26.1.x in Fedora 44, coordinating with RPM Fusion maintainers. A discussion also started about the possibility of updating Mesa in Fedora 43 as well.

Orphaning packages

• The weekly report of orphaned packages was sent out, listing numerous packages that are available for adoption and will be retired in six weeks if no new maintainer is found.
• Fabio Valentini announced the intent to retire the rust-handlebars5 compat package in Rawhide, as the CLI tool it provides (handlebars-cli) is no longer part of the main handlebars crate in version 6.

Across the project, the dominant focus was on preparing for the upcoming Fedora 45 release. This involved FESCo debating significant Change Proposals like a system-wide libxml2 update and a new GRUB package for Confidential Computing, while the Quality and ELN teams were busy testing and integrating major updates like Python 3.15 and preparing for OpenSSL 4. A key strategic initiative discussed by the Council and Atomic groups is the plan to use Konflux to build and ship bootc base images for the F45 cycle. Another common theme was the upcoming Flock conference, which impacted meeting attendance and served as a central point for planning, presentations, and resolving blockers. Concurrently, several groups were managing infrastructure changes, including the completed migration from Nagios to Zabbix and the ongoing move of repositories from Pagure to Fedora Forge.

Announcements

The F44 election cycle has concluded, with results announced for the Fedora Council, FESCo, Mindshare, and EPEL Steering Committee. This followed a final reminder to vote earlier in the week. In the lead-up to Flock 2026, the "#Commit History" campaign continued to highlight contributor stories, featuring interviews with speakers Jaroslav Reznik, Jona Azizaj, Justin Wheeler, and Peter Boy. The campaign also encouraged community members to share their own first commit stories, and an election-period interview with Council candidate Tomáš Hrčka was also published.

On the technical front, two change proposals for Fedora 45 were announced: a system-wide update to libxml2 that will require a mass rebuild, and the creation of a minimal GRUB EFI package for Confidential Computing. An important announcement explained the upcoming Microsoft Secure Boot certificate expiration, assuring users that Fedora is prepared and there is no need to panic. For testers and developers, non-official Fedora 44 RISC-V images are now available, and a new guide details how to onboard a Forgejo-hosted project to Fedora Konflux for CI/CD.

Council

This week, the Council's activity centered on the "Atomic This Week - 2026-06-09" update, which summarized the progress of the Atomic Initiative (formerly the bootc initiative). Key discussions focused on the plan to use Konflux for building and shipping the Fedora bootc base image, targeting the Fedora 45 release. The main blocker identified is securing approval from Fedora releng for a managed namespace, a topic to be discussed in person at Flock. The group also addressed the need for a clearer governance structure and contribution ladder to improve contributor access to Konflux. For the initiative's long-term future, the consensus is to create a new, permanent "Atomic SIG" dedicated to bootc base images, rather than merging with the Atomic Desktops SIG. Interested contributors are invited to join the #bootc:fedoraproject.org Matrix channel to participate.

Learn more about the Council team.

FESCo

Several new Change Proposals for Fedora 45 were introduced and discussed this week. A proposal to update libxml2 to version 2.15.3 was submitted, which is notable as it includes an ABI change requiring a system-wide mass rebuild and deprecates the python3-libxml2 subpackage. Maintainers of packages using the old Python bindings are encouraged to migrate to alternatives. Another new proposal aims to create a minimal GRUP EFI package specifically for Confidential Computing environments to boot Unified Kernel Images (UKIs). This proposal generated significant debate, with many contributors questioning the decision to create a new GRUB variant instead of using the existing systemd-boot, and challenging the rationale provided for its rejection.

In other news, the long-running Protobuf 5.x/6.x update was reported as complete and is now available in Rawhide. For those interested in testing upcoming changes, the NodeJS metapackage change is now available in a COPR for preliminary testing. Finally, the proposals for Erlang 27 and RPM 6.1 were formally submitted to FESCo for voting.

Learn more about the FESCo team.

Packaging Committee

During their weekly meeting, the Packaging Committee approved a change to make the Web bundling guidelines consistent with a prior FESCo decision (PR#1539), although they plan to revisit that underlying decision in a separate ticket. A significant open-floor discussion revolved around the process for packaging new cryptographic libraries, where a packager has been unable to get a required public response from the crypto team for over a year. The current plan is to escalate this to FESCo after the Flock conference if it remains unresolved. The committee also debated a proposal for using file triggers to generate shell completions but postponed a decision due to concerns about its compatibility with immutable systems (like rpm-ostree) and containers.

Learn more about the Packaging Committee team.

Mindshare

In the final Mindshare meeting of the current term, the committee focused on transitioning responsibilities and a major new proposal. Discussions covered the off-boarding process for the appointed representatives from CommOps and Marketing, highlighting an opportunity for new contributors to step into these roles. The primary topic was an experimental initiative proposed by the Fedora Council to use Open Collective for community fundraising to support event travel, starting with BalCCon. This aims to create a more agile reimbursement process outside of Red Hat's corporate systems. The committee showed broad support for the experiment, emphasizing the need for careful messaging to avoid misperceptions about Red Hat's funding commitment.

A significant forum discussion this week centered on a contributor's frustration with a non-responsive package maintainer, which sparked a broader conversation about the contributor experience. The thread highlighted the challenges volunteers face and the negative impact that a lack of feedback can have on contributor retention, a key area of concern for the Mindshare committee.

Learn more about the Mindshare team.

Workstation / GNOME

The Workstation Working Group held its bi-weekly meeting, covering several topics. Discussions included a proposal to drop Libcanberra and move sound handling into GNOME Shell, the use of AI for static analysis and duplicate bug detection, and the potential replacement of the Seahorse password manager with a more modern application like Key Rack. On the forums, a call was made for Fedora GNOME users to test a new open-source AI usage tracker called OpenUsage Community, providing an opportunity for community involvement. The ongoing conversation about a potential Fedora edition for NVIDIA's RTX Spark AI hardware also continued.

Decisions

• The Workstation WG meeting scheduled for June 16, 2026, is cancelled due to the Flock conference.
• Several topics from the June 9th meeting were deferred for two weeks, including discussions on status notifiers, replacing the Seahorse password manager, and integrating AI for accessibility features.

Learn more about the Workstation / GNOME team.

KDE

This week, the KDE SIG prepared for the final release of Plasma 6.7.0. The COPR repository for the Plasma 6.7 beta was decommissioned as the testing phase concluded ahead of the official release. This marks a key milestone for users and testers looking forward to the new stable version.

A discussion was also started regarding a user experience issue in KDE Discover, where the interface provides no progress indication during immediate updates, unlike the behavior for offline updates. The user was advised to report this feedback upstream to the KDE community, presenting an opportunity for contributors to engage with developers to improve the software.

Learn more about the KDE team.

Infrastructure

This week, the Infrastructure team announced two major milestones. First, the long-running migration from Nagios to Zabbix for monitoring is now complete, and Nagios has been shut down. The focus now shifts to refining the new Zabbix checks, reducing alert noise, and onboarding other teams to consume their own monitoring data. You can read the full announcement here. Second, Akashdeep Dhar and Lenka Segura were welcomed into the sysadmin-main group, granting them root access in recognition of their extensive contributions. The announcement and congratulations can be found on the discussion forum and the mailing list.

With several team members traveling for the Flock conference, availability may be reduced. During the week's meetings, the team triaged tickets related to dead mirror links and crypto spam, and discussed ongoing work to protect repositories against malicious pull requests. The monthly AWS usage report prompted a discussion about cleaning up unused QA instances to reduce costs. A new contributor was welcomed during the weekly meeting, and opportunities for community involvement include helping with open tickets and collaborating on the new Zabbix monitoring system.

Decisions

• The Nagios monitoring system has been officially decommissioned and replaced by Zabbix. Nagios services on noc01 and noc02 were stopped.
• Akashdeep Dhar and Lenka Segura were added to the sysadmin-main group, which has root access to the infrastructure.
• A patch to fix a FedoraMessaging issue on the wiki (#13395) was merged.
• The team will investigate and potentially delete unused QA instances in AWS to reduce costs.

Learn more about the Infrastructure team.

Quality

The Quality team's weekly meeting focused on the status of Fedora 45, particularly the recent landing of two major Changes: kmscon consoles and Python 3.15. These have introduced some known issues, such as broken kickstart installs and console problems on IoT and CoreOS, which require attention from testers. A call was made for a volunteer to organize Test Days for the F45 cycle, and the next kernel test week is expected in about three weeks. On the mailing list, a plan was proposed to simplify CI infrastructure by discontinuing legacy .ci. messages.

On the forums, a new version of the community-driven DNF UI tool was released, now using the official dnf5daemon for transactions. A significant discussion was sparked by a contributor asking "Is it worth contributing to the Fedora Project?" due to an unresponsive maintainer. This led to a broader conversation about the challenges of a volunteer-driven project and the processes for handling such issues. The team also welcomed a new potential contributor, Ephraim Kaov, who requested to join the QA group.

Decisions

• An action item was created for a volunteer to send out the F45 call for test days.

Learn more about the Quality team.

Design

The Design team's meeting this week was centered on preparations for the upcoming Flock conference. The team discussed progress on the presentation slideshow, beta wallpaper, and livestream splash screen. They also reviewed high-quality promotional videos from a new contributor, ProducerRob. Other key topics included the design for the Flock party badge, where they considered reusing existing assets, and a discussion on the Datagrepper icon, weighing the use of pre-made SVGs against custom designs to ensure recognizability at small sizes.

Decisions

• The general attendee badge for Flock will be awarded automatically through a web hook connected to the Pretix ticketing system, so a QR code poster for claiming it is no longer needed. The party badge will likely still require a manual claim process.
• A new ticket regarding labels will be postponed until the next ticket refinement meeting.
• Madeline Peck will host a meeting next week for team members who are not attending the Flock conference.

Learn more about the Design team.

Internationalization

The Internationalization team held its weekly meeting to discuss upcoming Fedora 45 changes. The team is considering postponing the variable fonts change for fonts-rpm-macros and is planning a new change to package upstream LibreOffice dictionaries as alternatives to the current Fedora hunspell dictionaries. On the mailing list, there was a call for Kurdish speakers to help correctly identify and tag existing translations that use the generic "ku" language code. The team also welcomed back a returning contributor, Javier Blanco, who will be assisting with Spanish translations.

Learn more about the Internationalization team.

COPR

This week, the COPR team published the release notes for the copr-backend server update that was performed during a planned outage on June 2nd. The announcement provides details and context for users and contributors about the changes implemented.

Learn more about the COPR team.

EPEL

During the weekly EPEL meeting, the main topic was repository lifecycle management. The steering committee discussed the timing of minor version retirement and decided to maintain the current policy, closing the related issue. The practical effects of this policy were highlighted in a mailing list thread concerning the recent retirement of EPEL 10.1, where users were reminded that EOL content is available from the archive mirrors. For packagers, a forum discussion clarified that requests for new branches should still be filed against pagure.io instead of the new Fedora Forge instance.

In other news, a final notice was sent to the epel-announce and epel-devel mailing lists regarding the impending retirement of python-django3 from EPEL 8 and 9. The package is end-of-life and has unpatched security vulnerabilities, and since no one has volunteered to maintain it, it and its dependents will likely be retired. The committee also agreed to find a new time for its weekly meetings to improve attendance.

Decisions

• The issue regarding EPEL minor version retirement timing was closed. The current policy will remain unchanged.
• The EPEL Steering Committee will find a new time for its weekly meeting. A poll will be sent to committee members to determine the best time.

Learn more about the EPEL team.

ELN

This week's ELN meeting covered several major upcoming changes and ongoing work. The Python 3.15 update has largely landed in ELN, a significant milestone as this is the version RHEL 11 will branch with. Preparations are also underway for the migration to OpenSSL 4, which is planned for next week in Rawhide and will subsequently land in ELN. Most of the ELN package set has been tested against the new version, and a compatibility package for OpenSSL 3 will be provided to ease the transition. Other discussions included resolving a packaging dependency issue for bootc images, following up on the Hyperscale kernel configuration problem with a new contact in the Red Hat kernel team, and the upcoming migration of the ELNBuildSync service to Fedora Infrastructure hosting.

Decisions

• The meeting scheduled for 2026-06-16 will be skipped due to the Flock conference. The next meeting will be held on 2026-06-23.

Learn more about the ELN team.

Atomic

The Atomic group's weekly meeting focused on the proposal to use Konflux for building and shipping the bootc base image, with the goal of having this in production for the Fedora 45 release. The main challenge identified is convincing Fedora Release Engineering to support the required managed namespace for signing and pushing artifacts. This topic will be a key discussion point at the upcoming Flock conference, where a presentation is being prepared. The group also discussed improving contributor access to Konflux and the long-term governance of the initiative's work, which will likely involve creating a new SIG to maintain the base images after the initiative concludes post-F45.

In the forums, user support discussions continued. One thread saw a user ask for updates on a Konsole TTY error on F44, suspecting an issue with Flatpak integration. Another conversation clarified why a locally installed RPM for Proton VPN on Silverblue is not updated via the Software Center and must be managed manually with rpm-ostree.

Decisions

During the Atomic meeting, the group formally agreed on the following points regarding the move to Konflux:

1. The group confirmed its consensus that using Konflux is the desired direction for building the bootc base image.
2. The primary blocker is convincing Fedora Release Engineering of the need for a managed namespace and artifact signing.
3. A change proposal for this move needs to be drafted in parallel with these discussions.

Learn more about the Atomic team.

CoreOS

In this week's CoreOS meeting, the team reviewed the Fedora 45 release schedule and confirmed that no immediate actions are required. The open floor session included a technical discussion about the boot-time flow of base.platform.d entries and the ignition-fetch.service, prompted by an Afterburn pull request. Another key topic was the status of a proposal to integrate Butane functionality directly into Ignition, as tracked in issue #2006, with the goal of targeting it for the Fedora 45 release. The team also noted which members will be attending the upcoming Flock conference.

Decisions

• spresti will investigate the operational ordering related to the Afterburn pull request.
• spresti will update issue #2006 with previous feedback and follow up with dustymabe regarding the proposal to integrate Butane into Ignition for Fedora 45.

Learn more about the CoreOS team.

IoT

During the weekly IoT meeting, the main topics were the upcoming migration from Pagure to Fedora Forge and the status of release testing. The team is preparing for the repository migration, which is considered urgent as Pagure's decommissioning is imminent. Regarding release engineering, a refresh of the Fedora 44 images is planned but is currently blocked waiting for an update to image-builder. A critical issue was discussed for Fedora 45 (Rawhide), where all OpenQA tests are failing across all architectures. This bug is a key focus for the team, and contributors are encouraged to help investigate the problem.

Learn more about the IoT team.

Alternative Images

In the weekly Alternative Images meeting, discussion focused on RISC-V progress and the migration from Pagure.io to GitLab. The final recompile of CentOS Stream 10 for RISC-V is nearly complete after resolving a %dist tag conflict by changing it to .el10rv. The team hopes to begin building the RISC-V images next week, aided by configurations provided by the RHEL team. This progress is significant for the broader community interested in RISC-V on CentOS.

The migration of key repositories to GitLab is complete as Pagure.io is being decommissioned. While internal documentation has been updated, there is an opportunity for contributors to help by updating the public docs.centos.org website to reflect these changes, as tracked in this work item. This ensures that contributors are not disrupted by the platform change and can easily find the new repository locations.

Decisions

• The following repositories were migrated from Pagure.io to GitLab, with the rest being archived: kiwi-descriptions, sig, spin-bugs, and anaconda-liveinst.

Learn more about the Alternative Images team.

Cloud

The Cloud SIG held its weekly meeting and discussed the recent successful migration of the cloud-sig to forge.fp.o. Thanks were given to the contributors who made this transition possible. The primary focus of the meeting was planning for the upcoming Flock conference.

A significant portion of the discussion was dedicated to organizing a Cloud-SIG meetup at Flock. This provides a key opportunity for contributors to connect in person. The group brainstormed several important topics for this meetup, including a strategy for handling image customizations, creating a formal release checklist, developing a 3-year strategic plan, and exploring the creation of a dedicated AI/ML cloud image.

Decisions

• A Cloud-SIG meetup will be held at the Flock conference. The time is still to be determined, but the location will be Room 1003.

Learn more about the Cloud team.

AI & ML

This week, the AI & ML group's activity focused on the ongoing effort to figure out NPU support in Fedora for the F43 release. A significant step forward was shared by Alessandro Lattao, who posted a link to a working COPR for FastFlowLM. This project enables running Large Language Models (LLMs) on AMD Ryzen AI NPUs. This provides a concrete opportunity for contributors to get involved by testing the new packages and helping to advance NPU enablement within the distribution.

Learn more about the AI & ML team.

RISC-V

This week, the RISC-V group announced the availability of non-official Fedora 44 images for community testing. These images feature a new "Omni" kernel variant intended to support a broader range of hardware. During the weekly meeting, the team noted that while the package delta for F44 is minimal, some boot issues have been reported. Work has now begun on Fedora 45, with the immediate priority being the integration of Python 3.15. Hardware updates included the addition of a Spacemit K3 board to the Koji build system. A decision was also made to establish a new SCM structure for RISC-V specific packages.

Decisions

• A new namespace for RISC-V specific package forks will be created on forge.fedoraproject.org. The repository structure will be /riscv/packagename (e.g., /riscv/gcc), forking from the main /rpms/ repositories.

Learn more about the RISC-V team.

Security

The Security SIG held a brief meeting this week, with low attendance as many contributors were traveling to the Flock conference. The group reviewed the open tickets in the main Security Forge and the Security Docs Forge, and contributors are encouraged to vote on ticket #8. A discussion arose about the meeting's weekly frequency, with suggestions to either move to a bi-weekly schedule or cancel meetings when there are no topics. This will be discussed further in a future meeting when more members are present.

Learn more about the Security team.

Go

A discussion was initiated on the mailing list regarding a packaging issue where the %{gosource} macro failed for the checkmake package. The macro generated a URL for the source tarball that resulted in a 404 error. The packager found a manual workaround by constructing the URL differently and questioned whether the problem stemmed from the upstream project's release process deviating from the norm. This thread presents an opportunity for Go packaging experts to clarify the expected behavior of the macro and best practices for handling such upstream inconsistencies.

Learn more about the Go team.

Perl

This week's activity for the Perl group focused heavily on package maintenance, including version updates and proactive compatibility fixes. Several packages were updated to be compatible with upcoming releases, such as perl-BDB for Perl 5.43.2+, perl-re-engine-RE2 for Perl 5.43.11, and perl-Net-SSLeay for OpenSSL 4.0. Additionally, several modules received version bumps, including perl-HTTP-Daemon, perl-HTTP-Message, and perl-Locale-Codes.

A key ongoing discussion revolves around the large number of orphaned Perl packages resulting from a maintainer's inactivity. A list of packages still needing adoption was circulated, presenting a significant opportunity for contributors to take ownership and help maintain the Perl ecosystem within Fedora.

Decisions

• The perl-BDB package was patched to rename a function, avoiding a name collision with the upcoming Perl 5.43.2+.
• The perl-re-engine-RE2 package was adapted to work with Perl 5.43.11.
• A fix was applied to perl-Net-SSLeay to ensure it builds with OpenSSL 4.0.
• The perl-WWW-RobotRules package was updated to fix its build and a dependency on DB_File.
• perl-HTTP-Daemon was updated to version 6.17, perl-HTTP-Message was updated to version 7.02, and perl-Locale-Codes was updated to version 3.90.

Learn more about the Perl team.

Other Discussions

• Aoife Moloney announced the results of the F44 Elections Cycle for the Fedora Council, Fedora Mindshare Committee, FESCo, and EPEL.
• In a discussion about the Fedora Mentor Summit at Flock 2026, Jona Azizaj announced the planned activities. These include daily "Lunch & Learn" sessions for informal networking, a sticker matching icebreaker to connect attendees, and a session to highlight the Fedora Contributor Recognition Program and its winners.
• A new topic was created to discuss including upstream branch information in Fedora packages. The main use case is to help developers easily find the correct branch for submitting bug reports and fixes. The conversation weighed the benefits of a dedicated field for this information against concerns that a branch name is mutable and less reliable than a commit hash.
• Yann Collette provided an extensive update on the Audinux repository for May 2026, detailing the addition of 32 new packages and 88 package updates for audio production software. In response to the detailed post, it was suggested that a Fedora Magazine article would be a great way to increase visibility, an idea which was well-received.
• In the "If you're on the kernel mailing list (LKML), aren't you concerned about AI?" discussion, the conversation continued about plagiarism and AI-generated code. Participants suggested using plagiarism detection tools similar to those in academic publishing. Frustration was also expressed regarding the high volume of automated commits on the LKML, which makes it difficult to follow human discussions.
• The discussion on how to include upstream URLs in Fedora packages continued, with a note that a previous proposal for a RepoURL tag in RPM was rejected in favor of using the existing VCS tag. An example was shared from the Hummingbird project, where for packages without a traditional upstream, the VCS field points to the package's location in Fedora's infrastructure.
• Adam Williamson proposed a plan to stop sending .ci. messages on the Fedora message bus. This change aims to simplify the CI infrastructure, as the system is considered legacy and its few consumers can be adapted to use other message sources like resultsdb directly.
• Gordon Messmer is seeking a reviewer for a new security analysis tool in Fedora CI. The proposed generic test uses "got-audit" to attach to running systemd services and check for unusual symbol resolutions, which could help detect issues like the XZ backdoor.
• Zbigniew Jędrzejewski-Szmek announced a change in Rawhide's systemd package regarding the autogeneration of library dependencies. The new method improves handling of soft dependencies for libraries loaded with dlopen(), allowing binaries to adapt their functionality based on which libraries are installed.
• Fabio Valentini announced that he is beginning to implement the Changes/Versioned_libgit2_packages proposal. The first step involves retiring the unused libgit2_1.8 package in Rawhide, with further changes and rebuilds planned for after Flock.
• Other discussions this week included a heads-up about fixes for dracut DHCP issues, a conversation about the civetweb package being retired in Rawhide, a clarification that repository composes use efficient hardlinks instead of copying RPMs, a new F45 Change Proposal to update libxml2, a discussion on a UTF-8 parsing issue in Java manifests, testing and feedback for the new Node.js Metapackages, continued discussion on the F45 Change Proposal for RPM 6.1, a query about using sidetags in Pull Requests, and a note on a similar security incident in Arch Linux in the context of the compromised Fedora account.

New Contributor Introductions

• Kevin Thomas (kevtt) introduced himself as a newcomer looking to get involved with the Join SIG, testing, and documentation to learn more about Linux and the community.
• Henry (henrymmey), a teenager from Germany, introduced himself with an interest in infrastructure, systems management, and Linux development, and is seeking guidance on where to contribute.

Package Updates

• Benson Muite announced an upcoming update for ThorVg in F44 and F43 to address a CVE.
• Frantisek Zatloukal confirmed that the mass rebuild for the icu 78.3 update is now complete.
• Sandro Mani announced plans to update gdal to version 3.13.1, which includes a soname bump, but was asked to hold off until the ongoing OpenSSL 4.0 rebuild is finished.
• In the thread about the fmt library soversion bump, Frantisek Zatloukal offered to handle the required mass rebuilds for both fmt and the dependent spdlog package in about two weeks.

Orphaning packages

• Jerry James orphaned spec-version-maven-plugin and jakarta-json as they are no longer required by antlr4-project. He noted that spec-version-maven-plugin is still a dependency for other packages and will need a new maintainer.
• Adam Williamson briefly orphaned xterm-console before quickly re-adopting it after realizing it was still needed.
• Viktor Erdelyi provided an updated build for the orphaned package wavemon. After encouragement to become the maintainer, Iñaki Ucar stepped in to formally adopt the package and start the un-retirement process, as Viktor was not yet a packager.

Across the project, a primary focus was on technical modernization and infrastructure migration. This was highlighted by the major mass rebuild for Python 3.15 in Rawhide, the Workstation team's plans to replace several core desktop components like gnome-keyring and dbus-daemon, and the continued migration of services and repositories to the new Fedora Forge platform. Alongside these technical upgrades, there was a strong emphasis on improving governance and community processes, demonstrated by the Council's work on a new "Fedora Innovation Lifecycle," the official release of new forum moderation guidelines, and discussions within the Docs and EPEL teams to refine workflows and policies. Much of this work was contextualized by the upcoming Flock conference, which influenced planning and was identified as a venue for key in-person discussions. Other common themes included the development of new offerings, such as a home server spin-off and a new graphical UI for DNF, and a consistent focus on community engagement through the ongoing Fedora elections and numerous calls for new package maintainers.

Announcements

This week, the Fedora 44 elections voting period opened and will run until June 12th, with candidate interviews available for review (e.g., Vít Smolík, Tomáš Hrčka). For users of the forums, new self-moderation guidelines and rules have been released to improve transparency and formalize community standards. On the technical front, a major mass rebuild for Python 3.15 in Fedora 45 has begun and successfully concluded, and packagers can now safely build in Rawhide again. Contributors were also notified of a planned infrastructure outage for server updates. In news relevant to the broader community, a recent Fedora 43 upgrade helped uncover a 20-year-old security bug in Microsoft Outlook related to unencrypted connections.

In preparation for the upcoming Flock conference, the CommOps team launched the #Commit History campaign, inviting contributors to share their origin stories. Fedora Magazine continued its series of interviews with Flock speakers, featuring insights from Jef Spaleta, Valentin Rothberg, Aleksandra Fedorova, Akashdeep Dhar, and Jona Azizaj. Additionally, the weekly Community Update detailed progress across various teams, including work on Fedora Badges, RISC-V for F44, and QE bug fixes. A helpful guide on installing Fedora across two disks was also published.

Council

In their weekly meeting, the Council discussed several key governance topics. They reviewed the draft for a new Fedora Innovation Lifecycle, deciding to formally introduce it after the Flock conference to allow for more community context-building. The group also approved the new moderation guidelines for the Fedora Discussion forum and initiated a broader conversation about improving the representation of community moderators within Fedora's governance structures. A consensus emerged that the current "Initiatives" framework is ineffective and should be replaced, with further discussion planned. Ongoing forum topics included a proposal for a Fedora AI Ecosystem and the eligibility of teens running for Council.

Decisions

• The Council agreed that the draft proposal for the Fedora Innovation Lifecycle will be formally proposed to the community after Flock. In the meantime, the Council will work to build more community awareness around it.
• The Council approved the current moderation guidelines for the Fedora Discussion forum for publication. A new ticket will be created to discuss how community moderators can be better represented in Fedora's governance structures.
• Regarding a past provenpackager revocation incident, the Council re-affirmed its decision not to publicly disclose confidential details of the incident. The focus will instead be on improving the Conflict of Interest Policy to prevent future issues.

Learn more about the Council team.

Mindshare

The main discussion for the Mindshare group this week continued to focus on the future of surveys within Fedora, specifically the proposal to shut down the LimeSurvey service. The topic was originally raised due to the sole maintainer's burnout, difficult billing changes, and community dissatisfaction with the quality of recent surveys. This week's contribution supported dropping LimeSurvey, suggesting that the Data WG could instead leverage existing, repeatable data sources for analysis. One example was using event data from Pretix via the Fedora message bus to gather insights on attendance, rather than relying on a survey. The idea of a specialized SIG for survey design was also raised to better separate statistical data gathering from simple feedback collection.

Learn more about the Mindshare team.

Workstation / GNOME

This week, the Workstation Working Group laid out plans for several significant technical transitions. Key initiatives include replacing the gnome-keyring daemon with 007, removing the legacy dbus-daemon to standardize on dbus-broker, and modernizing testing infrastructure by replacing xvfb-run with wl-headless-run. These efforts aim to streamline the desktop stack and align with modern practices. Contributor opportunities include finding a new maintainer for the orphaned Showtime package and helping update packages to use the new wl-headless-run testing utility.

In forum discussions, a proposal to undertake a chain of updates related to the mozjs JavaScript engine for the Cinnamon DE in Fedora 44 was debated. The consensus was to prioritize stability for the current release, deferring the larger migration but updating the existing mozjs128 package to include the latest security fixes. Another topic explored the possibility of creating a new Fedora edition for upcoming NVIDIA RTX Spark hardware, with community sentiment leaning towards leveraging existing AArch64 builds and creating documentation rather than introducing a new Spin.

Decisions

• The gnome-keyring daemon will be replaced with 007 in Fedora Workstation, with work being managed to ensure a smooth transition.
• A plan was initiated to remove the dbus-daemon package by addressing dependencies that pull it in, such as in the Anaconda installer.
• The xvfb-run utility will be incrementally replaced with wl-headless-run for testing; this will be added to the package maintenance checklist.
• Regarding the Cinnamon DE in Fedora 44, the decision was made to update the existing mozjs128 package but not to perform a larger migration to mozjs140 to avoid destabilizing a released version of Fedora.
• A long-term goal was set to remove the libcanberra dependency from core desktop packages by rerouting sounds directly to PipeWire.
• Newer LibreOffice dictionaries will be packaged and made available in parallel with existing aspell dictionaries to improve language support.

Learn more about the Workstation / GNOME team.

Server

The Server team held its weekly meeting with a strong focus on the development of a new home server spin-off. The main discussion revolved around user-friendly management and the initial software selection. The group reviewed a draft management guide, which led to a conversation about security practices for home use, including SSH key usage, firewall configuration, and remote access strategies. There was a consensus to leverage Ansible for configuration, with a plan to provide pre-configured playbooks to simplify setup for end-users. Using Cockpit for remote management was also highlighted as a secure and accessible option. The team also discussed which applications should be included by default, agreeing to start with a minimal set from the official Fedora repositories.

Learn more about the Server team.

Infrastructure

This week, the Infrastructure team's main operational focus was a planned mass update and reboot outage to apply the latest updates across servers. Significant progress was also made on the migration from Nagios to Zabbix for monitoring; the team is finalizing per-team notifications and is nearing the project's completion, with plans to announce the final switchover soon. Regular administrative tasks included reviewing the monthly AWS usage report and addressing untagged AWS resources.

A key topic of discussion was the future of the now-defunct scm-commits mailing list. A new forum thread was created to gather feedback from the community, especially packagers, on potential replacements. The primary options being considered are a public-inbox service, for which a proof-of-concept is already running, and leveraging the new Fedora Data Working Group (FDWG) platform for analysis and querying of commit data. Contributors are encouraged to join the discussion and share their use cases to help guide the final implementation. Other topics in the weekly and daily meetings included ticket triage and planning around upcoming events like Flock and a Red Hat Day of Learning, which may impact team availability.

Learn more about the Infrastructure team.

Release Engineering

The Release Engineering team's weekly meeting focused on the ongoing migration to the new Forgejo instance. A significant point of discussion was the migration of the fedora-scm-requests repository, which is blocked on updates to the fedpkg tool. This change will require a broad rollout to all package maintainers and is not expected to be completed before Flock. The team also explored opportunities for automation, identifying the release End-of-Life (EOL) process and mass branching as prime candidates for future work. Additionally, a scheduled task related to retiring packages with security issues was reviewed; it was determined that the underlying policy was never fully implemented, and the team decided to request its removal from the schedule.

Decisions

• The scheduled task "Notifications for retirement of packages with security issues" will be requested for removal from the schedule, as the associated policy was never finalized or implemented.
• Ticket #10160, a feature request for compose failure reporting, was closed as it is better tracked in the compose-tracker project.
• Samyak will chair the next meeting on June 8th.

Learn more about the Release Engineering team.

Quality

This week, the main highlight was a community discussion around a new tool, "Dnf-ui is ready for testing", a modern GTK4 graphical frontend for DNF5. The developer is actively seeking feedback on installation, usability, and functionality, providing a great opportunity for contributors to get involved. The discussion has already yielded valuable feedback on performance, transaction handling, and testing on Fedora Silverblue via Distrobox.

Routine activities for the Quality team continued with announcements for Rawhide nightly compose testing and the upcoming weekly meeting. On the mailing lists, discussions included a user report about a missing grub2 menu after kernel updates on Rawhide and a question about the process for closing bugs for Fedora 42, which has now reached its end of life.

Learn more about the Quality team.

Design

The main discussion this week centered on the ongoing effort to create a prototype for a modernized Fedora Media Writer. The original proposer acknowledged the community's continued interest and praised a functional prototype that another contributor developed based on the initial designs. However, the initiative has been temporarily put on hold due to other commitments and the need to investigate the existing codebase to avoid a complete rewrite. The conversation also included ideas about a web-based writer, referencing the Chromebook Recovery Utility as an example, and suggested that contributors could help by exploring the codebases of other popular tools like Rufus and Etcher for inspiration.

Learn more about the Design team.

Docs

The Docs team held their bi-weekly meeting to discuss several housekeeping and process-related topics. A major organizational change was the standardization of issue labels across all Docs repositories and the decision to consolidate project boards at the organization level to improve cross-repository tracking. The team also discussed how to handle outdated content, including an unsupported system upgrade path in Quick Docs and the ongoing effort to retire old Docs pages on the Fedora Wiki. A debate on contribution workflows took place regarding whether to enforce creating pull requests from forks, with the discussion set to continue in the ticket. Help is needed from the community to apply the new standardized labels to issues in the Quick Docs repository.

On the forums, a new discussion began about "AEO" (AI Engine Optimization) and improving the discoverability of Fedora's documentation for newcomers and automated tools. The conversation highlighted the need for better-organized menus and strategic linking to guide new contributors. In an ongoing topic, the new "Fedora Discussion Forum (Self-)Moderation Guidelines and Rules" were officially published on the docs website, replacing the obsolete Ask Fedora SOPs, and have now been added to Weblate for translation. Finally, a discussion about the legality of including NVIDIA driver installation instructions continued, with a user pointing out that Quick Docs already links to RPM Fusion, questioning the consistency of the policy.

Decisions

• The Docs team meeting on June 16, 2026, is canceled as it overlaps with the Flock contributor conference.
• All project boards will be consolidated at the organization level instead of being created per-repository. Existing repository-level boards will be migrated.

Learn more about the Docs team.

Legal

A discussion was initiated this week regarding the licensing of timidity code, which is bundled within the SDL3_mixer package currently being prepared for Fedora. The timidity README offers a choice between "the GNU GPL, the GNU LGPL, or the Perl Artistic License" without specifying versions, creating ambiguity for packaging. The conversation explored how to interpret this statement, considering the code's history predating GPLv3. The consensus was to assume the author intended versions available at the time, leading to an acceptable license combination for Fedora: GPL-2.0-or-later OR LGPL-2.0-or-later OR Artistic-1.0-Perl.

Learn more about the Legal team.

COPR

This week, the COPR team announced and performed a planned maintenance outage on June 2nd to update the copr-backend server. The outage lasted approximately one hour, during which build queue processing was stopped. Existing DNF packages and repositories remained available throughout the maintenance period. The update was completed successfully.

Learn more about the COPR team.

EPEL

During the weekly EPEL meeting, the main topic was a proposal to delay the retirement of EPEL minor versions. Currently, a minor version is retired on the same day a new RHEL minor version is released, which can surprise maintainers. A two-week delay was proposed to allow in-flight updates to reach the stable repository, but the committee decided to table the discussion to gather more feedback. The results of the Spring 2026 EPEL Steering Committee elections were also announced, with Diego Herrera joining as a new member and Carl George, Troy Dawson, and Jonathan Wright returning. Kevin Fenzi was thanked for 19 years of service as he retires from the committee. On the development mailing list, a discussion about updating OpenColorIO for EPEL 9 highlighted the challenges and general reluctance to introduce updates with library version bumps in stable EPEL releases.

Decisions

• The discussion regarding the EPEL minor version retirement timing was tabled until the next meeting to allow for more feedback in the issue tracker.
• The Spring 2026 EPEL Steering Committee elections concluded, with Diego Herrera, Carl George, Troy Dawson, and Jonathan Wright elected to the four open seats.

Learn more about the EPEL team.

CentOS Hyperscale

The CentOS Hyperscale SIG held its weekly meeting to discuss kernel updates, transactional systems, and tooling. After delays due to security work, new kernel updates for CentOS Stream 9 and 10 are planned for the upcoming week. The group discussed the possibility of shipping an LTS kernel but concluded against it for now, citing the benefits of tracking the Fedora kernel and the viability of using the stock kernel with modules from the Kmods SIG. Significant progress has been made on a dnf5 plugin for transactional updates, thanks to community contributions for Kalpa Desktop, which brings the goal of a transactional Hyperscale variant closer. Contributors interested in having specific packages from Fedora tracked and updated can reach out to the SIG.

On the tooling front, the hs-relmon tool now features a new interactive review mode to simplify package promotion, which was used to release wprof 0.4. In community news, Paweł Zmarzłowski announced his resignation from the SIG. The team also noted that their activity report is overdue and they plan to finalize and publish it soon. Finally, a cleanup of stale packages was performed to reduce repository metadata size, and dnsmasq was backported to the el9 branch to address a security vulnerability.

Learn more about the CentOS Hyperscale team.

ELN

The ELN SIG held one meeting this week, providing status updates on ELNBuildSync (EBS) and bootc. The EBS service has undergone a significant reorganization: its source code has been migrated to a new GitHub repository, its deployment process has been simplified, and a pull request has been submitted to host it within the Fedora Infrastructure OpenShift cluster.

There was also a discussion on the progress of creating bootc images for ELN. This effort is a prerequisite for producing bootc images for CentOS Stream 11. The current work is focused on creating the necessary compose image, with further technical discussions planned for a follow-up meeting.

Learn more about the ELN team.

Atomic

The Atomic group's main focus this week was the migration to the new Fedora Forge atomic organization, discussed during their weekly meeting. The team decided to begin by migrating repositories that do not depend on Konflux, such as documentation and issue trackers. Repositories requiring Konflux for CI/builds will be moved once the integration is unblocked. The discussion also confirmed that the new organization will be the home for bootc-related projects, including work on ELN and a potential move of the CentOS Stream bootc repository. Contributor opportunities include helping with documentation fixes and issue triage after the initial migration, with a cleanup session planned for a future video call.

In community discussions, new solutions were shared for technical challenges on immutable systems. A user provided an updated guide for running the Guix package manager on Fedora Silverblue, and another user shared their method for integrating the KeePassXC and Firefox Flatpaks.

Decisions

• Repositories that do not depend on Konflux (e.g., docs, issues) will be migrated first from GitLab to the new atomic organization on Fedora Forge.
• Repositories dependent on Konflux will be held back until the Konflux integration is complete.
• The bootc ELN work and the CentOS Stream bootc container repository are considered in scope for the new atomic organization.

Learn more about the Atomic team.

CoreOS

In this week's CoreOS meeting, the team discussed the upcoming Fedora 45 release cycle and progress on build system modernization. A key topic was the effort to switch CoreOS Assembler (COSA) to run on Fedora 44, with a plan to test the removal of a potentially unneeded dependency to move forward. Following successful work to repair the bootc pipeline, the team decided to re-enable Konflux for building the Rawhide stream. The group also planned the next steps for adopting bootc-image-builder, which includes moving partition layout definitions into the OCI container and staging the rollout across different release streams, starting with Rawhide.

Learn more about the CoreOS team.

AI & ML

During the weekly AI & ML meeting, the group discussed significant packaging updates, including a new version of ollama in rawhide and progress on updating onnxruntime, which is unblocked by a recent protobuf update. There is a call for community help to review several new packages, including the pi-coding-agent and emacs-agent-shell. In a related forum discussion on NPU support, it was noted that an xrt runtime package is now awaiting review. The meeting also addressed the "Fedora AI Developer Desktop" proposal, with a consensus that the SIG should serve as a collaborative space to shape such ideas before wider public announcement. This led to a re-commitment to create better "Getting Involved" documentation to improve the SIG's visibility and accessibility.

Decisions

• A new repository, editorial-guide-ramalama, will be created under the ai-ml forge namespace for an Outreachy internship project.
• A decision on the Skills Library refactor pull request will be made on or before the next meeting on June 18th.

Learn more about the AI & ML team.

Security

This week, the Security SIG held its weekly meeting, where the main topic of discussion was user privacy in default applications. Sparked by concerns around Firefox, the group considered creating a Fedora-wide policy to disable telemetry and AI features by default, ensuring users must explicitly opt-in. Given the sensitive nature of the topic, the consensus was to continue this conversation in person at the upcoming Flock conference.

A significant opportunity for contributor engagement was announced on the forums with the publication of a new static analysis report on Fedora 45 Critical Path Packages. The report identified 1,242 new findings since the last release, with an AI analysis flagging 14 important and 12 moderate-impact issues that may have security implications. Package maintainers and other contributors are encouraged to review these findings to help secure Fedora's core components.

Learn more about the Security team.

DotNET

The DotNET SIG welcomed a new potential contributor, Anugerah Tallenta Agung, who introduced themselves on the mailing list. As a university student and long-time Fedora user, they expressed interest in contributing to the .NET and gaming experience on Fedora. They are seeking guidance on how to get involved, specifically mentioning sharing their experiences and potentially helping with packaging. This provides an excellent opportunity for the SIG to engage with and mentor a new member. No technical discussions or decisions took place this week.

Learn more about the DotNET team.

Go

This week in the Go SIG, the weekly meeting was lightly attended, leading to the postponement of discussions on open tracker issues. The primary point of information was the announcement of the public Fedora 45 Change proposal to introduce Golang 1.27. This proposal outlines the standard update of the Go toolchain for the next Fedora release.

A discussion on the mailing list resolved a packaging issue where spectool failed to download a source tarball. The problem was identified as a mismatch between the %{gosource} macro's generated URL and the upstream git tag, which included a "v" prefix. The solution was to remove a custom %global tag definition from the spec file, allowing the macro to use its default, correct behavior.

Learn more about the Go team.

Perl

The main point of discussion this week was a call for new maintainers for a large number of orphaned Perl packages. Due to the inactivity of a previous maintainer, there is a risk of these packages being retired. This presents a significant opportunity for contributors to step up and take ownership of packages they are interested in. Other activity consisted of routine package maintenance, including several version updates and a bug fix.

Decisions

• The perl-WWW-RobotRules package was updated to version 6.03.
• The perl-Net-CalDAVTalk package was updated to version 0.17.
• The perl-Net-CardDAVTalk package was updated to version 0.11.
• A fix for procps-ng usage was merged for perl-IO-Socket-SSL.

Learn more about the Perl team.

Python

The Python team announced and executed the mass rebuild of packages for Python 3.15 in Fedora 45 (Rawhide). The process was conducted in a dedicated side tag to minimize disruption, starting on June 3rd. Maintainers were advised to pause their builds in the main Rawhide branch during this period. The side tag was successfully merged on June 6th, completing the transition.

With Python 3.15 now the default in Rawhide, the focus shifts to resolving any remaining build failures. Maintainers are encouraged to fix their packages, with guidance provided for handling common issues like test failures or broken dependencies. This is a key opportunity for contributors to help ensure their packages are compatible with the latest Python version.

Learn more about the Python team.

Other Discussions

• In a discussion about a request to package the ouch compression utility, community members explained that Fedora packaging is volunteer-driven. The requester highlighted the tool's memory safety as a key advantage over existing tools like unar and 7z. While there was interest in the tool, no one committed to packaging it.
• A user initiated a discussion about the use of AI in Linux kernel development, raising concerns about code quality, plagiarism, and the increased rate of change. The conversation touched on Fedora's own kernel validation challenges and whether an LTS kernel would be beneficial, with some contributors noting that kernel developers often consider LTS kernels to be of lower quality than the stable series Fedora already ships. It was also suggested that the main kernel mailing list (LKML) is no longer the appropriate venue for such discussions, which should instead be directed to subsystem-specific lists.
• A proposal was made to standardize the inclusion of upstream repository URLs in Fedora package metadata to improve automation, security analysis, and contributor onboarding. The discussion evaluated using the existing URL or VCS RPM tags. The VCS tag was favored as a more suitable candidate, though concerns were raised about the significant effort required for a mass update and the need for a clear benefit to package maintainers.
• Samyak Jain from Fedora Release Engineering announced that the fedora-comps repository has been migrated from Pagure to Fedora Forge. The repository, which maintains the XML files for installer groups and dnf metadata, is now located at https://forge.fedoraproject.org/releng/fedora-comps.
• Frantisek Zatloukal provided an update on the rebuilds for the ICU 78.3 update, stating that they would restart early the following week after other conflicting rebuilds, such as the Python 3.15 bump, were completed.
• Other topics discussed this week include a list of new packages added to Fedora, a query on how to easily add another user's fork as a remote in fedpkg, a clarification that the RPM 6.1 Change Proposal does not include a switch to the v6 package format, a report on static analysis findings in Critical Path packages which sparked a debate on responsible disclosure, and a reminder about the sunset of pagure.io clarifying its scope.

Orphaning packages

• Neal Gompa has orphaned dnfdaemon, which is based on dnf4, as all its consumers have migrated to dnf5daemon-server.
• Ben Beasley announced the orphaning of snakemake and a large number of its related Python packages. The decision was made to free up time, citing the high total maintenance effort and long-term concerns about bundled pre-compiled assets in the main package.
• Neal Gompa has orphaned the libyui stack of packages, including libyui-gtk, libyui-mga, and others, as they are no longer used by any packages in Fedora.
• Julian Sikorski has orphaned the qmc2 package because its upstream project is no longer maintained.
• The weekly automated report listed a large number of orphaned packages seeking new maintainers. A discussion followed about whether SIGs should be automatically removed as co-maintainers from orphaned packages, with differing opinions on the matter.

Package Updates

• Jerry James announced an upcoming update to the gap package to version 4.16.0, which will include a SONAME bump for libgap. This change is not expected to impact any other Fedora packages.
• Michael J Gruber announced that new versions of girara, zathura, and mupdf would be updated, involving SONAME bumps. The updates, which include important bug fixes, will be built in side-tags for both Rawhide and stable releases under FESCo exceptions.
• Artur Frenszek-Iwicki announced an update to kdsingleapplication in Rawhide, which included a SONAME bump. All affected dependent packages were subsequently rebuilt in a side tag.
• The Protobuf update has landed in Rawhide. A discussion revealed that the Java bindings had been disabled; work was started to re-enable them by packaging the necessary dependencies. Several packages that failed to build with the new version were identified, and pull requests to use the compatibility package are still pending for others.

New Contributor Introductions

• Pragyan Poudyal, who works at Red Hat, introduced himself and expressed his interest in contributing to Fedora as a package maintainer.
• Raghavan Kanagaraj introduced himself to maintain the intel-cmt-cat package. It was clarified that as a previously inactive packager, he needed to follow the process for returning contributors to be re-added to the packager group.
• Carl Byington, a former maintainer of libpst, requested sponsorship to package passwordsafe. Dominik 'Rathann' Mierzejewski sponsored him, welcoming him back into the packager group.