Across the various Fedora working groups, the primary shared focus this week was the successful completion and subsequent fallout management of the Fedora 45 Mass Rebuild, which required extensive coordination from Release Engineering, Quality, and language-specific SIGs (like Python and Perl) to triage build failures and ABI changes. Another major cross-team initiative is the ongoing infrastructure migration to Forgejo, with the Docs, Infrastructure, Design, and Release Engineering teams actively working to transition repositories away from Pagure ahead of strict deadlines. Security, cryptography, and compliance also emerged as a prominent theme, highlighted by FESCo's new two-factor authentication (2FA) mandate for packagers, the Security SIG's efforts to align with the EU Cyber Resilience Act (CRA), and system-wide cryptography updates like the transition to Sequoia. Finally, teams are heavily engaged in Fedora 45 feature stabilization and policy refinement, actively addressing cross-desktop bugs—such as the memory-crashing default wallpaper in KDE—while updating governance and packaging guidelines to reduce contributor burnout and streamline community workflows.

Announcements

For Fedora contributors, the Fedora 45 Mass Rebuild has officially completed, and a reminder was issued that the F45 Self-Contained Change proposal deadline has closed. To reduce contributor burnout and avoid split-brain conversations, an F46 Change Proposal aims to move all future Change discussions exclusively to the devel mailing list, ending simultaneous threads on Discourse. In other community news, the long-running Community weekly updates are being replaced by "This Week in Fedora". Developers looking to test new tools can engage with a proposed F45 Change to introduce encapsule, a new CLI utility for safely running untrusted internet scripts in isolated containers, which pairs nicely with a recent Fedora Magazine guide on sandboxing AI coding agents with microVMs.

Numerous technical Change Proposals were announced this week, notably for Fedora Atomic Desktops, which are slated to adopt the new Anaconda WebUI and gain web-based remote installation support. On the security and cryptography front, Fedora plans to transition RPM signature verification to Sequoia via a new %openpgpverify macro to support Post-Quantum Cryptography, and will begin phasing out the deprecated in-kernel Crypto Userspace API. System-level updates include deprecating the low-memory-monitor package in favor of native GLib handling, enabling systemd-oomd and zram swap by default on CoreOS, and updating authselect to both hardcode nss-altfiles and remove the outdated NIS profile. Finally, desktop users will benefit from an update to IBus 1.5.35, which improves XKB keymap handling across Wayland environments.

Council

The Fedora Council is currently seeking community feedback on a draft Conflict of Interest Policy intended to guide governance groups. Following initial discussions, the draft will be revised to ensure it only applies to governance bodies, removes overly strict recusal requirements (such as preventing FESCo members from voting on their own changes), and protects contributor privacy under GDPR by not requiring the disclosure of the specific nature of a conflict. In infrastructure news, the Council advanced the Fedora Forge usage policy after reaching a compromise to mandate a "tickets" repository for all organizations as a unified contact method, rather than automatically archiving inactive repositories after 12 months.

Additionally, the Council addressed a few administrative requests. They investigated suspicious Forge organization requests originating from newly created accounts; while a vague Software Engineering SIG request was rejected, the situation successfully led to the revitalization of the Java SIG by an established contributor. The Council also reviewed a trademark permission request to sell Fedora community stickers on a Slovak open-source web shop, and granted an exception for FreeIPA to host an organization on the Fedora Forge due to its foundational role in Fedora Infrastructure.

Decisions

