Across the various Fedora project groups, the primary shared focus this week was preparing for the upcoming Fedora 45 Beta release. Teams spanning Release Engineering, Quality, KDE, Server, ARM, Cloud, and Websites dedicated significant effort to testing release candidates, managing blocker bugs, and executing stable pushes during the Beta Freeze. Looking ahead to future releases, FESCo and the Packaging Committee are actively evaluating Fedora 46 and 47 Change Proposals, most notably the system-wide introduction of the Crystal programming language, a libical 4.x upgrade, and a Thin LTO build flag, while the Rust SIG coordinated ecosystem-wide rebuilds for the upcoming Shadow Stack feature. Additionally, there is a strong collaborative push toward architectural and procedural unification across the project; the Atomic and CoreOS teams are forming a working group to consolidate their base image efforts, the Council is finalizing the new Fedora Innovation Lifecycle framework, and infrastructure teams are actively handling major migrations like COPR's transition to Pulp.

Announcements

Framework recently announced that their new modular Laptop 12 is now available with Fedora KDE Plasma pre-installed, providing users with a hardware-validated experience out of the box. For users looking to maintain and recover their existing systems, new community tutorials detail how to monitor NVMe and SSD drive health using Performance Co-Pilot to catch subtle warnings before drive failure, as well as easy GUI methods for system recovery after a BTRFS boot failure using live USBs and snapshots.

On the development and packaging front, three new Fedora Change Proposals are seeking community feedback. A system-wide proposal for Fedora 46 seeks to introduce official native support for the Crystal programming language, utilizing a "Shard-as-RPM" model to ensure hermetic, reproducible, and offline builds. Another system-wide proposal for F46 aims to upgrade libical to the 4.x series, which breaks C API/ABI compatibility from the 3.x series and will require dependent applications to be rebuilt or patched. Lastly, a self-contained change intended for Fedora 47 introduces a Thin LTO Build Flag (%slim macro) to give developers the performance benefits of Link Time Optimization while reducing the excessive RAM requirements and compilation times typically associated with fat objects.

Council

The Fedora Council focused heavily on refining the new Fedora Innovation Lifecycle proposal and clarifying trademark guidelines for derived images this week. In a lengthy and sometimes tense chat discussion, the Council debated the role of the FESCo representative and how proposals move into the new "Sandbox" phase. They successfully compromised on an 8-point requirements-gathering framework that clarifies the FESCo and Mindshare representatives act as liaisons rather than binding vetoes. This framework is now being integrated into the draft Sandbox Review Process SOP and was workshopped in a dedicated meeting.

In the forums, members discussed when modified Fedora OS images (like bootc containers or VMs) require trademark removal, particularly for internal organizational use versus public CI infrastructure. The conversation highlighted a need for better default tooling and documentation so that developers creating custom images automatically generate a compliant "Fedora Remix" rather than accidentally violating trademark policies.

Decisions

• Agreed to integrate an 8-point requirements-gathering framework into the Fedora Innovation Lifecycle Draft, establishing that FESCo and Mindshare representatives will act as go-betweens, their respective committees having a full vote (via Matrix chat).

See the detailed report for the Council team.

Learn more about the Council team.

FESCo

FESCo held one meeting and handled several tickets and forum discussions this week. A major focus was reviewing the F45 Incomplete Changes Report, with FESCo voting to defer the "Libxml215" Change to Fedora 46 while requesting a separate compatibility package, declaring the "Filter Fedora Flatpaks" Change completed, and allowing the "Relocate RPM repository configs to /usr" Change to land before the final freeze. Other incomplete changes were reviewed and mostly deferred to the next meeting for updates.

In other activity, new Change Proposals were announced on the forum, including the introduction of the Crystal programming language and its packaging guidelines for F46, updating libical to version 4, and a Thin LTO Build Flag for F47. FESCo also processed non-responsive maintainer tickets and enacted the policy to conduct Changes discussions strictly on the devel mailing list.

Decisions

• The Changes Discussion Only On Devel List policy is now effective immediately. Future discussions will happen on the devel list, while Discourse will host read-only topics with sentiment polls.
• The Libxml215 Change (reviewed via the F45 Incomplete Changes Report) was deferred to Fedora Linux 46, with the requirement that a separate libxml2_2.13 compatibility package be created instead of a subpackage.
• The Relocate RPM repository configs to /usr Change (reviewed via the F45 Incomplete Changes Report) was allowed to land its remaining parts before the final freeze.
• The Filter Fedora Flatpaks for Atomic Desktop v2 Change (reviewed via the F45 Incomplete Changes Report) was officially declared completed.

See the detailed report for the FESCo team.

Learn more about the FESCo team.

Packaging Committee

The Packaging Committee met once this week and actively discussed seven tickets. A primary focus was the introduction and refinement of packaging guidelines for the Crystal programming language, including source package naming conventions, dependency resolution, and multi-version coexistence.

In addition to the Crystal language guidelines, the committee resolved several other documentation updates. This included merging an exception for limited aws-lc use in cryptographic policies, updating guidelines to use the %openpgpverify macro by default, and clarifying that Provides tags are not inherited by subpackages.

Decisions