• Agreed to advance the Fedora Forge usage policy by mandating a "tickets" repository for all organizations to facilitate communication, dropping the previous proposal for automatic repository archiving.
• Approved an exception to allow FreeIPA to create an organization on the Fedora Forge, recognizing it as a foundational ecosystem tool.
• Rejected a suspicious Forge organization request for a Software Engineering SIG because it was submitted by a brand-new account and failed to follow the documented SIG creation process.
• Agreed to revise the draft Conflict of Interest Policy to apply strictly to governance groups, protect GDPR privacy rights by not requiring detailed conflict explanations, and allow standard voting practices (like voting on one's own proposals) to continue with simple disclosure.

Learn more about the Council team.

FESCo

FESCo had a highly active week reviewing numerous Fedora 45 Change Proposals and discussing project policies. Major technical discussions included the Forgejo dist-git migration planning, a proposal to restrict Change Proposal discussions to the devel mailing list to prevent "split-brain" conversations, and a fast-track proposal to gate all stable release updates on rmdepcheck. The Enable Shadow Stack by Default on x86_64 proposal was deferred pending a clarified mitigation plan for affected software like Rust, Python extensions, and NVIDIA drivers.

On the security and contributor front, FESCo is officially requiring two-factor authentication (2FA) for all provenpackager group members, with a three-month grace period for existing members before their access is temporarily downgraded. A broader proposal to require 2FA for all packagers is also currently in the works. Additionally, the FESCo election policy was adjusted so that replacements for members stepping down mid-term will serve a full year if only one person drops out.

Decisions

• Change: RelocateRpmRepoConfigsToUsr was recategorized from a Self-Contained Change to a System Wide Change.
• For Change: libxml215, FESCo asked the Change Owner to update the wiki page to ensure critical path packages are fixed before the change is merged and to update for no releng-provided mass rebuild.
• Request to remove inactive software KVM projects: The barrier and input-leap packages will be retired without Provides being added.
• (Slightly) incompatible update request (one-off) for rust-routinator was approved.
• Adjust election policy regarding mid-term vacated seats was approved.
• Change: MariaDB 12.3 was approved.
• Change: MySQL 9.7 was approved.
• Change: Stratis Storage in Anaconda was approved.
• Change: Ruby on Rails 8.1 was approved.
• Change: Bash Color Prompt 1.0 was approved.
• Change: oo7 Secrets Service Provider was approved.
• Change: Fontconfig 2.18 was approved.
• Change: Disable Vendor Change by Default was approved.
• Change: LibreOffice Dictionaries was approved.
• Change: LibreOffice html help was approved.
• Change: Native Butane Config Support in Ignition was approved.

Learn more about the FESCo team.

Packaging Committee

During their 2026-07-23 meeting, the Packaging Committee addressed broken links in the DefaultServices guidelines (FPC#1556), agreeing that linking directly to the fedora-release source tree is too fragile and difficult to maintain. They also reviewed a draft update for NPM packaging guidelines (FPC PR#1553). Contributors noted concerns with the draft's example spec file—specifically regarding how bundled libraries are handled as separate source tarballs and the disabling of automatic requirements. The committee will wait for the Node.js SIG to finalize the draft and address these concerns before conducting a deeper review.

Additionally, the committee discussed the need for clearer versioning guidelines for pre-release snapshots. A pull request is currently being drafted to explicitly define the use of the ~^ syntax, ensuring that untagged snapshots sort correctly before tagged pre-releases (e.g., beta1). This clarification will be proposed for gradual adoption to avoid disrupting existing packages and to help maintainers avoid sorting errors.

Decisions

• The committee agreed to remove the fragile source tree links in the DefaultServices guidelines and replace them with a general text instruction directing packagers to check the fedora-release package directly.
• Formal review of the new NPM packaging guidelines is paused until the Node.js SIG removes the work-in-progress status and addresses initial feedback.

Learn more about the Packaging Committee team.

Mindshare

In their July 23 meeting, the Mindshare committee discussed shifting their social media strategy to rely on "Digital Ambassadors" rather than a dedicated Marketing team, proposing the use of Buffer to securely manage account access. This new direction will be tracked in a fresh ticket, replacing the outdated issue #26. The team also addressed regional support by reviewing a swag request for the French community (issue #126) and noted the need to update the Meetbot documentation to reflect Matrix-native commands.

On the contributor engagement front, the CommOps team is actively seeking new members and a committee representative, prompting the reopening of CommOps issue #145. Highlighting this opportunity, a new contributor with a communications background recently introduced themselves on the forum to join CommOps. Meanwhile, the committee continues to seek asynchronous votes to finalize the Mindshare representative for the Fedora Council.

Decisions

• Approved approximately $500 in swag for the French community to cover a year of local and regional distribution.
• Decided to close the three-year-old social media access ticket and open a new one focused on testing Buffer for Digital Ambassadors.
• Reopened the ticket for the vacant CommOps representative seat to encourage volunteer engagement.
• Extended the vote for the Mindshare Council representative by one week to allow for asynchronous participation due to a lack of meeting quorum.

Learn more about the Mindshare team.

Workstation / GNOME

The f45-backgrounds package is now available in Rawhide, introducing wide-gamut color support for the default Fedora 45 wallpaper. To provide a cleaner Appearance menu, the "Time of Day" animated wallpapers have been separated into optional, dedicated sub-packages for GNOME and MATE. Shortly after the release, testers reported that the default wallpaper was rendering as solid grey in KDE due to memory allocation limits being exceeded by the massive 12800x12800 .jxl image file (mailing list thread). The design team will shrink the image to 8K in the next update to resolve this.

On the networking side, a forum discussion highlighted an issue with Fedora's IPv6 behavior on networks with non-persistent prefixes. When a router reboots and fails to invalidate old prefixes, Fedora attempts to route through older IPv6 addresses instead of defaulting to the newest one, causing connectivity drops until the old lease expires. Contributors are looking into a proper NetworkManager or kernel-level fix, but in the meantime, users can employ NetworkManager dispatcher scripts listening for dhcp6-change events as a temporary workaround.

Decisions

• The "Time of Day" animated wallpapers have been split out of the main background packages into dedicated sub-packages (f45-backgrounds-gnome-time-of-day and f45-backgrounds-mate-time-of-day).
• The default Fedora 45 wallpaper resolution will be reduced to 8K to fix memory allocation failures in KDE Plasma.

Learn more about the Workstation / GNOME team.

KDE

This week, the KDE group discussed a multi-monitor window management behavior where connecting an HDMI display automatically moves all open windows to the external screen, even if the laptop screen remains the primary display. Participants identified that KDE remembers window layouts and specific monitor hardware identities from previous sessions, which is likely a side-effect of the desktop environment's new "session restore" feature. While some users appreciate this persistent layout, others find it disruptive, particularly when applications do not open on the currently active desktop.

Contributors noted that this is an upstream KDE matter rather than a Fedora-specific bug. The behavior has been reported to the KDE bug tracker, and users clarified that it persists even when virtual desktops are configured to switch independently for each screen. Developers and contributors interested in refining session restore logic, multi-monitor window placement, or adding options to clear saved monitor layouts are encouraged to engage with the upstream KDE community to help improve this functionality.

Learn more about the KDE team.

Server

During the weekly Server WG meeting, contributors advanced the Fedora home server spin-off by outlining a minimal KIWI development environment using libvirt, which will be documented in the home-server repository README. The group also discussed standardizing documentation styling, with a strong preference emerging for using backticks for CLI commands and file paths; a formal proposal will be added to the open pull request. In community news, voting to officially add Brett and Ro as working group members remains open until July 31, and contributors are encouraged to participate in manual installation testing for the upcoming Fedora 45 release.

In a forum discussion about Fedora's handling of non-persistent IPv6 prefixes, a community member provided a workaround for routers that fail to invalidate old prefixes after a reboot. Users experiencing connectivity drops can use NetworkManager's dispatcher.d to run a cleanup script on dhcp6-change, as there is currently no native kernel or NetworkManager option to force the system to exclusively use the newest IPv6 address.

Decisions

• For Fedora 45 release testing, the links in the tracking tickets will be updated to point to the newest test build, and the tickets will be left in their current status columns to restart the manual testing cycle.

Learn more about the Server team.

Infrastructure

This week, the Infrastructure team made significant progress on the RHEL10 migration, successfully transitioning the batcave Ansible control host and IPA (FAS) systems, which caused some expected temporary monitoring alerts. Preparations for the Fedora 45 Mass Rebuild are also underway, including the removal of the F45 autosign config to prevent unnecessary re-signing by robosignatory, aligning with the recent F45 self-contained change deadline. On the Forgejo front, the team packaged Forgejo 15.0.5, deployed a new CI runner for the Marketing team, and began prototyping ForgeFiler—a Flask web application designed to securely handle sensitive reports like Code of Conduct violations and GDPR requests in private repositories.

There are several excellent opportunities for contributor engagement this week. The team is actively looking for help investigating broken image links on older MediaWiki pages, resolving grokmirror missing repository issues, and improving Zabbix monitoring by investigating SLA structures to reduce alert fatigue. Additionally, work continues on a Grafana proof-of-concept for the Fedora Data Working Group and the deployment of the new siguldry signing bridge in the staging environment.

Decisions

• The team decided to set up a staging instance of public-inbox for SCM commits, utilizing yearly archives and placing it behind Anubis to evaluate its performance and manageability before a potential production rollout.

Learn more about the Infrastructure team.

Release Engineering

The Fedora 45 Mass Rebuild has successfully concluded, utilizing new retry logic scripts and updated, beginner-friendly documentation. Following the rebuild, Release Engineering ran the mass tagging script and filed FTBFS bugs for failing packages. To stabilize the buildroot and unblock Rawhide composes, several problematic builds—including desktop-backgrounds, jsoncpp, and openssl-pkcs11—were untagged. In other release news, F47 keys have been added to fedora-repos and are now available in updates-testing, and the f45-perl side tag was successfully merged to Rawhide.

Infrastructure migrations are progressing, with toddlers changes prepared for moving scm-requests from Pagure to Forgejo; a coordinated "flag day" will be scheduled once fedpkg updates land. For contributors looking to get involved, there are active efforts to consolidate mass rebuild script configurations and fix false positives in the need_rebuild.py tracker. Finally, maintainers are reminded to use the fedpkg request-unretirement command for automatic package unretirements rather than opening manual Releng tickets.

Decisions

• The process to re-sign F44 content with the F45 key will be separated into its own Standard Operating Procedure (SOP) document to improve the mass branching workflow.
• The legacy Pagure fedora-scm-requests repository will be archived only after the new Forgejo repository and related fedpkg changes are fully deployed and verified to prevent synchronization issues.

Learn more about the Release Engineering team.

Quality

The Fedora 45 mass rebuild is now complete, with the next major milestone—the branch point and first change completion deadline—scheduled for August 11th. During their weekly meeting, the Quality team reviewed upcoming F45 Changes to plan community Test Days, highlighting features like RPM 6.1, Podman 6, and DrmPanicFrontend. In news relevant to the broader Linux ecosystem, the team investigated unexpected font changes caused by freetype 2.18 that may also impact CentOS and RHEL. Additionally, it was noted that the mcelog package is currently unmaintained, prompting discussions about finding a new maintainer or replacing it with rasdaemon by default.

For contributors looking to get involved, nightly composes for Fedora 45 Rawhide are actively seeking release validation testing. Testers can also evaluate the new f45-backgrounds package, which separates the "Time of Day" animated wallpapers into optional sub-packages, though an update is pending to fix a bug where the massive 12K image size breaks KDE Plasma. The team also made a major revision to the Fedora CI documentation, added new KDE start/stop tests to openQA, and welcomed a new young contributor looking for a QA sponsor.

Decisions

• The team decided to group several major Fedora 45 Changes into dedicated test day tickets and initiated coordination with the respective package maintainers to organize these events.

Learn more about the Quality team.

Design

The Fedora 45 backgrounds are now available in Rawhide, introducing wide-gamut color support and splitting the "Time of Day" animated wallpapers into dedicated sub-packages. Following reports that the initial 12800x12800 resolution caused memory crashes in KDE and GIMP, the wallpapers are being scaled down to 8K. Looking ahead, the Fedora 46 wallpaper inspiration poll is live until July 31st, asking the community to choose between four STEM figures whose names start with "U". In infrastructure updates, the team successfully migrated the upstream fedora-logos repository from Pagure to the Design team's Forgejo space, alongside updates to the fedora-remix-logos package.

For contributors looking to get involved, new UX and web design opportunities are available. The Fedora Websites and Apps team is seeking a design for a new credits page to showcase project contributors. Additionally, Project Resistor, a Fedora Remix, needs UX assistance to improve its Jekyll-based website. The team also finalized the YouTube thumbnails for Flock 2026 and continues iterating on a community onboarding flyer and an onboarding video series.

Decisions

• The upstream fedora-logos and fedora-remix-logos repositories have been officially adopted by the Design team and migrated to Forgejo.
• The F45 default wallpapers will be resized to 8K to resolve memory allocation issues.
• The "Time of Day" animated wallpapers for F45 have been separated into dedicated GNOME and MATE sub-packages for a cleaner appearance settings experience.

Learn more about the Design team.

Docs

The Docs team's primary theme this week was platform migration and content consolidation. A major focus remains the Forgejo migration tracker, driven by the strict July 31, 2026, deadline to move all active documentation repositories off Pagure.io. While the majority of Pagure repositories have been successfully migrated, contributors are finalizing the last few pending moves, including the Defensive Coding Guide and the i3 SIG docs. To further streamline information, the team also opened a new ticket to coordinate with Commops to resolve duplicate Special Interest Group (SIG) documentation that is currently split between the legacy Fedora Wiki and the official docs site.

Contributors looking to get involved can assist with the next phase of the Forgejo migration. With the Pagure deadline approaching, the team needs help opening separate planning tickets for remaining GitLab repositories (which involve more complex CI pipeline migrations) and reaching out directly to the owners of various GitLab and GitHub repositories to coordinate their moves.

Decisions

• The team operationally resolved to formally trigger Commops to complete the SIG wiki page migration to eliminate duplicate content.
• Remaining GitLab repository migrations will be handled via separate, dedicated planning tickets rather than the main tracker.

Learn more about the Docs team.

Internationalization

During the Internationalization meeting, the team reviewed upcoming Fedora 45 changes, noting that proposals for fontconfig (System Wide Change) and LibreOffice Dictionaries (Self Contained Change) are currently moving through the approval process. The F45 mass rebuild has also finished with under 1,000 failures, and package maintainers are urged to check the failure logs for their packages. Specific rebuild failures with ibus-table and ibus-typing-booster were noted and are actively being investigated.

To help prepare for upcoming releases, contributors are encouraged to assist with Fedora 43 bug triaging by fixing outstanding issues or deferring them to a later release. The team also reviewed the upcoming schedule, highlighting the July 21 deadline for Self Contained Change proposals and the August 11 deadline for both branching Fedora Linux 45 from Rawhide and the testable completion checkpoint.

Learn more about the Internationalization team.

EPEL

This week, EPEL focused on infrastructure improvements and package maintenance, prominently featuring a proposal for EPEL 11's minor version design that was also discussed in the weekly meeting. To prevent private mirroring errors, the proposal suggests keying URLs off the CentOS $stream variable rather than the RHEL $releasever_minor variable, though this first requires RHEL derivatives to stop improperly defining $stream. In package news, an accidental soname change in ImageMagick broke dependencies in EPEL-8 and EPEL-9, but patched builds have been published and are awaiting testing karma. Additionally, a slightly incompatible update replacing p7zip with 7zip is pending further discussion in upcoming meetings.

For contributors, feedback is requested on a planned migration to libgit2 v1.9 for EPEL 9 and 10 to resolve multiple CVEs; the maintainer plans to submit pull requests to affected packages soon. Other notable updates include CVE fixes for ntfs-3g and a contributed fix to fedpkg that enables feature branch workflows directly from EPEL minor version branches.

Learn more about the EPEL team.

ELN

During the July 21st meeting, the SIG announced that image-builder is now successfully building ELN qcow2 images, with hyperscaler images up next. The ELN mass rebuild is currently in progress following the F45 mass rebuild, presenting an engagement opportunity for contributors to help fix over 40 packages currently failing to build (F45FTBFS). Another contribution opportunity involves providing a ppc64le VM to the upstream retsnoop developer to fix architecture-specific bugs. In broader news, LXQt has been added to Extras in preparation for EPEL 10, python-wheel was dropped from ELN proper, and progress continues on bootc with a Konflux tenant merged and plans to explore composefs native images in the future.

Decisions

• To prevent disruptive surprises, future image change requests (such as altering default partition layouts or dropping firmware) will be filed in the ELN bug tracker and discussed during meetings.
• boot.iso images will now only be created for BaseOS to match CentOS Stream and RHEL, which saves disk space and speeds up composes by over 30 minutes.

Learn more about the ELN team.

Atomic

This week, the Atomic group saw a brief but helpful update regarding system recovery. In a forum discussion on how to reset the root password in Silverblue, a community member highlighted that official documentation is now available for resetting passwords via rescue mode on Atomic Desktops. This provides a standardized and reliable resource for the broader Linux community when troubleshooting locked atomic systems.

Learn more about the Atomic team.

CoreOS

During the CoreOS meeting on 2026-07-22, the team highlighted that the proposal to merge Butane into Ignition has officially entered the FESCo voting phase. As part of this transition, Butane will undergo a procedural freeze to shift active development directly into the Ignition repository, a move expected to greatly improve configuration composability for users. Additionally, the group reviewed the Fedora 45 release schedule, noting that the proposal submission deadline for Self-Contained Changes has passed, with the next checkpoint for retiring orphaned packages scheduled for August 4th.

A significant portion of the meeting focused on a potentially disruptive proposal to increase the default /boot partition size for new installs. Developers raised concerns that older nodes retaining the smaller partition might eventually lose the ability to upgrade, forcing users to reprovision. To prevent users from accidentally clobbering custom data partitions during this process, an action item was created to form a small working group. This group will brainstorm failure scenarios and design safeguards against inadvertent data destruction, presenting an excellent opportunity for contributors to get involved in shaping safe upgrade paths and documentation.

Learn more about the CoreOS team.

AI & ML

This week, the AI & ML SIG focused on team roster management and establishing infrastructure for AI agent skills development. A notable change in membership occurred as a contributor requested to step down from the SIG due to time constraints and LLM-related burnout (Issue #36). On a broader scale, the group is actively working on standardizing AI capabilities using the Agent Skills specification, which allows guided, agent-neutral skill definitions to be shared, improved, and used by any model.

To support this growing initiative, the SIG successfully established a new "Skills Reviewers" sub-team to create, review, and curate shared AI skills in the skills-library repository (Issue #31). The necessary infrastructure, including a new FAS group and a linked Forgejo team, has been fully deployed and seeded with initial volunteers. For contributors looking to get involved, there is an immediate opportunity to provide feedback on the initial draft of the human reviewer guidelines, which has just been submitted as a pull request.

Decisions

• Establishment of the Skills Reviewers Team: The SIG officially created the skills-reviewers sub-team in FAS and Forgejo, granting them write access to the ai-ml/skills-library repository. A lightweight review process was instituted, requiring at least one reviewer approval before merging skill PRs (Issue #31).
• Membership Update: Proceeded with the removal of salimma from all AI/ML SIG access control lists (FAS, Forgejo, and Discourse) per their request to step away from the group (Issue #36).

Learn more about the AI & ML team.

RISC-V

The Fedora 45 mass rebuild is actively underway, with core components like binutils and annobin completed, and GCC 16 and Python 3.14 currently in progress. The team is managing build times across 19 RISC-V builders, noting intermittent build failures on RVA23 hardware and system hangs on P550 boards during Rust builds—though a recent SiFive firmware update resolves the latter. To improve build infrastructure, new high-RAM Titan boards from Arace are arriving, and contributors can help optimize Koji builder profiles to automatically route heavy packages to these faster nodes. Meanwhile, the transition from the K3 vendor kernel to Fedora RISC-V "omni" kernels continues, supported by updated documentation for K3 bootstrap and Milk-V Jupiter.

In broader ecosystem news discussed during the July 21 SIG meeting, PR 778 was merged into upstream rhboot/shim, paving the way for proper signed shim packaging in future releases. Additionally, the team is conducting virtualization testing on remote K3 hardware (including OVMF firmware tests) and engaging in technical discussions with Qualcomm engineers regarding a hardware-probing syscall to detect RISC-V extensions.

Decisions

• The team will delay switching the mass rebuild tracker over to F45 until the GCC 16 rebuild is fully complete.
• Despite upstream progress on shim, the SIG will continue using the current standalone shim-unsigned-riscv64 package for the time being to ensure boot stability while the official Fedora packaging is sorted out.

Learn more about the RISC-V team.

Security

This week, the Security SIG focused heavily on aligning Fedora's security documentation with the EU Cyber Resilience Act (CRA) requirements (Ticket #14). During their weekly meeting, the team discussed creating a unified SECURITY.md file that designates Red Hat as the formal CRA steward while maintaining Fedora's community security processes. To improve visibility, contributors proposed surfacing these new policies and a standard security.txt file on Fedora's main marketing sites once completed (Ticket #16).

The group is also working on formalizing private vulnerability reporting channels and embargo processes. Ongoing discussions include setting up a secure Bugzilla component for incoming package and platform reports (Ticket #17), establishing Fedora representation on the private linux-distros mailing list alongside a pre-disclosure agreement (Ticket #13), and potentially creating a Fedora Badge to act as a "hall of fame" reward for external security researchers who submit valid reports (Ticket #18).

Decisions

• The SIG will use Ticket #14 to document the overarching CRA compliance plan and spin off individual Forgejo tickets for each of the six specific CRA guideline items to allow for parallel work.
• New security documentation will temporarily be hosted in the forge/security/docs repository to prevent bureaucratic delays while drafting the content.

Learn more about the Security team.

Go

This week, the Go packaging community discussed the introduction of docker-credential-helpers to Fedora. In a thread about packaging the application, contributors shared guidance on handling empty vendor archives and properly configuring CGO_CFLAGS and GO_LDFLAGS using macros to correctly build the pass and secretservice helpers. Additionally, an excellent contributor engagement opportunity has arisen: a call for reviewers and sponsors was made for a new contributor who has successfully recreated the SRPM to adopt the orphaned fx package and is currently awaiting a package review.

Decisions

• When packaging Go applications with empty vendor archives, spec files should retain the standard vendor macros to ensure consistency across Go packages and future-proof against new dependencies.
• An empty modules.txt warning from rpmlint (caused by a lack of vendored modules) is not considered a blocker for package approval.

Learn more about the Go team.

Perl

The major focus this week is the Perl 5.44 upgrade, which has been approved by FESCo. A dedicated f44-perl build-root has been created for the delicate process of bootstrapping core modules. To avoid disruptions, contributors are explicitly instructed not to build anything into this new build-root, though they may freely continue pushing upgrades to Rawhide in parallel. In other ecosystem news, a rebuild for MySQL 9.7 was initiated for perl-DBD-MySQL, and perl-Coro-Multicore was manually patched to resolve an atfork_child naming collision with Perl 5.43.2+. Several routine version bumps were also merged for packages like perl-HTTP-Message and perl-ExtUtils-MakeMaker-CPANfile.

Decisions

• A pull request to build perl-HTTP-Daemon with Module::Build on RHEL was rejected and closed. Maintainers decided against carrying custom, untested patches in the repository, opting instead to strictly follow upstream development.

Learn more about the Perl team.

Python

Due to an incompatible ABI change in the Python 3.15.0b4 release, the team initiated a targeted rebuild of approximately 750 Python packages with extension modules in Rawhide. The rebuild took place in a dedicated side tag and experienced some delays due to slow s390x builders, culminating in a massive Bodhi update. The rebuild was officially completed on July 25, and normal Rawhide package builds have now resumed.

Maintainers of the roughly 30 packages that failed to rebuild during this process are asked to investigate and fix their builds in the side tag. The remaining failing packages are being tracked in a dedicated Bugzilla ticket (PYTHON3.15b4), presenting a clear opportunity for contributors to help get the remaining packages updated for the new Python 3.15 ABI.

Decisions

• Contributors were instructed to temporarily halt building Python packages with extension modules in Rawhide to avoid disrupting the side-tag rebuild and testing process.
• As of July 25, the side tag was successfully merged, and the temporary freeze on Rawhide builds for these packages was lifted.

Learn more about the Python team.

Other Discussions

• Hummingbird Community Meeting - 23 July 2026 discussed the agenda for their upcoming meeting. Topics included AI's impact on open source, maintainer overload, and utilizing "factory" patterns for automated PRs to ensure contributions meet project standards.
• In How the Fedora 45 Sausage is Made, Simon de Vlieger shared a blog post detailing the process of producing Fedora, from packages to final artifacts like ISOs and disk images.
• A Change Proposal to use Sequoia for OpenPGP verification sparked a debate. The proposal suggests introducing an %openpgpverify macro to replace GnuPG with Sequoia, but developers strongly argued for keeping the existing %gpgverify macro name to avoid massive ecosystem churn and API/ABI breakage.
• The Shadow Stack by Default on x86_64 Change Proposal aims to enable hardware-enforced protection against ROP exploits. Discussions highlighted the need for i686 builds in testing repositories and clarified QEMU/libvirt support for the feature.
• A discussion on i686 removal - easy win set proposed adding ExcludeArch: %{ix86} to roughly 3,400 leaf packages to save build resources. While some suggested an opt-in approach for i686 instead, the consensus leaned towards moving forward with this opt-out approach via a formal Fedora 46 Change Proposal.
• The Disable in Kernel Crypto Userspace API (Phase 1) Change Proposal seeks to restrict the deprecated API to known users before upstream removes it entirely. Maintainers raised concerns about losing rootless access to LUKS containers for non-AES ciphers and VeraCrypt support, though the change is primarily about preparing users for the inevitable upstream removal.
• Adam Williamson announced a new feature for on-demand openQA testing of dist-git pull requests. Contributors can now comment /openqa test on a PR to trigger tests on the corresponding Packit scratch build, with results reported directly back to the PR.
• The RelocateRpmRepoConfigsToUsr Change Proposal intends to move RPM repository configurations from /etc to /usr. Adam Williamson raised concerns that this could disrupt existing workflows and scripts, suggesting it be escalated from a self-contained to a system-wide change.
• A Change Proposal for Web Based Remote Installation Support for Atomic Desktops aims to allow secure remote installations via the Anaconda WebUI. This opt-in tech preview will authenticate users with a PIN over HTTPS, bypassing the need for VNC/RDP clients.
• A targeted rebuild of Python packages with extension modules was announced for Rawhide due to an incompatible ABI change in Python 3.15.0b4. Maintainers were asked to hold off on building affected packages until the side-tag was successfully merged.
• Other discussions included a user trying to release a new version of a package, reminders for the F45 Self-Contained Change Proposal Submission deadline (and a duplicate reminder), complaints about slow s390x builds during the mass rebuild, a Change Proposal for LibreOffice Dictionaries, a review request for dupeguru, a fix for an outdated golang package on koji el8 build machines, questions about GCC plugins packaging for AFL++, inquiries if nextcloud-client is still maintained, a proposal to deprecate low-memory-monitor, an update for IBus 1.5.35, a proposal for Encapsule isolated devel containers, a proposal to switch to the Anaconda WebUI for Fedora Atomic, a proposal to hardcode nss-altfiles in Authselect profiles, a proposal to remove the Authselect NIS Profile, a proposal to enable systemd-oomd and zram swap for CoreOS, a patch submission for libndp, a clarification on why FTBFS bugs are no longer filed between mass rebuilds, a request of exemption for f45-backgrounds, and a request to add a CUDA backend to the Ollama package.

Orphaning packages

• Emanuele Petriglia inquired about the orphaned "fx" package, noting it was rewritten in Go, and successfully recreated the SRPM for review.
• Automated reports listed orphaned packages looking for new maintainers on June 21 and again on July 18.
• Efraim Kaov offered to step up for mcelog package maintenance and co-maintainership since it is outdated.
• The mysql8.0 package is retiring in Rawhide as it reached EOL upstream.
• Gabriel L. Somlo announced orphaning yosys/nextpnr & related packages due to a lack of time and unresponsive co-maintainers.
• A reminder was sent regarding the list of long term FTBFS packages to be retired in August.
• A request was made to unretire sugar packages (sugar and sugar-browse).

Package updates

• The f45-backgrounds package is available, but its initial 12800x12800 image broke KDE Plasma, prompting a resize to 8192x8192.
• An unannounced soname bump for nettle caused FTBFS for multiple packages, leading to a workaround using the nettle3.10-devel compat package.
• Similarly, an unannounced soname bump for openssl-pkcs11 broke rng-tools and the compose process, which was quickly fixed in a side tag.
• InsightTooklit 5.4.6 is coming to rawhide, requiring rebuilds for alizams and petpvc.
• A planned Flint soname bump was postponed because e-antic is not yet compatible.
• A shadow rebase and libsubid SONAME bump was announced, requesting rebuilds for apptainer, buildah, podman, and skopeo.
• The release of jimtcl 0.84 introduced a jimtcl soname bump affecting openocd.
• The Perl 5.44 upgrade has started in a dedicated build-root.

New contributor introductions

• Luca Albrecht

Across the various Fedora working groups, a primary shared focus is the execution of the Fedora 45 Mass Rebuild, which aligns with widespread efforts to modernize core toolchains, system defaults, and developer environments. Another major cross-team initiative is the ongoing infrastructure migration from Pagure to Forgejo, requiring coordination across FESCo, Release Engineering, Design, and Docs. Artificial intelligence and automation have also emerged as a prominent, dual-sided theme: while teams like AI & ML, Security, and Release Engineering are actively developing AI agents to automate nightly compose log analysis and vulnerability scanning, Infrastructure and Release Engineering are simultaneously deploying defensive measures—such as retaining the Anubis system and disabling web-based git blame—to mitigate aggressive AI web scrapers. Finally, there is a strong, unified push toward improving community governance and the contributor experience, evidenced by the drafting of new usage and conflict of interest policies, the creation of the Docs Captain pilot program, and the development of modernized onboarding materials.

Announcements

For Fedora contributors, the Fedora 45 Mass Rebuild has officially started, and maintainers are encouraged to track build failures on Koji. Related to package maintenance, a list of long-term FTBFS (fails to build from source) packages has been published; these packages have failed to build since Fedora 42 and will be retired in early August unless they are fixed or exempted. On a celebratory note, the latest Fedora Podcast (episode 056) highlights the 2026 Fedora Contributor Recognition Program winners, featuring a great conversation with Justin Forbes and Ankur Sinha about keeping the project running and welcoming.

Several new self-contained Change Proposals have also been announced for Fedora 45. The distribution's default databases are slated to be updated to the latest LTS releases, MySQL 9.7 and MariaDB 12.3. The ODBC stack is being modernized to replace static driver registrations with auto-generated configurations using per-driver drop-in snippets. LibreOffice will see two major packaging improvements: the introduction of upstream-sourced hunspell dictionaries for better version syncing, and a switch to HTML-based, noarch help files to significantly reduce repository space. Finally, to simplify Fedora CoreOS provisioning, a proposal aims to enable Ignition to natively accept Butane YAML configurations directly at first boot, removing the need for a separate transpilation step.

Council

During the bi-weekly meeting, the Council reviewed the draft Conflict of Interest Guidelines and agreed to publish the document on Discourse for a two-week public feedback period, offering a key opportunity for community engagement before the rules are formalized. The Council also discussed the upcoming Fedora Forge Usage Policy, focusing heavily on the proposed rules for archiving inactive repositories. To avoid disruptive surprises for existing contributors, the Council formally took ownership of the policy's publication but decided to delay its release until a consensus is reached on how to handle repository archiving. Additionally, members were reminded of an open ticket regarding the Fedora logo license, which will be closed as the license cannot be changed.

On the forums, the discussion surrounding the Fedora Innovation Lifecycle continued with a focus on re-imagining "Initiatives." Members proposed a lightweight, self-managed alternative to the Sandbox process that would allow contributors to showcase multi-release work without strict deadlines or approvals, relying instead on simple "heartbeat" checks to ensure the projects remain active.

Decisions

• The Council will publish the drafted Conflict of Interest Guidelines on Discourse for a two-week public feedback period before making any formal decisions.
• The Council formally took over the finalization and publication of the Fedora Forge Usage Policy, but will resolve the ongoing debate regarding the archiving of inactive repositories before publishing it under the Policy Change Policy framework.

Learn more about the Council team.

FESCo

This week, FESCo processed a massive wave of System-Wide Change proposals for Fedora 45, establishing a clear theme of modernizing core toolchains, system defaults, and developer environments. Significant proposals under review include switching the default Secrets Service to oo7, disabling DNF vendor changes by default, and updating major stacks like LLVM 23, Ruby on Rails 8.1, and MySQL 9.7. During their weekly meeting, the committee discussed the upcoming Forgejo distgit migration, agreeing to wait for a published roadmap to ensure proper community feedback on permissions, push rules, and CI integrations before proceeding.

FESCo also addressed late-arriving changes impacting the mass rebuild schedule. While the GNU Toolchain Update was approved to proceed, the Shadow Stack enablement was postponed due to unresolved concerns about breaking third-party applications and Rust-based packages. Other common work topics this week included infrastructure housekeeping (such as updating election policies and issue templates) and routine package maintenance, including handling non-responsive maintainers and retiring inactive software projects.

Decisions

• Approved the GNU Toolchain Update Change proposal.
• Approved the Grub EFI For Confidential Computing Change proposal.
• Approved the Lazarus with multiple widgetsets Change proposal.
• Approved the LLVM 23 Change proposal.
• Approved a one-off incompatible update request for rust-routinator.
• Approved adding new co-maintainers to the ledger package following the non-responsive maintainer process.

Learn more about the FESCo team.

Workstation / GNOME

In a brief follow-up to the Fedora Workstation Working Group meeting minutes, it was confirmed that the group will be taking a short break from their regular meeting schedule. Due to members traveling to the GUADEC conference and other scheduling conflicts, all meetings for the remainder of July have been called off.

Decisions

• All Fedora Workstation Working Group meetings for July are canceled. The next meeting is scheduled to take place on August 4, 2026.

Learn more about the Workstation / GNOME team.

Server

The Server Working Group held a weekly meeting (with the agenda and summary posted to the mailing list) focusing on release testing, documentation, and the Fedora home server spin-off. To make F45 release testing more accessible for contributors, the team introduced a new project board and ticket system, which will eventually be automated. For the home server spin-off, a contributor volunteered to set up and document a local Kiwi development environment so others can easily join the effort. The group also discussed updating the contributor's guide to remove outdated Pagure links and welcomed upcoming documentation contributions regarding mDNS and Ansible usage on Fedora.

Decisions

• The working group agreed to begin F45 release testing using the newly created ticket system, adapting the tickets as necessary throughout the testing process.
• A server-specific documentation style guide will be drafted to track styling and phrasing decisions that deviate from or add to the main Fedora Docs Style Guide.

Learn more about the Server team.

Infrastructure

The Fedora Infrastructure team kicked off the F45 mass rebuild on July 15th, ensuring autosigning was enabled for the f45-rebuild tag. A significant portion of the week's effort was dedicated to migrating various infrastructure hosts and virthosts to RHEL10, which involved careful timing to minimize builder outages. On the mailing list, the team discussed the effectiveness of the Anubis anti-scraper system. Contributors concluded that Anubis remains absolutely critical for preventing infrastructure outages and managing CPU load, even if some modern AI agents can bypass its proof-of-work challenges.

Operational troubleshooting addressed several immediate issues, including a stalled Bodhi consumer pod that halted Rawhide and ELN updates, PR merge failures on node-exporter, and misrouted EPEL mirrors. The team is also actively improving monitoring by adjusting Zabbix checks and advancing the Forgejo deployment with new metrics templates and foundational work on private issues. Contributors looking to engage can assist with AWS IAM role configurations for projects like Testing Farm and Logdetective, or help refine Apache LoadBalancer timeouts to handle external proxy delays more gracefully.

Decisions

• Anubis will be retained across the infrastructure as a critical defense against web scrapers and bots.
• Autosigning was officially enabled for the f45-rebuild tag to support the ongoing mass rebuild.

Learn more about the Infrastructure team.

Release Engineering

The Fedora 45 Mass Rebuild was a central focus this week, with the tracker ticket coordinating readiness across toolchain updates and a meeting discussion clarifying the standard operating procedure for verifying driving changes before commencing. To improve future rebuilds, contributors are exploring ways to update the mass rebuild scripts so they automatically check Bodhi and skip packages that recently failed gating. In community tooling news, an experimental AI Agent was introduced to autonomously analyze Rawhide nightly compose logs and identify root causes of failures, offering a new way for contributors to help triage issues. Meanwhile, the migration to Forgejo continues, with the kiwi-description repository successfully moved and plans forming to replace Pagure AMQP messages with Forgejo webhooks.

Routine release engineering tasks included resolving git repository unpacker errors, setting up Koji tags for ELN image-builder, and processing side tags for the Perl 5.44 update.

Decisions

• The Robotics Spin has been officially dropped from Fedora Linux 45 and removed from the build configuration.
• The web-based git blame feature in Fedora Package Sources has been deliberately disabled to mitigate massive abuse from AI web crawlers; contributors must now clone repositories and use git blame locally.
• The .composeinfo format was updated to include a release_type field, enabling downstream Beaker automation to distinguish between Beta and Final releases.

Learn more about the Release Engineering team.

Quality

The most significant development this week is the launch of on-demand openQA testing for dist-git pull requests. Contributors can now trigger automated tests by simply commenting /openqa test on a PR, with success or failure states reporting directly back to the interface. In other tooling updates, a compose critical package generation script was merged (with Bodhi integration ongoing), openQA test coverage was extended for KDE and Workstation applications, and UI/UX improvements were applied to the testdays-web platform to clarify when events are ready for result submissions. The "Heroes of Fedora Quality Q2" report was also published to celebrate community contributions.

For ongoing contributor engagement, the QA team is calling for community validation on several new nightly composes. Testers with available time are encouraged to review and submit results for Fedora 45 Rawhide 20260718.n.0, Fedora 45 Rawhide 20260715.n.0, and Fedora-IoT 45 RC 20260713.0.

Learn more about the Quality team.

Design

The Design team is actively preparing for upcoming releases and events, including initial planning for the Fedora 46 wallpaper with community polls focusing on "U"-themed inspirational figures. Emma Kidney published a blog post detailing the new collaborative design workflow used for Flock 2026 branding. In other project updates, the team finalized the LoLa AI Package Manager mascot, resolved data issues to generate Flock 2026 YouTube thumbnails, and is working on migrating the fedora-logos repository from Pagure to the Design team's Forgejo space to streamline package updates.

For contributors looking to get involved, there are ongoing efforts to create a Contributor Onboarding Video Series, where the team is currently crowdsourcing opinions on background music. There are also open opportunities to design avatars for Fedora's Matrix bots, including Zodbot, Meetbot, Nonbot, and the new Moderation bot. Furthermore, the team is heavily refining a community onboarding poster to ensure it serves as excellent "rookie reading material" while remaining visually cohesive, accessible, and cost-effective for community members to print.

Decisions

• Community Poster Redesign: During the July 13th meeting, the team decided to remove solid color banners from the community onboarding poster layout. This decision prioritizes core alignment and spacing, improves visual cohesion, and significantly reduces ink consumption for community members printing the materials at their own expense.

Learn more about the Design team.

Docs

The Fedora Docs team is finalizing its migration away from Pagure.io ahead of the platform's July 31 shutdown, urging maintainers to move remaining repositories to Forgejo (Issue #35). Infrastructure and workflow improvements are a major focus this week, with ongoing work to refactor the local docsbuilder.sh preview script to use updated, secure containers (Issue #19) and efforts to implement automated Forgejo Actions CI monitoring to catch silent production site build failures (Issue #53). Additionally, the team is exploring a massive UI/UX overhaul to better support knowledgebase-style content in the Antora theme, and community brainstorming is highly encouraged even for those not ready to write code (Issue #51).

To decentralize documentation maintenance, the team is launching the "Fedora Docs Captain" pilot program (Issue #50). This initiative pairs subject-matter experts with experienced technical writers to revamp documentation for the Kernel, Multimedia, and AI/ML SIGs. Volunteers are actively needed to serve as sponsors or team leads for these pods. In a related effort, a community initiative is underway to consolidate scattered multimedia, hardware driver, and third-party codec documentation into a single authoritative source to improve the new user experience (Issue #58).

Decisions

• Repository settings across all docs/* repositories will soon be updated to enforce new contribution guidelines, requiring contributors to submit pull requests via forks rather than pushing directly to repository branches (Issue #46).
• The "Fedora Docs Captain" pilot program will be timeboxed and evaluated at the Fedora 45 release to determine whether to scale the initiative to other Special Interest Groups or conclude the experiment (Issue #50).

Learn more about the Docs team.

EPEL

This week, the EPEL team focused on package updates, security retirements, and early planning for EPEL 11. Notably, syncthing has been retired from EPEL 8 and 9 due to unfixable security vulnerabilities and SQLite incompatibilities; users are advised to upgrade to RHEL 10 to continue using it. Concurrently, updates for syncthing v2 were pushed to stable for EPEL 10.2 and 10.3. During the weekly meeting, the steering committee also approved incompatible updates for rust-routinator and ffmpeg, with the ffmpeg update planned to land in epel9-next first to allow maintainers time for necessary adjustments.

Looking ahead, early planning discussions for EPEL 11 have begun. A key topic of discussion is addressing feedback from enterprise users who mirror repositories directly by URL (such as with Satellite or Foreman) and were disrupted by recent changes to metalinks and baseurls. A proposal is currently being drafted to remediate this URL structure in EPEL 11—and potentially implement it smoothly in EPEL 10 as well—to ensure a more predictable experience for users.

Decisions

• Approved the incompatible update request for rust-routinator (Issue #369).
• Approved the incompatible update for ffmpeg 5 to 7, which will be introduced in epel9-next first (Issue #370).

Learn more about the EPEL team.

ELN

In the ELN meeting, the primary discussion focused on the delayed enablement of bootc images for Fedora ELN. Progress has been slow due to review bottlenecks on the Konflux side, prompting suggestions to move all ELN container builds into Konflux. By standardizing the pipeline and removing bootc as a special case, the group hopes to resolve structural build issues and improve the overall RHEL-on-Konflux experience.

The team also clarified the roadmap for future bootc images, noting that the Fedora ELN bootc image (to be hosted at quay.io/fedora/eln-bootc) will serve as a precursor to upcoming CentOS Stream 11 builds. Because CentOS Stream 11 is still in early bootstrap, contributors agreed to schedule a dedicated conference call to coordinate the integration of Konflux, pungi, and bootc configurations across both the Fedora and CentOS Stream ecosystems.

Learn more about the ELN team.

Atomic

During the Fedora Atomic Initiative meeting, progress was shared regarding Enterprise Linux Next (ELN) base images. Contributors are currently waiting on reviews for Konflux tenant configuration merge requests that will switch the setup from minimal-plus to standard, which is required to complete the ELN base image builds. Once merged, the team will need to determine the process for pushing the resulting base image to the correct namespace, presenting an area where contributors familiar with Konflux might be able to assist.

In broader news relevant to the Linux community and bootc users, an initiative is underway to split Ignition into a standalone RPM, allowing it to be included in more workflows such as bootc container image builds. Additionally, a Fedora 45 change proposal was highlighted that aims to provide native Butane configuration support directly in Ignition. If implemented, this will eliminate the need for the intermediate Butane-to-Ignition conversion step, allowing users to use Butane directly for their instances.

Learn more about the Atomic team.

CoreOS

During the CoreOS meeting, the team reviewed the Fedora 45 Release Schedule and warned that the ongoing Mass Rebuild may cause temporary turbulence and CI breakages in the rawhide stream. The change proposal to enable systemd-oomd and swap on Zram by default was finalized and moved forward in the release process. In other community news, contributors are seeking reviews on an Afterburn pull request designed to make logic less Azure-specific, and members discussed strategies for better surfacing bugs caught in the next stream before they reach stable releases.

A significant portion of the meeting focused on the ongoing need to increase the /boot partition size for new installs, an issue recently highlighted by failing tests on aarch64 rawhide. Acknowledging the complexity of this migration, several contributors volunteered to form a dedicated working group to address it, offering an excellent engagement opportunity for those interested in helping architect a solution for core system storage limits.

Decisions

• The team approved the systemd-oomd and swap on Zram change proposal and officially marked it ready for the Fedora Change Wrangler.
• A dedicated working group was formed to tackle the /boot partition size limits, with an initial action item to draft a comprehensive list of requirements for the migration effort.

Learn more about the CoreOS team.

Kernel

This week, a user reported an issue with the Rawhide nodebug kernels setup process. The repository configuration file required to set up the repo on new systems is currently missing from the server, causing the standard wiki instructions to fail.

While the .repo file is missing, the actual repositories are still present and intact on the server. This presents a quick engagement opportunity for infrastructure or kernel contributors to restore the missing file and fix the setup process for the broader community relying on these nodebug kernels.

Learn more about the Kernel team.

AI & ML

The AI & ML SIG is making strides in integrating AI into Fedora workflows, highlighted by a new proof-of-concept AI agent analyzing Rawhide nightly composes to identify failure root causes. To support these efforts, the SIG is formalizing an AI skills library and has established a new "Skills Reviewers" sub-team to curate shared, agent-neutral AI skills. On the hardware front, the SIG is addressing the growing interest in shared GPU infrastructure by initiating a draft for an Acceptable Use Policy to define trust models and access controls for Fedora's GPU hardware.

There are several immediate opportunities for contributors to get involved. The SIG is actively seeking maintainers for new llama.cpp backends (with a priority on Vulkan) and testers for the newly introduced pi-coding-agent in Rawhide, particularly on non-x86 architectures like aarch64. Additionally, developers interested in LLMs are encouraged to help expand the AI Skills Library or integrate other local LLMs into the existing coding agents.

Decisions

• Skills Reviewers Team: The SIG officially approved the creation of a skills-reviewers sub-team on Forgejo. Seeded with six initial members, the team will manage the ai-ml/skills-library repository and implement a lightweight review process requiring at least one approval before merging new Agent Skills. (Ticket #31)
• GPU Infrastructure Access: It was agreed that existing GPU infrastructure (gpu01) will be strictly earmarked for CI purposes during the F45 release cycle. General access requests will be temporarily closed as wontfix while the hardware remains in a "transitionary/exploration" phase and the formal Acceptable Use Policy is drafted. (Ticket #34)

Learn more about the AI & ML team.

RISC-V

The Fedora 45 rebuild for RISC-V is currently about 25% complete, and the team continues to make steady progress resolving remaining issues on the Fedora RISC-V tracker. Hardware capacity has expanded, with four RVA23 units—including community-contributed hardware—now active in the Fedora RISC-V Koji. Furthermore, technical discussions are actively underway with hardware vendor SpacemiT's Linux team to improve virtualization support and resolve known issues.

For those looking to get involved with the group, requirements for a potential RISC-V intern have been drafted and published, offering a new engagement opportunity for prospective contributors.

Decisions

• The team decided to optimize the F45 rebuild by importing approximately 50% of "noarch" packages directly from the primary Koji into the RISC-V Koji, which will save significant time and compute resources.

Learn more about the RISC-V team.

Security

The Security SIG held a meeting this week primarily focusing on secure development practices and how end-users can verify Fedora's security posture. The group highlighted existing safeguards like the package review process and mandatory hardening compiler flags, while also discussing the integration of automated vulnerability management tools. Notably, the conversation covered the new ProdSec scanner (Trustshell) and Hummingbird, a tool that uses AI to scan for CVEs and automatically generate pull requests for Rawhide packages. The team also explored the potential of mapping Fedora's practices against the OpenSSF baseline checklist.

Contributors looking to get involved can review the meeting agenda and logs on the forum. Several topics were deferred due to time constraints, providing an excellent opportunity for asynchronous engagement on the SIG's issue tracker, particularly regarding the Cyber Resilience Act (CRA) requirements and Linux-distros mailing list policies.

Decisions

• The discussion on aligning Fedora's security documents with the "Vulnerability and Incident Policy" CRA requirement (Ticket #14) was postponed to next week's meeting.
• The Linux-distros discussion (Ticket #13) was deferred to be handled asynchronously on the issue tracker.

Learn more about the Security team.

Gaming

David Campbell announced the release of Hnefatafl Copenhagen 6.1.1, a strategic board game with historical roots similar to Chess or Go. Linux gamers interested in trying it out can install the game by enabling the dcampbell24/hnefatafl-copenhagen Copr repository. Once installed, it can be launched directly from the application menu or by running hnefatafl-client in the terminal.

Learn more about the Gaming team.

Go

In a recent discussion, Tadej Janež sought advice on packaging docker-credential-helpers for Fedora. Because the upstream project includes macOS and Windows-specific helpers (osxkeychain and wincred), the conversation focused on excluding these unnecessary modules and their dependencies from the vendor tarball using go2rpm. Mikel Olasagasti provided a solution to remove the directories prior to archiving, which successfully cleared out the unneeded dependencies.

This process resulted in an essentially empty vendor archive, prompting Tadej to ask follow-up questions about handling SPEC file macros that operate on empty vendor sources and resolving an rpmlint error caused by a zero-length modules.txt file. Contributors with Go packaging experience are encouraged to join the thread to help resolve these final packaging hurdles.

Decisions

• The package will use pre_commands and exclude_directories in the go-vendor-tools.toml configuration to explicitly remove the OS X and Windows credential helpers (osxkeychain/ and wincred/) from the vendor archive and licensing checks.

Learn more about the Go team.

Perl

This week, the Perl group focused heavily on routine package maintenance and version updates. Michal Josef Špaček successfully merged multiple version bumps, updating perl-Test-Inter to 1.13 across PR #9, PR #10, and PR #11, as well as updating perl-HTTP-Date to 6.08 in PR #5, PR #6, and PR #7. In broader Linux community news, Michal Schorm submitted a patch to fix a Failure to Build From Source (FTBFS) in perl-SDL caused by underlying code behavior changes, which was subsequently merged by Hans de Goede. Additionally, contributors looking to engage with RHEL compatibility can review Yaakov Selkowitz's newly opened pull request for perl-HTTP-Daemon to build the package using Module::Build on RHEL.

Decisions

The group approved and merged the FTBFS fix for perl-SDL. They also officially accepted the version bumps for perl-Test-Inter (1.13) and perl-HTTP-Date (6.08) across their respective repository branches.

Learn more about the Perl team.

Other Discussions

• Hummingbird Community Meeting - 23 July 2026: Laura Santamaria announced the next Hummingbird community meeting and gathered agenda items, including a demo of Project Bluefin's factory, Red Hat Hardened Images, and agentic frameworks like Hive.
• If you're on the kernel mailing list (LKML), aren't you concerned about AI?: A user raised concerns about the surge of AI-generated code in the Linux kernel and the potential for plagiarism or training data injections, prompting a reference to Linus Torvalds' stance on the matter.
• Fedora AI/ML SIG Meeting (2026-07-16): The AI/ML SIG discussed recruiting maintainers for the llama.cpp backend, testing pi-coding-agent, establishing a Skills Reviewers sub-team, and navigating the governance of GPU hardware access for CI purposes.
• F45 Change Proposal: Enable Shadow Stack by Default on x86_64 (system-wide): A proposal to enable hardware-enforced Shadow Stack protection by default for C, C++, and Rust applications on supported x86_64 machines in Fedora 45 sparked discussions about backward compatibility, hardware support, and implementation details.
• F45 Change Proposal: Disable Vendor Change by Default (system-wide): A proposal aims to configure DNF5 to prevent automatic package vendor changes during transactions by default, ensuring system stability while allowing explicit vendor transitions via configuration rules or command-line flags.
• Looking for zig co-maintainer for Fedora and EPEL: The maintainer of the Zig package requested help, especially during release cycles and for EPEL, and received an offer of assistance for ARM64 bootstrapping and fixes.
• Help needed with matrix-synapse: A maintainer asked for help building the latest version of matrix-synapse on Fedora 44 and older, noting that an ongoing package review is currently blocking progress.
• F45 Change Proposal: LibreOffice html help (self-contained): A proposal to switch LibreOffice's embedded help system to HTML files distributed as noarch packages aims to save repository space, prompting brief discussions on how to handle systems without a web browser installed.
• Non-responsive packager check for @sham1: A non-responsive maintainer process was initiated for the ledger package, but the maintainer quickly replied, apologizing for their absence and promising to catch up on their packages.
• Non-responsive maintainer: crosa: A user initiated the non-responsive maintainer process for Cleber Rosa regarding Avocado-VT related packages, which are currently blocking Python 3.14 compatibility in Fedora 43.
• Other discussions included a list of long term FTBFS packages to be retired, an RFC on Prometheus exporters naming and configuration, an F45 proposal for LibreOffice Dictionaries, a strategy for i686 removal of leaf packages, a request to unretire sugar packages, and the announcement of on-demand openQA testing of dist-git PRs.

Orphaning packages

• Orphaning xset and xrdb: Peter Hutterer announced the orphaning of the xset and xrdb packages, inviting anyone who still has a use for them to take over maintenance.

Package updates

• Orphaned package wavemon updated to 0.9.7: A user provided an updated COPR build for the orphaned wavemon package (version 0.9.7) for Fedora 44, offering occasional future builds without committing to long-term maintenance.
• z3 soname bump: Jerry James announced an upcoming soname bump for z3 version 5.0, which will require rebuilding opam and prusa-slicer.
• Node.js rolling stream: upgrade path for current nodejs22: A discussion was started regarding the upgrade path for users currently on the nodejs22 stream in F44/Rawhide as the project transitions to a metapackage approach.
• Flint soname bump: Jerry James announced an update to flint version 3.6.0, which includes a soname bump requiring rebuilds for several dependent packages like Singular and polymake.
• libupnp soname bump: Gwyn Ciesla announced an upcoming upgrade for libupnp to 22.0.3 in Rawhide, confirming that dependent rebuilds will be handled.

New contributor introductions

• Mohab Soliman, a mechatronics engineer from Egypt with experience in 3D printers and FreeCAD, introduced themselves to the 3D printing SIG and asked for guidance on contributing.
• Jesus De Los Reyes Larraga, a QA/platform engineer, introduced themselves, offering their expertise in infrastructure, automated testing, and various programming languages to contribute to the ecosystem.
• Philip Czarnik, a software developer from Germany with experience in Angular, Java, Python, and C/C++, introduced themselves and expressed interest in volunteering 2-4 hours to start contributing.

Across the various Fedora teams, the primary focus is squarely on preparations for the upcoming Fedora 45 release, driven by the impending July 15th mass rebuild and critical change proposal deadlines. Concurrently, a massive, project-wide infrastructure migration is underway as multiple groups transition their repositories, issue trackers, and CI/CD pipelines away from legacy systems like Pagure.io toward Forgejo and GitLab. Security and system stability also remain top priorities, highlighted by the enforcement of mandatory 2FA for packagers, active patching of high-severity CVEs in groups like EPEL and Perl, and proposals to gate stable release updates on reverse dependency checkers (rmdepcheck). Finally, there is a strong, unified push to improve contributor onboarding and cross-team collaboration through standardized documentation, centralized Kanban boards, and the restructuring of community governance, such as the formalization of the new Atomic SIG and the proposed AI Working Group.

Announcements

The Fedora Council has paused the Community Initiatives process effective immediately, noting that the current framework has proven ineffective for surfacing new ideas. Consequently, the AI Developer Desktop proposal has been closed as an official initiative, though independent exploration and collaboration within the community are still highly encouraged. While existing approved initiatives (Fedora Forge, Atomic, and Docs 2026) will continue their scheduled terms, the Council is actively seeking community feedback on a proposed "sandbox" lifecycle process to better evaluate and champion future innovations in a more open, transparent way.

For Fedora 45 contributors, several critical deadlines are approaching to ensure a smooth release. The F45 Mass Rebuild is scheduled to begin on July 15, 2026; maintainers needing to exclude packages must add a noautobuild file to their dist-git repositories. Also due on July 15 is the keepalive deadline for Spins and Labs, requiring maintainers to acknowledge their tracking tickets and ensure packages are up to date to guarantee inclusion in the upcoming release. Finally, a list of long-term FTBFS (Fails To Build From Source) packages failing since F42 has been published; these will be retired around August 5 unless maintainers intervene to fix them or request an exemption from FESCo.

Council

The Council discussed the Draft Council Proposal for the Fedora Innovation Lifecycle (also tracked in Ticket #564), which aims to create a structured pathway for experimental features, though some members raised concerns about potential process overhead. In other community news, the Council is exploring Open Collective for external fundraising targeting the Fedora Linux 45 cycle, seeking to address moderator burnout by formalizing support and escalation pathways, and reviewing the Authorized Analytics Volunteer Agreement to safely manage community health data under GDPR. Additionally, a recap of the 2026 Strategy Summit was published, highlighting discussions on governance, engineering, and community initiatives, while a ticket regarding FESCo election voting rights was closed and deferred to FESCo.

On the infrastructure and legal side, updates were debated for the Fedora Forge usage policy regarding repository archiving, and AI agent context was merged into the Council Tickets tracker. Legal and trademark discussions continued regarding FedoraCVE.org, 3rd-party community sites, Red Hat's EU CRA Stewardship proposal, and confusing Weblate Terms & Conditions for translators, where it was affirmed that the Fedora Project Contributor Agreement takes precedence. Finally, the Council agreed to migrate the historical Fedora Budget repository and acknowledged the need to enhance Fedora's public-facing presence.

Decisions

• Fedora Atomic Naming: The Council approved the use of the "Fedora Atomic" name for bootable container base images of Fedora.
• Provenpackager Revocation Disclosure: The Council decided not to publicly disclose the confidential details or voting record of a past provenpackager revocation incident, opting instead to focus on improving the project's Conflict of Interest policy to prevent future governance issues.

Learn more about the Council team.

FESCo

This week, FESCo focused on reviewing upcoming Fedora 45 Change Proposals and refining packaging policies. Key community discussions centered around disabling DNF vendor changes by default, enabling Shadow Stack on x86_64, and adding Stratis storage support to Anaconda. During their weekly meeting, the committee postponed discussions on the Forgejo dist-git migration and the Engineering representative's responsibilities to gather more input. Furthermore, FESCo is seeking volunteers and feedback for an upcoming proposal to make 2FA mandatory for all packagers, following the recent enforcement and grace period announcement of 2FA for provenpackagers.

Decisions

• Cryptography Libraries: Dropped the signoff requirement from the defunct "Fedora crypto team" for new cryptography libraries. FESCo will act as the gatekeeper until a new public review process is established.
• ELN Draft Builds: Permitted the ELNBuildSync (EBS) service to use and promote draft builds in Koji side-tags inherited from eln-build for ELN rebuild batches.
• Non-responsive Maintainer: Approved adding ankursinha and jflory7 as additional admins to the ledger package.
• Change: Lazarus with multiple widgetsets: Approved the proposal to offer the Lazarus IDE built with multiple widgetsets.
• Change: LLVM 23: Approved the system-wide update of all LLVM sub-projects to version 23.
• Change: Grub EFI For Confidential Computing: Approved the introduction of an independent, minimal GRUB bootloader package for UEFI to quickly boot Unified Kernel Images (UKI).

Learn more about the FESCo team.

Mindshare

During the Mindshare Committee meeting, members highlighted the impending shutdown of Pagure.io at the end of the month, urging contributors to migrate any remaining repositories to avoid disruptions. The committee also reviewed a funding request for All Things Open 2026, noting a need for more local community engagement and outreach to staff the event before approving the budget. Meanwhile, on the forums, the Polish Fedora community discussed their upcoming infrastructure migration and confirmed that their continued use of Fedora domains and logos complies with the project's Community Sites and Accounts trademark guidelines.

Decisions

• Assigned new term owners for the committee's charter areas: @theprogram will lead Regional Event Support, @t0xic0der will lead Digital Ambassadorship, and @jnsamyak will lead the Recognition Service.
• Decided to hold an asynchronous ticket vote to select the Fedora Council Representative, with @t0xic0der and @jnsamyak running as candidates.
• Deferred the budget vote for All Things Open 2026 pending further outreach to identify and include more local attendees.

Learn more about the Mindshare team.

Diversity & Inclusion

During their weekly meeting, the DEI team reviewed early survey feedback from the 2026 Fedora Mentor Summit, noting that the topic-based mentor lunches were highly praised, though ambient noise levels were a concern to address for next year. In infrastructure news, the team successfully completed their migration to Forgejo and is currently updating their issue templates to match the new platform. The team also concluded a discussion regarding age verification legislation, deciding that any official project-wide stance falls under the purview of the Fedora Council rather than the DEI team.

Planning is officially underway for the 2026 Fedora Week of Diversity, which is targeted for October. The team is organizing a 2-3 hour virtual event featuring short 10-20 minute talks and is currently brainstorming an overarching theme, with "Respect the Culture" as an initial proposal. There are immediate opportunities for contributors to get involved with the event by volunteering for speaker management, event logistics, content marketing, and design roles.

Decisions

• Approved Mat H (@theprogram) as a new official member of the DEI Team.
• Agreed to format the 2026 Fedora Week of Diversity as a short virtual event and transition execution planning to its dedicated repository.
• Decided to close the age verification policy discussion, deferring any official project statements to the Fedora Council.

Learn more about the Diversity & Inclusion team.

Workstation / GNOME

This week, the Workstation Working Group focused heavily on desktop stability and upcoming upstream improvements during their July 7 meeting. Key technical discussions highlighted the need for better GNOME Shell reliability during power management events and GPU resets, particularly on AMD and hybrid graphics systems. The group also debated desktop crashes caused by inotify instance exhaustion—likely tied to web process leaks in Epiphany—and plans to consult the Linux UAPI Group for a resolution. On the feature side, GNOME Shell is adopting SVG cursor support to eliminate blurry pointers on high-resolution displays, and progress continues on integrating voice control (Anthony) with IBus.

In the community forums, a user started a discussion regarding the new in-kernel NTFS driver (NTFSPLUS) merged in Linux 7.1. The user noted that the driver is currently disabled in Fedora's kernel configuration and inquired if there are plans to enable it as a module or by default, replacing the existing ntfs-3g symlink.

Decisions

• The Working Group agreed to consult the Linux Userspace API (UAPI) Group to help resolve the ongoing inotify resource management issues.
• Matthias Clasen will engage with the upstream release team to monitor new package dependencies and will advocate for rearchitecting Mutter to better survive GPU resets.
• Due to member unavailability during the first half of August, the group decided to adjust the schedule for upcoming meetings.

Learn more about the Workstation / GNOME team.

KDE

The rollout of KDE Apps (Gear) 26.04 on Fedora 43 appears to have successfully reached users. Previously, this update was blocked because it required a newer version of the gpgme package (2.0+), which would have introduced a soname bump that conflicts with Fedora's stable release update policies. Recent user feedback confirms that a workaround or solution has been implemented, and the KDE Gear 26.04 update is now actively landing on Fedora 43 systems.

Learn more about the KDE team.

Server

In their July 8th meeting, the Server Working Group focused on streamlining Fedora 45 release testing and expanding server documentation. The team reviewed ongoing pull requests for DNSmasq and PXE boot configuration, noting successful validation for UEFI clients while continuing to troubleshoot legacy BIOS network loading issues. Additionally, the group discussed the initial steps for organizing Kiwi development for the upcoming Fedora home server spin-off, identifying the need for a comprehensive development environment setup guide, and shared various homelab storage use cases involving NFS, Samba, and Syncthing.

To improve community engagement in quality assurance, the group is overhauling its testing tracking by moving to a Kanban-style project board on the Fedora Forge. This new system will feature individual tickets for specific tests, making it significantly easier for community contributors to pick up testing tasks, run them in local virtual machines, and report results for each new Rawhide build.

Decisions

• For release testing, the group will create one ticket per test on a project board, including the build date in the title. Tests will start in a "To Do" column and move to either "Passed" or "Failed." Upon a new build release, the ticket titles will be updated and moved back to "To Do."

Learn more about the Server team.

Infrastructure

The Infrastructure team is preparing for the Fedora 45 mass rebuild starting July 15, which includes enabling autosigning for the f45-rebuild tag. On the monitoring and operations front, the team successfully removed legacy Nagios and collectd systems, fully transitioning to Zabbix, and refined COPR Zabbix warnings to reduce alert fatigue. Hardware maintenance is ongoing, with several RHEL10 virthosts being reinstalled with minimal downtime. Additionally, recent Koji server timeouts caused by wiki scrapers overloading proxies were identified and resolved.

In development news, major progress was made on Private Issues functionality for Forgejo, and CI infrastructure was expanded with new Forgejo Actions runners. To improve code quality, the team merged a pull request to restore pre-commit hooks in the infra/ansible repository, pinning them to hashes and introducing an .ansible-lint-ignore file to allow for gradual compliance. Furthermore, discussions are underway regarding Datanommer PostgreSQL operations, specifically exploring a migration to Kubernetes using CloudNativePG and upgrading to Timescale/PG18.

Decisions

• Squash commits were enabled for the infra/ansible repository.
• The OpenQA memory alert threshold in Zabbix was increased to 95% to reduce unnecessary notifications during heavy loads.
• The copr/certbot role was officially moved to the main ansible/roles directory.
• The openshift-apps playbooks are actively being converted to use the app-actions role, with a significant batch of playbooks successfully migrated and merged this week.

Learn more about the Infrastructure team.

Release Engineering

This week, Release Engineering focused heavily on preparations for the upcoming Fedora 45 cycle, with the F45 Mass Rebuild scheduled for July 15th and the creation of F47 release signing keys underway. Significant infrastructure improvements are also in progress, including the successful production migration of the fedora-scm-requests repository to Forgejo and the ongoing integration of Konflux CI with Fedora's Forgejo using a newly established global bot account. Additionally, Koji tags were configured to allow image-builder to build for ELN, and a script issue preventing the creation of detached signatures for the butane release was resolved.

Contributors should be aware that the web-based git blame feature in Fedora Package Sources has been disabled to mitigate abuse from AI scrapers; users are advised to clone repositories and use git blame locally instead. Maintainers receiving orphaned package warnings for oxygen-icon-theme dependencies can safely ignore them, as this is a known false positive stemming from its migration to kf6-oxygen-icons and will not result in auto-retirement. Finally, multiple packages were unretired, and stalled EPEL requests were processed to keep community packages moving forward.

Decisions

• Fedora 45 Spins: The Robotics Spin will be dropped starting with the Fedora Linux 45 release.
• Koji Policies: Following FESCo approval, the Koji hub policy was updated to allow draft builds for ELN within specific eln-build-side* tags to improve the reliability of ELN rebuild batches.
• Infrastructure Security: Web-based git blame endpoints in dist-git are intentionally blocked due to massive crawler abuse.
• Konflux CI Integration: The team decided to use a global konflux-bot token via Pipelines-as-Code global repository settings rather than distributing secrets to individual tenant namespaces, improving security and simplifying operations.

Learn more about the Release Engineering team.

Quality

The Quality team successfully concluded the Kernel 7.1 test week and is currently reviewing the Fedora 45 change list to plan upcoming test days for major transitions like RPM 6.1, GNOME 51 Alpha, and Stratis Anaconda support. There are several new opportunities for community testing and feedback, including a newly developed GTK4 frontend for DNF5 and a secure automated build workflow for pre-built NVIDIA kernel modules. Furthermore, contributors can now show off their team affiliation using the new Quality group on Discourse, which syncs with FAS and provides a custom bug flair for user profiles.

In testing infrastructure and policy, a major proposal was introduced to gate all stable release updates on rmdepcheck, a reverse dependency static checker designed to prevent updates from breaking dependencies in Fedora and EPEL. Tooling continues to improve, with the openQA dist-git PR test feature nearing production and new event banner features merged into testdays-web. Internally, the team is also discussing process refinements, including experimenting with four-week sprints and maintaining a curated board of accessible issues for new contributors.

Learn more about the Quality team.

Design

The Fedora Design team has finalized the F45 wallpaper and officially launched the Fedora 46 Wallpaper Epic. The F46 design will be inspired by a famous STEM figure whose last name begins with "U," with a community inspiration vote and mindmap session scheduled for July and August. Alongside release artwork, the team is actively developing branding for several community projects, including a lobster mascot for the LoLa AI Package Manager, a logo for the Testing Farm's Artemis provisioning service, and a Mobility SIG logo for the Phosh Tour.

There are several excellent opportunities for community engagement this week. Anyone in the Fedora community is welcome to contribute to the F46 Wallpaper sketches and drafts phase. Additionally, designers can jump into fun, low-pressure tasks like creating an avatar for the Matrix Moderation Bot or helping to illustrate Community Personas that will visually represent the diverse types of Fedora contributors.

Decisions

• The Fedora 46 Wallpaper will be inspired by a famous STEM figure whose last name begins with "U".
• The Community Personas project was converted into a larger Epic to be properly scoped and broken down into smaller tickets during the upcoming sprint.
• The upstream fedora-logos repository will be adopted and moved off pagure.io into the Fedora Design Team space to ensure it is maintained.

Learn more about the Design team.

Docs

This week, the Fedora Docs team focused heavily on structural improvements and cross-team collaboration. A major initiative was proposed to unify Fedora Multimedia Documentation, aiming to consolidate scattered guides on third-party codecs and hardware drivers into a single authoritative source to improve the user experience. To support this and other cross-team efforts, the team is organizing a "Fedora Docs Captain" pilot program with the Kernel, Multimedia, and AI/ML groups to decentralize documentation leadership and pair subject-matter experts with Docs team sponsors. Additionally, efforts to improve contributor engagement are underway, including welcoming a new volunteer writer and restructuring the contributor guides (and its introductory article) into a dedicated, highly visible module on the landing page.

Behind the scenes, several repository alignment tasks were completed to streamline workflows and avoid confusion for existing contributors. The team successfully finalized a standardized issue labeling system and common README format across the organization. Furthermore, all project boards were migrated from individual repositories to the organization level to provide a better overview of ongoing work.

Decisions

• Project Boards: All project boards have been successfully migrated to the organization level, and per-repository boards should no longer be used (Ticket #48).
• Issue Labels: A simplified, standardized set of issue labels (categorized by type, effort, priority, and status) has been finalized and deployed across all repositories within the docs organization (Ticket #40).
• Repository READMEs: A common README format has been approved and successfully implemented across key documentation repositories (Ticket #36).
• Repository Alignment: The overarching repository alignment tracker was closed, with any remaining incomplete subtasks now being tracked in their own dedicated issues (Ticket #18).

Learn more about the Docs team.

Internationalization

During the Internationalization meeting, the team discussed upcoming changes for Fedora 45, highlighting that an initial draft for the LibreOffice Dictionaries change has been submitted. Contributors are encouraged to propose any additional Self-Contained Changes before the July 21st deadline. The group also reviewed the upcoming release schedule, noting the major toolchain updates deadline on July 13th and the mass rebuild starting on July 15th.

To help with ongoing maintenance, a call to action was issued for Fedora 43 bug triaging. Contributors are asked to engage by reviewing the 45 remaining bugs reported against Fedora 43 to either fix them or move them to a later release.

Learn more about the Internationalization team.

EPEL

This week, the EPEL community evaluated a proposal to gate all stable release updates on rmdepcheck, a reverse dependency static checker designed to prevent updates from breaking package installability. While the initiative is generally supported to ensure stability, mailing list discussions highlighted concerns regarding transient CI network failures and the potential burden of fixing dependent packages maintained by unresponsive contributors. Additionally, maintainers are coordinating major incompatible updates to resolve severe CVEs. This includes a planned upgrade of ffmpeg in EPEL 9—which will first receive a 5.1.10 patch before transitioning to version 7.1.5 via epel9-next—and an update to rust-routinator 0.15.2 that removes a vulnerable, off-by-default feature.

Decisions

During the weekly meeting, the steering committee voted to approve a documentation pull request clarifying the policy against building packages against non-default modules. The committee also initiated asynchronous in-ticket voting for the ffmpeg and rust-routinator incompatible update requests to prevent blocking contributors from moving forward.

Learn more about the EPEL team.

ELN

The ELN SIG met on July 7 to discuss significant infrastructure and tooling upgrades. Notably, ELNBuildSync 1.3.2 has successfully migrated from CentOS Stream hosting to Fedora Infrastructure, and FESCo has approved draft build support in EBS, which is currently being prepared for deployment. The Content Resolver has also been ported to dnf5 by new contributor James Troy, cutting run times in half (from 6-7 hours down to 2-3). Additionally, the team is finalizing bootc images and coordinating with release engineering to ensure they are properly synced to Fedora's Quay registry.

To align ELN with RHEL 11 expectations, the SIG is preparing to migrate several image types to use image-builder in the pungi configurations, starting with qcow2 guest images and modernizing the boot.iso. Contributors should prepare for the upcoming Fedora 45 mass-rebuild, which will trigger a flurry of activity to fix build failures. There are also immediate opportunities for contributors to help resolve the remaining ~17 failures and OpenSSL 4.0 porting issues from the recent ELN mass rebuild.

Decisions

• Transition ELN non-cloud images (starting with qcow2 and boot.iso) to image-builder to lead RHEL 11 development, with cloud images to follow pending coordination.
• Publish bootc images to a dedicated quay.io/fedora/eln-bootc repository rather than grouping them with other containers.
• Delay the production deployment of Koji draft build support in EBS until after upcoming maintainer PTO to ensure stability.

Learn more about the ELN team.

Atomic

During their weekly meeting, the Fedora Atomic Initiative discussed ongoing efforts to migrate the fedora-bootc repository to the unified pipeline. While organizational access on the forge is ready, the team must implement a workaround for the Konflux service account token by creating a dedicated FAS account for repository owners to properly restrict namespace access. Contributors also briefly discussed the future of boot media, noting a shared desire for a neutral Anaconda GUI installer capable of pointing to any bootc registry. In the forums, community interest continues to grow around the proposal to create a systemd-sysexts SIG, which aims to build and distribute systemd system-extensions for atomic systems.

Decisions

• Following the Fedora Council's approval of the "Atomic" name, the group officially agreed to formalize the Atomic SIG.
• The team will set up a wiki page for the new SIG and request a dedicated Fedora calendar so contributors can subscribe specifically to Atomic meetings without inheriting events from all other Fedora SIGs.

Learn more about the Atomic team.

CoreOS

During the CoreOS meeting, the team reviewed the upcoming Fedora 45 release schedule, noting the mass rebuild on July 15 and the change proposal deadline on July 21. Contributors discussed submitting official change requests for Ignition Native Butane Support and the Ignition submodule split to increase visibility across the broader Linux community. The team also evaluated enabling UEFI boot and TPM support on AWS. Because requiring TPM would drop support for legacy instance types, they opted to defer TPM enforcement to future unified kernel image (UKI) releases to avoid disrupting existing users.

In community discussions, interest continues to grow around the proposal to create a systemd-sysexts SIG. This Special Interest Group aims to build and distribute systemd system-extensions using Fedora content, providing a new way to extend atomic systems with software that doesn't run well in containers or Flatpaks. Contributors interested in helping set up official builds (likely in Konflux), documentation, and distribution methods are encouraged to join the effort.

Decisions

• The team agreed not to enable TPM support on current Fedora CoreOS AWS AMIs to avoid breaking compatibility with legacy instance types. Instead, TPM support will be applied exclusively to the sealed/UKI images once they are ready.

Learn more about the CoreOS team.

Alternative Images

During the Alternative Images meeting, the project's migration from Pagure to GitLab was reported as complete for both the website and image building. A remaining task—and an opportunity for contributors—is to retire the old Pagure repositories or update their README files to point to the new locations. In broader news relevant to the Linux community, CentOS Stream 9 and 10 are rolling out new Secure Boot certificates and shims. The quarterly image builds were paused to wait for final package updates (such as fwupd for CentOS Stream 9) and will commence next week.

Additionally, CentOS Stream RISC-V repositories are now built, signed, and ready. The team is currently waiting on a CentOS infrastructure ticket to create the necessary targets and tags before they can begin generating the RISC-V images.

Decisions

• The quarterly image builds were scheduled for next week to ensure all new Secure Boot certificates and updated packages are fully integrated.
• The initial RISC-V rollout will consist of two specific images: a generic qcow2 image meant for virtual machines and a raw image designed for P550 hardware.

Learn more about the Alternative Images team.

AI & ML

This week, the AI & ML group announced that pre-built binary NVIDIA open kernel modules are now available for community testing outside of the AI Desktop Remix. On the organizational front, the group is heavily focused on improving contributor onboarding and defining its community structure. Active discussions include evolving the SIG into the "Fedora AI Working Group" to reflect a broader scope encompassing both hardware enablement and open AI best practices, creating a welcoming first-page navigation experience, and establishing a formal "Skills Reviewers" sub-team to curate shared AI skills.

To avoid conflating general community participation with hardware privileges, a proposal is underway to scope gpu01 host access exclusively to the ai-packagers-sig while keeping the main ai-ml-sig open to all interested users. This infrastructure management theme is also reflected in ongoing efforts to clean up GitLab group mappings.

Decisions

• A rewrite of the repository README was merged to better guide new and returning contributors on how to find work, file tickets, and communicate.
• A request for experimental development access to the gpu01 host was closed after clarifying that the machine is strictly reserved for CI testing (such as testing the ROCm stack) rather than personal development.

Learn more about the AI & ML team.

RISC-V

The RISC-V group is currently progressing through the F45 rebuild, which is approximately 20% complete, and preparing for the upcoming F46 mass rebuild expected around July 15. On the infrastructure side, Jason Montleon successfully consolidated the RISC-V kernel repositories, moving builds from GitHub to Copr and integrating 'omni' kernels directly into the RISC-V Koji. Additionally, a proposal has been drafted regarding migrating the RISC-V documentation from the Wiki to Forge, presenting a great opportunity for community feedback and contributor engagement.

During the July 7th meeting, the team highlighted ongoing hardware developments, notably the active investigation of virtualization on RVA23 hardware (SpacemiT K3) alongside upstream QEMU and kernel developers. While there are known issues currently being documented for upstream resolution, hardware capacity is expanding, with a new K3 unit en route to serve as an additional Koji builder. Contributors should also note that general group activity is expected to slow down through July and August due to summer holidays.

Learn more about the RISC-V team.

Security

During the Security SIG meeting (agenda outlined in the forum discussion), the team focused on establishing official Fedora representation on the linux-distros mailing list to better coordinate embargoed CVEs. To support this, the group will draft a formal policy for reading members into embargoed issues to present to FESCo. The SIG also discussed the organization of security documentation, concluding that upcoming systemd and SELinux hardening guides will be published in Fedora's Quick Docs to ensure optimal search engine visibility for end users.

Discussions regarding the Cyber Resilience Act (CRA) and the formulation of a "Vulnerability and Incident Response Policy" were deferred to the next meeting due to time constraints. Contributors interested in shaping Fedora's security policies, managing vulnerability responses, or writing technical security documentation are highly encouraged to join the upcoming meetings and assist with these foundational efforts.

Decisions

• Bugzilla will be used to manage private tickets for linux-distros issues until the new Forge platform fully supports private issues.
• The SIG will draft a formal policy for handling embargoed security information and present it to FESCo for feedback and approval.
• Initial security hardening documentation will be placed in Quick Docs rather than the Security SIG team pages to improve discoverability.

Learn more about the Security team.

Perl

This week's activity in the Perl group focused entirely on package maintenance and security updates. The most critical update for the broader Linux community was the version bump of perl-DBI to 1.650 across multiple branches (PRs 3, 4, and 5), which successfully patched three security vulnerabilities: CVE-2026-14739, CVE-2026-14740, and CVE-2026-14380.

Other routine maintenance included version bumps for perl-WWW-Salesforce to 0.400 and perl-Razor-Agent to 2.88. For contributors managing database dependencies, a pull request for perl-Test-mysqld was merged to utilize -any virtual provides for MariaDB and MySQL, which should streamline future package builds and dependency resolution without causing disruptive surprises.

Decisions

• Security Patches: The group approved and merged updates for perl-DBI to version 1.650 to resolve CVE-2026-14739, CVE-2026-14740, and CVE-2026-14380.
• Dependency Management: The group decided to implement -any virtual provides for MariaDB/MySQL dependencies in perl-Test-mysqld.
• Package Updates: Version bump pull requests were approved and merged for perl-WWW-Salesforce (0.400) and perl-Razor-Agent (2.88).

Learn more about the Perl team.

Python

Elliott Sales de Andrade initiated a discussion on updating Zarr to v3, noting that the current v2 build fails to build from source (FTFBS) on Python 3.15. While an initial mass prebuild attempt a year and a half ago encountered several failures, those underlying issues have since been resolved or the affected packages have been retired.

To successfully move forward with the Zarr v3 update, contributor assistance is currently needed to review the python-donfig package.

Learn more about the Python team.

Other Discussions

• How can we improve the Changes Process?: Discussion continued on improving the Fedora Changes process. Maxwell G summarized the feedback, noting support for both a git-based approach and the current wiki workflow, while highlighting the pain points of split discussions across devel@, Discourse, and other platforms. He proposed focusing first on the discussion process, suggesting keeping initial feedback on the devel list and posting read-only digests to Discourse, and asked for co-owners for a formal FESCo proposal on this matter.
• F45 Change Proposal: Enable Shadow Stack by Default on x86_64 (system-wide): Aoife Moloney announced a proposed change for Fedora 45 to enable Shadow Stack protection by default on supported x86_64 machines for applications built with gcc, clang, and rustc. Christoph Erhardt clarified that this protection applies to all binaries carrying the SHSTK note, regardless of the programming language they were written in.
• Proposal: gate all stable release updates on rmdepcheck: Adam Williamson proposed gating all stable release updates (Fedora and EPEL) on the rmdepcheck reverse dependency static checker to prevent updates that cause unsatisfiable dependencies. The proposal received strong support, with discussions on whether to extend this to Rawhide and Branched, how to handle waivers, and the technical implementation details, leading to a consensus to submit a lightweight FESCo ticket for approval.
• Packages providing Flatpak sandbox escapes via vulnerable MIME Type Handler: Sebastian Wick raised concerns about packages like wine providing Flatpak applications a way to escape sandboxes via vulnerable MIME type handlers that execute arbitrary code. The discussion explored the root causes, the responsibilities of different projects (Flatpak, Wine, Freedesktop), and potential solutions, with Michael Cronenworth agreeing to drop the .desktop file registration in favor of the binfmt-misc handler in the core wine RPM to mitigate the issue in Fedora.
• F45 Change Proposal: Disable Vendor Change by Default (system-wide): Aoife Moloney announced a Fedora 45 change proposal to disable automatic vendor changes in DNF5 by default, preventing packages from silently switching vendors during transactions. The discussion highlighted that while some users prefer the current behavior for testing third-party repos like Copr, the change provides better consistency and safety, especially for derivatives like Fedora Asahi Remix, and still allows explicit vendor changes via command-line options.
• Looking for zig co-maintainer for Fedora and EPEL: Jan Drögehoff sought a co-maintainer for the zig package, especially for EPEL, and Marko Kostic volunteered to help. After some initial issues with FAS account synchronization, Marko was successfully added as a co-maintainer, and Rénich Bon Ćirić also joined to assist.
• Help needed with matrix-synapse: Kevin Fenzi bumped an older thread asking for help with maintaining matrix-synapse, inquiring if there had been any progress on getting Synapse's latest version to build on F44 and below.
• Spins and Labs Keepalive Deadline: 2026-07-15: Aoife Moloney reminded maintainers of Fedora spins and labs to acknowledge their Pagure tickets by July 15, 2026, to confirm their inclusion in Fedora 45. Dan requested and received a ticket for the Cinnamon spin.
• review request - dupeguru - a GUI tool to find duplicate files: Carl Byington submitted a review request for dupeguru, a Python/Qt5 GUI tool for finding duplicate files. Barry asked about Qt6 support, and Carl noted an outstanding upstream pull request for the conversion.
• Looking for a new maintainer for Phoc and Phosh DE packages: Tomi Lähteenmäki sought new maintainers for several Phoc and Phosh packages due to a lack of time. Sam Day volunteered to take over as the primary maintainer for phoc, phosh, phosh-mobile-settings, phosh-tour, and stevia.
• Other discussions included a list of new packages in Fedora Linux, an issue with GCC plugins packaging for AFL++, troubleshooting s390x cloud images hanging on libvirt/qemu, an F45 Change Proposal to adopt PURL Metadata, the Fedora 45 Mass Rebuild Notification, a request for a sponsor for the sckoc package, a request to unretire sugar packages, and the announcement of the Koji 1.36.1 release.

Orphaning packages

• EPEL SIG should clean up their own mess: Leigh Scott expressed frustration over being expected to maintain the EPEL Cinnamon stack, stating it wasn't his responsibility and giving notice to orphan and retire the entire stack. This led to a discussion about appropriate communication and the structural issues with Bugzilla assignments for EPEL packages.
• Orphaning hexchat: Kevin Fenzi announced plans to orphan the hexchat package, suggesting it be retired since upstream was archived in 2024 and it currently fails to build in Rawhide. He recommended users switch to zoitechat, a GTK3 drop-in replacement that recently entered Fedora.
• List of long term FTBFS packages to be retired in August: Miro Hrončok posted the second weekly reminder listing long-term FTBFS (Fails To Build From Source) packages scheduled to be retired from Fedora 45 on August 5, 2026. Dominik 'Rathann' Mierzejewski requested a PR to add mingw subpackages to the gsm package to resolve a dependency issue.

Package updates

• Protobuf update: Petr Menšík provided an update on the Protobuf rebase, noting that he prepared updates for the protobuf-c and protobuf3-c libraries, ensuring compatibility and creating a COPR repository for testing.
• [heads-up] mutter and gnome-desktop3/4 soname version bump for rawhide: Milan Crha coordinated rebuilds for packages affected by the mutter and gnome-desktop3/4 soname version bumps in the GNOME 51.alpha updates. Sam Day assisted by rebuilding phoc, phosh, phosh-mobile-settings, and stevia in the side tag, allowing the update to be successfully pushed to Rawhide.
• libical 4.0 for rawhide (when?): Milan Crha provided an update on the transition to libical 4.0 in Rawhide, listing packages that build successfully, those with available patches, and those with generic build failures. Mamoru TASAKA backported a PR for cairo-dock-plug-ins to assist with the transition.
• [heads-up] gvfs dropped 'archive' and 'afp' in 1.61.1 (rawhide): Milan Crha notified maintainers that gvfs dropped 'archive' and 'afp' support in version 1.61.1, causing build failures for packages like nemo. Leigh Scott quickly rebuilt nemo in the side tag to resolve the issue.
• OCaml 5.5.0 rebuilds: Jerry James announced and completed a mass rebuild of OCaml packages for the update to OCaml 5.5.0 in a side tag, which was subsequently merged into Rawhide.
• RFC: incompatible update for routinator for Fedora and EPEL 9 and 10: Michel Lind issued an RFC for an incompatible update to routinator (version 0.15.2) for Fedora and EPEL to address multiple high-severity CVEs and a path traversal vulnerability. He disabled automatic pushes and submitted a FESCo request for approval.
• Sequoia-PGP updates with PQC support: Fabio Valentini announced updates to sequoia-pgp applications and libraries that include support for Post-Quantum Cryptography (PQC) algorithms following the ratification of RFC 9980.
• gnome-shell 51.alpha update for rawhide changes gnome-shell api to 51: Milan Crha notified maintainers that the gnome-shell 51.alpha update changes the API to 51, requiring updates for several GNOME shell extensions.
• [Scitech]LabPlot rebuild for liborigin update: Alexander Ploumistos requested rebuilds of LabPlot for F43, F44, and F45 following the release of liborigin 3.0.4, and confirmed the removal of obsolete transition tags from version 2.0.0.

New contributor introductions

• Ikar's introduction: Ikar introduced themselves as a software engineer and long-time Linux user looking to contribute around 5 hours a week to Fedora.
• Mohab Soliman's introduction: Mohab Soliman, a mechatronics engineer from Egypt, introduced themselves and expressed interest in contributing to Fedora's engineering and gaming parts.
• Raul Perez' introduction: Raul Perez, a software engineer from Spain, introduced himself and shared his extensive background with Linux and open source, expressing a desire to start with small contributions to Fedora.

Across the various Fedora working groups, the primary focus is actively preparing for the upcoming Fedora 45 release cycle, marked by a large influx of system-wide Change Proposals such as GNU Toolchain updates, Fontconfig 2.18, and the transition to oo7 as the default secrets provider. Concurrently, a major infrastructure modernization effort is underway, with multiple teams—including Infrastructure, Release Engineering, and Docs—coordinating the final stages of the repository migration from Pagure to Forgejo, alongside the adoption of Konflux for unified container builds and Zabbix for system monitoring. On the governance front, leadership has indefinitely paused the Community Initiatives process to design a new Technology Innovation Lifecycle (Sandbox) for incubating large, experimental features. Despite the resulting closure of the AI Developer Desktop proposal, artificial intelligence remains a strong technical focus across the project, with groups exploring local LLM integrations like the "Anthony" voice assistant and expanding AI/ML framework packaging. Finally, security and compliance are key priorities, as teams ramp up policy preparations for the EU Cyber Resilience Act (CRA) and push necessary incompatible package updates to mitigate high-severity vulnerabilities.

Announcements

The Fedora Council has paused the Community Initiatives process, closing the AI Developer Desktop proposal until a new strategic direction mechanism is designed, and is actively seeking community feedback on a proposed Technology Innovation Lifecycle Process (this statement was also cross-posted to the announce and devel-announce lists). In community news, the F44 Election Results have been announced for the Council, FESCo, Mindshare, and EPEL Steering Committee. Additionally, maintainers are urged to review the list of long-term FTBFS (Fails To Build From Source) packages scheduled for retirement in early August ahead of the Fedora 45 branch so they can be fixed or exempted.

A large batch of Change Proposals has been submitted for Fedora 45. System and security updates include enabling Shadow Stack by default on x86_64, switching to oo7 as the default Secrets Service Provider to replace KWallet and GNOME Keyring, and disabling DNF5 vendor changes by default to prevent unexpected package overwrites in multi-vendor setups. Core software updates feature a GNU Toolchain update (GCC 16.2, glibc 2.44, binutils 2.47, GDB 17.2), Ruby on Rails 8.1, and Fontconfig 2.18. Finally, user experience improvements are proposed with Stratis Storage support in Anaconda and a highly customizable Bash Color Prompt 1.0.

Council

The Council made a significant shift in project governance this week by suspending the Community Initiatives process indefinitely. As a result, the Fedora AI Developer Desktop Initiative proposal was closed, though contributors are strongly encouraged to continue this work through collaborative spaces like the AI/ML SIG. Leadership is now directing community feedback toward the proposed Fedora Innovation Lifecycle (Sandbox) to establish a better framework for incubating large, experimental features. In other news relevant to the broader Linux ecosystem, the Council officially approved extending the "Fedora Atomic" branding to encompass Fedora's bootable container base images.

To improve contributor engagement and clarity, a new community policy document was merged to help manage user expectations around volunteer response times. The Council also finalized the F44 Council election interview questions, shifting the focus toward candidates' strategic visions and governance experience. Furthermore, new discussions are underway regarding improvements to Fedora's public-facing presence to better attract new contributors, alongside a forum thread clarifying trademark guidelines for regional community sites migrating their infrastructure.

Learn more about the Council team.

FESCo

This week, FESCo reviewed a large batch of Fedora 45 Change Proposals, including updates to the GNU Toolchain, LLVM 23, Ruby on Rails 8.1, Fontconfig 2.18, Bash Color Prompt 1.0, and libxml2. Major system-wide feature discussions included enabling Shadow Stack by default on x86_64, disabling DNF5 vendor change by default, switching the default secrets service provider to oo7, and adding Stratis storage support in Anaconda. The committee also debated policy and infrastructure topics, such as the upcoming Forgejo distgit migration, handling pre-built binary content in node_modules, and whether to drop signoff requirements from the defunct Fedora crypto team to unblock modern cryptography libraries like aws-lc.

In terms of contributor engagement and process, FESCo is looking for volunteers to co-own an upcoming Change Proposal to make 2FA mandatory for all packagers. During their weekly meeting, members clarified that the proposed "technology innovation lifecycle" (sandbox) process is not intended to bypass FESCo approval. Finally, the non-responsive maintainer process was initiated for the ledger package, opening the door for new co-maintainers to take over.

Decisions

• Council Representative: It was agreed that decathorpe will continue as FESCo's Council representative until the end of his current term.
• ELN Draft Builds: FESCo approved permitting the ELNBuildSync (EBS) service to use draft builds in Koji sidetags inherited from eln-build for ELN rebuild batches. The Kojihub policy will be updated to grant the eln-buildsync user permissions to tag and promote these draft builds.

Learn more about the FESCo team.

Mindshare

This week, the Mindshare group discussed using Fedora trademarks with 3rd party projects. A representative from the Polish Fedora community, which has been active since 2003, sought guidance on compliance regarding their fedora.pl domain, automated emails, logos, and favicons after losing their infrastructure sponsor. Respondents directed the inquiry to the official Fedora trademark guidelines, highlighting that the community's usage likely falls under the allowable provisions for "Community Sites and Accounts."

Learn more about the Mindshare team.

Workstation / GNOME

The Fedora Workstation Working Group discussed "Anthony," a voice-driven desktop assistant utilizing local large language models (LLMs) for task automation and accessibility. The team explored hardware constraints, security improvements—such as transitioning from TCP ports to D-Bus portals for flatpak sandboxing—and leveraging existing accessibility trees. Contributors are encouraged to test the project and help with internationalization efforts by aligning it with IBus speech-to-text initiatives. Additionally, the upcoming Fontconfig 2.18 release was noted, which may require a rebuild of all font packages due to cache format changes.

On the forums, a community proposal to merge GNOME Software and DNFdragora into a single, unified package manager for all Fedora editions was met with skepticism. Respondents highlighted that GNOME Software must remain distro-agnostic, the merger would not suit environments like KDE Plasma, and maintaining a strict separation between GUI application management and CLI package management remains the preferred, less confusing approach for users.

Decisions

• The group decided to explore integrating the Anthony voice control project into Fedora Workstation as a default feature.
• A dedicated meeting will be organized to discuss collaboration between the Anthony project and general IBus speech-to-text efforts.
• The regular meeting schedule will be paused for the month of July to accommodate summer travel and the GUADEC conference, with plans to reconvene in August.

Learn more about the Workstation / GNOME team.

Server

The Server Working Group met on July 1, 2026 to coordinate early testing for the upcoming Fedora 45 release and to advance the new Fedora Home Server spin-off. To proactively catch virtual machine and networking issues, the team is starting F45 Rawhide testing ahead of schedule, with an immediate focus on VM images and NFS client connections. A dedicated project board will soon be established to organize these F45 testing efforts, providing a clear and accessible way for community contributors to get involved.

Significant progress was also made on the Fedora Home Server spin-off. The group finalized the core application stack for the upcoming alpha release, prioritizing essential home lab services, privacy, and self-hosted management. Furthermore, the team discussed the image development process, comparing KIWI and Image Builder. To lower the barrier to entry for new contributors, they opted for a local-first development philosophy, ensuring anyone can build and test the spin-off images on their own machines.

Decisions

• The alpha version of the Fedora Home Server spin-off will initially include Samba, NFS, Mail service (IMAP/POP3 storage), Cockpit, Calendar and to-do server, Apache reverse proxy, and Ansible.
• The working group will use the home server repository to share all configuration data and installation instructions, allowing interested contributors to easily set up their own local image development environments.

Learn more about the Server team.

Infrastructure

This week, the Infrastructure team focused heavily on monitoring modernization, officially removing Nagios and Collectd in favor of Zabbix, while actively refining Zabbix triggers, predictive disk space checks, and SLA structures. Significant progress was also made on OpenShift migrations, including standardizing openshift-apps playbooks to use a new deployment role and migrating ELNBuildSync. Routine maintenance continued with careful RHEL 10 virthost reinstalls to avoid outages, and testing Forgejo 15.0.3 in staging. The team also resolved several minor service disruptions, including a Postorius 500 error caused by missing email bodies and Anubis proxy lockouts.

In the forums, a helpful discussion clarified the roles of Bugzilla, Forgejo, and Dist-Git for users confused by the ongoing transition away from Pagure. Contributors also explored the possibility of shared LLM inference services for community applications like Log Detective, and proposed restoring pre-commit hooks in the infra/ansible repository to gradually improve code quality. For contributors looking to get involved, the ongoing Zabbix template refinements and Ansible playbook conversions offer excellent, low-risk entry points into infrastructure work.

Decisions

• Nagios and Collectd are officially deprecated and are being removed from Ansible and servers.
• Pagure.io will become read-only at the end of July, with Fedora-related projects migrating to the new Forgejo instance (forge.fedoraproject.org).
• Old openQA Proof-of-Concept instances running in AWS will be deleted to save resources.

Learn more about the Infrastructure team.

Release Engineering

The Fedora 45 release cycle is officially ramping up, with the Mass Rebuild scheduled for July 15th and the creation of F47 release signing keys due shortly after. The Release Engineering team is currently reviewing several F45 system-wide changes, including Stratis Storage in Anaconda, Fontconfig 2.18, and disabling DNF vendor changes by default. In broader news, investigations into building a Fedora container base image using Konflux are ongoing, and an updated respin of Fedora 44 featuring Linux kernel 7.1 is planned for the coming weeks.

Infrastructure migrations from Pagure to Forgejo are continuing, prompting active architectural discussions on whether to process fedora-scm-requests using native Forgejo Actions or by extending the existing Toddlers infrastructure. During their weekly meeting, the team also clarified procedures for stalled EPEL requests and coordinated prep work for the upcoming mass rebuild. Furthermore, a significant pipeline improvement was unblocked when FESCo approved a policy to allow draft builds for ELN, which will allow the ELNBuildSync process to safely restart after crashes without prematurely consuming NVRs.

Decisions

• FESCo approved a policy permitting the ELNBuildSync service to use draft builds in Koji sidetags inherited from eln-build for ELN rebuild batches (Ticket #13374).
• The team clarified that users requesting to take over stalled EPEL packages must already be official package maintainers (in the FAS packager group) before they can be added as repository collaborators (Meeting).

Learn more about the Release Engineering team.

Quality

The Quality team saw active discussions and tool developments this week, highlighted by a community proposal to eliminate Fedora's version numbering in favor of automatic, version-less updates. The community largely pushed back on the idea, noting that the current release model is necessary for users who prefer to delay updates for stability, and that rolling-release alternatives already exist. In broader ecosystem news, a new GTK4 frontend for DNF5 called DNF UI has reached its 0.3.x series and is actively seeking user feedback. Behind the scenes, Quality Engineering (QE) advanced their compose-critical package script to an MVP state, progressed on the Dist-git PR test feature, and investigated significant bugs, including a grub2 issue breaking image builds and a haveged update causing boot failures.

There are several immediate opportunities for contributors to get involved in testing. The team is calling for participation in the Linux Kernel 7.1 Test Days (running June 28 to July 4) for Fedora 43 and 44, which was also announced on the test mailing list. Additionally, testers are invited to validate the latest Fedora 45 Rawhide 20260630.n.0 nightly compose to help ensure the stability of upcoming releases.

Learn more about the Quality team.

Design

The Design team is finalizing the F45 default wallpaper following the end of its feedback period, and is actively working on several branding initiatives, including simplified icons for Fedora Messaging tools, Artemis, and various Matrix bot avatars. Infrastructure and asset management were also key topics, with discussions on migrating the fedora-logos package from pagure.io and whether to archive old Community Blog and Fedora Magazine image repositories. Additionally, preparations are underway to automate Flock 2026 YouTube thumbnails using Inkscape extensions and schedule data.

A major focus this week is the development of a Contributor Onboarding Video Series to help newcomers navigate Fedora's systems. To make these videos more authentic, the team has launched an open call for horizontal video footage from past Fedora events to replace stock assets. Contributors are also invited to help design Community Personas that visually represent different types of Fedora participants, offering a highly creative way to get involved.

Decisions

• Community Event Footage: The team aligned to solicit horizontal video footage from Fedora events via an open call on Fedora Discussions to replace stock assets and enhance future video content.
• Icon Design Refinement: The Datagrepper interface icon will be simplified, moving away from complex line art to utilize color blocks and shading for improved visual clarity at smaller sizes.

Learn more about the Design team.

Docs

The Fedora Docs team is actively modernizing its infrastructure and continuous integration pipelines. A major focus is refactoring the local preview script (docsbuilder.sh) and exploring a shared Forgejo Actions workflow that utilizes a pre-built container image to enable fast, cross-referenced CI builds for individual pull requests. To address security issues in outdated containers, the team plans to transition container builds to Konflux and Quay.io, aligning with broader Fedora infrastructure practices. Additionally, the team is finalizing its migration to Forgejo ahead of the July 31 Pagure.io sunset, investigating monitoring solutions for staging build failures, and evaluating tools like CryptPad for collaborative draft writing.

To better distribute documentation maintenance and empower subject matter experts, the team launched a "Fedora Docs Captain" pilot program to embed documentation liaisons within specific groups, starting with the Kernel, Multimedia, and AI/ML SIGs. There are immediate opportunities for contributors to help refactor multiple contribution guides—including those for Quick Docs and new modules—to emphasize the modern local authoring workflow. The team is also working to unblock and refine the documentation translation processes alongside the localization team.

Decisions

• Repository PR and Forking Guidelines: During the June 30 meeting, the team agreed that pull requests should normally be submitted via a fork, particularly for changes requiring lengthy discussion and refinement. However, organization owners and content owners who maintain an article on an ongoing basis may submit pull requests from upstream branches or push directly. Repository settings will be adjusted to enforce branch protections, ensuring only owners can push to main and requiring at least one review approval before merging.

Learn more about the Docs team.

Internationalization

In a recent discussion, returning contributor Javier Blanco inquired about the current activity levels on the translation mailing lists. The community welcomed him back and clarified that the mailing lists are currently quiet because the majority of localization work is now handled upstream, with contributors often utilizing alternative communication channels such as Matrix and forums.

To provide deeper context on the state of the localization community, Jean-Baptiste shared two presentations detailing the structural health and tooling of open-source translation efforts. These included an analysis of language community health using 20 years of Fedora translation data and a proposal for new tools to improve translator efficiency. Contributors interested in improving localization workflows and community collaboration are encouraged to review these resources.

Learn more about the Internationalization team.

EPEL

This week, the EPEL team focused heavily on addressing security vulnerabilities through necessary incompatible updates and package retirements. Notably, caddy was updated across multiple branches to resolve 22 CVEs, and an incompatible update for routinator was proposed to address several high-severity vulnerabilities. Contributors are also discussing a proposal to drop the rust-rpki binary subpackage to simplify package maintenance. Furthermore, early planning discussions for EPEL 11 have begun, with current conversations centering around the challenges of maintainer ownership and content resolver workflows.

Decisions

• The steering committee approved an incompatible update for syncthing to v2 in EPEL 10.3 and 10.2. Because of outdated SQLite and Golang dependencies in older RHEL releases, syncthing will be retired in EPEL 8 and 9 around July 14 to mitigate unresolvable CVEs.
• The committee confirmed the rollout of the incompatible update replacing p7zip with 7zip in EPEL 9, which has been pushed to testing without automatic karma or time-based pushes to ensure adequate community feedback.

Learn more about the EPEL team.

ELN

The ELN SIG meeting on June 30, 2026, was brief due to low attendance and participants being occupied with other tasks, such as debugging EBS with Fedora Infrastructure. Consequently, no major subjects were discussed, and no formal decisions were made during this session.

For those looking to engage with the group, contributors are encouraged to bring topics for discussion to the next scheduled meeting, which will take place on Tuesday, July 7, 2026, at 12:00 EDT.

Learn more about the ELN team.

Atomic

The Fedora Atomic Initiative discussed a draft Change Proposal to unify all atomic and bootc variant pipelines into a single monorepo using Konflux. This consolidation aims to streamline infrastructure across teams by establishing a shared atomic tenant for bootc base images, Atomic Desktops, and potentially Fedora CoreOS. To manage the scope and avoid disrupting existing workflows, the migration will be iterative. The immediate focus is moving bootc images to the new forge to verify builds, which will be followed by dedicated change requests for official artifact signing and the broader pipeline unification.

In community discussions, interest continues to build around the proposal to create a systemd-sysexts SIG. This initiative presents a great opportunity for contributors to help design the official building, distribution, and documentation of systemd system-extensions, which are crucial for extending atomic systems with software that doesn't run well in containers or Flatpaks.

Decisions

• The team agreed to pursue a unified atomic Konflux tenant and monorepo to house current bootc base images, Atomic Desktops, and potentially future variants.
• The pipeline unification will be broken down into smaller, sequential change requests, starting with migrating bootc images to the new forge and establishing artifact signing before fully transitioning other variants.

Learn more about the Atomic team.

CoreOS

In the CoreOS meeting, the team reviewed upcoming Fedora 45 changes, noting that a GoLang update and an RPM 6.1 version bump will require dedicated tracking issues and investigation, while the adoption of PURL metadata is not expected to affect Fedora CoreOS. Contributors interested in packaging can engage with the ongoing work to support passing Butane configs directly to instances, which prompted a restructuring of how Ignition and Butane are maintained. For the broader Linux community, Podman 6.0 has officially landed in Rawhide and is ready for testing. Additionally, the forum proposal to create a systemd-sysexts Special Interest Group (SIG) continues to gather support from developers interested in building and distributing systemd system-extensions.

Decisions

• The team agreed to combine the Ignition and Butane spec files, making Butane a subpackage of Ignition and archiving the standalone Butane spec.

Learn more about the CoreOS team.

AI & ML

During their July 2nd meeting, the AI & ML SIG discussed upcoming packaging and testing plans, noting that the ollama 0.30.x update will likely be delayed until Fedora 46 due to upstream instability with llama-cpp. The group is actively seeking testing and packaging help to diversify supported llama-cpp backends, particularly for the upcoming Vulkan transition. In broader community news, there is an active proposal to evolve the SIG into the "Fedora AI Working Group" to better reflect its expanding scope in both hardware enablement and open AI best practices. Additionally, there is a large backlog of open tickets for packaging major AI frameworks and tools—including TensorFlow, Bazel, and various Python libraries—alongside early discussions about proposing a dedicated Fedora AI Spin and building hardware-enabled inferencing images.

To boost contributor engagement, the SIG is revamping its documentation to create a more welcoming onboarding experience and is forming a new "Skills Reviewers" sub-team to curate shared AI skills using the Agent Skills specification. The group also addressed the management of donated AMD GPU nodes (like gpu01), emphasizing the need for public documentation to clarify hardware allocation and CI usage. This initiative aims to ease bureaucratic friction, provide transparency on how community hardware is utilized, and make it easier for contributors to understand how they can leverage these resources.

Decisions

• @jflory7 will open a ticket to propose a new "Hardware" module for the documentation site to track and manage hardware donated for Fedora Infrastructure.
• @jflory7 will chair the next SIG meeting on July 16, 2026.

Learn more about the AI & ML team.

RISC-V

The RISC-V group focused heavily on expanding infrastructure and hardware support this week. Discussions are underway with the cloud vendor Scaleway to host potential Fedora Koji builders in their Paris datacenter, an effort being coordinated through RISE. Hardware availability for developers is also improving: the newly released Milk-V Titan boards are currently shipping to RISC-V engineers for Fedora use, which will further aid platform optimization and broader Linux ecosystem integration.

On the software front, active development continues on the Fedora Omni kernel to expand support for devices like the Muse Pi Pro and K3, while steady progress is being made on the Fedora RISC-V tracker. To avoid disruptive surprises, contributors should note ongoing 'fedora-devel' discussions regarding potential improvements to the Changes Process, as well as internal deliberations about implementing two-factor authentication (2FA) for packagers.

Decisions

• It was decided to provision an additional "K3" hardware unit (sponsored by CLE) to maintainer DavidA to serve as a new Fedora RISC-V Koji builder.

Learn more about the RISC-V team.

Security

The Security SIG held a meeting this week to welcome new members from Red Hat's Product Security and Open Source Office. The expanded team will focus on navigating the upcoming EU Cyber Resilience Act (CRA) and implementing practical, developer-centric security measures. The group also initiated a debate on the scope of the Security Docs repository, specifically whether it should consolidate all Fedora security topics or strictly house documentation actively maintained by the SIG to prevent stale content. This documentation discussion will continue in upcoming meetings.

For contributors looking to get involved, the SIG noted that help is needed with defining security policies, which are obligatory for the CRA Steward role. Community members can follow the published meeting agendas to see when topics of interest are being discussed or drop into open office hours to participate.

Decisions

• Agendas for upcoming meetings will be published in advance. If there are no agenda items, the scheduled time will serve as informal open-floor office hours.
• Formal decisions within the SIG now require a quorum of at least three member votes.

Learn more about the Security team.

Go

During the Go SIG meeting, members discussed the upcoming Go release and shared that a mass prebuild of Go 1.27rc1 has been completed; contributors are encouraged to review the prebuild results report to catch any potential regressions. The team also highlighted ongoing work on a new Go utility designed to test Kubernetes installations locally on VMs, which will help validate new Fedora Kubernetes releases (like 1.36) before deployment. Furthermore, participants praised Fedora's current approach to vendored Go packages, noting it provides a smoother packaging experience compared to other ecosystems.

In terms of packaging standards, the SIG reviewed Issue #67 regarding CGO_CFLAGS. A contributor proposed establishing default values for these flags that are consistent with Fedora's standard build practices, as some packages currently require manual configuration to build correctly. The team will investigate past configurations and work toward defining sensible defaults that packagers can easily override if necessary.

Learn more about the Go team.

Perl

This week's activity in the Perl group centered around package maintenance and compatibility pull requests. Notably, a pull request for perl-Module-Starter-Plugin-CGIApp was submitted to fix compatibility with Module::Starter 1.80+ author arrayrefs. Additionally, contributors opened PRs to prevent building Class::Storage::Debug in bootstrap mode for perl-SQL-Abstract and to utilize -any virtual provides for MariaDB/MySQL dependencies within perl-Test-mysqld.

Decisions

• The maintainer for perl-Module-Starter-Plugin-CGIApp decided against adopting the %autorelease and %autochangelog macros, requesting their removal from the pending compatibility pull request.

Learn more about the Perl team.

Rust

Michel Lind submitted a Request for Comments (RFC) to drop the rpki binary subpackage from the rust-rpki crate. These unneeded programs were accidentally shipped due to a bug in older versions of cargo2rpm (< 0.3.0) and unnecessarily complicate package maintenance by requiring frequent license audits for statically-linked dependencies.

Since the crate is currently only used by routinator, Lind proposed retiring the binary packages to simplify ongoing maintenance. As this counts as a package retirement, Lind is seeking clearance on the EPEL side and noted that the removal could be gated to only affect Fedora 45 and newer if required.

Learn more about the Rust team.

Other Discussions

• Future of the Fedora i3 Spin in Fedora Linux 45 (cross-posted to the devel and i3wm mailing lists): Justin Wheeler called for new maintainers to keep the i3 Spin alive for F45, noting light maintenance recently. Dan Čermák and Eduard Lucena stepped up to continue packaging and comps/bug tracking respectively, ensuring the Spin will continue to be produced.
• Hummingbird Community Meeting Notes - 25 June 2026: Laura Santamaria shared notes from the Hummingbird community meeting, discussing community growth, DevConfCZ recaps, AI integration with a "human-in-the-loop" approach, image requests, and LTS strategy. Adam Miller and Jorge Castro further discussed the potential of integrating AI agents natively into the OS via an OpenClaw experience.
• Some news about the Audinux activity for June: Yann Collette shared updates on the Audinux repository, highlighting the return of kernel-rt builds and listing 21 new packages (mostly audio plugins and tools) and 140 package updates added in June 2026.
• How can we improve the Changes Process?: Maxwell G proposed modernizing the Fedora Changes Process by moving away from the Wiki and wikitext to a Git-based repository using Markdown and structured metadata (like YAML/TOML frontmatter). The discussion highlighted frustrations with the current fractured discussions across mailing lists and Discourse, and the burden on the Change Wrangler, though some raised concerns about the maintenance of custom web apps versus using existing forges.
• F45 Change Proposal: Grub EFI For Confidential Computing (self-contained): Aoife Moloney announced a proposal to create an independent, minimal GRUB package for UEFI to boot Unified Kernel Images (UKIs) for Confidential Computing. The thread discussed the trade-offs of using an intermediate "bootstrap" kernel versus a minimal GRUB, with Lennart Poettering noting that Windows has proven PCR prediction viable for broad audiences and Linux is getting closer to that goal.
• How can I contact the crypto team?: Gordon Messmer inquired about adding AWS's s2n-tls and aws-lc to Fedora, noting modern crypto libraries are moving away from runtime configuration. Simo Sorce and others debated the risks of relying on corporate-owned libraries like aws-lc that don't integrate well with distribution policies, while acknowledging that upstreams like rustls are increasingly defaulting to them over OpenSSL.
• binary content in node_modules: Gordon Messmer asked about handling pre-built binaries and WebAssembly files bundled inside node_modules during Node.js package reviews. He suggested using a tool like npm2rpm to avoid bundling modules with native binaries, requiring them to be installed as system modules instead.
• Distribution conditionals in spec files: Florian Weimer proposed updating the Packaging Guidelines to explicitly permit macros like %fedora, %rhel, %centos, %epel, and %hummingbird. The discussion revealed a divide between maintainers who prefer a single spec file across multiple distributions (like LLVM) and those who find the resulting "macro jungle" harder to read and maintain.
• F45 Change Proposal: oo7 Secrets Service Provider (system-wide): Aoife Moloney shared a proposal to switch the default Secrets Service provider from KWallet and GNOME Keyring to oo7. Bilal Elmoussaoui (oo7 author) clarified that it automatically migrates existing keyrings and supports multiple keyrings, addressing concerns about compatibility and maintenance of the older daemons.
• Inactive packager script notifications from fork (and a related thread): Several active packagers received false-positive inactivity notifications. Jef Spaleta apologized, explaining that while testing the script's transition to the Forgejo API on a personal fork, the @username mentions in the ticket templates accidentally triggered live notifications.
• Other discussions included a call for a zig co-maintainer, a proposal to Disable Vendor Change by Default, the Council Bi-Weekly Meeting Agenda, packaging the JS Trix editor, a list of New packages in Fedora Linux, multiple review swaps requests across the lists, FCOS release related issues on ppc64le, the archiving of fedora-lorax-templates, dropping rust-rpki's rpki binary subpackage, the Council Statement on the Future of Community Initiatives (and duplicate), the expiration of the MPEG-4 Visual final patent, a proposal for Stratis Storage in Anaconda, a proposal for Bash Color Prompt 1.0, an invitation to the Java SIG Matrix room, and an issue with s390x cloud images hanging.

Orphaning packages

• List of long term FTBFS packages to be retired in August: Miro Hrončok posted the first reminder for packages failing to build from source since F42, which will be retired before F45 branching.
• Orphaned package wavemon updated to 0.9.7: Viktor Erdelyi provided a COPR build for the orphaned wavemon package, and Iñaki Ucar successfully unretired and updated it in Fedora.
• Question about the orphaned "fx" package: Emanuele Petriglia asked about the controversy that led to fx being orphaned and subsequently submitted a Bugzilla review ticket to package its new Go-based rewrite.
• Orphaned packages looking for new maintainers: An automated report listed packages that will be retired in six weeks unless adopted by a new maintainer.

Package updates

• [rawhide] fmt and spdlog upgrade/soname bump: Frantisek Zatloukal announced rebuilds for packages depending on fmt-12.1.0 and spdlog-1.17.0 in a side tag.
• [heads-up] libcamel soname version bump in evolution-data-server 3.61.1: Milan Crha completed the soname bump and side tag merge for evolution-data-server.
• [heads-up] updating onnx to 1.21.0 & onnxruntime to 1.26.0 in rawhide: Diego Herrera announced an upcoming soname and protobuf version bump for onnx and onnxruntime.
• RFC: incompatible update for routinator for Fedora and EPEL 9 and 10: Michel Lind announced an incompatible update to routinator 0.15.2 to fix multiple high-severity CVEs, including a path traversal vulnerability.
• Highfive 3.3.0 coming to rawhide: Ankur Sinha successfully updated highfive to 3.3.0.
• GNOME 51.alpha update: Milan Crha created a side tag for the GNOME 51.alpha update and invited other maintainers to include their related updates.
• xmlsec 1.3 update: Tomas Halman announced that the xmlsec 1.3 update has landed in Rawhide.
• Upgrade to sundials 7.8.0: Antonio Trande announced an upcoming upgrade to Sundials 7.8.0 in Rawhide.
• F45 Change Proposal: Ruby on Rails 8.1 (self-contained): Aoife Moloney forwarded a proposal by Vít Ondruch to update the Ruby on Rails stack to 8.1.
• F45 Change Proposal: GNU Toolchain Update (system-wide): Aoife Moloney forwarded Carlos O'Donell's proposal to update the GNU Toolchain to gcc 16.2, binutils 2.47, glibc 2.44, and gdb 17.2.
• F45 Change Proposal: Fontconfig 2.18 (system-wide): Aoife Moloney forwarded Akira TAGOH's proposal to update fontconfig to 2.18.

New contributor introductions

• Self Introduction: Simone: Simone (tollsimy), a computer engineer with a background in electronics, embedded systems, and cloud infrastructure, introduced themselves and expressed a desire to give back to the Fedora community.