• Approved and merged the documentation exception for limited aws-lc use in CryptoPolicies (Ticket #1566).
• Agreed to use crystal-lang as the source package name for the Crystal compiler to cleanly unretire an old package and maintain clean Git history (Issue #1567).
• Determined that Crystal shard source packages will be prefixed unconditionally with crystal-, but application subpackages will use their bare upstream names.
• Merged guidelines clarifying that Provides tags are not inherited by subpackages or source RPMs (Ticket #1563).

See the detailed report for the Packaging Committee team.

Learn more about the Packaging Committee team.

Mindshare

Mindshare and CommOps saw steady activity this week regarding onboarding, documentation, and event planning. In the Fedora Community Ops channel, members focused on updating broken links in the Join SIG documentation, integrating new contributors, and utilizing the zodbot cookie system for peer appreciation.

Meanwhile, the Fedora Mindshare team discussed administrative policies, clarifying reimbursement requirements for event attendees. The group heavily focused on reviewing, voting on, and tracking various global event sponsorship requests, including events in the Philippines, India, Czechia, and the United States, alongside implementing new quarterly labels for better ticket management.

Decisions

• Quarterly sorting tags (Q1-Q4) were successfully implemented for Mindshare issues to better organize budget allocations and tickets (Ticket #150).
• Conference registration fees for non-Red Hatters in the US or Canada, as well as fees up to $500 in Europe, do not require BEAR (Business Entertainment and Amenities Review) pre-approval, provided the attendee is not a government employee or contractor (Fedora Mindshare).
• The team agreed to continue grouping the activity of the Mindshare and CommOps groups together for the 'This Week in Fedora' reports rather than separating them (Fedora Mindshare).

See the detailed report for the Mindshare team.

Learn more about the Mindshare team.

Magazine

In the Fedora Magazine chat, the team discussed recent publications and upcoming article proposals. The Framework Laptop 12 article was published and quickly accumulated 1.6k views, with members resolving a brief link caching issue immediately following its release. Bots also cross-posted links to the Fedora 45 Beta Release Announcement and a new article proposal regarding Flock to Fedora session recordings.

On the technical side, a contributor reported an issue where it is currently impossible to log out of the Fedora Magazine WordPress instance. The issue has been forwarded to the appropriate infrastructure contacts for resolution.

Learn more about the Magazine team.

Diversity & Inclusion

The Diversity & Inclusion team has officially kicked off preparations for the 2026 Fedora Week of Diversity (FWD). The event is planned as a 2-3 hour virtual session scheduled around October 9th, bearing the working theme "Respect the Culture."

Currently, the group's primary focus is gathering volunteers and coordinating logistics. Discussions in the DEI Matrix room revolved around setting up event registration via Pretix, sourcing speakers, and retrieving design assets from previous years to expedite marketing efforts.

Decisions

• The 2026 Fedora Week of Diversity will be a short, 2-3 hour virtual event with 10-20 minute talks, scheduled around October 9th.
• The team will reuse and adapt the 2024 design assets instead of requesting new ones, to bypass the Design Team's 4-6 week turnaround time.

See the detailed report for the Diversity & Inclusion team.

Learn more about the Diversity & Inclusion team.

Workstation / GNOME

The Workstation and GNOME team is heavily focused on integrating the GNOME 51 Release Candidate into the upcoming Fedora 45 release and Rawhide. A notable call for testers was announced to evaluate a newly proposed implementation of Google Drive integration in GNOME, aiming to replace the previously dropped support. In parallel, developers successfully resolved a critical auto-login regression in GDM for Fedora 44 and are actively tracking down compositor issues affecting openQA tests.

Additionally, the Fedora Workstation Working Group met to discuss strategic approaches for managing Flatpak metadata certification on Flathub, focusing on how to align upstream packages with Fedora's policies without causing friction. Meanwhile, preparations are underway for the Fedora 45 Blocker Review meetings and promotional efforts, including a request for authors for the Fedora Magazine's release article.

Decisions

• The Working Group decided to defer the evaluation of a custom metadata certification process for FlatHub packages to the issue tracker for further investigation and future deliberation. (Meeting Summary)

See the detailed report for the Workstation / GNOME team.

Learn more about the Workstation / GNOME team.

KDE

The KDE group focused heavily on preparing for the Fedora 45 Beta release, dealing with blocker bug reviews, installer regressions, and package updates. Key troubleshooting efforts involved the new Anaconda Web UI lacking advanced storage features, a workaround to force the slitherer tool to use the XCB platform, and debugging a Kirigami color accent regression in KDE Frameworks 6.29. Planning has also begun for the Fedora Magazine "What's New in Fedora KDE" article for F45, which will cover Plasma 6.7 and 6.8.

In addition to desktop environment components, the team addressed Kinoite-specific bug reports, including failures with Discover's automatic updates and graphical glitches during AV1 video playback. KDE Frameworks 6.30 has been successfully built for Fedora 43, 44, 45, and Rawhide, and is now awaiting testing and Bodhi karma.

Decisions

• Submit a "What's New in Fedora KDE" article for Fedora 45 focusing on Plasma 6.7 with a brief mention of 6.8 (Issue #725).
• Use an XCB platform workaround for the slitherer tool to bypass a bug in time for the Fedora 45 beta.
• Proceed with migrating to the oo7 Secrets Service Provider for most login managers, relying on blowfish wallet auto-migration while accepting that GPG-encrypted wallets are not yet supported for migration.

See the detailed report for the KDE team.

Learn more about the KDE team.

Server

This week, the Server group focused heavily on preparing documentation and testing for the upcoming Fedora 45 release. In documentation, members reached a consensus to restructure the guide by introducing a new "Postinstallation Customizations" section immediately following "Installation", while retaining the existing "Virtualization" and "Containerization" navigation titles. A formal asynchronous vote has been initiated for the naming of its subsections. In parallel, a Fedora Quality proposal to reduce the list of release-blocking legacy storage interfaces (such as PATA, SCSI, and Hardware RAID) during installation was shared for feedback.

Matrix discussions touched upon homelab power consumption optimization, the transition from MBR to GPT for ARM images (and how maintaining Raspberry Pi 3 support hinders features like systemd-repart), as well as stylistic choices for documentation readability. Finally, progress continues on testing F45 Beta builds and creating a guide for Software Management using DNF.

Decisions

• Created a new main documentation section titled "Postinstallation Customizations", to be placed second in the navigation tree after "Installation". (Meeting Log)
• Retained the current top-level documentation navigation bar names, including "Virtualization" and "Containerization". (Meeting Log)
• Revoked preliminary votes on documentation subsection titles in favor of an asynchronous voting period on the issue tracker. (Meeting Log)

See the detailed report for the Server team.

Learn more about the Server team.

Infrastructure

The Infrastructure group progressed on several key services, including provisioning storage for the new Forgejo Dist Git production instance and deploying the public-inbox service to staging. They also diagnosed an intermittent Kerberos pre-authentication issue impacting Packit scratch builds and initiated the migration of the Matrix Moderation bot to Fedora's internal infrastructure.

Routine maintenance included reviewing AWS resource usage and tagging compliance, troubleshooting Fedora 45+ Ansible compatibility, and handling various FAS group and Koji heavybuilder requests.

Decisions

• Mirrors located in Iran (.ir) cannot be hosted or listed in MirrorManager due to US export control regulations (Ticket #13536).
• A new policy is being drafted for Official Fedora Matrix rooms, which will require the inclusion and proper configuration of the new official Fedora moderation bot (@moderation:fedoraproject.org) (Forum).

See the detailed report for the Infrastructure team.

Learn more about the Infrastructure team.

Release Engineering

This week, the Release Engineering team focused heavily on preparing for the Fedora 45 Beta release, actively managing the Beta Freeze by executing multiple stable pushes and generating Beta release candidates. A significant blockage involving the F44F (Flatpak) updates-testing compose—which had timed out on database connections and halted hundreds of updates—was successfully resolved after applying a hotfix to the bodhi-server. Additionally, network issues with proxies in the APAC region causing repository checksum mismatches were investigated and mitigated.

A Fedora 45 Blocker Review meeting took place to evaluate several bugs affecting the Beta, resulting in decisions on multiple blockers and freeze exceptions. The team also handled various routine requests, including bulk ACL removals (which are now facilitated by a new automation script), unretiring packages via the newly introduced self-service workflow, generating detached signatures for the ignition 2.27.0 release, and processing stalled EPEL branch requests.

Decisions

• Accepted Bug 2526278 (initial-setup multiple GPUs) as a Fedora 45 Beta Freeze Exception.
• Accepted Bug 2524952 (kmscon NULL pointer dereference) as a Fedora 45 Beta Blocker.
• Accepted Bug 2526398 (Anaconda crash reporting failure) as a Fedora 45 Beta Blocker.
• Rejected Bug 2524726 (pcmanfm-qt update) as a Fedora 45 Beta Freeze Exception.
• Closed Bug 2502678 (DiscoverNotifier updates) as NOTABUG for Fedora 45 Final.

See the detailed report for the Release Engineering team.

Learn more about the Release Engineering team.

Quality

Fedora 45 Beta preparations are in full swing as the Beta freeze started on August 25, and the Go/No-Go decision is scheduled for September 10. The group is actively testing Beta candidates and tracking blockers. A proposal has been raised to significantly reduce the list of release-blocking storage interfaces during installation (dropping obsolete technologies like PATA and SCSI), acknowledging hardware access constraints.

In tooling news, Issuebot is now fully deployed to help manage Common Issues, and the Quality team submitted their requirements for the upcoming Bugzilla replacement. The community is also organizing multiple Test Days covering the 7.2 kernel, Internationalization (i18n), KDE 6.7, Anaconda features, and Fedora CoreOS.

Decisions

• Anaconda failing to report simulated crashes to Bugzilla was accepted as a Fedora 45 Beta blocker.
• A kmscon crash during headless Raspberry Pi 4 installations was accepted as a Fedora 45 Beta blocker because it breaks text-mode initial setup.
• A proposed criteria change to remove PATA, SCSI, Firmware RAID, Hardware RAID, Fibre Channel, and FCoE from the list of release-blocking storage interfaces is under active discussion.

See the detailed report for the Quality team.

Learn more about the Quality team.

Websites and Apps

This week, the Websites and Apps team focused on resolving image path issues on the KDE edition page and preparing the site for the upcoming beta release. Contributor @fesinan worked with @glb to migrate external KDE image assets into the local repository, mitigating the risk of upstream link breakage. During this process, they identified a structural issue in the CMS YAML files where removing hidden sections breaks Vue array offsets, highlighting a need for future refactoring.

Additionally, the team discussed testing the beta release site on the staging environment. A recent fix for issue #423 enables beta pages for clients without JavaScript, which doubles the number of generated pages. While there were concerns about Nuxt memory limits and leaks during these larger builds, local testing indicated the build succeeded without requiring increased node memory. The team agreed to test the build on staging a few days before the release candidate is finalized.

Decisions

• The beta version of the website will be built and tested on the staging server a few days before the release candidate to verify that the build system can handle the increased page count resulting from issue #423.
• Image assets for the KDE page will be hosted locally in the repository and prefixed with kde-plasma- rather than relying on external KDE content delivery networks.
• The hidden "Get started developing with Fedora KDE Plasma Desktop" section will remain in the CMS YAML for now, as removing it would break hardcoded array offsets in the current Vue components.

Learn more about the Websites and Apps team.

Design

The Fedora Design team officially kicked off the Fedora 46 Wallpaper project, drawing inspiration from mathematician Karen Uhlenbeck after a community vote. The team is exploring creative themes like minimal surfaces, gauge theory, and curved spaces, and has issued an open call for contributors to submit ideas and sketches. In other areas, the team continued its Fedora Design Docs Revamp by drafting new "How to Join" and "FAQ" pages, though publication has been deferred to allow for more internal review.

Additionally, the team processed design updates for ongoing tickets, opting to simplify the poster designs in Ticket 40. Notably for the broader Linux community, the team announced that the updated EPEL steering committee badge design marks the final badge request the Design team will accept and process through their ticket queue.

Decisions

• The Design team will no longer accept badge design requests through their ticket queue, making the EPEL steering committee badge (design#60) the final one processed this way.
• The publication of the new FAQ and "How to Join" documentation was deferred until the end of the current or next sprint to allow for sufficient internal review.
• Ticket 40 will be reverted to an earlier, simplified design version to improve clarity, reducing the number of listed teams from nine to three.

See the detailed report for the Design team.

Learn more about the Design team.

Docs

This week, the Docs team made significant progress on cleaning up legacy documentation. A custom script was developed to successfully catalog over 670 obsolete Wiki pages, paving the way for a major cleanup of content that has been unedited for years. Alongside this, new requests were made to remove or archive End-Of-Life (EOL) distribution pages to improve documentation relevance.

In community discussions, users shared a shell script for identifying active kernels and confirmed that combining powertop and tuned resolved power usage regressions on Fedora 44. Organizationally, the Docs team refined their pull request workflows and implemented a new open-contribution method for building biweekly meeting agendas.

Decisions

• Biweekly meeting agendas will now be crowdsourced; an empty forum thread will be created immediately after each meeting to gather topic suggestions, starting with the 2026-09-08 meeting.

See the detailed report for the Docs team.

Learn more about the Docs team.

Internationalization

The Internationalization group focused heavily on preparing for the upcoming Fedora 45 release, noting that three i18n Changes are now testable in QA, and organizing the upcoming Fedora 45 i18n test week. The team was also reminded to continue triaging open bugs for Fedora 43.

In ticket discussions, the group addressed resource management on Weblate by archiving obsolete documentation, centralized their issue tracking, and handled user inquiries regarding upstream translations and out-of-date release docs.

Decisions

• Archived documentation, specifically the sysadmin and install guides, will be removed from Weblate to conserve system resources, though their underlying Git repositories will be retained.
• Issue tracking for individual localization-docs repositories will be redirected to the centralized localization tracker using an external URL configuration.
• EOL releases (Fedora 26-42) will not be removed from Weblate by the localization team as long as they are still published by Fedora Docs; requests to hide them must be directed to the Docs team.
• Translation bugs for upstream projects, such as a reported KDE Plasma Vault issue, must be reported directly to the upstream teams rather than handled downstream in Fedora.

See the detailed report for the Internationalization team.

Learn more about the Internationalization team.

Legal

Jilayne Lovejoy notified the Legal group about a proposed update to the SPDX license inclusion guidelines. This update would potentially allow linux-firmware licenses to receive an SPDX license ID, which is relevant news for the broader Linux community dealing with firmware licensing.

Learn more about the Legal team.

COPR

COPR is currently migrating existing projects to use Pulp for storing build results, which may temporarily leave some builds in a pending state. Additionally, several technical issues were addressed this week, including website instability, a CentOS 10 Stream build failure caused by missing DNF packages, and a bug in the new Pulp upload process that was incorrectly consuming user quotas and causing queue backlogs.

Decisions

• The COPR team decided to proceed with migrating existing projects to Pulp in alphabetical order by owner name (excluding Packit projects), which may temporarily block some user builds.
• A fix (PR #4469) was proposed and accepted for deployment to resolve a bug where workers getting stuck while uploading to Pulp were incorrectly eating up concurrent build quotas.

See the detailed report for the COPR team.

Learn more about the COPR team.

EPEL

The major update this week is the transition of ffmpeg from version 5 to 7 in EPEL 9 Next (for CentOS Stream 9). To ensure stability for applications not yet ready for version 7, a compatibility package (ffmpeg5) has been introduced to house older libraries and headers. This update is currently in testing and will eventually move to regular EPEL 9 when RHEL 9.9 is released.

In infrastructure news, the Release Engineering team is actively preparing for the retirement and archiving of EPEL 10.2 in tandem with upstream RHEL transitions. They also successfully resolved a symlink bug that previously caused users to accidentally download the wrong EPEL 10 minor release package. Overall operations remain stable, which was reflected by a brief, issue-free weekly steering meeting.

Decisions

• Upgrade ffmpeg from version 5 to 7 in EPEL 9 Next, and introduce an ffmpeg5 compatibility package to prevent breakages in dependent packages. (Mailing List Announcement)
• Deploy an Ansible infrastructure fix to stop the epel-release-latest-10 symlink from churning and correctly lock it to the 10.2 path, addressing user dependency errors. (Ticket #117)

See the detailed report for the EPEL team.

Learn more about the EPEL team.

ELN

The ELN group had a quiet week regarding formal meetings, but resolved several infrastructure and configuration issues via chat. Notably, it was confirmed that ELN is no longer using modularity, which is relevant for upcoming infrastructure configuration updates. Additionally, a minor configuration gap in rpmlint was identified where .eln release tags were not correctly recognized, and a fix is being implemented.

The group also diagnosed and fixed a silent failure in the ELN buildsync (EBS) system caused by an unhandled asynchronous error following a network hiccup in late August. Once the ELN pod was restarted, backlogged build triggers processed successfully. Finally, significant refactoring work is underway for EBS to improve long-term maintainability while the group awaits a broader decision on multi-target support.

Decisions

• ELN is officially no longer using modularity, allowing infrastructure teams to drop modular-specific tags like eln-modular-updates-candidate.
• The rpmlint configuration's ReleaseExtension regular expression will be updated to support .elnNNN release tags to prevent false positive warnings.

See the detailed report for the ELN team.

Learn more about the ELN team.

Atomic

A major proposal was introduced to unify the base image efforts between Fedora CoreOS and the Atomic (bootc) initiatives, aiming for a single set of unified artifacts by the Fedora 46 release. To advance this effort and combine operations, a new working group is being formed with open calls for volunteers across the community. In addition, a new systemd-sysexts SIG is being organized to build and distribute system extensions based on Fedora content, which will greatly enhance the extensibility of atomic systems without relying strictly on containers.

Technical discussions clarified that Atomic Desktop images will maintain their current /opt and /usr/local symlinks to /var, and will continue to use official Fedora branding rather than shipping generic packages by default. For downstream users deriving custom builds (Fedora Remixes), efforts will focus on simplifying and documenting the rebranding and package-swapping process rather than altering the upstream Atomic artifacts.

Decisions

• A working group will be formed to explore unifying base image efforts between Fedora CoreOS and Atomic (bootc) for a targeted Fedora 46 release. (Meeting)
• Atomic Desktop images will continue to use symlinks to /var for /usr/local and /opt. Since they are considered "final" derivable images, changing this natively is unsupported, though downstream builders can modify the setting. (Issue #126)
• Atomic Desktop images will continue to ship official Fedora branding instead of generic packages. Downstream builders making derivatives (Remixes) will be supported via improved documentation and simpler package swapping methods. (Issue #125)
• A request to include powertop in Atomic images was declined; power tuning on Fedora should be managed through tuned. (Issue #127)

See the detailed report for the Atomic team.

Learn more about the Atomic team.

CoreOS

The Fedora CoreOS group focused on resolving critical SELinux-related regressions this week, specifically issues involving home_dir in Ignition and podman-machine-os CI failures. To prevent shipping broken images, the team halted the standard rollout, opted to temporarily pin policycoreutils and selinux-policy packages to older versions, and delayed the release to the following week.

Additionally, the group continued reviewing Fedora 45 change proposals, identifying action items for OpenSSL 4.0 rebuilds and integrating systemd-oomd with zram. A new Fedora SIG for systemd system-extensions (systemd-sysexts) was proposed, and dedicated sessions were scheduled to explore unifying CoreOS and bootc efforts.

Decisions

• Pinned policycoreutils and selinux-policy packages to older versions across stable, testing, and next streams to bypass SELinux regressions and prevent broken image releases (Issue #2216 and Issue #2217).
• Decided to delay the CoreOS release rollout to Tuesday (after the US holiday) to accommodate ad-hoc builds fixing the SELinux regressions.
• Rolled out Ignition Native Butane Support to the next stream (F44-based) to gather early feedback before the F45 rebase.

See the detailed report for the CoreOS team.

Learn more about the CoreOS team.

IoT

During the Fedora IoT Working Group Meeting, the team reviewed the status of current and upcoming releases. Fedora 45 is currently in its freeze period, and upgrades from Fedora 44 have tested successfully without issues. Fedora 44 stable builds remain green, with the exception of a known clevis issue. Meanwhile, the Fedora 46 (Rawhide) build experienced a temporary failure due to a Koji GSSAPI authentication error.

Additionally, an ongoing bug affecting ignition-edge has been confirmed as fixed in a newer release. The updated package now needs to be built and included in the distribution.

Learn more about the IoT team.

ARM

The ARM group this week focused heavily on hardware-specific troubleshooting and preparations for the upcoming Fedora 45 Beta release, highlighted by an announcement for the Fedora 45 Blocker Review Meeting. A notable success was diagnosing offline update failures on the Raspberry Pi 5, where missing Real-Time Clocks (RTC) caused GPG signature verification to fail during early boot. Contributors found that swapping chronyd for systemd-timesyncd acts as a reliable workaround to persist timestamps.

In addition to RPi5 troubleshooting, developers addressed an SELinux permission bug preventing initial-setup from running in F45 (which is fixed in Beta 1.2). Other community members shared progress on enabling measured boot on the Raspberry Pi 4 using a Letstrust TPM, while field reports trickled in regarding boot challenges on newer Snapdragon X laptops and Lenovo T14s post-installations. Notably, Fedora 43 is now considered strictly unsupported for newer Raspberry Pi 5 board revisions.

Decisions

• Fedora 43 is no longer supported on newer Raspberry Pi 5 board revisions; users must transition to Fedora 44 or upcoming Fedora 45 images. (Mailing List Thread)
• To bypass the broken initial-setup on Fedora 45 Beta 1.1, testers should temporarily set SELinux to permissive mode or disable it until the upstream fix in Beta 1.2 is available.

See the detailed report for the ARM team.

Learn more about the ARM team.

Cloud

In the Fedora Cloud room, the group is preparing for the Fedora 45 Beta release. A call for testing was issued because many Cloud tests remain unexecuted, particularly for Xen. While some Azure test results have been submitted, additional community help is required to complete the testing matrix, especially for AWS.

Learn more about the Cloud team.

Kernel

This week, the Kernel group primarily focused on resolving a critical bootloader installation issue triggered by recent kernel updates in the Fedora Kernel chat. A change enabling CONFIG_OF on x86 resulted in an empty /proc/device-tree directory, causing GRUB to misidentify the environment and fail during installation. The kernel configuration was quickly reverted to bypass the GRUB bug.

Other discussions included troubleshooting OpenQA test failures on aarch64 architectures, debugging the new DRM panic screen, and addressing minor build warnings in kernel selftests.

Decisions

• Revert the CONFIG_OF configuration on x86 builds to eliminate the empty /proc/device-tree directory, providing a workaround for GRUB's faulty environment detection heuristic.

See the detailed report for the Kernel team.

Learn more about the Kernel team.

AI & ML

The AI & ML SIG discussions this week focused on documentation, package updates, and the group's overarching vision. A primary point of conversation was the AI Developer Desktop spin; its inclusion and placement within the SIG remain controversial, prompting a decision to further refine the SIG's proposed mission and vision. On the packaging front, a PyTorch/libstdc++ update is currently waiting on the freeze, preparations are being made for a ROCm 10 rebuild which appears to be a minor update, and Fabric was updated to its latest release in COPR.

In addition to technical updates, group members discussed the major industry news of Nvidia acquiring Hugging Face. Furthermore, early work has started to turn the "This Week in Fedora" summaries into a regular column on the Community Blog.

Decisions

• Merged Pull Request #3 to scaffold Antora modules for SIG focus areas.
• Decided to hold off on finalizing the SIG's vision and mission in order to further discuss and refine the placement of the AI Developer Desktop spin.

Learn more about the AI & ML team.

RISC-V

The RISC-V group focused heavily on kernel debugging, hardware enablement, and package rebuilds for Fedora 45 and 46. The F45 RISC-V build is notably on target to be released in sync with the primary architectures. Significant effort went into bisecting and fixing a boot failure on SpacemiT K3 boards using updated firmware, which culminated in a functional 7.2.3 omni kernel. Desktop environment testing on the Milk-V Titan also yielded excellent results using AMD GPUs on Fedora 44.

On the infrastructure and packaging front, developers tackled major rebuild blockers (including vxl, fastnetmon, catch, and llvm) and handled Koji builder memory exhaustion. Discussions highlighted the need for a modern replacement to the outdated koji-shadow script to automate rebuilds, alongside identifying an Anaconda bug that inadvertently enables unavailable update repositories for Fedora 45 installations.

Decisions

• Drop the 'Orange Pi RV2: regulator PCIe and PHY related updates' and 'OrangePi R2S devicetree tweaks' from upcoming 7.2/7.3 kernels, as they are either unnecessary or break PCIe.
• Send the successful 7.2.3 omni kernel to Koji for F45 to allow the creation of updated testing images.
• Require non-scratch package builds in the RISC-V Koji instance to be coordinated by core maintainers to avoid NVR (Name-Version-Release) misalignments with the upstream Fedora Koji.
• Treat Anaconda's default enablement of the Fedora 45 updates repositories as a bug, as it causes 404 errors during network installations.

See the detailed report for the RISC-V team.

Learn more about the RISC-V team.

Security

The Security SIG held a meeting this week focusing heavily on the creation of a new Fedora Privacy SIG and the ongoing issue of misfiled CVEs. To avoid ideological drift, the proposed Privacy SIG will be strictly scoped to technical tasks such as analyzing packages for privacy issues, maintaining lists of problematic packages, and creating privacy-preserving default configurations (e.g., disabling AI in Firefox or fuzzing location data in geoclue2).

Additionally, the group addressed the severe deluge of misfiled CVEs (exceeding a 90% false-positive rate) impacting the Fedora ecosystem. This is largely tied to a deprecated vulnerability scanner. In the Matrix channel, the team also clarified Fedora's kernel CVE patching pipeline—noting fixes frequently land before CVEs are even assigned—and agreed that the upcoming public search engine indexing of Matrix channels poses no security risks.

Decisions

• Logged meeting discussions to the Draft Proposal for Fedora Privacy SIG ticket and agreed to continue exploring packages that need privacy-preserving overrides.
• Decided to open a dedicated tracking ticket in the Security SIG repository to monitor progress on CVE-to-package mapping and PURL (Package URL) metadata, assisting upstream coordination efforts.

See the detailed report for the Security team.

Learn more about the Security team.

Gaming

The developer of Inertia Blast II and other LÖVE2D games successfully tested their projects on a mobile phone running Fedora PocketBlue Remix, noting that touch controls function correctly out of the box. Due to time constraints, the developer is reaching out to the Fedora community for assistance with packaging and distributing these titles.

Learn more about the Gaming team.

Go

Discussion in the Fedora Golang channel focused on packaging macros and tooling. A contributor encountered macro expansion failures when switching to %gocheck2 in their image-builder spec file (as seen in this build log). This was quickly resolved by clarifying the need to add BuildRequires: go-vendor-tools so the macro expands properly.

Additionally, the group discussed how best to incorporate Go tools (such as mockery) in spec files when they are declared via a go.mod tool directive, prompting a suggestion to potentially create a new %gotool macro to standardize the process.

Learn more about the Go team.

Perl

The Perl group saw routine automated package maintenance this week. Packit Bot submitted pull requests to update the perl-Date-Manip package to upstream release 7.00 for both the f45 branch and the rawhide branch. Both updates were subsequently approved and merged by Jitka Plesnikova.

Decisions

• Merged the pull request to update perl-Date-Manip to upstream release 7.00 on the f45 branch.
• Merged the pull request to update perl-Date-Manip to upstream release 7.00 on the rawhide branch.

Learn more about the Perl team.

Python

On the python-devel mailing list, a contributor shared their approach to resolving a packaging namespace conflict for dupeguru. Because the upstream maintainers were unresponsive, the packager reorganized the source code into a dedicated dupeguru namespace to prevent collisions in the global Python module space.

In the Fedora Python Matrix channel, members discussed ongoing package reviews, noting a temporary outage in the review service, and welcomed a new contributor seeking guidance on a first project.

Decisions

• To prevent global namespace conflicts, the dupeguru package source code was reorganized into a dedicated namespace for Fedora, bypassing an unresponsive upstream.

Learn more about the Python team.

Rust

This week, the Rust SIG focused on mass package cleanup, security updates, and coordinating ecosystem-wide rebuilds. Maintainers successfully orphaned approximately 180 unused leaf library packages in Rawhide to reduce technical debt and maintenance burden. Significant progress was also made on security fronts, specifically by shipping updates for the lru crate to address RUSTSEC-2026-0253 across all supported Fedora and EPEL branches.

In addition, the team assisted with the upcoming Fedora Shadow Stack feature by rebuilding a targeted list of Rust-dependent packages. Work also continues on complex application updates, including resolving git-pinned dependency issues in the fish shell and navigating architecture-specific test failures in the time crate.

Decisions

• Rebuilt a specific list of Rust-dependent packages using the latest Rust compiler to ensure compatibility with the upcoming Fedora Shadow Stack feature.
• Orphaned approximately 180 unused leaf library packages in Rawhide as part of a "spring cleaning" effort.
• Retired the const-cstr package from Fedora after it was orphaned for over 6 weeks due to being unmaintained and unsound (RUSTSEC-2023-0020).

See the detailed report for the Rust team.

Learn more about the Rust team.

Other Discussions

• Miroslav Suchý listed the new packages added to Fedora over the last month on the forum, prompting questions from users about the criteria and testing process for new software inclusion before release.
• Rénich Bon Ćirić announced the formation of the Fedora Crystal SIG on the forum to coordinate the packaging and lifecycle of the Crystal compiler and ecosystem, inviting packagers, testers, and enthusiasts to get involved.
• Yann Collette shared an update on Audinux activity for August on the forum, highlighting the addition of 24 new audio packages (including low-load NAM-A2 plugins) and 103 package updates.
• Arjun Shankar followed up on the F45 Change Proposal for enabling Shadow Stack, asking for proven packagers to help bump and rebuild 27 remaining packages shipping .so files that are incompatible with the updated Rust toolchain, which Maxwell G subsequently completed.
• Christopher raised concerns that Google is disabling the ability to send emails from @fedoraproject.org addresses via the GMail web client, leading to a discussion about alternatives, SPF/DKIM/DMARC configurations, and the historical liability hurdles of Fedora hosting its own authenticated SMTP gateway.
• Adam Williamson notified the community that due to new internal Red Hat device policies, he is rigorously splitting his personal Fedora contributions from his Red Hat identity, meaning his typical Fedora Bugzilla activity will now come from a new vanity email address.
• Jonathan Wakely noted that installing vim-default-editor does not affect visudo, which continues to use nano because sudo does not launch a login shell, prompting a conversation about finding a cleaner system-wide override without manual sudoers.d edits.
• Gordon Messmer proposed deploying his got-audit ELF namespace tampering scanner—written after the xz-utils attack—as a non-gating, generic Fedora CI test for packages with systemd services, though some developers warned about false positives and Codeberg's new anti-LLM terms of service.
• Norbert Manthey proposed hardening Fedora applications by appending -fno-strict-overflow, -fno-strict-aliasing, and -fno-delete-null-pointer-checks to the default compilation flags, but GCC team members heavily criticized the idea, arguing these flags cripple performance and break valid C++ code without offering real security benefits.
• Tobias Girstmair asked for advice on packaging vim-classic—an AI-free fork of Vim 8—so that it can seamlessly coexist with Fedora's standard vim packages, perhaps via a -as-vim subpackage of symlinks similar to the default-editor mechanism.
• Other discussions included an extended deadline for submitting Bug Tracker Workflows, questions on goprep directory naming, a patch for teamd on the libteam mailing list (link), fixing failed F44 Flatpak composes that block other updates, the F45 Blocker Review Meeting, potential updates to the SPDX license list, a criteria change proposal, taking over the rubygem-factory_bot package, a review swap for grub2-confidential-computing, and the F45 i18n test week on the g11n list.

Orphaning packages

• Johannes Lips announced the orphaning of elementary-icon-theme due to build failures and limited usefulness outside of specific desktop environments.
• Michel Lind provided a heads-up that he is removing himself from 214 packages due to shifting priorities and concerns surrounding GenAI/LLM use within the FOSS community.

Package updates

• Milan Crha announced side tags for the GNOME 51.rc updates for Rawhide and F45 branched.
• Gwyn Ciesla is updating motif in Rawhide to a maintained fork, requiring a soname bump and side-tag rebuilds for several dependent packages.
• Artur Frenszek-Iwicki is upgrading the Free Pascal Compiler to fpc-3.2.4~rc2 in Rawhide and F45, providing patches for several related build failures.

Contribution opportunities

Testing and Quality Assurance (QA) Testing is highly accessible for non-members and crucial for the upcoming releases. Community members can participate in Test Days for Linux Kernel 7.2 and F45 Internationalization (I18n), or execute Cloud tests for F45 Beta on AWS and Xen. Testers are also needed for specific features, such as the proposed GNOME Google Drive integration and the large FFmpeg 5 to 7 update in Bodhi. Additionally, anyone can help QA by voting asynchronously on proposed blocker bugs prior to review meetings via the blockerbugs app or by verifying the many bugs currently in the ON_QA state.

Writing, Documentation, Translation, and Design Contributors with creative or language skills have numerous avenues to get involved. Writers can draft or review articles for the Fedora Magazine, including coverage for the F45 Beta Release, session recordings from Flock, or "What's New" articles for Workstation and KDE. Documentation tasks include updating the Beginner's Guide and cleaning up legacy Wiki pages. For designers and artists, the Fedora Design team is collecting sketches and digital art for the Fedora 46 Wallpaper Project in Ticket #76, while the DEI team needs volunteers for marketing, design, and video editing.

Event Organization, Community Operations, and Policy Review General community members can provide valuable feedback on overarching proposals like the GDPR/data access legal agreement, the Sandbox Review Process, the Privacy SIG proposal, and the systemd-sysexts SIG creation. On the operations side, CommOps has a sore need for general wiki triage on pages like event sponsorship. Organizers can step up to manage speakers, schedules, and Pretix logistics for the 2026 Fedora Week of Diversity, or volunteer to staff the Fedora booth locally at All Things Open 2026 via Ticket #128.

Packaging, Infrastructure, and Software Development Developers and packagers can adopt newly orphaned packages like mcelog, package shards for the new Crystal SIG, or help port Rust crates away from unmaintained dependencies (e.g., migrating off bincode or proc-macro-error). Web developers are needed to refactor hardcoded Vue array offsets into named keys in the Fedora Websites 3.0 repository. Infrastructure and Python skills can be put to use by building EPEL10 dependencies for Mailman servers (Ticket #13519), tracking down Koji build failures for Rawhide OSTree commits, or writing a koji-shadow replacement in Python for RISC-V. New coders are highly encouraged to introduce themselves in the Fedora Python Matrix channel, where existing members are actively offering mentorship and starter projects.

Across the various Fedora groups, the primary focus is the progression of the Fedora 45 release, with teams actively navigating the Beta freeze, conducting Blocker Review meetings, and completing QA and feature testing. Concurrently, significant infrastructure and tooling transitions are a shared priority; multiple groups are gathering workflow requirements for an upcoming Red Hat Bugzilla replacement, finalizing the migration from the newly retired Pagure.io to the Forgejo-based Fedora Forge, and integrating modern build systems like Konflux. Package maintenance and policy refinement also dominate daily operations, characterized by widespread updates to packaging guidelines across ecosystems (including Python, NodeJS, and cryptography), coordinated responses to security advisories (notably RUSTSEC vulnerabilities), and the mass-orphaning of inactive packages. Finally, strategic structural alignments represent a common operational thread, highlighted by the EPEL 10 mass branching and repository restructuring, as well as ongoing proposals to unify CoreOS with Bootc technologies.

Announcements

Critical deadlines have arrived for Fedora 45 contributors: the "Complete" deadline for F45 Changes requires all tracker bugs to be updated to ON_QA, coinciding with the Fedora 45 Beta freeze, Bodhi updates-testing enablement, and Software String freeze. Additionally, contributors must meet a September 1 deadline to submit bug tracker workflows to help identify a replacement for Red Hat Bugzilla as its maintenance winds down. On the community engagement front, the Fedora Badges application has been completely revamped with a modern, fast single-page interface, and content creators can now utilize editorial-guide-ramalama, a new RAG-based local AI assistant designed to verify article drafts against Fedora's editorial guidelines before submission.

For the broader Linux community, several new technical guides have been published. Users can learn how to monitor drive health using Performance Co-Pilot (PCP) to catch subtle warnings of SSD or NVMe failure before data loss occurs. Those interested in local AI development can explore a guide on running Ollama locally with Podman to keep host systems clean and isolated, as well as a tutorial on how to safely sandbox AI coding agents using microVMs to prevent unauthorized automated access to production clusters or local work environments.

Council

The Fedora Council met to discuss the Fedora Forge Usage Policy and the proposed Innovation Lifecycle (Sandbox). The Council achieved consensus on the Forge Usage Policy, clarifying CI resource access for spins and remixes, and establishing a notification-only process for new remixes.

Additionally, extensive debate took place regarding the level of early technical oversight required for the Innovation Sandbox, prompting the scheduling of a dedicated follow-up workshop.

Decisions

• The Fedora Forge Usage Policy will be updated for version 5 to explicitly state that spins and remixes are permitted CI resources. Requests for infrastructure resources for new remixes must CC a Council member for visibility, but formal Council approval is not required.
• The Fedora Forge Usage Policy will remain open for one final week of feedback; if there are no further edits, it will proceed to an official Council vote.
• The Council will hold a dedicated, public video call on Thursday, September 3, 2026, at 14:00 UTC+1 to workshop the Innovation Lifecycle Proposal to resolve ongoing debates about FESCo's involvement.

See the detailed report for the Council team.

Learn more about the Council team.

FESCo

During this week, FESCo held a meeting to discuss ongoing system transitions and policy updates, including the rollout of 2FA for provenpackagers, the handling of binary executable content in node_modules, and the timeline for gathering requirements for Fedora's upcoming Bugzilla replacement. The committee also finalized a major policy change regarding where Fedora Changes discussions will take place moving forward.

In ticketing and forum activity, FESCo formally approved the use of AWS-LC for cryptography in Rust packages, bringing clarity to package maintainers struggling with the ring crate. Additionally, several non-responsive maintainer tickets were processed, resulting in package handovers and the mass-orphaning of inactive maintainers' packages, while a draft for Crystal packaging guidelines was submitted for community review.

Decisions

• Approved the F46 Change: Changes Discussion Only On Devel List, making it effective immediately. Discussions regarding Changes will now happen solely on the devel mailing list and will no longer be simultaneously discussed on Discourse.
• Approved the inclusion and use of the aws-lc-sys and aws-lc-rs crates for cryptography in Fedora to replace the ring crate wherever possible, via Ticket #3679. This exception will be documented in the Packaging Guidelines.
• Agreed to close the re-review of the F45 Change: RelocateRpmRepoConfigsToUsr, as major known issues affecting rpm-ostree, anaconda, and container composes have been resolved or mitigated.
• Approved extending the deadline for gathering Bugzilla replacement requirements to September 4th to accommodate additional feedback from teams, as discussed in Ticket #3664.
• Approved mass-orphaning of packages for non-responsive maintainers cleber (Ticket #3659) and gui1ty (slated for Sep 4 per Ticket #3678), while approving the handover of packages for benzea (Ticket #3672) and prarit (Ticket #3665).

See the detailed report for the FESCo team.

Learn more about the FESCo team.

Packaging Committee

This week, the Packaging Committee's activity focused on updating and clarifying packaging guidelines across various ecosystems to prevent contributor confusion and accommodate structural changes. A new ticket was opened to document an exception for limited aws-lc use within the system-wide CryptoPolicies.

In the NodeJS ecosystem, new guidelines for using different nodejs versions have been finalized to detail how packaged streams should be utilized after the upcoming metapackage change. Additionally, the Python packaging guidelines are being revised to explicitly state that using %pyproject_buildrequires automatically satisfies the mandatory python3-devel build requirement, making redundant declarations unnecessary.

Decisions

• Consensus was reached to update the Python build requirements guidelines to explicitly clarify that utilizing %pyproject_buildrequires automatically fulfills the mandatory python3-devel dependency.
• The proposed guidelines for using different nodejs versions were marked as ready to merge after incorporating guidance on handling runtime dependencies and shebangs.

See the detailed report for the Packaging Committee team.

Learn more about the Packaging Committee team.

Mindshare

This week, Mindshare focused heavily on in-person event representation, travel funding, and committee governance. The core theme connecting the active tickets is establishing a strong physical Fedora presence at regional open source conferences and ensuring proper internal representation on the Fedora Council.

The committee received two new travel support requests: one to record on-site Fedora Podcast episodes and present a talk at Texas Linux Fest 2026, and another to host a Fedora sub-booth alongside Red Hat India at IndiaFOSS 2026. Meanwhile, action was requested on the open Fedora Council Representative Nomination ticket to clarify earlier voting miscommunications and finally select the Mindshare liaison for the Fedora Linux 44 cycle.

See the detailed report for the Mindshare team.

Learn more about the Mindshare team.

Workstation / GNOME

The Workstation / GNOME group reviewed progress on several upstream and integration initiatives this week. Key topics included resolving recent bug-reporting friction with the Showtime project, acknowledging the failure of the current Flatpak strategy regarding Flathub integration, and discussions around Bazaar as a potential GNOME Software replacement.

Additionally, community members provided updates on restoring Google Drive integration for GNOME, noting that testing is temporarily delayed while developers adapt to recent upstream changes. Preparations are also underway for the Fedora 45 Blocker Review meetings, with a call for asynchronous QA voting.

Decisions

• The working group confirmed that the effort to filter the Fedora Flatpak repository remains formally blocked by the pending GNOME Software redesign, per the meeting summary.
• It was decided that the integration of the Bazaar app store requires a new contributor to take over the review process, as the original contributor is no longer responding.
• Neal Gompa will review the ticket regarding the replacement of xvfb-run with wl-headless-run for GNOME packages and close it if no further action is required.
• Allan Day will chair the next working group meeting, with Matthias Clasen serving as secretary.

See the detailed report for the Workstation / GNOME team.

Learn more about the Workstation / GNOME team.

KDE

KDE Gear 26.08.0 is now available for testing on Fedora 44 and newer. While a minor bug regarding missing icons in Dolphin's "Details" mode was identified, an upstream patch has already been secured for the forthcoming 26.08.1 release. Additionally, the Fedora QA team has scheduled an upcoming Fedora 45 Blocker Review meeting to address proposed blockers and freeze exceptions for the upcoming Beta and Final releases.

See the detailed report for the KDE team.

Learn more about the KDE team.

Server

The Server group met on August 26 to discuss Fedora 45 release testing and Project Ansible support. For F45 testing, the team is actively verifying features and installations, though hardware limitations for ARM and RAID setups have caused minor bottlenecks, prompting targeted volunteer efforts. A minor, non-blocking bug regarding Kickstart was identified during the testing phase.

On the Ansible support front, the working group verified that the Wildfly role functions properly when Java 25 is configured. The team agreed that the Wildfly and post-install modules are near completion and will serve as pilot projects, with beta user testing slated to begin in two to three weeks. In addition, the Fedora QA team announced Blocker Review meetings for Fedora 45.

Decisions

• The Server working group will use the post-install and Wildfly Ansible modules as pilot projects, with beta user testing slated to begin in two to three weeks. (Meeting Log)

See the detailed report for the Server team.

Learn more about the Server team.

Infrastructure

The Fedora Infrastructure team has officially entered the Fedora 45 Beta infrastructure freeze, which will remain in place until mid-September to ensure stability for the upcoming release. In major ecosystem news, Pagure.io has been officially retired as an active platform and transitioned into a read-only static archive for historical purposes. Concurrently, the team is heavily preparing the new Forgejo instance (Fedora Forge) to take over production Dist Git duties, including provisioning storage, refining access controls, and finalizing project board support.

Ongoing maintenance focused heavily on RHEL 10 migrations, with Zabbix servers successfully upgraded and Mailman servers queued next. The team also addressed a severe spam attack on the fedora-devel mailing list by banning the offending user, cleaning the archives, and implementing new moderation headers. Finally, various monitoring improvements were discussed, including stabilizing database OOM kills and tuning OpenShift app load balancer metrics.

Decisions

• The Fedora 45 Beta infrastructure freeze is in effect from August 25 until approximately September 15. Frozen production hosts cannot be modified without sign-off from sysadmin-main or rel-eng.
• Pagure.io has been officially turned off as an active service and converted into a read-only historical archive.
• A freeze break was approved for the new-updates-sync script to ensure RHEL users receive the correct EPEL 10 epel-release-latest symlink and avoid dependency errors.
• A generic internal guest account was enabled for Zabbix to allow the Copr team to easily forward status metrics to Grafana without complex SAML authentication.
• A new FAS group, sysadmin-public-inbox, was created to manage the public-inbox OpenShift deployment.

See the detailed report for the Infrastructure team.

Learn more about the Infrastructure team.

Release Engineering

The Release Engineering team enacted the Fedora 45 Beta Freeze on August 25 and began tracking Beta release tasks. A significant amount of the week was spent navigating infrastructure hiccups, including a Koji hub DDoS that stalled builds and dropped mounts, F44 Flatpak compose timeouts, and Rawhide ostree compose failures. In a F45 mass branching retrospective, the team noted successes in automation but highlighted the need to strictly prevent massive, disruptive updates right before branching.

Meanwhile, several infrastructure requests were addressed, including the setup of a temporary empty repository for F46 OpenH264 to bypass 404 errors until binaries are published. The new fedpkg request-unretirement tool saw active testing by maintainers, revealing some quirks regarding Rawhide branch unblocking.

Decisions

• The Fedora 45 Beta Freeze went into effect on August 25.
• Blocker bugs and freeze exceptions for the Beta release were accepted, including fixes for anaconda-webui crashes, kmscon initial-setup breakage, and the inclusion of LLVM 23.
• A large batch of Fails-To-Install (FTI) packages for F45 in the NEW state were retired as per the release schedule.
• Releng will update docs and templates to firmly warn maintainers against pushing last-minute disruptive changes right before mass branching.
• binutils-2.47.50-4.fc46 and ELN equivalents were untagged due to regressions breaking Rust builds.
• An empty repo was established for F46 OpenH264 to prevent 404 errors during builds while awaiting Cisco's binary uploads.
• The coreos-pool tagging keys were updated by removing the F43 key and adding the F46 signing key.

See the detailed report for the Release Engineering team.

Learn more about the Release Engineering team.

Quality

The Quality group was highly active this week as Fedora 45 reached its Beta freeze and Bodhi enablement point. The GNOME 51 test day concluded successfully with 30 participants submitting 135 test results. Early manual validation testing for Fedora 45 was also completed, uncovering multiple bugs across different architectures.

Additionally, the team evaluated proposed blockers in their Beta blocker review meeting, deciding on key anaconda-webui and kmscon bugs. The group is also urgently compiling requirements for the upcoming Red Hat Bugzilla replacement system, which are due by September 1st.

Decisions

• Accepted Fedora 45 Beta Blockers for an anaconda-webui review screen crash (Bug 2519654) and a kmscon bug that breaks console initial-setup on ARM minimal (Bug 2484542).
• Accepted Fedora 45 Beta Freeze Exceptions to pull LLVM 23 into Fedora 45 (Bug 2506941), to address missing obsolete packages for Python 3.14 (Bug 2492124), and to fix an anaconda-webui dependency issue preventing soas livespin creation (Bug 2517903).
• Declared User switching restart failure as an Accepted Final Blocker, but rejected it as a Beta Blocker (Bug 2501857).

See the detailed report for the Quality team.

Learn more about the Quality team.

Design

This week, the Design team saw continued progress on graphic design requests and repository maintenance, though some coordination activities were paused due to Madeline being on PTO. New artwork was submitted for the EPEL Steering Committee badge, and the migration of historical repositories to the new Forge organization was reviewed.

See the detailed report for the Design team.

Learn more about the Design team.

Docs

This week, the Fedora Docs team held a meeting to discuss ongoing projects, including the frontpage redesign and proposed updates to the Release Notes process. A major milestone was reached with the merging of a long-standing pull request that restructures the team documentation, successfully splitting the Docs Contributors Guide into its own module for better visibility.

Additionally, the team evaluated ticket activity, opening a new discussion on archiving or removing End-of-Life (EOL) distribution pages and processing a membership request. The team is actively seeking community input on the frontpage redesign and continues to request help with manual wiki migrations.

Decisions

• The Release Notes process will be updated to include clear documentation questions in the Fedora Change template, which will directly affect all Fedora Change owners. (Meeting Log)
• The Docs Contributors Guide has been moved into a separate module to allow placement on the Docs landing page, finalizing the team documentation restructuring. (Issue #55)
• Docs group membership requests will be denied unless the applicant has already made demonstrable contributions to repositories within the Docs organization on Forge. (Issue #60)

See the detailed report for the Docs team.

Learn more about the Docs team.

Internationalization

The Internationalization group focused on optimizing translation resources and streamlining issue tracking. Key discussions included centralizing the issue tracker for localization-docs repositories by redirecting them via API to the main localization tracker, and removing archived documentation (sysadmin and install guides) from Weblate to save resources.

Additionally, the team fielded requests regarding unsupported Fedora releases and an upstream KDE translation error. Both were closed and redirected to the appropriate channels (Fedora Docs and the upstream KDE translation team, respectively), clarifying the scope of the Fedora localization team's responsibilities.

Decisions

• Archived and unpublished documentation (Sysadmin Guide and Install Guide) will be removed from Weblate to free up resources, while keeping their underlying Git repositories.
• Unsupported (EOL) Fedora releases will remain in Weblate as long as they are still published on Fedora Docs; requests to hide them must be directed to the Fedora Docs team.
• Translation issues for upstream projects (such as KDE Plasma Vault) are out of scope for Fedora Localization and must be reported directly to upstream translation teams.

See the detailed report for the Internationalization team.

Learn more about the Internationalization team.

EPEL

This week, the EPEL group successfully completed the EPEL 10.3 mass branching, officially shifting standard development on the epel10 branch to target the upcoming EPEL 10.4 release. Packagers wanting to build specifically for EPEL 10.3 must now request and use a dedicated epel10.3 branch. The transition went smoothly, overcoming some infrastructure adjustments required for the new "10s" repository naming scheme.

Simultaneously, the team deployed the first phase of the EPEL 10 "de-z-ification" initiative. CentOS 10 systems with the latest release package will now use the new epel-10s metalink pointing to 10.4, while RHEL changes will follow in the fall with the release of RHEL 10.3. The team also addressed a minor but impactful bug regarding symlink churn for the EPEL 10 release RPM, temporarily fixing it to prevent repository dependency errors for users.

Decisions

• Builds submitted to the default epel10 branch now target EPEL 10.4 following the completion of the EPEL 10.3 mass branching. Packagers who need to build against EPEL 10.3 specifically must request and use the epel10.3 branch.
• The first phase of the EPEL 10 "de-z-ification" proposal was put into production. CentOS 10 systems now utilize the epel-10s metalinks and paths, which redirect to the epel-10.4 repository, to prevent package dependency issues on private mirrors. Details were announced on the discussion forum.
• The MirrorManager mapping logic for EPEL 10 was adjusted to use explicit minor versions (e.g., epel-10.4) with redirects for prior minor versions, rather than keeping the existing mapping and setting up redirects for future ones. (Discussion Post)

See the detailed report for the EPEL team.

Learn more about the EPEL team.

CentOS Hyperscale

During the August 26, 2026 meeting (log), the CentOS Hyperscale SIG announced that the wprof tool has graduated from incubation and is now available in Fedora and EPEL 10. The SIG has rebased to 7.1 kernels and plans to transition to 7.2 shortly after Fedora does. In broader ecosystem news, AlmaLinux is actively considering building the Hyperscale kernel for its users, which sparked discussions on kernel signing limitations and potential expansion of Hyperscale packages into AlmaLinux's extra repositories.

The group also discussed the progression of transactional Hyperscale updates, noting that core elements have been ported to dnf5. Work is actively proceeding on packaging these components, tracked via Bugzilla issues 2521657, 2521661, and 2521666. Additionally, a KDE proposal to improve enterprise technologies was highlighted for its strong alignment with Hyperscale's system snapshot capabilities.

Decisions

• The SIG decided to retain the EPEL 9 builds of wprof in the experimental hsx repository, despite its graduation to standard repositories for Fedora and EPEL 10.
• Davide Cavalca and Neal Gompa will finalize and submit the delayed Hyperscale quarterly report this week.

Learn more about the CentOS Hyperscale team.

ELN

During the August 25, 2026 meeting, the ELN SIG focused on infrastructure, sync processes, and tooling improvements. The group discussed options for building ELN and CentOS toolbox and container images, specifically weighing whether to migrate from Kiwi to image-builder for CentOS parity or to wait for future Konflux adoption; the decision was deferred for further investigation. The team also debated how to optimize the ELN Build Sync (EBS) timeout duration to prevent buildroot breakage during high-load events like mass rebuilds, with discussions moving to the tracker.

Most significantly for the broader Fedora and Linux packaging ecosystem, the SIG reached a consensus to stop using the Rawhide GPG key for ELN. Instead, they will provision a dedicated ELN key starting with the F46/EL11 branching. This key will be rotated approximately every three years to align with RHEL branching, which should resolve the recurring signing-related disruptions that typically happen during the Fedora branching process.

Decisions

• The SIG agreed to provision a new, dedicated GPG key for ELN starting with the F46/EL11 branching, rather than continuing to use the shared Rawhide key. This key will be rotated roughly every 3 years (aligned with RHEL branchings) to avoid widespread signing-related breakages during Fedora branching. (Meeting log)

Learn more about the ELN team.

Atomic

The Fedora Atomic group successfully added base and compose images for Fedora 45 in Konflux, while actively working to resolve build failures for IoT images alongside the IoT team. Ticket discussions highlighted a strong theme around improving the bootc image derivation process, focusing on trademark compliance and filesystem structure.

Administratively, steps were taken to grant write access to new maintainers for the base-images repository on both GitLab and the Fedora Forge. Users also reported a critical bug causing emergency mode on non-BTRFS filesystems (ext4/XFS) following recent system updates, which is currently under investigation.

Decisions

• Sean Thrailkill and Hristo Marinov were formally approved for maintainer access to the base-images repository and the Fedora Forge.
• A new Fedora Account System (FAS) group will be created for maintainers to safely isolate bot permissions on the Forge.
• The IoT team will fix their Konflux image builds now that they are aware of the failures, and coordinate future strategy for CoreOS, bootc, and IoT images.
• Ticket #125 will strictly track logos, release, and release notes packages for derived builds, with a separate ticket (#126) opened to track the /usr/local and /opt symlink issues.

See the detailed report for the Atomic team.

Learn more about the Atomic team.

CoreOS

During the week of August 24-30, 2026, the CoreOS group held one meeting to review pending action items, coordinate around the Fedora 45 (F45) release schedule, and discuss a major proposal to unify CoreOS and Image Mode/Bootc. Key discussions revolved around navigating the F45 beta freeze to implement zram/oomd enablement, and scheduling the F45 Test Day for September 21st.

The team had a highly positive initial reaction to the Bootc unification proposal, viewing it as a natural progression that could reduce duplication of effort across Fedora variants. This initiative will be proposed to the Bootc community next week to evaluate feasibility and alignment.

Decisions

• Tentatively scheduled the Fedora CoreOS 45 Test Day for 2026-09-21 (tracked in CoreOS #934).
• Agreed to prioritize completing the zram/oomd implementation for F45 and address any beta freeze exceptions afterward if necessary.

See the detailed report for the CoreOS team.

Learn more about the CoreOS team.

ARM

This week, the ARM group primarily discussed hardware compatibility and upcoming release blockers. A user reported a kernel error when attempting to boot an older Fedora 43 installation on a Raspberry Pi 5 Model B Rev 1.1. The issue was bypassed by upgrading to a Fedora 44 image, prompting maintainers to close the inquiry since Fedora 43 is no longer a focus.

Additionally, QA announced the upcoming Fedora 45 Blocker Review Meeting scheduled for August 31, 2026. Community members were invited to participate in the triage of proposed blockers and freeze exceptions for the Beta and Final releases.

Decisions

• Maintainers will not investigate or support boot issues specific to Fedora 43 on newer hardware revisions (like the Raspberry Pi 5 Rev 1.1), as development focus has shifted to Fedora 44 and newer.

See the detailed report for the ARM team.

Learn more about the ARM team.

Hummingbird

This week, an update was shared in the Hummingbird Community Meeting - 20 August 2026 thread regarding a new project. Jorge Castro announced that a version of Bluefin built on Hummingbird technology is essentially finished and will serve as a full peer to Dakotaraptor. He emphasized his complete commitment and support for this variant, noting that initial code pushes to its new repository are expected shortly.

Learn more about the Hummingbird team.

AI & ML

The AI & ML group met to discuss ongoing packaging efforts and long-term goals (meeting log). Work on PyTorch 2.13 has temporarily stalled in Rawhide and Fedora 45 due to a libstdc++ update that conflicts with ROCm, causing build breaks. Meanwhile, ROCm 10.0 (previously referred to as ROCm 8) was released on August 26. This major upgrade marks a shift in AMD's release pace and support model. The group is currently evaluating potential ABI breakage, though efforts are slightly hampered by libabigail crashing on debuginfo packages.

The group also explored the feasibility of shipping "open weights" AI models (like Nvidia's Nemotron 3 or AMD's open models) directly in Fedora. The consensus is that training or rebuilding these models from scratch within Fedora's build system (Koji) is currently unrealistic due to extreme hardware requirements (e.g., 64x MI300 GPUs) and timeouts. Doing so would require dedicated infrastructure proposals and deep-pocketed sponsors to provide heavy cloud compute resources.

Decisions

• ROCm 10.0 packages will be staged and maintained in the ROCm packagers preview COPR until basic testing is completed and the scope of ABI changes is fully quantified.

Learn more about the AI & ML team.

Security

This week, the Security SIG's primary focus was discussing a draft proposal for a new Fedora Privacy SIG, which originated from earlier conversations about maintaining the ff-disable-ai-ml package. The group debated the appropriate scope for such a SIG, noting that while security and privacy are closely related, a dedicated Privacy SIG might inadvertently attract ideological or political debates rather than technical contributions.

To address these concerns and ensure good optics—particularly to avoid appearing antagonistic toward the AI/ML SIG—the group agreed to postpone any formal launch. Instead, members will take extra time to review the RFC and intend to focus initially on concrete, ad-hoc technical work, such as packaging clear privacy config toggles for users.

Decisions

• Deferred the formal creation and announcement of the proposed Privacy SIG to allow members more time to review the draft and refine its scope.
• Agreed to focus on tangible, ad-hoc technical implementations (such as packaging user privacy toggles) to establish a technical foundation before officially spinning off a new SIG.

See the detailed report for the Security team.

Learn more about the Security team.

Go

During the Go SIG meeting, it was announced that Go 1.27.0 is now available in Rawhide. Maintainers will soon move this update into Fedora 45 and trigger a mass prebuild on COPR. The SIG is also preparing to retire Go 1.25 in Fedora 43 in favor of Go 1.26, aligning with upstream Kubernetes requirements which have dropped support for 1.25 across all supported releases.

Additionally, the team discussed a new method for handling security vulnerability reports. A community member modified an upstream CRI-O script to generate govulncheck output in openvex format. This script makes it much faster to verify if a package is actually affected by specific CVEs without having to run manual checks for each one. The script will be shared publicly on platforms like GitHub or Forgejo to help maintainers triage Bugzilla tickets more efficiently.

Decisions

• Move Go 1.27.0 into Fedora 45 and perform a mass prebuild on COPR.
• Open a ticket to retire Go 1.25 in Fedora 43 and transition to Go 1.26 to support recent Kubernetes releases.

Learn more about the Go team.

Perl

This week's activity on the Perl mailing list consisted entirely of package maintenance pull request notifications from Michal Josef Špaček. Key updates centered around the perl-DBD-ODBC package, which was re-submitted for Fedora review, updated with a new EPEL10 package, and received miscellaneous updates. Additionally, the perl-Archive-Extract package received version 0.90 version bumps across multiple branches.

Decisions

• The perl-DBD-ODBC package was re-submitted for Fedora review and merged.
• An EPEL10 package was created and merged for perl-DBD-ODBC.
• The perl-Archive-Extract package was bumped to version 0.90 across several pull requests.

Learn more about the Perl team.

Python

This week, the Python group discussed the behavior of %pyproject_patch_dependency when packaging multiple Python distribution packages in a single specfile. They agreed that its current behavior—filtering dependencies from all distributions—is sensible for most use cases but needs to be properly documented. An option to filter by a specific distribution name might be considered in the future.

In addition, flit-core has been updated to version 4. A deprecated compatibility package, python3-flit-core3, was introduced for packages that still require older versions. However, maintainers are expected to eventually migrate their packages to flit-core 4+.

Decisions

• Maintain the current behavior of %pyproject_patch_dependency (filtering from all dists) when multiple distributions are present, but document it properly.
• Update flit-core to version 4 and provide a deprecated python3-flit-core3 compatibility package for packages that have not yet migrated, with the expectation that all packages will eventually migrate to flit-core 4+.

Learn more about the Python team.

Rust

This week, the Rust group focused heavily on addressing various RUSTSEC security advisories and dealing with unmaintained crates across the ecosystem. Significant efforts were directed toward updating critical dependencies, notably the lru and git2 crates, to mitigate vulnerabilities, alongside planning migrations away from archived crates with unfixed soundness issues like smartstring, bitmaps, sized-chunks, and im-rc.

A major theme of the week was coordinating package updates and rebuilds gracefully. Because of the large number of dependent packages in the Fedora ecosystem, temporary compatibility packages are being introduced (such as for git2), and the group finalized a strategy for handling security rebuilds for affected packages they do not directly co-maintain, prioritizing cross-team communication over unilateral action.

Decisions

• Rather than invoking provenpackager privileges to force rebuilds of applications affected by the cxx RUSTSEC advisory, the group will file targeted bugs against the applications, linking the advisory and advising maintainers to simply rebuild their packages (Issue #36).
• A temporary rust-git2_0.20 compatibility package will be added to the repositories to prevent breaking a large number of dependent packages while they are being ported to git2 v0.21.0 (Issue #30).
• The group will wait until lru v0.18 is available in the repositories before attempting to patch the bounds for dependent packages like pydantic (Issue #39).

See the detailed report for the Rust team.

Learn more about the Rust team.

Other Discussions

• Michael Scherer initiated a discussion on Dynamic users with sysusers and bootc/image mode, noting that sysusers.d in image mode can cause UID mismatches on upgrades, and proposed amending packaging guidelines to pair it with a tmpfiles.d fragment to properly chown files in /var.
• Mattia Verga posted the latest report on Inactive packagers for the F45 release cycle, prompting a request from Miroslav Suchý to include plain text lists of usernames directly in the email rather than relying solely on the ticket tracker links.
• Norbert Manthey proposed to Extend default compiler settings to harden applications by adding flags like -fno-strict-overflow and -ftrivial-auto-var-init=zero. Daniel P. Berrangé noted that while the latter eliminates vulnerabilities, it can cause non-trivial performance degradation (e.g., 9% in virtio-blk) that maintainers must address.
• SY Wang raised an issue regarding No response from the main admin on a libxsmm pull request open for two months. Other users noted similar issues and advised following the formal nonresponsive maintainer policy via Bugzilla.
• Tobias Girstmair asked for advice on Questions on packaging vim-classic so it can coexist with standard vim. Maxwell G and Simon de Vlieger suggested starting with renamed or suffixed binaries rather than using the alternatives system.
• Aoife Moloney announced a DEADLINE: Please Submit your Bug Tracker Workflows by Sept 1, 2026 to collect workflow requirements for an eventual Red Hat Bugzilla replacement, though the tight deadline was questioned by Quality team members.
• Chihurumnaya Ibiam reported a FTBFS/FTI Page Not Found issue in an auto-generated comment link, which Miro Hrončok promptly fixed while reminding contributors to report tooling issues directly to the releng ticket tracker.
• Henryk Paluch noted that the Package Sponsorship page points to decommissioned pagure.io, and was directed to the new Fedora Forge tracker and an open pull request designed to fix the documentation.
• Kevin Fenzi confirmed the spam wave is over, stating that the spammers were banned, the archives cleaned, and new header rules were added to block similar messages.
• Orion Poplawski posted Help wanted with ansible mysql/mariadb collections, seeking a new maintainer for ansible.mysql as they are migrating to ansible.mariadb; Andreas Haupt volunteered to take it over.
• Other discussions included an announcement of the upcoming F45 Blocker Review Meeting, and two PRs from Bojan Smojver to address a Failed F44 Flatpak compose holding back updates.

Package updates

• Dominik 'Rathann' Mierzejewski announced an [SONAME BUMP] ffmpeg upgrade from 8.1 to 9.0 for Rawhide and F45, successfully rebuilding all dependents in a COPR with minimal issues.
• Milan Crha noted the target for libical 4.0 for rawhide is now Fedora Linux 46 due to its incompatibility with the 3.x series API.
• Gwyn Ciesla announced an Upcoming gumbo-parser soname bump to version 0.14.0 in Rawhide, noting dependent packages have built fine in a side tag.
• Christoph Erhardt warned about a SONAME bump in Rawhide: mimalloc 3.5.0, which will require pull requests for dependent packages like moarvm, mold, and rakudo.
• Milan Crha organized a GNOME 51.rc update for rawhide and f45, creating side tags (f46-build-side-149189 and f45-build-side-149193) for maintainers to group their package builds.
• Milan Crha shared a heads-up that gnome-autoar 0.5.0 drops gnome-autoar-gtk in rawhide, and plans to push it to F45 if there are no undetected users.

Orphaning packages

• Peter Hutterer is Orphaning evtest, evemu and some X11 utilities (sessreg, x11perf, etc.), noting that evtest functionality has been superseded by libinput record.
• The automated Orphaned packages looking for new maintainers report highlighted a massive list of unmaintained packages; in response, Henryk Paluch volunteered for python-aexpect and Ben Beasley adopted several Rust crates (rust-find-crate, rust-hidapi, rust-tinystr).
• Benson Muite is Orphaning python-proton-vpn-api-core because tracking its new native Rust extensions and submodule dependencies is too time-consuming.

New contributor introductions

• Charles Haithcock introduced himself as a former RHEL kernel troubleshooter who is now working on Fedora kernel bugs and hopes to become more entrenched in the community.
• Bri Mo introduced himself as an applied AI/ML engineer and OSINT enthusiast running Silverblue 44 and container-first workflows with Podman.

Contribution opportunities

Testing and Quality Assurance: Community members looking for highly accessible ways to contribute can help streamline the release process by voting on proposed blocker bugs and freeze exceptions using the blockerbugs app (requested by Workstation/GNOME, KDE, Server, Release Engineering, and ARM). Testers are also needed to evaluate Google Drive integration in GNOME, the KDE Gear 26.08.0 release, ROCm 10.0 packages, and transactional updates. More involved QA tasks include investigating Atomic Desktop boot failures on non-BTRFS systems, benchmarking tuned-ppd performance, and writing test cases for upcoming Anaconda test days or CoreOS testing events.

Design, Documentation, and Community Governance: Non-developers can make significant impacts by shaping project identity, documentation, and policies. Designers are invited to create an avatar for the Matrix Moderation Bot or submit artwork for the upcoming Fedora 46 Wallpaper call. Documentation volunteers can guide the Docs frontpage redesign (Issue #6, Issue #52), assist with Wiki cleanup (Issue #43), and modernize the Request for Resources process. Contributors are also encouraged to review and provide feedback on the Fedora Forge Usage Policy, the Innovation Lifecycle Proposal, Draft Crystal Packaging Guidelines, the Privacy SIG RFC, and the CoreOS Unification proposal. Additionally, bilingual users can report translation errors directly to upstream translation teams.

Programming and Scripting: Software developers have opportunities to write automation tools and patch ecosystems. Scripting tasks include using the Forgejo API to redirect localization issue trackers, building tools to adjust NodeJS shebangs, and creating a programmatic fix for EPEL 10 symlink churn. UI/UX developers can tackle low-hanging fruit by adding a power-off option to the GNOME initial setup screen, building system snapshot integrations aligned with KDE's enterprise goals, or developing user-facing privacy toggles. Rust developers are urgently needed for security auditing and migrating Fedora packages away from unmaintained crates like smartstring (Issue #38) and updating git2 dependents.

Packaging, Infrastructure, and Sysadmin: Contributors with packaging and system administration skills are highly sought after to adopt orphaned packages resulting from unresponsive maintainers, including PackageKit-Qt5, ansible.mysql, and Python utilities (sponsorship is available for adopters of packages like python-aexpect). Python packagers can also assist by migrating spec files to flit-core v4+. Infrastructure volunteers can help prepare for RHEL 10 by building missing EPEL packages needed to migrate Mailman servers, fix Ansible inventory macros, and update the Koji theme footer URI. Furthermore, packaging contributors can help create generic Fedora remix assets to ease trademark compliance for derived bootc builds.

Across the Fedora project, a major unified focus is the urgent preparation for the Fedora 45 Beta Freeze on August 25, 2026. Multiple groups—including Release Engineering, Quality, and various architecture and desktop SIGs—are finalizing mass branching, managing fails-to-install (FTI) packages, and conducting Blocker Review meetings to triage critical issues, such as widespread rpm-ostree breakages caused by the recent RPM repository configuration relocation to /usr. Concurrently, significant infrastructure shifts are a central theme, highlighted by the decommissioning of pagure.io into a read-only static archive and the formulation of usage policies for the new Forgejo-based Fedora Forge. Finally, routine package and system maintenance remains a shared priority, with teams actively auditing inactive maintainers, coordinating mass rebuilds for EPEL 10.3 and RISC-V, and modernizing packaging strategies across language-specific ecosystems like Python, Perl, and Rust.

Announcements

Significant infrastructure shifts are underway as pagure.io transitions to a permanent, read-only static archive, cementing the new Forgejo-based Fedora Forge as the primary development platform. Accordingly, the Fedora Council is finalizing the Fedora Forge Usage Policy, which restricts the new forge strictly to Fedora-related projects, marking a departure from the previous general-use scope of Pagure. In brighter community news, the Fedora Badges service has been completely rebuilt from the ground up into a fast, modern single-page application and is currently heading to production.

As Fedora 45 approaches its Beta Freeze, developers are urgently reminded that all F45 system changes must be marked "Complete" by August 25. Concurrently, routine maintenance has identified over 200 inactive packagers for the F45 release cycle; affected contributors must comment on their tracking tickets to avoid being removed from the packager group. Finally, contributors and general Linux enthusiasts are invited to participate in the Fedora 45 Test Days starting August 17 to help evaluate major upcoming software changes—including GNOME 51, RPM 6.1, and OpenSSL 4.0—on both real hardware and virtual machines.

Council

This week, the Fedora Council focused on policy development and event planning. A revised draft (Version 3) of the Fedora Forge Usage Policy was published for an extended community feedback period before an impending Council vote. Additionally, the Council began brainstorming Call for Papers (CfP) themes for Flock to Fedora 2027, and initiated a discussion on clarifying the AI-Assisted Contributions Policy regarding commit message attribution.

See the detailed report for the Council team.

Learn more about the Council team.

FESCo

FESCo had a busy week managing package maintainer responsiveness, assessing feature changes for Fedora 45, and planning the requirements for Fedora's upcoming Bugzilla replacement. The committee addressed major regressions in rpm-ostree caused by the RelocateRpmRepoConfigsToUsr change, opting to grant maintainers a few more days to implement fixes before forcing a revert. In addition, FESCo handled multiple non-responsive maintainer tickets and approved several system-wide changes, including dropping the NIS profile from authselect and updating python-cloudflare for certbot.

Decisions

• FESCo approved the Change to Drop low-memory-monitor package, retiring it and starting a non-responsive maintainer process for its owner.
• The committee agreed to give developers until Friday to fix the rpm-ostree breakages caused by the RelocateRpmRepoConfigsToUsr change; otherwise, the change will be reverted for Fedora 45.
• FESCo approved the Authselect Remove NIS Profile change proposal.
• An updates policy exception for python-cloudflare was approved to facilitate a major update to certbot.
• Due to a lack of majority during the meeting, FESCo decided to return the vote for Changes Discussion Only On Devel List to the ticket.
• The following changes were officially marked as accepted for Fedora Linux 45: Anaconda WebUI Fedora Atomic, Encapsule isolated devel containers, Web Based Remote Installation Support for Atomic Desktops, and IBus 1.5.35.

See the detailed report for the FESCo team.

Learn more about the FESCo team.

Mindshare

The Mindshare group met on August 20, 2026 (meeting log) to share recent announcements and review open tickets. Key news included the production launch of Fedora Badges v3.x (Announcement, Try out) and Framework's announcement of their new Laptop 12 featuring an optional Fedora KDE pre-installation.

Due to low attendance, comprehensive ticket resolutions were largely deferred to asynchronous communication. Members reviewed event planning for Data Con LA 2026 (Issue 143) and All Things Open 2026 (Issue 128). They also discussed structural topics, including how to handle historically vacant Marketing and CommOps seats (such as CommOps Issue 145) on the committee.

Decisions

• The committee decided to alternate future weekly meetings between Matrix chat and video formats to improve attendance (see Issue #135).
• Committee discussions regarding the vacant Marketing and CommOps seats (e.g., CommOps Issue #145) will be moved to the main Mindshare channel to determine whether to bring those seats back to the broader electoral pool.
• It was decided to resolve Issue #131 asynchronously by the end of the month via a final summary comment.

Learn more about the Mindshare team.

Diversity & Inclusion

The Diversity & Inclusion group has begun early planning for the 2026 Fedora Week of Diversity. The event is tentatively scheduled around October 9th as a short, 2-to-3-hour virtual event featuring 10-to-20-minute talks. The current proposed theme is "Respect the Culture," though the group is actively open to brainstorming other options.

Learn more about the Diversity & Inclusion team.

Workstation / GNOME

This week, the Workstation Working Group focused on cleaning up default installations and third-party repositories. They discussed the removal of GNOME Boxes from the default installation, a change likely slated for version 52, while keeping GNOME Connections. Additionally, they approved the removal of PyCharm from third-party repositories due to its outdated Community Edition.

Elsewhere on the forum, users expressed concerns over the maintenance status of Ptyxis and suggested Fedora prepare a contingency plan. More details can be found in the Workstation Working Group Meeting Summary and the Ptyxis discussion.

Decisions

• Approved the removal of PyCharm from the Fedora Workstation third-party repositories, as the Community Edition no longer exists as a separate codebase. (Meeting Summary)
• Decided to remove GNOME Boxes from the default installation, effectively delaying the action until version 52, while keeping GNOME Connections in the default set. (Meeting Summary)

See the detailed report for the Workstation / GNOME team.

Learn more about the Workstation / GNOME team.

KDE

This week, the KDE group announced that KDE Gear 26.08.0 is built for Fedora 44+ and ready for community testing. Community discussions focused on user requests for changes to the Fedora repositories and spins, specifically regarding the inclusion of Kgamma2 for Wayland and a debate over offering a "Minimal Installation" option for the KDE desktop to reduce default application bloat.

In addition, the Fedora QA team notified the KDE mailing list about the upcoming Fedora 45 Blocker Review Meeting for the Beta release, encouraging early votes on proposed blocker bugs.

Decisions

• The KDE Plasma Edition SiG released the KDE Gear 26.08.0 update to Bodhi for community testing on Fedora 44 and newer.

See the detailed report for the KDE team.

Learn more about the KDE team.

Server

The Server working group held a meeting this week focusing on Fedora 45 release testing, Ansible support restructuring, and documentation improvements. A new member joined the group to help document homelab, Podman, and systematic backup strategies. Additionally, Adam Williamson announced the upcoming Fedora 45 Blocker Review Meeting, encouraging members to review and vote on proposed blockers in advance.

Decisions

• The group agreed to split the current 'post-installation' documentation article into several shorter, more specific articles (e.g., First steps, Networking, Storage, Security hardening, Automatic updates, Backups) housed in a separate subdirectory.
• The group decided that the Ansible postinstall role will be structured as a single role using boolean variables to toggle specific tasks, which will eventually be packaged as an Ansible Collection and distributed via both Ansible Galaxy and RPM.

See the detailed report for the Server team.

Learn more about the Server team.

Infrastructure

The Infrastructure team completed a major planned outage to apply updates, reboot servers, and advance the RHEL 10 migration, which now has only 33 hosts remaining. Notable infrastructure changes included moving download servers to BBR congestion control for improved syncing, preparing the pagure-ro01 VM as a read-only archive ahead of the pagure.io shutdown, and successfully migrating the Matrix moderation bot to official Fedora infrastructure. Additionally, the the-new-hotness bot was fixed to resume filing Bugzilla bugs after a token expiration.

In the community and services space, a discussion is ongoing regarding the deprecation of the retrace.fedoraproject.org server, as the maintaining ABRT team no longer exists. While QA finds the service valuable, it currently lacks active maintainers. Forgejo development continued with monitoring implementation and SSH enabled on staging, while several authentication bugs affecting FreeIPA and accounts.fedoraproject.org are under active investigation.

Decisions

• The pagure-ro01 VM is now live and will serve as the read-only static archive for the upcoming pagure.io turnoff.
• The official Matrix Moderation bot has been migrated to Fedora infrastructure (@moderation:fedoraproject.org), with a draft policy introduced for managing official Fedora Matrix rooms.
• The retrace.fedoraproject.org server is slated for retirement due to a lack of active maintainers, pending a final call for volunteer engineers.
• Download servers have been moved to BBR congestion control, resulting in significant package syncing gains.

See the detailed report for the Infrastructure team.

Learn more about the Infrastructure team.

Release Engineering

The Release Engineering team focused heavily on the Fedora 45 release cycle, finalizing post-fixes for the mass branching process and preparing for the Beta Freeze scheduled for August 25. As part of this cycle, FTI (Fails To Install) packages in the NEW state were processed for retirement, and a Blocker Review meeting was announced for the upcoming Beta release. Furthermore, progress was made on infrastructure improvements, such as preparing the new Fedora 46 (Rawhide) openh264 builds for Cisco and enhancing documentation.

A significant operational shift highlighted this week is the full transition to self-service package unretirements. Maintainers opening unretirement tickets were directed to use the fedpkg request-unretirement command instead. To support this, the background tooling (toddlers) was updated with retry logic and fixes for Koji tag resolution on Rawhide. The team also handled routine requests to untag buggy updates (such as freeipa and bash-color-prompt) to prevent widespread test failures, and processed multiple EPEL stalled package handovers.

Decisions

• Package unretirements are now fully self-service. Maintainers should use fedpkg request-unretirement instead of opening Releng tickets, as advised in multiple unretirement requests.
• The Fedora 45 Beta Freeze will take effect on Tuesday, August 25, 2026.
• bash-color-prompt-0.96-1.fc46 was untagged due to unintended visual changes to the root terminal prompt.
• freeipa-4.13.3-1.fc46 was untagged to prevent a serious upgrade bug from gating all subsequent Rawhide updates.

See the detailed report for the Release Engineering team.

Learn more about the Release Engineering team.

Quality

Fedora 45 branching is mostly complete, though it was heavily complicated by the late-stage landing of the RPM repo config relocation to /usr. This required urgent patching across Anaconda, openQA, and Kiwi, and currently leaves ostree broken. Early manual validation testing for Fedora 45 is ongoing and has already surfaced notable bugs, including missing initial setup screens on non-graphical disk images (affecting Server and Minimal) and system freezes during shutdown.

In broader community news, a significant discussion highlighted performance and efficiency regressions caused by the default switch from power-profiles-daemon to tuned-ppd. Users and developers are actively debating whether to adjust the default TuneD profiles or revert the change entirely. Additionally, QA efforts are moving forward to formally propose replacing the unmaintained mcelog package with rasdaemon.

Decisions

• The group agreed to support an upcoming formal Change proposal to replace mcelog with rasdaemon by default, as mcelog is minimally maintained and fails on modern, unsupported CPUs. (Discussed in the Quality meeting and forum thread)

See the detailed report for the Quality team.

Learn more about the Quality team.

Design

This week, community members praised the newly revealed Fedora 45 wallpaper on the Fedora 45 Wallpaper Inspiration Poll. The team is already preparing for the next release, having recently held the Fedora 46 wallpaper mindmap call. In documentation news, the Design Docs have been revamped with newly published How We Work and Meetings pages.

On the tracking side, a contributor is asking for scoping clarification on the Community Personas project to determine whether deliverables should include a comic or just character illustrations. Additionally, older legacy repositories like designassets have been successfully migrated to the new design organization on Forge to preserve their history before Pagure is deprecated.

Decisions

• The legacy designassets repository (along with several others) was formally migrated to the new design organization on Forge to preserve historical content before Pagure is retired (Ticket #82).

Learn more about the Design team.

Docs

This week, the Docs team and community members engaged in a discussion regarding the Fedora Installer's recommendation for a separate /boot partition, exploring the technical constraints and historical reasons behind it. Additionally, a broken link reported on a Fedora test results wiki page was addressed and resolved after being properly routed to the Quality team.

Decisions

• Outdated links to the relval package documentation in the Release validation instructions wiki template were fixed by the Quality team. (Issue #61)

See the detailed report for the Docs team.

Learn more about the Docs team.

Internationalization

The Internationalization group held a meeting on August 17 to review the progress of Fedora 45 changes, bug triaging for Fedora 43, and upcoming test events. Three changes for Fedora 45 (Fontconfig 2.18, LibreOffice Dictionaries, and IBus 1.5.35) have been accepted and will be transitioned to the MODIFIED state before next week's ON_QA deadline. Contributors were also reminded of key Fedora 45 milestones approaching on August 25, including the Beta Freeze, Bodhi updates-testing activation, and the 100% Code Complete deadline.

Learn more about the Internationalization team.

Legal

Vitaly inquired on the legal mailing list about the licensing of a JavaScript port of CPython's argparse (thread). The question centered on whether the port could be licensed under PSF-2.0 alone, rather than carrying the full CPython license stack, since the original code was added in 2010. Richard Fontana followed up by addressing the question directly on the upstream pull request.

Learn more about the Legal team.

COPR

Branched Fedora 45 chroots, which are builds copied from Rawhide, are now enabled and available for use in Fedora Copr. This update was announced on the copr-devel mailing list.

Decisions

• Branched Fedora 45 chroots have been enabled in Fedora Copr (source).

Learn more about the COPR team.

EPEL

This week, the EPEL team's primary focus was preparing for the upcoming EPEL 10.3 mass branching scheduled for August 24, 2026. This process will create the EPEL 10.4 tags and involves temporarily disabling builds to the epel10-candidate target, as announced on the epel-announce and epel-devel mailing lists and discussed during the weekly meeting.

Additionally, the team discussed two package updates moving into testing: the new epel-release update for CentOS Stream 10 and a long-awaited ffmpeg compatibility package for EPEL 9. Both updates require community testing and feedback.

Decisions

• Proceed with the EPEL 10.3 mass branching on 2026-08-24, temporarily disabling builds to the epel10-candidate target during the process.

See the detailed report for the EPEL team.

Learn more about the EPEL team.

Atomic

This week, the Atomic group saw brief activity across two forum discussions. A moderator action took place on an older discussion regarding Lenovo shipping ThinkPad laptops with Fedora, splitting off newer posts into a dedicated topic for new AI-ready ThinkPad models.

Additionally, a discussion regarding the behavior of /opt and /usr/local as symlinks in Silverblue and bootc images received a response. It was clarified that existing systems heavily rely on this legacy behavior, and any proposed changes to make them regular directories would require a comprehensive migration path.

Learn more about the Atomic team.

CoreOS

The CoreOS group met on August 19, 2026 (meeting log) to review the Fedora 45 Release Schedule ahead of the beta freeze. The team evaluated several proposed Fedora 45 system-wide changes to determine their impact on Fedora CoreOS, updating their F45 tracker. Most reviewed changes, such as LLVM 23, CMake variable drops, and disabling vendor changes by default, are expected to be transparent to FCOS.

The group also discussed ongoing work and blockers. Incomplete branching for fedora-bootc images is currently holding up Rawhide and Fedora 45 progress. Ongoing investigations continue for the relocation of RPM repo configs (Issue #2172) and the impacts of an OpenSSL upgrade (Issue #2165) and RPM cryptographic policy changes (Issue #2085).

Decisions

• Determined that the DisableVendorChangeByDefault change does not require specific accommodation work for FCOS, though users performing derived container builds should be aware of potential impacts.
• Confirmed that the LLVM-23 and CMake_drop_install_vars transitions should be transparent to FCOS.
• Decided to adopt the Grub2LightForConfidentialComputing bootloader exclusively in future confidential computing efforts (e.g., sealed/UKI images), rather than utilizing it for general usage in F45.
• Assigned enablement and dependency testing for FESCO Ticket #3661 (conditional on Fedora 45+) to volunteer Angel Cervera Roldan.

Learn more about the CoreOS team.

IoT

The Fedora IoT Working Group met to discuss the status of stable and upcoming releases ahead of the Fedora 45 Beta Freeze on August 25, 2026. Fedora 44 remains stable, with testing progressing well on a new Greenboot update. However, both Fedora 45 and Fedora 46 have encountered critical installation failures that caused their OpenQA tests to be canceled. The group is actively triaging these bugs, particularly focusing on issues related to Anaconda and rpm-ostree.

Decisions

• File a bug against Anaconda regarding the recent installation failures and officially flag it as a blocker for the Fedora 45 Beta release.
• Open an official issue/bug tracker for the rpm-ostree failure impacting Fedora 45, as the primary maintainer is currently on PTO.

See the detailed report for the IoT team.

Learn more about the IoT team.

ARM

Adam Williamson announced the upcoming Fedora 45 Blocker Review meeting, scheduled for August 24, 2026, at 16:00 UTC on Matrix. The agenda includes evaluating 3 proposed blockers and 3 proposed freeze exceptions for the Beta release against the Fedora Release Criteria.

Learn more about the ARM team.

Hummingbird

The Hummingbird group held its community meeting on August 20, 2026 (summarized here). Key updates included the introduction of the Gorget project for managing source tarballs and dependencies, progress on the bootable host (which is dropping the "bootc" name for trademark reasons), and broader Fedora Atomic Initiative efforts to expand Konflux access outside of Red Hat. The group celebrated reaching 3,100 packages in the repository and over 500 users of their images on public GitHub.

A major topic of discussion centered around establishing contributor pathways and building trust within a highly automated, SLSA-compliant environment. The team acknowledged that current restrictions (such as build logs hidden behind private logins) clash with Fedora's open philosophy and act as a barrier to external contribution. To address this, they agreed to break the contributor ladder down into three distinct areas: infrastructure code, build system operations, and image content creation.

Decisions

• The bootable host project is dropping the name "bootc" due to trademark reasons (Meeting notes).
• Managed Konflux infrastructure on the Fedora instance is being made available outside of Red Hat; tenant access can now be granted to anyone with a standard Fedora account (Meeting notes).
• The Hummingbird contributor ladder will be broken down into three distinct pathways to accommodate different access levels and interests: core infrastructure code, internal factory/build system configuration, and image content creation (e.g., spec and container files) (Meeting notes).

Learn more about the Hummingbird team.

Kernel

The kernel-ark os-build branch has been rebased. This continues a standard cadence established since version 5.15, aligning with upstream releases. By rebasing near the end of a release cycle when outstanding merge requests are minimal, the team ensures that patches carried by Fedora remain no more than one release out of date. This practice maintains the project's spirit of openness and makes patches easier to apply to other trees.

Decisions

• The kernel-ark os-build branch was rebased, continuing the established cadence of rebasing for every upstream release (which will continue for 7.3, 7.4, etc.).

Learn more about the Kernel team.

RISC-V

The Fedora RISC-V group successfully concluded the mass rebuild for Fedora 45, leaving a delta of fewer than 1,000 packages. The team is preparing to analyze the remaining "fails to build from source" (FTBFS) packages and unresolved dependencies once another full delta rebuild is complete. In the weekly meeting, members also highlighted solid progress on building installer images utilizing Anaconda and image-builder.

On the hardware front, the team is actively debugging glibc mutex failures on Titan (DP1000) boards and has temporarily disabled some builder boards due to proxy issues. Additionally, members suggested starting Fedora 46 preparations earlier than usual to maintain momentum while the package delta remains manageable.

Decisions

• Temporarily disabled specific hardware boards in the build cluster due to a proxy failure (source).
• Enabled coredumps to investigate and resolve glibc mutex failures occurring on Titan (DP1000) boards (source).

Learn more about the RISC-V team.

Security

The Security group focused on privacy-enhancing initiatives and SELinux integration for systemd-run0 this week. During their August 20th meeting, the SIG debated adopting a package (ff-disable-ai-ml) that disables Firefox AI/ML features, ultimately concluding that a dedicated Privacy SIG would be a more appropriate home. Consequently, a draft proposal for a new Fedora Privacy SIG was created and is currently open for feedback.

In SELinux developments, discussions on the systemd-run0 policy issue thread yielded a path forward for making run0/systemd natively SELinux-aware. This upstream fix will dynamically calculate target user contexts, bypassing the current architectural limitations of PAM transitions via PID 1.

Decisions

• The proposal to move the ff-disable-ai-ml repository to the Security SIG was placed on hold in favor of creating a dedicated Privacy SIG. (Meeting Log)
• The group agreed to draft a proposal for a new Fedora Privacy SIG. (Meeting Log)
• It was agreed to pursue an upstream fix making systemd-run0 natively SELinux-aware, rather than relying on static policy rules to handle transitions. (Mailing List)

See the detailed report for the Security team.

Learn more about the Security team.

DotNET

This week, Amine Kheddache introduced a free AI chat platform called Ptero on the DotNet SIG mailing list. The tool requires no signup and provides access to multiple large language models. It is designed to assist C# and .NET developers with debugging, generating boilerplate code, brainstorming architecture patterns, and explaining complex concepts like LINQ and async.

Learn more about the DotNET team.

Perl

This week, the Perl group focused on routine package updates and continuous integration testing. Michal Josef Špaček opened and merged four pull requests (PRs 13 through 16) to bump the perl-Mozilla-CA package to version 20260813. In addition, Steve Traylen continued work on PR #5 for perl-SQL-Abstract to disable the Perl bootstrap, successfully triggering a Packit CI scratch build to test the configuration.

Decisions

• Merged updates to bump the perl-Mozilla-CA package to version 20260813 via PR #13, PR #14, PR #15, and PR #16.

Learn more about the Perl team.

Python

This week, the Python group clarified that redundant manual license file declarations can be safely removed from specfiles in favor of using %pyproject_save_files --assert-license unconditionally, provided the package requires flit-core 3.11 or newer (Drop second copy of LICENSE file?).

The group also agreed on a migration strategy for the backwards-incompatible flit-core v4 release. To avoid widespread build failures for packages pinning flit-core < 4, the primary package will be updated to v4 while simultaneously introducing a deprecated v3 compatibility package. This will allow time to gradually patch dependent users (Plan for flit-core v4).

Decisions

• Specfiles requiring flit-core >= 3.11 can safely drop manual %license directives and rely exclusively on %pyproject_save_files --assert-license (Source).
• The migration to flit-core v4 will be handled by updating the main package to v4 and providing a deprecated v3 compatibility package, allowing dependent packages to be patched incrementally over time (Source).

Learn more about the Python team.

Rust

This week, the Rust group discussed a proposal for a new RPM packaging strategy aimed at eliminating the large volume of empty feature subpackages by using conditional metadata dependencies instead. Contributors weighed the impact of the currently generated Rust feature packages, noting that while they constitute a significant percentage of Fedora's package count, their actual payload and size remain negligible. Additionally, a new package review request for rust-ssh2 was submitted.

See the detailed report for the Rust team.

Learn more about the Rust team.

Other Discussions

• Jakub Kadlčík provided an update on a prototype for a reimagined Fedora Package Review Process using Forgejo pull requests, custom Copr build scripts, and vendored dependency handling.
• Yann Droneaud asked if the kernel configuration and System.map files duplicated between /boot and /lib/modules could be deduplicated using symlinks, successfully testing a boot where symlinks pointed to /lib/modules.
• Orion Poplawski announced that the community.mysql ansible collection has been renamed and is seeking a new maintainer for the ansible.mysql collection.
• Following an s390x builder outage, Kevin Fenzi and Michel Lind discussed resource constraints and Koji lag metrics, noting that s390x builds are significantly delaying active maintainers.
• Petr Sklenar reported that an update to file 5.47 caused systemd .service files to be misidentified, breaking brp-mangle-shebangs; maintainers are advised to explicitly install unit files with 0644 permissions.
• Gwyn Ciesla volunteered to step in and save the matrix-synapse package after it was retired due to failing to install.
• Adam Williamson requested that developers stop hardcoding static lists of Fedora releases in their tooling, recommending automated endpoints like Bodhi's releases API.
• Henryk Paluch asked for clarification on the pagure.io decommissioning, and it was clarified that src.fedoraproject.org (dist-git) remains unaffected until a future migration to Forgejo.
• Bojan Smojver submitted a pull request to Bodhi to systematically address compose failures caused by hitting open file limits.
• Norbert Manthey proposed extending Fedora's default compiler flags (e.g., -fno-strict-overflow) to prevent overly aggressive optimizations that could introduce security vulnerabilities.
• Other discussions this week included a report of a nonresponsive maintainer for low-memory-monitor, stats from the inactive packager check for F45, a non-responsive maintainer check for ddcutil, an announcement that pagure.io is now a read-only static archive, a request to retire python-PyPDF2 and pdf-stapler, a call for package review swaps, the unretiring of bodhi-server, a reminder of the F45 Changes Complete deadline, and a notice regarding a license change in mysql-connector-java.

Orphaning packages

• Peter Hutterer announced he is orphaning evtest, evemu, and several X11 utilities as they are unmaintained upstream.
• Neal Gompa orphaned showtime because the upstream project now refuses bug reports from non-Flatpak builds; it was quickly adopted by Fabio Valentini.
• Lumír Balhar orphaned python-tiktoken, which is a leaf package.

Package updates

• Julian Anderson requested a Koji retrigger for golang 1.25.13 and 1.26.6 updates, which were then fixed by Alejandro Saez Morollon after identifying an upstream regression.
• Dan Horák issued a heads up for an update to sg3_utils-1.49 containing a soname bump, requiring a sidetag rebuild for dependent packages.
• Jerry James notified the list of a soname bump for z3 that will require reverse dependencies to be rebuilt.

New contributor introductions

• Jose Lopez introduced themselves as an embedded systems engineer interested in packaging, low-level Linux development, and eventually Linux kernel drivers.

Contribution opportunities

For contributors interested in Testing, Quality Assurance, and General Feedback, there are numerous entry-level opportunities across the project that do not require specialized team membership. Community members are highly encouraged to help with Fedora 45 early manual validation testing, test branched F45 builds, and participate in the Internationalization Test Week starting September 7. Users can quickly assist by testing the KDE Gear 26.08.0 Bodhi update, the new epel-release update, and the freshly launched Fedora Badges v3.x platform. Furthermore, anyone can help shorten release meetings by asynchronously voting on blocker bugs and freeze exceptions using the Blockerbugs app. General feedback is widely requested on several community-wide topics, including the Fedora Forge Usage Policy, Conflict of Interest Guidelines, AI-assistance attribution in commits, the Privacy SIG proposal, and the Ptero AI tool for .NET (mailing list thread).

Those with Writing, Design, and Event Organization skills are highly sought after to support project infrastructure. Documentation writers can tackle server-side "white spots" (like Podman containers, HPC, and domain controllers), review installer and partition layout guides, or update Workstation marketing materials to reflect that GNOME Boxes is no longer a pre-installed application. Artists and UX contributors are invited to help shape and illustrate the Community Personas project, review legacy assets in designassets, or propose new QA data visualizations in Ticket #923. On the events and community side, volunteers are needed to organize the 2026 Fedora Week of Diversity (FWD)—which has openings for schedule management, marketing, and video editing—or staff the Fedora table at All Things Open 2026 (Issue #128). Contributors seeking leadership roles can also look into open committee seats on CommOps (Issue #145).

Contributors proficient in Package Maintenance can step in to keep the distribution healthy by adopting orphaned packages, claiming retired packages using fedpkg request-unretirement, or co-maintaining packages currently facing the non-responsive maintainer process (Ticket #3678 / sponsors issue tracker). Language-specific packagers can provide feedback on the proposal for "features/extras" packaging without subpackages, assist with the Python flit-core v4 migration by patching dependency constraints, or review pending packages like rust-ssh2. Community members are also encouraged to participate in cross-team package review swaps to help unblock dependencies.

Finally, there are critical Systems Engineering and Debugging tasks for developers and sysadmins. The Infrastructure team welcomes newcomers to help port packages for the RHEL 10 migration and is urgently seeking 1-2 engineers to take over maintenance of the retrace (FAF) crash analytics server. System architects and engineers can jump in to investigate severe installation failures, such as IoT's Anaconda boot failure and rpm-ostree bugs, or analyze CoreOS's OpenSSL upgrade impacts and FESCO Ticket #3661 enablement. There are also specialized opportunities to investigate RISC-V mass rebuild build failures, help systemd-run0 become natively SELinux-aware upstream, or submit YAML manifests and container files to the new Hummingbird build factory using standard pull requests.

Across the various Fedora groups, the overarching focus this week was on the successful Fedora 45 mass branching and its subsequent release preparations, which drove extensive testing, mass rebuilds (particularly for the RISC-V architecture), and CI/CD validation efforts. Concurrently, infrastructure and engineering teams were heavily engaged in major system upgrades, notably migrating services to RHEL 10, executing planned server outages, transitioning repositories to Forgejo, and implementing network blocklists to mitigate aggressive automated scraping that temporarily disrupted operations. Policy and governance updates were also a central theme, as the Council and FESCo worked to finalize the Fedora Forge Usage Policy, establish new Conflict of Interest guidelines, and address community concerns regarding AI-integrated software and regulatory liability under the EU Cyber Resilience Act. Finally, routine ecosystem maintenance and security remained high priorities, evidenced by the active processing of non-responsive maintainers, Out-of-Band security patching for vulnerabilities like the "Zapscape" kernel flaw, and ongoing dependency and macro improvements across language stacks like Python and Go.

Announcements

On the development and infrastructure front, Fedora 45 successfully completed its mass branching on August 11 (following an initial notification), placing the release into a post-branch freeze until a successful compose. Change owners were also reminded that all F45 changes needed to be testable by August 11. Contributors should prepare for a six-hour planned infrastructure outage on August 20 for server upgrades and RHEL 10 migrations. Policy updates are also underway, with the Council seeking feedback on the proposed Fedora Forge Usage Policy for the project's internal Forgejo instance. In broader ecosystem news, Mark J. Wielaard was honored with the Distinguished Service Award in Software Freedom by the Software Freedom Conservancy for his decades of foundational work on tools like Valgrind, elfutils, and Sourceware.

For those looking to get involved, the Fedora QA team is calling for volunteers for the upcoming Fedora 45 Test Days (detailed further in a Fedora Magazine article), starting with GNOME 51 on August 17 and followed by testing for RPM 6.1 and installation media. If you are a newcomer unsure of where to start interacting with the community, Episode 058 of the Fedora Podcast provides a comprehensive guide to Fedora's communication channels. Finally, users can check out a new tutorial on how to monitor NVMe and SSD drive health using Performance Co-Pilot (PCP).

Council

This week, the Council focused heavily on community policies and governance processes. Significant progress was made on the Fedora Forge Usage Policy, with the Council agreeing to adjust guidelines around Personally Identifiable Information (PII) and dropping the automated repository archival rule in favor of a mandatory "tickets" contact repository for organizations. Additionally, the Council agreed to propose a new Conflict of Interest guideline requiring neutral oversight during private decisions involving access rights.

Other major topics included a proposal by Red Hat to act as the Open Source Software Steward for Fedora under the EU Cyber Resilience Act (CRA) to shield volunteer contributors from regulatory liability. The community also discussed user concerns over AI features embedded in packaged software, clarifications to the AI-Assisted Contributions Policy, and an updated draft of the Fedora Innovation Lifecycle to create a sandbox for large experimental changes.

Decisions

• Agreed to update the Fedora Forge Usage Policy to include a short sentence on handling Personally Identifiable Information (PII) under the Code of Conduct section, address remaining feedback in a v.3 draft, and allow one more week of community review before voting.
• Agreed to propose a new Conflict of Interest guideline for governance groups, stating that private decisions regarding access rights should require mediation or oversight from project leadership (FPL/FCA/FOA) if a conflict of interest exists, and to gather community feedback before formalizing the change.

See the detailed report for the Council team.

Learn more about the Council team.

FESCo

This week, FESCo held one meeting, participated in three forum discussions, and handled 19 tickets. During the meeting, FESCo noted that the completion deadline and mass branching for Fedora 45 had arrived, and briefly discussed the need for mitigations against aggressive automated scraping on the src.fedoraproject.org infrastructure. On the forums, community members initiated a discussion on whether Fedora needs a formal policy or labeling system for packages that introduce AI-powered features, highlighting concerns about data privacy and unexpected behavior.

A significant portion of FESCo's activity in tickets involved voting on Change proposals for F45 and F46, resulting in the approval of several new features including a WebUI installer for Fedora Atomic, the deprecation of the NIS profile in authselect, and the introduction of a new encapsule developer container tool. Additionally, FESCo processed multiple non-responsive maintainer tickets, resulting in the orphaning of some packages and the assignment of new maintainers to several critical components like thermald and mcelog.

Decisions

• Approved Change: Web Based Remote Installation Support for Atomic Desktops (Ticket #3670).
• Approved Change: Anaconda WebUI Fedora Atomic (Ticket #3666).
• Approved Change: Encapsule isolated devel containers (Ticket #3668).
• Approved Change: IBus 1.5.35 (Ticket #3669).
• Approved Change: Authselect Remove NIS Profile (Ticket #3662).
• Approved Change: Disable in Kernel Crypto Userspace API Phase 1 (Ticket #3667).
• Approved Change: Enable systemd-oomd and zram swap for CoreOS (Ticket #3661).
• Approved Change: Sequoia openpgpverify (Ticket #3660).
• Approved an updates policy exception for python-cloudflare (Ticket #3674).
• Approved a one-time updates policy exception for thermald across all Fedora branches to fix power management issues (Ticket #3673).
• Approved the non-responsive maintainer process for the owner of python-avocado and python-aexpect, leading to the packages being orphaned (Ticket #3659).
• Approved adding new co-maintainers for thermald, libfprint, fprintd, and fwts under the non-responsive maintainer policy (Ticket #3672).

See the detailed report for the FESCo team.

Learn more about the FESCo team.

Ambassadors

This week, the Ambassadors group received a single announcement regarding the Call for Sessions for the Everything Open 2027 conference. Fedora contributors are encouraged to submit proposals for talks or tutorials relating to Linux, open source, security, or operations by September 6, 2026. For more details, see the mailing list post.

See the detailed report for the Ambassadors team.

Learn more about the Ambassadors team.

Workstation / GNOME

This week, the scheduled Workstation Working Group meeting was cancelled due to a scheduling conflict. The primary discussion in the community centered around the future of the Ptyxis terminal emulator in Fedora, as its original author confirmed he is no longer maintaining the project.

Community members discussed potential alternatives to replace Ptyxis, including Ghostty and GNOME Console. To determine an official path forward and prevent wasted effort by community translators on an abandoned upstream project, a formal ticket was filed with the Workstation Working Group.

See the detailed report for the Workstation / GNOME team.

Learn more about the Workstation / GNOME team.

Server

During the week of August 10-16, 2026, the Fedora Server group focused on Fedora 45 branched release testing and documentation restructuring. The group celebrated the availability of group-wide CI/CD runners for the first time. Significant discussions were held regarding the Home Server spin-off, specifically evaluating a new virtualized Kiwi development and testing environment.

In documentation, the group decided to streamline by merging tutorial and use-case files into a single "Use cases" section. Testing for F45 is actively underway, though a partition type issue in the VM build requires a fix.

Decisions

• The documentation structure will be updated by creating a new "use cases" section that merges all use-case and tutorial files, leading to the deletion of the dedicated "Tutorials" section.
• The Working Group will finalize the specific restructuring details for the post-installation documentation sections in the related tracking ticket and vote on it during the next meeting.
• All working group members are requested to test the new virtualized build environment by following the Home Server README to build a dummy Fedora image.

See the detailed report for the Server team.

Learn more about the Server team.

Infrastructure

This week, the Infrastructure team focused heavily on migrating services to RHEL 10, scheduling a major 6-hour outage for August 20 to handle mass updates, reboots, and VM reinstallations. To combat severe scraping traffic on Fedora infrastructure (which temporarily spiked server loads and disrupted Anubis on Pagure), the team successfully implemented a new user-agent blocklist. The team is also officially migrating the Matrix moderation bot to Fedora's OpenShift infrastructure, alongside drafting new policies for "official" Matrix rooms. Finally, the legacy retrace.fedoraproject.org server is being decommissioned due to a lack of maintenance.

Decisions

• A 6-hour infrastructure outage is scheduled for August 20 at 20:00 UTC for mass updates, reboots, and RHEL 10 migrations.
• The unmaintained retrace.fedoraproject.org server will be shut down and decommissioned.
• The primary rsync servers have been switched to the BBR congestion control algorithm to improve download speeds.
• The Fedora Matrix moderation bot will be officially migrated to Fedora Infrastructure (@moderation:fedoraproject.org).

See the detailed report for the Infrastructure team.

Learn more about the Infrastructure team.

Release Engineering

This week, the Release Engineering team successfully completed the mass branching of Fedora 45 off of Rawhide, with Rawhide officially transitioning to Fedora 46. Concurrently, the mass re-signing process for Fedora 45 packages and the generation of the Fedora 47 IMA key took place. Additionally, the team finalized the migration of all Release Engineering repositories to Forgejo (fedora-scm-requests).

Other notable activities involved fixing an early signing issue for ELN packages, updating staging environments for koji-image-builder testing, and refining internal tools, such as creating a dedicated team to validate SCM requests and reduce notification spam. Maintainers are also reminded to use the new fedpkg request-unretirement feature instead of filing Releng tickets for routine package unretirements.

Decisions

• Fedora 45 was successfully branched from Rawhide, making Rawhide officially Fedora 46.
• Package maintainers no longer need to open Release Engineering tickets for package unretirements; they must now use the fedpkg request-unretirement command (requires fedpkg v1.48+).
• All Release Engineering repositories have been fully migrated to Forgejo.
• A new group (forge-releng-scm-validators) was established to handle SCM requests directly, resolving the issue of excessive pings to all members of the releng organization.
• The Fedora 43 signing key was removed from the coreos-pool and replaced with the Fedora 46 key.
• Nonresponsive maintainer processes were executed for the user cleber, resulting in the orphaning of their packages.

See the detailed report for the Release Engineering team.

Learn more about the Release Engineering team.

Quality

The Quality group focused on system performance, package default configurations, and preparations for the Fedora 45 release. Significant attention was brought to performance and power efficiency regressions caused by the switch to tuned-ppd, prompting discussions on how to better adjust the default TuneD profiles. Additionally, community testers successfully verified a critical GRUB Out-of-Memory fix in Rawhide.

In Quality Engineering (QE), early manual validation testing for Fedora 45 has started and already uncovered several significant bugs. The team also prepared tooling for the upcoming release, testing Issuebot in production and marking it ready for F45.

Decisions

• Issuebot has been successfully tested in production and is formally ready to run for the Fedora 45 release cycle.
• The GRUB Out-of-Memory fix was verified to work in Rawhide, allowing the pending rollout to Fedora 44 to proceed.

See the detailed report for the Quality team.

Learn more about the Quality team.

Design

Between August 10 and August 16, 2026, the Design team continued to refine key graphical assets for Fedora projects and internal tools, alongside ongoing UX work for the Fedora Design Docs revamp. Major discussions revolved around finalizing the character details for the LoLa AI Package Manager mascot and aiming to complete avatars for the Fedora Matrix bots by the end of the current sprint. Additionally, historical design assets were preserved through a repository migration from Pagure to the active Forge.

Decisions

• Migrated the legacy designassets repository from Pagure to the Design organization on Forge to preserve historical content and history.
• Utilized the Matrix ID @admin:fedoraproject.org as the official handle for the newly rolling-out moderation bot, which will require an avatar.

See the detailed report for the Design team.

Learn more about the Design team.

Docs

The Docs team met to discuss ongoing efforts to clean up outdated Fedora Wiki pages, exploring automated approaches using the MediaWiki API to replace tedious manual deletions. They also evaluated a new experimental CI site builder relying on Podman and discussed adopting the Vale linter, deciding to introduce it as a recommendation for local authoring before enforcing it in CI. Concurrently, a community forum discussion took place regarding the documentation and rationale behind recommending a separate /boot partition in Fedora installations. Team tickets tracked a new membership request, a broken link in the Server test results wiki page, and the extensive historical wiki cleanup effort.

Decisions

• The Vale linter will be introduced as a recommended tool for local authoring rather than a strict CI requirement to avoid blocking contributors with excessive errors.
• Mass deletion of obsolete Docs-related wiki pages (such as Fedora 8 and 11 guides) will continue, with script-based automation via the MediaWiki API being actively explored to streamline the process.

See the detailed report for the Docs team.

Learn more about the Docs team.

Internationalization

This week, the Internationalization group received a cross-posted invitation to speak at the Everything Open 2027 conference. Community members are encouraged to submit session proposals covering topics like Linux, open source, AI, security, and operations before the September 6, 2026 deadline.

See the detailed report for the Internationalization team.

Learn more about the Internationalization team.

Legal

This week, the Legal group discussed whether Copr projects are permitted to download and use proprietary software, specifically the NVIDIA CUDA toolkit, during the build process for otherwise free and open-source packages like cuda-python. The primary concern raised was that utilizing proprietary dependencies during a build could inadvertently include proprietary code in the resulting binaries, such as through inlined headers. The prevailing consensus was that this practice is not allowed if it results in the distribution of content that violates Fedora's allowed licensing rules.

Decisions

• Software built, hosted, and distributed in Copr must be governed entirely by an acceptable Fedora license. Downloading proprietary software (like the NVIDIA CUDA toolkit) during a Copr build process is generally unacceptable if it causes the resulting binary to include proprietary content, such as inlined code from proprietary headers.

See the detailed report for the Legal team.

Learn more about the Legal team.

COPR

A scheduled outage for the COPR servers was announced for 2026-08-12 at 07:30 UTC, lasting approximately three hours. The downtime allowed the team to update COPR packages to newer versions, providing bug fixes and new features to the general Linux community using the build service.

Community members with questions or issues were encouraged to use the Fedora Build System Matrix channel (#buildsys:fedoraproject.org) or comment on the associated infrastructure ticket.

Learn more about the COPR team.

EPEL

This week, the EPEL group focused heavily on repository architecture and package updates. The Steering Committee unanimously approved the "de-z-ification" of EPEL 10, aligning its repository structure with the upcoming EPEL 11 release by utilizing the $stream variable for CentOS while leaving RHEL without a suffix.

In package news, maintainers announced the migration of libgit2 dependents in EPEL 9 and EPEL 10 to the supported v1.9 branch to address security vulnerabilities, as well as minor updates to uv and ruff in the EPEL 10.3 testing repositories.

Decisions

• The EPEL Steering Committee unanimously approved the "de-z-ification" of EPEL 10. CentOS streams will use suffixed repository paths (e.g., epel-10s) while RHEL uses unsuffixed paths (e.g., epel-10), aligning with the approved EPEL 11 design.
• Packages depending on libgit2 in EPEL 9 and EPEL 10 will be migrated from the obsolete v1.7 branch to the supported v1.9 branch via pull requests.

See the detailed report for the EPEL team.

Learn more about the EPEL team.

ELN

The ELN group met this week to discuss recent updates, including the publication of bootc images, the minimization of go-vendor-tools for RHEL 11, and variant reorganizations such as moving Live images to a new AltImages variant and adding a new Extensions variant. The group also noted the F45 branching process, which temporarily paused builds, and highlighted that the next branching in six months will coincide with the RHEL 11 branching.

Additionally, the group discussed mitigating database bloat in Koji caused by failing draft build retries. A proposal was also made to adopt a separate GPG key for ELN content starting with Fedora 46 to reduce the frequency of key rotations from twice a year to once every three years.

Decisions

• Pursue a dedicated GPG key for ELN content starting with the F46/EL11 branching cycle to reduce key rotations, initiating the process by filing a releng ticket.
• Deploy a fix to the build sync tooling to prevent retries of consistently failing draft builds from rapidly filling up the Koji database.

See the detailed report for the ELN team.

Learn more about the ELN team.

Atomic

The Atomic group had a quiet week. During a brief meeting, members noted that ongoing Konflux integration work for Atomic Desktops is continuing. On the forums, a community member inquired about /opt and /usr/local functioning as symlinks in Silverblue and asked whether future Fedora bootc images will transition to using regular directories instead.

Learn more about the Atomic team.

CoreOS

CoreOS met once this week to discuss the Fedora 45 release schedule and a severe kernel vulnerability. Fedora 45 recently branched from Rawhide, and the team is preparing the necessary updates for coreos-installer and bootc images, alongside monitoring for F46 key signing issues in Rawhide.

The team also reviewed the recent "Zapscape" kernel vulnerability (CVE-2026-64561). They decided to issue an out-of-band kernel update for the testing and next streams to mitigate the issue for VM workloads immediately, rather than waiting for the scheduled stable release next week.

Decisions

• Issue an out-of-band kernel update for the testing and next streams to address the Zapscape vulnerability (CVE-2026-64561) prior to the next scheduled stable release.
• Use a package override via GitHub actions to fast-track the fixed kernel without promoting the entire testing-devel/next-devel stream.

See the detailed report for the CoreOS team.

Learn more about the CoreOS team.

ARM

During this week, the ARM group had a brief discussion regarding kernel availability for the Raspberry Pi 5. A community member inquired about a Fedora 44 (F44) kernel, noting the reliability of the current F43 kernel updates. It was confirmed that F44, F45, and Rawhide kernels are already available for the device in the existing COPR repository.

Learn more about the ARM team.

Alternative Images

In their recent meeting, the Alternative Images group announced that RISC-V tags and targets have been successfully set up, representing a major first step toward creating new RISC-V images. Furthermore, Kiwi descriptions for RISC-V have been provided by Andrea.

The group is designating the upcoming week as "image week." During this time, they will conduct their regular quarterly image updates and officially begin generating RISC-V images specifically for QEMU virtual machines and P550 hardware.

Decisions

• To begin generating RISC-V images specifically targeting QEMU and P550 hardware during the upcoming week.
• To proceed with the regular quarterly image updates next week.

Learn more about the Alternative Images team.

AI & ML

The AI & ML SIG met to discuss the upcoming ROCm 7.14 update for Fedora 46 and the use of the pi-coding-agent tool (available in Fedora 45) for automating day-to-day packaging review tasks. A major point of discussion was a proposal to split the AI/ML SIG into two distinct groups (packaging vs. end-user AI adoption). The group unanimously decided against the split, opting to maintain a "big-tent" approach while improving documentation to clarify roles. In other news, an all-new Electron RPM was submitted to unblock Podman Desktop in Fedora, alongside updates to Podman Desktop in COPR and a proof-of-concept Atomic Fedora CSB bootc image.

Decisions

• The proposal to split the AI/ML SIG into two separate groups (Packaging and AI Use) was rejected; the SIG will maintain a unified, "big-tent" structure.
• Clarified that membership in the general ai-ml-sig FAS group does not grant packaging commit rights, maintaining a clear security boundary for compliance efforts like the EU Cyber Resilience Act.

See the detailed report for the AI & ML team.

Learn more about the AI & ML team.

RISC-V

The Fedora 45 RISC-V mass rebuild is 85% completed (around 20,000 packages), significantly aided by community members and Red Hatters who contributed new builders to parallelize the process. You can view the rebuild status numbers here. Other focus areas included investigating a failed LLVM build with RISC-V patches, co-writing Koji querying scripts, and exploring "Agentic SDLC" ideas for automated FTBFS triage and image boot testing.

A major challenge this week involved AI scrapers bringing down the Koji hub over the weekend, which resulted in numerous build failures.

See the detailed report for the RISC-V team.

Learn more about the RISC-V team.

Security

The Security group held an open-floor meeting this week, where members discussed their roles, kernel maintenance, and the upcoming packaging of module-jail for Fedora. On the forums, a mass scan report from OpenScanHub was published for Fedora 45 Critical Path Packages, calling for maintainers to review AI-flagged security findings. Additionally, a complex architectural issue regarding systemd-run0 and SELinux was brought to the mailing list, with a request for community input on the best path forward.

Decisions

• Justin Forbes will maintain the Fedora package for module-jail and work to integrate it into the proper repositories as an opt-in security feature.

See the detailed report for the Security team.

Learn more about the Security team.

Go

The Go SIG met this week and primarily discussed the upcoming Go 1.27.0 release, which is expected soon alongside embargoed CVE patches for the 1.26 and 1.25 branches. The group also discussed architecture support, noting that i686 (32-bit x86) builds are increasingly being excluded from specific packages, though linux/386 remains a first-class port in the Go ecosystem and cannot be entirely purged yet due to system dependencies.

Decisions

• The SIG will run a mass prebuild once Go 1.27.0 is released to identify and fix any broken packages before requesting a mass rebuild.

See the detailed report for the Go team.

Learn more about the Go team.

PHP

This week, the PHP group received an update regarding an ongoing dependency resolution issue in EPEL where php-devel incorrectly pulls in php8.4-devel instead of the default PHP 8.3 stack. Remi Collet reported that although the package itself has been fixed, both the affected and fixed versions currently coexist in the EPEL-10.3 buildroot, meaning the issue remains unresolved.

Learn more about the PHP team.

Python

This week, the Python group evaluated a provisional dependency patching macro to simplify package builds and discussed formalizing its behavior. They also reached consensus on an RFC to expand automatic python(abi) dependencies to all file types installed in Python library directories.

Additionally, discussions were opened regarding a migration strategy for the upcoming flit-core v4 release to ensure compatibility ahead of the Fedora 46 branch, and guidance was provided to packagers dealing with upstream applications that pollute the global Python namespace.

See the detailed report for the Python team.

Learn more about the Python team.

Other Discussions

This week in Fedora, there were updates to the package review process and SCM request infrastructure, along with a multitude of package updates, soname bumps, and mass branching for Fedora 45.

• Fedora Package Review Process reimagined prototype development is ongoing, with Jakub Kadlčík updating the Copr custom build feature implementation and support for vendored sources to inch closer to an optimal Forgejo and Packit integration.
• A new tool named Kiritan was introduced by Fyra Labs as a Rust-based alternative to createrepo_c, promising significantly faster execution and lower RAM usage.
• The pagure.io sunset & scm-requests migration is officially finished for SCM requests, and the team is now finalizing a static page mirror and a workaround for private issues.
• In the binary content in node_modules thread, Gordon Messmer announced a major update to npm2rpm, providing new test packages for evaluating node dependency bundling.
• A non-responsive maintainer check was initiated by Federico Pellegrin to contact Lubomir Rintel (lkundrak) due to unanswered PRs and bugs across multiple packages.
• A discussion about compose failures with too many files concluded that the issue is likely due to a file descriptor leak in Bodhi rather than system file limits being configured too low.
• The community celebrated as Mark J. Wielaard received the Distinguished Service Award in Software Freedom at FOSSY 2026, recognizing his decades of service maintaining essential tooling like Valgrind, elfutils, and Sourceware.
• Maxwell G started a nonresponsive maintainer check for Sandro (gui1ty), noting a lack of activity since late 2025 across 77 packages.
• Tomas Kopecek proposed to drop Python 2 support from remaining Koji components in upcoming releases (1.37 or 1.38), creating a legacy branch for security updates instead.
• Other discussions this week included a call for sessions for Everything Open 2027, a planned infrastructure outage on August 20, the planned shutdown of the unmaintained retrace.fedoraproject.org service, the successful completion of the Fedora 45 Mass Branching (after its initial announcement), a reminder for the F45 Changes Testable deadline, reports on findings by static analyzers for F45 Critical Path Packages, and an error in the procps Ukrainian translation file.

Orphaning packages

• Gabriel L. Somlo is orphaning yosys, nextpnr, and related packages, which were subsequently picked up by Alexander F. Lent.
• Peter Hutterer is orphaning evtest, evemu, and several X11 utilities, with xkill already claimed by Artur Frenszek-Iwicki.
• An automated report detailed a large list of orphaned packages looking for new maintainers before they are automatically retired.
• Lumír Balhar is orphaning python-pipdeptree due to upstream shifting the main engine to Rust, complicating its dependency chain.

Package updates

• Pavel Raiskup announced the release of Mock v6.8 and mock-core-configs v45.1, featuring a new separate_check config option and a system_monitor plugin, though manual side-tag builds were needed to bypass some Bodhi gating issues.
• Marek Kasik prepared a poppler soname bump to 26.08.0 in Rawhide, coordinating rebuilds with dependent packages like Inkscape and LibreOffice.
• Luya Tshimbalanga announced the f45-backgrounds update, detailing fixes to allow lossy JPEG XL wallpapers to correctly render on KDE Plasma.
• Xavier Bachelot announced a libnfs 7.0.0 soname bump, providing a side tag for dependent package maintainers to rebuild against.
• Kaleb Keithley is updating Apache Thrift to 0.24.0, which includes a SONAME bump in rawhide.
• Milan Crha announced a libedataserver soname version bump for the 3.61.2 release in Rawhide.
• Jerry James notified the list about an upcoming z3 version 5.1 soname bump.
• Michael J Gruber announced a soname bump for girara, zathura, and mupdf to bring the latest versions to Fedora via side-tags.
• Ondrej Nosek released rpkg-1.70 and fedpkg-1.48, noting that the projects are now hosted on Fedora Forge and documentation is available on Readthedocs.
• Fabio Valentini warned about an upcoming pygit v1.20.0 update that removes several deprecated symbols and breaks backwards compatibility.

New contributor introductions

• Dirk Nehring introduced themselves as a long-time Linux user and VDR plugin author, looking for a sponsor to help package and maintain VDR plugins in Fedora.

Contribution opportunities

Community members with hardware access or environments for testing can immediately contribute to quality assurance efforts across various groups without needing prior team membership. Testers are needed to validate Fedora 45 bare-metal and VM builds, monitor Rawhide for CoreOS key signing breakages, and test new out-of-band CoreOS kernel updates addressing Zapscape. Users with specific hardware can test kernels on Raspberry Pi 5 or prepare to test upcoming RISC-V and P550 alternative images. Additionally, general contributors can test pi-coding-agent in Fedora 45, evaluate the provisional Python %pyproject_patch_dependency macro, run the Home Server README image build, clone the experimental docs-fp-o-ci-test site builder, or evaluate the separate_check feature in Mock 6.8. Those experiencing performance drops on modern hardware can also assist the Quality team in debugging TuneD configuration profiles.

Developers and packagers can step up to adopt orphaned packages (such as python-avocado, evtest, bottles, and Zim), or sponsor new maintainers like Dirk Nehring (Ticket #13470 for rust-plotters-backend). There is a high demand for fixing Fails To Build From Source (FTBFS) issues during the Go 1.27.0 mass prebuild, RISC-V LLVM patches, and EPEL migrations. Scripting opportunities include refining mass rebuild scripts (Ticket #13428, PR #13051), improving Bodhi update checks (Ticket #13468), assisting with a test assets repository server, packaging Zig applications for Workstation, or designing UI-side Ansible tasks for Zabbix. Additionally, package maintainers should review the August 2026 OpenScanHub report to resolve static analyzer findings or take over the retrace.fedoraproject.org service.

Contributors with writing or visual design skills can pick up valuable tasks without deep technical setups. The Design team welcomes interns and new contributors to illustrate Community Personas or create event flyers using tools like Inkscape. Writers can restructure the Server post-installation guide into self-contained AsciiDoc topics, write Kickstart coverage for dnsmasq, clean up legacy wiki pages (Issue #43), fix documentation links like relval (Issue #61), or propose content to the AI/ML documentation (Issue #38). Contributors can also clear legacy pagure.io links from the Fedora Ansible repository comments. Translators, however, are asked to pause localization on Ptyxis until a new default Workstation terminal is finalized.

Anyone in the wider community can provide valuable feedback on overarching project governance, legal policies, and community advocacy. Open discussions seeking input include the Fedora Forge Usage Policy, the Innovation Lifecycle proposal, Workstation WG issue #520 regarding terminal emulators, and the overarching policy on packages containing AI-powered features. Legal experts can evaluate open-source licensing edge cases involving dynamic linking or draft the GPU Acceptable Use Policy (Issue #35), while SELinux experts can advise on systemd-run0 integration. Finally, all contributors are encouraged to share their Fedora-related expertise by submitting session proposals to the Everything Open 2027 conference before September 6, 2026.

Across various Fedora groups, a major shared focus this week was preparing for the upcoming Fedora 45 release cycle, which included executing mass rebuilds, coordinating early manual validation testing, and finalizing change proposals ahead of the imminent branching deadline. Infrastructure transitions were another critical common item, particularly the project-wide effort to gather requirements for replacing Red Hat Bugzilla and the successful migration of source control requests from Pagure to Fedora Forge, which requires maintainers to update their fedpkg toolchains. Hardware architecture improvements were also prominent, with multiple groups dedicating resources to testing and expanding build capacities for ARM and RISC-V devices. On the community front, organizing teams focused heavily on preparations for the FrOSCon 2026 event, while several other groups—including Packaging and Diversity & Inclusion—chose to pause regular meetings or shift to ad-hoc structures to prevent organizer burnout. Finally, navigating the rise of Artificial Intelligence emerged as a cross-cutting theme, prompting discussions around user privacy, default opt-in policies for third-party packages, and strategies for local AI development.

Announcements

Major workflow transitions are underway for Fedora contributors, starting with the planned decommissioning of Red Hat Bugzilla within the next six months. FESCo has opened a ticket tracker for planning and gathering requirements for a future Red Hat BugZilla replacement to document workflows impacted by this shift. Additionally, the fedora-scm-requests queue has officially migrated from Pagure to Fedora Forge following its scheduled start on August 5th. Maintainers must update to the new fedpkg version 1.48 to continue submitting new package and branch requests, as the old Pagure system is now obsolete. In other maintenance news, a final reminder was issued listing long-term FTBFS (Fails to Build From Source) packages slated for retirement from Fedora 45, urging maintainers to fix or seek exemptions for affected software. Finally, the Fedora RISC-V community is seeking testers for an updated Fedora 44 server image that features out-of-the-box support for SpacemiT K3 boards and improvements for K1 hardware.

For the broader Linux community, new guides are available detailing how to run Ollama locally with Podman on Fedora Linux for containerized, private AI development, and how to monitor your drive health with Performance Co-Pilot to prevent sudden data loss from failing NVMe or SSD drives. Lastly, a recent attendee shared a positive retrospective on developing with Fedora and their first Flock conference, highlighting the community's welcoming culture and the behind-the-scenes efforts of volunteers and sponsors.

Council

Between August 3 and 9, 2026, the Council discussed a new user concern regarding the introduction of AI-powered features in third-party packages, highlighting the need for packaging guidelines around user privacy and opt-in defaults. The Council also continued reviewing the proposed Fedora Forge Usage Policy, incorporating community feedback into a new draft. Additionally, a temporary "private issues" workaround was proposed for Fedora Forge while native support is being developed upstream, sparking discussions on how the Council and other sensitive groups will handle private tracking.

Decisions

• No formal Council decisions were finalized during this period.
• The Fedora package maintainer for Atuin decided to disable its new AI and hex features by default due to dependency creep and privacy concerns, pending a more robust opt-in or sub-packaging strategy.

See the detailed report for the Council team.

Learn more about the Council team.

FESCo

This week, FESCo focused heavily on reviewing and voting on F45 and F46 Change Proposals, handling administrative tickets, and addressing updates policy exceptions. Several major Change Proposals were formally approved for Fedora 45, including the modernization of the ODBC Stack, enabling systemd-oomd and zram swap for CoreOS, and transitioning to Sequoia for openpgpverify. Conversely, the committee rejected the proposal to hardcode nss-altfiles in authselect profiles, encouraging further collaboration among affected initiatives like CoreOS and atomic bootc.

In addition to changes, FESCo initiated a project-wide requirements gathering phase for Fedora's eventual Bugzilla replacement. They also approved an urgent updates policy exception for thermald to resolve power management issues on newer Intel laptops, and handled several non-responsive maintainer tickets to ensure long-term package health.

Decisions

• Accepted multiple F45 Changes: ODBC Stack Modernization, LibreOffice Dictionaries, Native Butane Config Support in Ignition, LibreOffice html help, Authselect Remove NIS Profile, Enable systemd-oomd and zram swap for CoreOS, and Sequoia openpgpverify.
• Rejected the F45 Change: Authselect: Hardcode nss-altfiles in profiles, requesting further collaboration among atomic, bootc, and coreos teams to find a viable solution.
• Approved an urgent updates policy exception for thermald across all Fedora branches to fix Intel power management issues.
• Approved a Soname Change Policy Exception Request for Qt-Advanced-Docking-System.
• Approved non-responsive maintainer actions for benzea, granting ngompa co-maintainer admin rights for thermald, libfprint, fprintd, and fwts.
• Agreed to launch a project-wide requirements gathering tracker to collect user stories and identify a suitable Bugzilla replacement.
• Updated the release schedule for F46 onwards to move the Major Toolchain Updates/Changes deadline to a week before the mass rebuild.

See the detailed report for the FESCo team.

Learn more about the FESCo team.

Packaging Committee

The Packaging Committee held a brief meeting this week. The agenda was notably light, with no new tickets submitted for review. The only active item mentioned was a work-in-progress pull request for Node.js. Due to upcoming vacations for key members, the committee agreed to suspend meetings for the rest of August.

Decisions

• The committee will skip its next scheduled meeting in two weeks due to member vacations, postponing the next gathering until the first week of September.

See the detailed report for the Packaging Committee team.

Learn more about the Packaging Committee team.

Mindshare

Mindshare held a brief meeting this week but concluded early due to a lack of quorum. Despite the early adjournment, organizers noted ongoing progress on various tickets and highlighted upcoming events, specifically FrOSCon and Data Con LA.

Additionally, community members are actively organizing the Fedora presence for FrOSCon 2026. The project booth is confirmed and swag items are being gathered, alongside an open call for volunteers to assist at the booth and share their work with attendees.

See the detailed report for the Mindshare team.

Learn more about the Mindshare team.

Ambassadors

The Ambassadors group focused entirely on final preparations for the Fedora booth at FrOSCon 2026, which takes place August 15-16 near Bonn, Germany. The team has successfully secured a booth space, promotional materials, and a new tablecloth, and they are actively seeking volunteers and project showcases from the community to help run the event.

See the detailed report for the Ambassadors team.

Learn more about the Ambassadors team.

Diversity & Inclusion

The Diversity & Inclusion group is putting its regular team meetings on hiatus to prevent organizer burnout and shift focus toward concrete, event-driven goals. Discussion in the "Time to take a break?" thread confirmed that regular meetings have become stagnant without specific deliverables, and organizers will now lean into forming ad-hoc teams for events like the Fedora Mentor Summit, Fedora Week of Diversity, and Fedora Appreciation Week.

Calendar entries for the regular DEI meetings are being removed, but this will not halt ongoing initiatives. Future activities will be organized through dedicated calls for volunteers and planned in their respective event repositories.

Decisions

• Regular DEI Team meetings are officially placed on hiatus, and corresponding Fedora and Google Calendar entries are being deleted.
• Future DEI efforts will shift to an ad-hoc, event-specific model focusing on time-boxed initiatives rather than standing meetings.

See the detailed report for the Diversity & Inclusion team.

Learn more about the Diversity & Inclusion team.

Workstation / GNOME

The Workstation Working Group discussed upcoming upstream GNOME changes, including plans for GNOME 52+ to replace GNOME Software with a Flatpak-focused installer called "Bazaar" and a new system updater, though Fedora will stick with GNOME Software for the time being. The group also evaluated newly integrated features like the IBus speech-to-text functionality, noting performance delays and missing default models, and reviewed the transition of GNOME Boxes to a Flatpak-only application which currently requires further polish on fractionally scaled screens.

On the forum side, community members engaged in a technical discussion regarding Btrfs RAID1 and nodatacow files (such as Libvirt virtual machine images), proposing theoretical file system mechanisms to ensure data recoverability during bit rot without full metadata checksumming.

Decisions

• Fedora will continue using GNOME Software for the time being, despite upstream GNOME's long-term plans (GNOME 52+) to replace it with a new installer called Bazaar.
• The memory retention issue in IBus speech-to-text, where the model remains loaded after the input method is removed, will be officially treated and tracked as a bug.

See the detailed report for the Workstation / GNOME team.

Learn more about the Workstation / GNOME team.

KDE

The KDE group discussions this week focused on a user-reported issue regarding computer freezes under Plasma (Wayland) after upgrading to Fedora 44. The system becomes unresponsive during screen lock, with the nvidia-modeset/kthread_q process consuming 100% of the CPU, requiring a sysreq reboot to resolve.

See the detailed report for the KDE team.

Learn more about the KDE team.

Server

This week, the Server Working Group officially reached quorum with the addition of new members and made progress on release testing and automation infrastructure. Discussions centered heavily on upcoming Fedora 45 changes, identifying bugs in VM and ARM partition types, and reviewing default packages to prevent unnecessary bloat in server environments.

The group also advanced its Ansible support project by merging initial post-installation modules and beginning work on a CI pipeline using self-hosted Forge runners. Furthermore, the WG continued refining its documentation structure, debating the best ways to present post-installation configuration tasks to users.

Decisions

• The Working Group decided to contact the upstream Cockpit team to request the removal of unnecessary dependencies, such as SPICE, from the Cockpit VM module to prevent unwanted package bloat on standard server installations.
• The Server Working Group's Ansible repository will be formally structured around small, tightly focused roles that are assembled into larger playbooks, avoiding monolithic scripts.

See the detailed report for the Server team.

Learn more about the Server team.

Infrastructure

The Infrastructure team was highly active this week, handling multiple system migrations, upgrades, and investigating service anomalies. Key efforts included advancing the RHEL 10 migrations for miscellaneous hosts, rolling out OpenID Connect enrollment for the Release Schedule Planner, and addressing intermittent authentication issues following the recent IPA cluster reinstall. The team also announced an upcoming scheduled outage for the Copr servers and discussed transitioning Matrix moderation duties to official Fedora infrastructure, including a formalized policy for official Matrix rooms.

Additionally, developers introduced substantial updates to Tahrir, the Tahrir API, and Forgejo, improving performance and enabling new features like private issue tracking in the forge environment. Investigations were also launched into src.fedoraproject.org 503 errors caused by heavy scraper activity and Fedora mailing list emails being falsely flagged as spam by the SpamHaus blocklist.

Decisions

• Migrate the Matrix moderation bot hosting to official Fedora infrastructure (@moderation:fedoraproject.org).
• Implement a new policy for official Fedora Matrix rooms, requiring the moderation bot to be present, a :fedoraproject.org room alias, and appropriate sub-space assignment.
• Block the creation of a Bugzilla component and FAS group for Security Bugs until FESCo formally approves the proposed security policy changes.
• Create new Fedora Account System (FAS) tracking groups for Copr projects: netfyr and sosreport.

See the detailed report for the Infrastructure team.

Learn more about the Infrastructure team.

Release Engineering

This week, the Release Engineering team focused heavily on infrastructure migrations and preparations for the Fedora 45 release cycle. A major milestone was the successful migration of the scm-requests repository from Pagure to Forgejo on August 5th, which necessitates that community members update their fedpkg utilities to version 1.48 or greater. The team also began extensive preparations for the F45 mass branching scheduled for August 11th, which included executing the mass re-signing of F45 content with the new F46 key.

In addition to release cycle preparations, the group handled various system and package fixes. They deployed a fix to prevent releng-bot from pinging unrelated users during SCM requests, resolved an issue where ELN packages were signed with the wrong key, and bypassed a Bodhi sidetag limitation affecting shadow-utils. Multiple package unretirement and stalled maintenance requests were processed, and the team highlighted that unretirements can now be executed directly via the updated fedpkg CLI without requiring a ticket.

Decisions

• The fedora-scm-requests repository was officially migrated from Pagure to Forgejo; maintainers must update to fedpkg v1.48 or greater to submit new package and branch requests.
• Package unretirements no longer require a Release Engineering ticket; maintainers should now use the newly introduced fedpkg request-unretirement command.
• Created a dedicated forge-releng-scm-validators group to handle SCM request approvals, preventing releng-bot from unnecessarily pinging unrelated community members.
• Created the quay.io/fedora/eln-bootc repository to enable the uploading of ELN bootc images from composes.

See the detailed report for the Release Engineering team.

Learn more about the Release Engineering team.

Quality

The Quality team focused heavily on early manual validation for Fedora 45 this week, placing a special emphasis on ARM devices to catch significant bugs before the branch and freeze periods. The team is also actively organizing the next round of Fedora Test Days and collaborating with the Data team to identify interesting QA and build metrics—such as Bodhi karma and Koji completion rates—for future data visualizations.

In addition to testing, the group discussed hardware monitoring defaults, noting that the mcelog daemon consistently fails on modern AMD CPUs. They are currently gathering community feedback on potentially replacing it with rasdaemon. Tooling improvements were also a major theme, with updates to fedora-easy-karma, a revived issuebot in staging, and discussions around deploying a shared test asset server for openQA and Fedora CI.

Decisions

• Begin early manual validation testing for Fedora 45 prior to branching and freezes, with a particular focus on ARM hardware.
• Initiate a broader community discussion regarding replacing the mcelog daemon with rasdaemon by default due to hardware incompatibility on modern CPUs.
• Add the currently proposed Test Day events to the Fedora Test Days calendar to prevent concurrent scheduling overlaps.
• Explore the integration of actual user-runnable regression test suites (e.g., Vulkan/GL conformance, kernel test suites) into upcoming Test Days.

See the detailed report for the Quality team.

Learn more about the Quality team.

Design

The Design team concluded the community poll for the Fedora 46 wallpaper inspiration, selecting American mathematician Karen Uhlenbeck as the winner. Following the poll, the team is organizing a mind map meeting to brainstorm the wallpaper's conceptual design. In other activities, community members shared a proposed wallpaper on the mailing list, and drafts for revamped Design Documentation pages were posted for review.

Decisions

• The Fedora 46 wallpaper design will be inspired by American mathematician Karen Uhlenbeck.

See the detailed report for the Design team.

Learn more about the Design team.

Internationalization

The Internationalization (i18n) group held a meeting this week to review the progress of Fedora 45 changes and coordinate upcoming release deadlines. Key discussions involved tracking the completion of F45 changes, ongoing bug triaging efforts for Fedora 43, and scheduling the upcoming internationalization test week.

Decisions

• The Fedora 45 i18n test week is scheduled to take place from September 7th to September 13th, 2026.

See the detailed report for the Internationalization team.

Learn more about the Internationalization team.

EPEL

This week, the EPEL group focused significantly on improving the repository structure and mirror paths for EPEL 11 to avoid user errors during mirroring and upgrades. The steering committee successfully voted to adopt a new "de-z-ification" policy for EPEL 11, which will rely on the $stream variable for CentOS Stream users rather than adding a 'z' suffix for RHEL minor versions. Additionally, the community discussed potential breaking updates to packages like certbot, uv, and ruff in EPEL 10, and highlighted a new way to track RHEL lifecycle milestones via the Red Hat Insights roadmap.

Decisions

• Approved the EPEL 11 portion of the "de-z-ification" policy, which will restructure repository names, redirects, and symlinks to utilize the $stream variable for CentOS Stream rather than the $releasever_minor 'z' suffix for RHEL systems.
• Agreed that the official branch naming for the CentOS Stream variant in EPEL 11 will be 11s.

See the detailed report for the EPEL team.

Learn more about the EPEL team.

ELN

The ELN SIG met this week to discuss significant updates to their build pipeline and image generation processes. Key highlights include the production deployment of ELNBuildSync 2.0.1, the inclusion of bootc images in standard composes, and the successful migration of all major cloud images (EC2, Azure, GCE, qcow2) to image-builder.

Additionally, the group discussed restructuring ELN variants, introducing a new AltImages variant for live images and a new Extensions variant to decouple RHEL Extensions from EPEL. Plans were also outlined to completely split ELN Extras into its own target to cleanly bootstrap EPEL N+1 and preview CentOS SIGs, with a call for community feedback on the design.

Decisions

• Re-tool ELN Extras to build in a completely separate target and compose to properly isolate EPEL macros and facilitate CentOS SIG previews.
• Separate RHEL Extensions content into a distinct Extensions variant rather than an EPEL allowlist due to a lack of overlap.
• Migrate WSL image builds to image-builder following the successful migration of hyperscaler cloud images.
• Merge GitLab MR 86 to minimize dependencies in go-vendor-tools and cut a new release.

See the detailed report for the ELN team.

Learn more about the ELN team.

Atomic

The Fedora Atomic Initiative met this week to discuss infrastructure updates and package releases. Progress was made on configuring Konflux service accounts for the Fedora Forge, with a new merge request proposed to unblock testing. Additionally, a recent policy change for the bootc package means that Bodhi updates now only require a +1 score to proceed, which should clear up the backlog of aging updates. In release news, bootc 1.16.6 has reached the stable repository, and work is underway for the 1.16.7 release.

Decisions

• Bodhi updates for the bootc package now only require a +1 score to proceed, which will prevent updates from sitting in the backlog until they become obsolete.

See the detailed report for the Atomic team.

Learn more about the Atomic team.

CoreOS

CoreOS held a meeting on August 5 to review ongoing action items and prepare for the upcoming Fedora 45 branching. Key discussions included ongoing tests for the /boot partition size to prevent data corruption during re-provisioning, preparations for the Fedora 45 Test Day, and the integration of approved FESCo changes into Rawhide. Additionally, the team discussed the pending archival of the Butane repository into Ignition.

Decisions

• Contributors with pending pull requests to the Butane repository should hold off or expect delays, as the repository is being archived and its codebase is being merged into the Ignition repository following the approval of FESCo ticket #3650.

See the detailed report for the CoreOS team.

Learn more about the CoreOS team.

AI & ML

This week, the AI & ML group focused on administrative tasks, specifically processing a membership update. A contributor requested to be removed from the group and related access lists due to time constraints and the challenges associated with packaging complex upstream AI projects. The request was completed, and the contributor was successfully removed from the relevant groups.

Decisions

• Approved and processed the removal of contributor salimma from the AI/ML and PyTorch Special Interest Groups (SIGs).

See the detailed report for the AI & ML team.

Learn more about the AI & ML team.

RISC-V

The RISC-V group focused primarily on the ongoing Fedora 45 mass rebuilds, successfully resolving a major Python 3.15 Beta 4 ABI breakage and completing the bootstraps for Perl 5.44 and Rust. Rebuilds for OCaml have started, with Golang and R queued up next.

Significant hardware additions were made to the build pool, including five Milk-V Titan (DP1000) machines and four SpacemiT K3 systems, to improve build capacity. The team also addressed hardware instability challenges with SpacemiT K1/K3 SoCs linked to vector instructions and OpenSBI issues, and discussed a gnulib/glibc conflict that required a workaround.

Decisions

• Implemented a workaround in Fedora to address a gnulib/glibc compatibility bug (Sourceware BZ 34437 / Fedora BZ 2502638) that was causing build failures.
• Expanded the RISC-V build pool by officially integrating five Milk-V Titan machines and four SpacemiT K3 systems.

See the detailed report for the RISC-V team.

Learn more about the RISC-V team.

Security

This week, the Security group discussed recognizing vulnerability reporters with a dedicated Fedora badge and evaluating compliance with the linux-distros mailing list rules. In the forums, a community review of the new Fedora-maintained hardening documentation led to minor improvements, while the OpenScanHub team published their latest static analyzer findings for Fedora 45 critical path packages.

Decisions

• Approved moving forward with a Vulnerability Reporting Badge to reward individuals who report security flaws.
• Decided to consult Fedora Legal to determine if the existing Fedora Project Contributor Agreement (FPCA) satisfies linux-distros rules, or if a separate Fedora Pre-Disclosure-Agreement (FPDA) is needed.

See the detailed report for the Security team.

Learn more about the Security team.

DotNET

The DotNET group confirmed the final steps for the end-of-life (EOL) transition for .NET 8 and .NET 9. Omair Majid announced that the dotnet8.0 and dotnet9.0 packages will be dropped from Rawhide shortly, timed to occur just before the Fedora 45 branch day on August 11, 2026.

While they are being removed from Rawhide, both versions will remain available and continue to receive updates in existing Fedora versions (up to Fedora 44) until their official EOL in November 2026. Michael Cronenworth acknowledged the change, noting that Jellyfin 12 is currently on the horizon with release candidates available.

Decisions

• The dotnet8.0 and dotnet9.0 packages will be dropped from Rawhide ahead of the Fedora 45 branch day.

See the detailed report for the DotNET team.

Learn more about the DotNET team.

Perl

This week, the Perl group focused heavily on routine package maintenance, consisting of upstream version bumps and importing packages into EPEL branches. Key updates included merging newer releases for packages like perl-ExtUtils-CppGuess, perl-PDF-Reuse, perl-HTTP-Cookies, perl-Crypt-SMIME, and perlbrew. Additionally, successful efforts were made to integrate perl-Protocol-WebSocket into EPEL8 and EPEL9, alongside establishing the first EPEL10 build for perl-SQL-Abstract.

Decisions

• Merged version bumps for perl-ExtUtils-CppGuess (0.271), perl-PDF-Reuse (0.44), perl-HTTP-Cookies (0.12), perl-Crypt-SMIME (0.34), and perlbrew (1.02) to keep packages aligned with upstream releases.
• Approved and merged EPEL package imports for perl-Protocol-WebSocket (EPEL8 and EPEL9) and perl-SQL-Abstract (EPEL10) to expand package availability for Enterprise Linux distributions.

See the detailed report for the Perl team.

Learn more about the Perl team.

Ruby

Vít Ondruch announced that following the recent landing of Ruby on Rails 8.1 in Fedora, an update for version 8.1.3.1 was also released this week. The community is encouraged to test these new releases and report any issues they might encounter.

Decisions

• Pushed the Ruby on Rails 8.1.3.1 update to Fedora.

See the detailed report for the Ruby team.

Learn more about the Ruby team.

Other Discussions

This week in the Fedora community, discussions focused on transitioning away from Red Hat BugZilla, establishing style guides for mailing lists, and managing the email volume on the devel list. Additionally, there were multiple package soname bumps, discussions about orphaning outdated packages, and warm welcomes to several new package maintainers.

Contribution opportunities

Contributors with testing and quality assurance skills can easily jump into numerous highly accessible opportunities. The community is invited to test the Packager Dashboard staging environment and report bugs on its issue tracker. Testers are also needed for Fedora 45 manual validation (especially on ARM), F45 Server bare-metal/VM images, fedpkg v1.48+ features, Flatpak-only GNOME Boxes on fractionally scaled displays, newly landed Ruby on Rails 8.1, dotnet10.0, and Atomic's bootc 1.16.6. Hardware owners can evaluate /boot partition scenarios (notes), test Omni F44 images on SpacemiT K1/K3 or Milk-V Titan, and assist with testing LLVM pull request 629. Additional opportunities include Fedora 43 i18n bug triaging and contributing to Test Day planning.

For those with strong communication, writing, or organizational skills, community feedback is actively sought on the Fedora Forge Usage Policy, the AI-powered features policy, and hardware monitoring defaults (mcelog vs. rasdaemon). Contributors can submit user stories to the FESCo Bugzilla replacement tracker, restructure Server post-installation guides, or review Design Processes documentation. Event enthusiasts can volunteer for the FrOSCon 2026 booth, give talks, create A4 teaser pages for project showcases, or join organizing efforts for Fedora Week of Diversity, Appreciation Week, and the Mentor Summit.

Developers, designers, and system architects can tackle highly specific technical challenges across the project. Programmers can debug memory leaks in GNOME's new IBus speech-to-text, troubleshoot KDE Plasma Wayland screen lock freezes with NVIDIA drivers, and investigate OpenSBI bugs on RISC-V K1/K3 SoCs. System architects are invited to help design the ELN and ELN Extras separation (Issue #61 and Issue #62). Designers can streamline GNOME's action dialog buttons, design the Vulnerability Reporting Badge, or join #design:fedoraproject.org for the Fedora 46 wallpaper brainstorm. Data enthusiasts can also suggest QA-related data visualizations.

Contributors experienced in package maintenance and systems administration can make an immediate impact by adopting orphaned or non-responsive packages such as nextcloud-client, rust-zoxide, cinnamon-screensaver, and python-pivy, or by helping the AI & ML group package PyTorch. Packagers are also needed to resolve Failing to Install (FTI) EPEL packages, test EPEL 10 uv and ruff updates, minimize go-vendor-tools dependencies, and apply OpenScanHub security patches. Systems administrators can write Server Ansible roles, configure self-hosted Forge runners, and help implement RPM macro and Lua support for the Fedora 45 PURL proposal.