Across the Fedora ecosystem, the primary immediate focus is managing the final stages of the Fedora 45 release, which is currently in a "NO-GO" status targeting October 27, prompting groups like Release Engineering, Quality, Workstation, and Server to rapidly evaluate late-stage blocker bugs and freeze exceptions. Simultaneously, a massive structural shift is underway as the Bootable Image Unification effort concludes the Atomic Initiative, transferring ownership to the CoreOS Working Group and establishing a highly minimal atomic-seed image as the foundation for future immutable builds. In tandem with these initiatives, infrastructure modernization is a shared priority, with multiple teams actively migrating workloads from GitLab to the new Fedora Forgejo instance, adopting Konflux for continuous integration, and restructuring documentation under a unified root component. Finally, looking beyond the current final freeze, steering committees and Special Interest Groups are actively laying the groundwork for Fedora 46—including major system-wide proposals like the transition to RPM v6 and the removal of the legacy DNF4 stack—while advancing cross-architecture support for RISC-V and deploying vital language stack updates.

Announcements

Fedora 45's final release is currently a NO-GO with the next target date set for October 27, though the community is still invited to celebrate at the virtual release party scheduled for October 30. In community news, the latest Fedora Podcast breaks down the differences between Fedora Hummingbird Linux and standard container images, asking users to share their specific real-world use cases.

To avoid disruptive surprises, contributors are explicitly reminded of the scope of provenpackager privileges, with warnings against modifying packages (such as converting to %autorelease) without maintainer consent. On the technical front, Fedora 45 will modernize the virtual console by replacing fbcon with kmscon. Looking ahead, a massive wave of Fedora 46 Change Proposals has been announced: major system-wide updates include transitioning to the RPM v6 package format, the complete removal of the legacy DNF4 stack and modularity, and introducing a daemon for unprivileged eBPF access. Additional F46 proposals cover an LMDB 1.0 transition, migrating the libvirt network filter to NFTables, updating to libchewing 0.14, and standardizing Emacs package packaging with new RPM macros and dependency generators.

Council

The Council held a meeting regarding the Bootable Image Unification (Atomic Fusion) effort. Key discussions focused on Architectural Decision Records (ADRs) involving monorepos, debates over migrating legacy builds from GitLab to Forgejo, and organizing the atomic tracker backlog into structural tiers.

A major outcome of the meeting was defining the architecture for new bootable images, which will begin with an extremely minimal "seed" image meant for internal team use and as a foundation for layered products. Additionally, it was announced that the Atomic Initiative will officially shut down on October 31st, 2026, marking the successful transfer of ownership to the broader group.

Decisions

• The Atomic Initiative will officially end after Fedora 45 and will shut down on October 31st, 2026, at which point @nimbinatus will step down from the Council since ownership has been successfully transferred. (Source)
• A new atomic-seed repository was created on Forgejo (under the MIT license) to build a foundational seed image containing only a strict minimal package set: the kernel, systemd, SELinux policy, Podman, and bootc. (Source)
• The seed image will initially omit a bootloader to reduce complexity for specific automotive variants and will be tested using QEMU for direct kernel booting. Because it lacks a bootloader, it will not be exposed to general users on Fedora download pages. (Source)
• The team categorized the Atomic tracker backlog items into three new structural tiers (level one, level two, and level three). (Source)

Contribution opportunities

• Contributors are invited to review and comment on ADR-0003, which proposes using a monorepo for all configurations, continuous integration, and testing code to streamline atomic image building. (Source)

Learn more about the Council team.

FESCo

This week, FESCo held one meeting and handled an exceptionally high volume of system-wide and self-contained Change Proposals on the forums for Fedora 45, 46, and 47. Major topics of discussion included the retirement of DNF4 and Modularity, transitioning to the RPM v6 package format, moving the SELinux policy store to /etc/selinux, and updating various language stacks and tools.

In their meeting and ticket discussions, the committee addressed several administrative and policy items. They finalized a membership change, approved and published a policy reminder regarding the boundaries of provenpackager access, and processed the final status of incomplete changes for the upcoming Fedora 45 release. Additionally, they began determining how to safely phase out highly vulnerable NetworkManager VPN plugins without severely disrupting existing users.

Decisions

• Approved and sent a policy reminder to the community reaffirming that provenpackagers must not apply mass changes (such as converting to %autorelease or %autochangelog) without prior maintainer consent (Ticket #3687, Meeting).
• Agreed to address the removal of vulnerable NetworkManager-{vpnc,fortisslvpn} plugins by first publishing a Fedora Magazine article to warn users on how to migrate, before eventually pulling the packages from the base layer of atomic installs (Ticket #3693, Meeting).
• Processed the F45 Incomplete Changes report, officially retargeting several incomplete changes—such as "Disable Vendor Change by Default" and "Enable Shadow Stack by Default on x86_64"—to Fedora 46 (Ticket #3682).
• Completed the non-responsive maintainer process for lkundrak, transferring heavily utilized packages (like NetworkManager and wpa_supplicant) to new volunteers and orphaning the remainder (Ticket #3681).
• Approved offboarding duffy from FESCo and onboarding maxamillion to serve the remainder of the vacant seat's term (Ticket #3689, Ticket #3695).

Contribution opportunities

• FESCo is looking for a volunteer to help write a Fedora Magazine article explaining the removal of the vulnerable NetworkManager-{vpnc,fortisslvpn} plugins and guiding users on how to migrate. (Meeting)
• Help is needed to clear out the remaining F45 Final Blocker bugs as the release approaches: F45 blocker bug list. (Meeting)
• The Fedora Council is currently brainstorming themes for Flock 2027 and is looking for community ideas and feedback: Flock to Fedora 2027 CfP Themes Brainstorming. (Meeting)

Learn more about the FESCo team.

Packaging Committee

The Packaging Committee held a meeting this week but didn't reach a quorum, meaning no official decisions could be finalized. The primary topic of discussion centered around procedural rules for ticket votes and quorum requirements, particularly in relation to the pending "snapshot ticket."

Members debated whether ticket votes should eventually pass by majority after a certain timeframe or if they must always be resolved during a live meeting when blocking negative votes exist. The snapshot ticket remains deferred due to the lack of quorum and an ongoing disagreement over the best way to indicate a snapshot within a string. The committee will attempt to resolve the issue at their next meeting in two weeks.

Learn more about the Packaging Committee team.

Mindshare

This week, the Mindshare group focused heavily on event planning, governance, and infrastructure adjustments. A major priority was organizing the upcoming Fedora Linux 45 Release Party, scheduled for October 30, 2026. The committee also reviewed several event sponsorship requests, including IndiaFOSS, LinuxDays Prague, and a high school game jam in Spokane, alongside discussions about revamping the large event funding process and acquiring new physical event boxes.

Additionally, the group tackled operational bottlenecks and community representation. With the Fedora Design team at capacity, Mindshare established new policies for event badges, requiring proposers to supply their own designs with a 30-day lead time. Governance discussions centered on reallocating the vacant CommOps representative seat on the Mindshare Committee to other active SIGs, and the team initiated tests using Buffer to decentralize and expand community access to Fedora's social media channels. High-level philosophical discussions also took place regarding the alignment of LLM-gen-AI models with Fedora's open-source foundations.

Decisions

• The Fedora Linux 45 Release Party is scheduled for October 30, 2026, from 13:00 to 16:00 UTC.
• Due to capacity limits within the Design team, event organizers requesting Fedora Badges must now provide a 30-day advance notice and supply their own badge artwork designs.
• The Community Ops team will revoke its representative seat on the Mindshare Committee, allowing the committee to reallocate the position to other active groups (such as Documentation or AI SIGs) as per Ticket #154.
• The proposal to establish an annual formal open call for CY2027 Large Event Funding Proposals was rejected in favor of maintaining a flexible, quarterly capacity planning approach based on previous years' events.
• Mindshare will test using Buffer for social media management with Mastodon and LinkedIn to lower the barrier for social media contributions and offer access to more people in the short term.

Contribution opportunities

• Volunteers are needed for drafting social media content for Mastodon, LinkedIn, Instagram, and YouTube using graphics provided by the Design Team for the F45 Release Party.
• Future volunteers are requested to assist with video editing and post-production for YouTube content related to the F45 Release Party.
• The Design Team is no longer able to accept Fedora Badges artwork requests; Mindshare is putting out a call to recruit a new team of volunteer designers to focus exclusively on creating badges.
• Contributors interested in representing the Fedora Project at FOSSASIA 2027 are encouraged to list their names on the event's Wiki document to apply for travel sponsorship.

Learn more about the Mindshare team.

Magazine

This week, the Fedora Magazine team welcomed a new prospective contributor who brings technical writing experience and an eagerness to explore and write about open-source software. In their welcome messages, existing community members shared onboarding documentation and emphasized that the Magazine is actively looking for more writers.

Learn more about the Magazine team.

Fedora Join

This week, the Fedora Join group focused on improving onboarding processes and updating community navigational resources. A community member made significant progress analyzing the outdated apps.fedoraproject.org portal, successfully running the environment locally on Fedora 43. Key issues were identified for resolution, including broken icons, 404 errors on legacy SOP links, and stale application references that require updates in the infrastructure's Ansible repository.

Additionally, the team discussed ways to improve ticket visibility by updating the "Welcome to Fedora" issue templates. The goal is to automatically tag team members and owners to ensure reliable notifications for new onboarding tickets, though further testing is needed to confirm if tagging functions correctly within the templates.

Decisions

• Decided to defer the update of the frontend libraries for apps.fedoraproject.org to a separate future task, as the current stack successfully runs on Fedora 43 without immediate modernization.

Contribution opportunities

• Representatives of various Fedora application and infrastructure teams (including Zabbix, Ask Fedora, Elections, FedoCal, and Ipsilon) can expect to be contacted on Matrix to verify active services and provide updated links for the apps.fedoraproject.org modernization effort.
• Contributors familiar with Forgejo are encouraged to test and confirm whether group tags (such as @join/Members) function correctly when embedded inside issue templates.

Learn more about the Fedora Join team.

Ambassadors

The Ambassadors group has initiated planning for the Fedora Project's in-person presence at the FOSSASIA 2027 Summit. FOSSASIA is a major open-source technology conference in the Asia Pacific region, and the group is actively calling on contributors to help organize and represent Fedora at the upcoming event.

Decisions

• Fedora Mindshare will prioritize FOSSASIA 2027 event sponsorships for individuals who actively contribute to organizing the Fedora Project's presence at the conference.

Learn more about the Ambassadors team.

Workstation / GNOME

The Workstation/GNOME group's activities this week centered around preparations for the upcoming Fedora 45 release, including identifying and addressing release blockers and freeze exceptions. Notable technical discussions focused on resolving a regression introduced in Fedora 44 where non-wheel users cannot install updates via GNOME Software due to a dnf5 limitation, as well as ongoing efforts to fully automate the generation of appstream-data metadata for software centers.

In community support, members clarified why certain KDE Frameworks (kf6-*) libraries are preinstalled on GNOME systems, tracing the requirement back to dependencies in background base packages. The Working Group also set their weekly agenda, touching on upcoming initiatives such as LLM-based summaries and Atomic Workstation discussions.

Decisions

• Established a product requirement that unprivileged local and LDAP users must be allowed to install updates by default, restoring functionality lost in Fedora 44. The issue is being pursued upstream in dnf5 (Ticket #531).
• Agreed that Fedora packages should transition away from using the deprecated appstream-util for AppStream metadata validation (Ticket #507).

Contribution opportunities

• Vote on proposed Fedora 45 blocker bugs and freeze exceptions via the blockerbugs app prior to the Blocker Review meetings to help streamline the QA review process.

Learn more about the Workstation / GNOME team.

KDE

The KDE SIG has made KDE Plasma 6.8.0 and KDE Apps 26.08.2 available via a combined COPR to accommodate the Fedora 45 final freeze. Users testing this prerelease are advised that a soname bump in libplasma requires the temporary removal of certain apps (such as Merkuro, KWeather, KClock, and KAlgebra), and developers are actively tracking upstream fixes for bugs expected to be resolved in Plasma 6.8.1 or 6.8.2.

In other discussions, community members clarified why KDE Frameworks (kf6-*) packages are preinstalled on GNOME-based Fedora 45 beta systems, tracing the requirement back to background packages rather than direct Qt application dependencies. There is also an ongoing discussion to reintroduce the bup package to Fedora to fully support the kup backup features newly integrated into Plasma 6.8.

Contribution opportunities

• Volunteer to package and maintain bup in the Fedora repositories to enable versioned backups for the new Plasma 6.8 kup utility (Ticket #732).
• Help test the KDE Plasma 6.8.0 and KDE Apps 26.08.2 combined COPR release to ensure a smooth transition once the Fedora 45 freeze is lifted.

Learn more about the KDE team.

Server

This week, the Server Working Group focused heavily on Fedora 45 (F45) release testing and advancing its Ansible support initiatives. During F45 testing, a known release-blocking issue resurfaced involving the KVM image and initial-setup due to a Kiwi configuration conflicting with partition type specifications. Additionally, the F45 aarch64 netinst image exceeded its 1.4G size limit, prompting a proposal to increase the limit to 1.5G.

On the development front, the group made progress on Ansible integration, successfully merging idempotency pull requests and claiming the fedoraserver namespace on Copr for future packaging. Members also expressed enthusiasm for the Cockpit team's upcoming GUI for Ansible, which aligns perfectly with the server automation goals. Finally, the group initiated early explorations into system resilience and snapshot-based backups utilizing LVM2, with plans to support BTRFS via snapper integration.

Decisions

• Proposed bumping the Server aarch64 netinst image size limit from 1.4G to 1.5G to accommodate the growing F45 image size. (Source)
• Claimed the fedoraserver group alias on Copr to centralize the group's Ansible collection and utility RPM packaging efforts. (Source)
• Agreed to set up a dedicated test and demo server to trial and refine Ansible support for Server Services. (Source)

Contribution opportunities

• Community members are encouraged to review and vote on F45 blocker and freeze exception bugs ahead of the upcoming F45 Blocker Review meeting.

Learn more about the Server team.

Infrastructure

This week, the Infrastructure team operated under the Fedora 45 final infrastructure freeze, which culminated in a "no-go" decision during the F45 Final Go/No-Go Meeting. Major operational tasks included troubleshooting network reachability timeouts between Red Hat-hosted Fedora infrastructure and packages.redhat.com (which temporarily broke Copr builders), and replacing a failing Power9 hypervisor due to hardware controller issues.

On the development side, the Forgejo migration effort saw significant progress. The team tested and merged several backend features for private issues, updated the API, and began packaging Forgejo 15.0.10. Meanwhile, several staging environment adjustments were completed, including restoring API access for bots on discussion.stg and successfully transitioning docs.stg builds to pull directly from the new staging Forge repository.

Decisions

• The F45 Final Go/No-Go Meeting resulted in a "no-go" decision for the Fedora 45 release candidate.
• The Fedora Design Suite documentation will migrate directly to Forge to simplify maintenance, eliminating the need to set up OpenID Connect for the Fedora MediaWiki API.
• Hardware for the vmhost-p09-copr03 Copr builder was permanently swapped with a spare machine rather than being reinstalled again, due to a degrading disk controller.

Contribution opportunities

• F45 Release Party Speakers: The team is seeking volunteers to present a 10-15 minute session (either live or pre-recorded) about Fedora Forge at the F45 release party on October 30. Reach out in the Fedora Forge Matrix channel if interested.
• Mote Scripting Enhancements: There is a great introductory scripting task available to add error checking and database cleanup capabilities to the mote script, which sorts meeting minutes into teams (Ticket #12873).
• AI Code Review Formatting: Contributors bothered by the verbosity of Forgejo's LLM code reviews are encouraged to submit a pull request to the upstream ai-code-review tool to change the default output format or add configuration options, as discussed on the forum.

Learn more about the Infrastructure team.

Release Engineering

The Release Engineering team is currently navigating the Fedora 45 Final Freeze. A significant portion of the week was dedicated to evaluating blocker bugs, managing stable pushes, and generating Final Release Candidate (RC) composes. The most recent Fedora 45 Go/No-Go meeting resulted in a "No-Go" decision, so further RC composes and fixes are being integrated before the final release.

In addition to release preparation, the team managed several infrastructure and package updates. This included processing package unretirement requests, generating detached signatures for the ignition 2.28.0 release, and resolving build issues by adjusting Koji tags for packages like python-nanobind and rawhide-gcc-snapshot-build. Discussions are also ongoing on the forum regarding a potential transition to a new Rust-based repository generation tool.

Decisions

• Evaluated and accepted multiple Fedora 45 blocker bugs and freeze exceptions during the Oct 12 Blocker Review Meeting.
• Approved package unretirement requests and main admin transfers for various packages, including urdfdom, python-sphobjinv, wannier90, and picard.
• Untagged python-nanobind-3.1.0-1.fc46 from Rawhide to prevent build failures for dependent packages, as detailed in issue 13556.
• Updated the rawhide-gcc-snapshot-build Koji tag to inherit from f46-build/rawhide-build to ensure packages correctly target Rawhide, as detailed in issue 13554.
• Disabled updates-testing for Fedora 45 and prepared the final fedora-release and fedora-repos updates, documented in issue 13550 and Bugzilla 2547462.

Contribution opportunities

• A community contributor has invited collaboration to test and potentially adopt kiritan & subatomic, a highly performant, Rust-based alternative to createrepo_c that significantly reduces memory usage and execution time.

Learn more about the Release Engineering team.

Quality

The Quality team focused on the impending Fedora 45 release, evaluating late-stage blockers and freeze exceptions. Due to the absence of a suitable Release Candidate, the team declared an automatic NO-GO for F45 Final, shifting the targeted release to October 27. Consequently, discussions opened regarding a proposal to bump the Server aarch64 netinst image size limit to 1.5G to handle the F45 image growth.

The team also conducted the Podman Conmon-v3 Test Day and finalized preparations for the upcoming GRUB EFI for Confidential Computing Test Day. A Cockpit Test Day planned for this cycle was pushed back to the next release. Additionally, after debates in the blocker review meeting, a new initiative was launched to formulate a clear strategy for handling CVE-related freeze exception requests on packages absent from release media.

Decisions

• The Fedora 45 Final release was declared an automatic NO-GO due to the lack of a suitable Release Candidate, delaying the target date to October 27.
• During the F45 blocker review meeting, it was decided to temporarily accept non-media CVEs as Freeze Exceptions to prevent users from obtaining vulnerable packages while updates-testing is disabled. A new ticket was created to establish a long-term strategy for these scenarios.
• The regular QA meeting scheduled for October 12 was cancelled in observance of a Canadian public holiday.
• A proposal was submitted to bump the aarch64 Server netinst image size limit from 1.4G to 1.5G.

Contribution opportunities

• Help is requested to test and investigate the oo7 keyring invalid content type bug to see if it breaks any pre-installed applications. The team needs this data to decide if it should block the F45 release.
• Community members are invited to participate in the GRUB EFI for Confidential Computing Test Day, which will run from October 19 to 25.
• Users running Podman are encouraged to test and leave feedback based on the Podman Conmon-v3 Test Day cases.

Learn more about the Quality team.

Websites and Apps

The Websites and Apps team focused heavily on website maintenance and user experience improvements this week. A significant effort went into refining download pages: the team added macOS direct download links for the Fedora Media Writer to the workstation download page to bypass confusing GitHub repository links, successfully implementing API caching to avoid build rate limits. Additionally, they fixed a caching bug on the CoreOS download page that was displaying stale release data to end users, ensuring it now fetches live updates dynamically.

Other discussions revolved around infrastructure and translation tooling. The team removed the broken PeerTube video feed from the Fedora start page after persistent errors. On the community side, members discussed refining translation configurations to prevent translating names and terms of service in Weblate, clarified the expected behavior of Fedora Badges permission checks, and noted user reports regarding a confusing login loop and UI bug when accessing the Fedora Wiki.

Decisions

• Removed the PeerTube latest video feed block from start.fedoraproject.org until a suitable replacement is found, due to persistent "502 Bad Gateway" errors (Ticket #436).
• Updated the CoreOS download page to bypass its previous Nuxt caching configuration and fetch live release data directly, preventing stale versions from being displayed to users.
• Decided to prefix non-translatable YAML keys (such as people's names and phone numbers) with an underscore (_) to automatically exclude them from Weblate localization.

Contribution opportunities

• Investigate and fix a UI bug on the Fedora Wiki login redirect page that displays a button incorrectly labeled "0", which causes a login loop for users.
• Contribute to the upstream ai-code-review tool by submitting a pull request to make the LLM review output format less verbose and more configurable.
• Submit pull requests to the Fedora Websites repository to prefix non-translatable YAML keys (e.g., names and contact info on the Flock event pages) with an underscore (_) to correctly remove them from Weblate.

Learn more about the Websites and Apps team.

Design

The Design team is finalizing visual assets and promotional graphics for the F45 Virtual Release Party (design#86), having successfully tested a new SVG generation workflow utilizing Claude, which will be detailed in an upcoming blog post. Additionally, developers from the Anaconda project have submitted a pull request to add CSS branding for the new WebUI installer and are seeking co-maintainer access to the design/packages repository to efficiently manage ongoing updates.

Internally, the team is actively restructuring their workflow by setting up automated ticket due dates in a sandbox environment and implementing a new labeling system to separate feature improvements from operational tasks. They are also clearing out stale backlog tickets and expanding documentation, including a newly submitted guideline for JPEG XL and an updated documentation repository for the Design Suite.

Decisions

• The team established a standard procedure for handling stale backlog tickets: they will tag the original reporter to check for activity, direct them to brand book resources, and close the ticket if no response is received. (Meeting Log)
• The team agreed to establish a separate queue or classification using a feature/improvements label to categorize strategic suggestions, preventing the standard ticket queue from becoming an unverified idea repository. (Meeting Log)
• The team decided to replace the fountain pen with a paintbrush in mockup 1C of the CDUX logo to offer better visual dynamics and incorporate a Fedora blue color. (Meeting Log)

Contribution opportunities

• Community members are encouraged to test the newly updated design-suite-docs repository using either local HTTP or Podman before its integration with Fedora Docs.
• A repository owner is needed to grant co-maintainer permissions to Anaconda developers on the design/packages repository so they can manage CSS branding for the new WebUI installer. (Matrix Chat)
• Reviews are requested for the pull request adding CSS for the new WebUI installer frontend.
• The new guideline for JPEG XL has addressed feedback and is ready for final review or merging.

Learn more about the Design team.

Docs

This week, the Docs team focused heavily on documentation infrastructure architecture and preparing release notes for Fedora Linux 45. A major structural shift is underway to consolidate various documentation repositories under a single root component. This long-term change will significantly improve content discoverability by allowing documentation modules from different Special Interest Groups (SIGs) to be displayed together seamlessly, while allowing each team to maintain their own source repositories.

Concurrently, the team finalized important user-facing release notes, prominently featuring the transition to native LibreOffice spell-check dictionaries. On the maintenance front, preparations are in motion to modernize branch naming conventions—specifically transitioning from prod to main—and to establish more robust continuous integration testing for staging environments.

Decisions

• Decided to unify all documentation repositories under a single ROOT component; this will allow the inclusion of modules across different repositories while automatically dropping the component name from the generated URLs to prevent link breakage. (Issue #66)
• Approved renaming the core site-building prod branch to main and moving the stg environment to a dedicated builder repository on the staging Forge to facilitate better pre-merge testing. (Issue #61)
• Merged an update to the site-building script to support configurable repository branch names via DOCS_REPO_BRANCH, ensuring OpenShift jobs do not break during the upcoming branch renaming transition. (Issue #64)
• Finalized the Fedora 45 release note for the LibreOffice Dictionaries change; users installing the new libreoffice-dict-<lang> packages will need to use --allowerasing, which will explicitly remove legacy hunspell-<lang> and libreoffice-langpack-<lang> packages. (Issue #434)

Contribution opportunities

• Feedback Requested: Documentation contributors are invited to review and suggest important commands for a newly drafted Git cheat sheet for writers, designed to simplify Git workflows for non-developers.
• Testing and Review: Reviewers are needed to help structure, approve, and test the integration of the Fedora Design Suite documentation as a new component on the Fedora Docs staging instance.
• Workflow Coordination: Contributors who maintain documentation repositories or custom automation should stay alert for the upcoming branch renaming from prod to main to ensure continuous compatibility with their workflows.

Learn more about the Docs team.

COPR

This week, the COPR community reported a couple of service-related issues on the mailing list. Jean-Marc LIGER observed that several builds have been stuck in a "pending" state for multiple days, noting a curious pattern where affected accounts start with the letter 'L' and pointing out a stalled Pulp migration. Additionally, Ian Pilcher reported that builds were failing due to curl timeout errors when attempting to reach packages.redhat.com.

Learn more about the COPR team.

EPEL

The EPEL team has been actively managing package updates and refining documentation this week. A major update to qt6 (from 6.6.2 to 6.10.3) in EPEL 9 is currently underway, which required rebuilds for several dependent packages like obs-studio, qcoro, and qt-creator. Additionally, version updates for uv (to 0.13.x) and ruff (to 0.17.x) are planned for the EPEL 10 leading branch and newer Fedora releases following the Fedora 45 Final Freeze.

On the procedural side, community members have proposed new documentation for build-tagging to clarify processes introduced with EPEL 10. Routine maintenance also saw updates to Noctalia, contributions to packaging guidelines, and investigations into the impact of retiring Bugzilla.

Decisions

• Following community feedback, the planned updates for uv (0.13.x) and ruff (0.17.x) will not be shipped to Fedora 43 because the release is nearing End-of-Life and the updates contain minor breaking changes. The updates will still proceed for F44, F45, and the EPEL 10 leading branch.

Contribution opportunities

• Community members are asked to test the qt6 update in EPEL 9 (which includes packages like obs-studio, obs-studio-plugin-vkcapture, qcoro, and qt-creator) to ensure no breakages or missing dependencies went unnoticed.
• Feedback is requested on a proposed documentation pull request regarding build-tagging to improve clarity for contributors.

Learn more about the EPEL team.

ELN

During their October 13 meeting, the ELN SIG discussed preparations for building boot.iso with image-builder (tracked in this pull request) and assigned ownership to investigate a bug where KDE Discover is failing in ELN (issue #633). The team also noted that recent ELN Extras pull requests have been merged, leaving the Extras repository in better shape.

In broader Linux news, the group is making significant progress on introducing ELN to the RISC-V architecture. The team is preparing to begin bootstrapping soon and plans to target RVA23 as a baseline. To prevent any disruptive surprises for existing contributors, the group clarified that these new RISC-V builds will take place on the Fedora RISC-V alternate Koji, keeping them separate from the main Fedora Koji.

Decisions

• ELN builds for the RISC-V architecture will be hosted on the Fedora RISC-V alternate Koji rather than the main Fedora Koji.
• The RISC-V effort for ELN is officially planning to target RVA23 as a baseline architecture.

Learn more about the ELN team.

Atomic

The Atomic group is undergoing a major transition as the Fedora bootc initiative officially concludes on October 31, 2026, at which point ownership will transfer to the CoreOS Working Group. During the October 15 unification meeting, the team laid the groundwork for merging Fedora CoreOS and Atomic efforts, including the proposal of a new foundational "seed image" architecture to serve as a baseline for user consumption and derivative products.

Significant infrastructure shifts are also underway as the group transitions away from GitLab. The team is actively migrating base image workloads to the new Fedora Forgejo and pushing to establish Konflux as the group's production-level CI/CD tool. Ongoing debates include whether to adopt a monorepo approach for atomic images to streamline future builds and how to best provide standardized "bootimages" for users exploring Image Mode.

Decisions

• The bootc initiative will officially shut down on October 31, 2026, with ownership of the base images and workflows transferring to the CoreOS Working Group (Meeting Notes, Issue #92, Issue #137).
• The team will migrate base image work and related repositories from GitLab to the new Fedora Forge (Forgejo) to ease maintenance and prevent monitoring neglect (Issue #75, Meeting Notes).
• A new atomic-seed repository was created on Forgejo under an MIT license to build the foundational seed image, starting with a minimal five-package set (kernel, systemd, Podman, selinux-policy, bootc) before deciding on further additions like bootloaders (Epic #144, Meeting Notes).
• Permissions in the Atomic organization on Forgejo were updated so that the Members team has "Write access to everything except Packages" (Issue #143).

Contribution opportunities

• Konflux Permissions Fixes: Help is needed to resolve a permissions issue to grant all Fedora contributors read-only access to Konflux tenants (Issue #91).
• Konflux Governance: Contributors are needed to help define the contribution ladder and governance structure to automatically grant developers access to Konflux tenants (Issue #91).
• ADR Review: The team is seeking reviews and comments on Architectural Decision Record (ADR) 3, which proposes a monorepo for all configurations, continuous integration, and testing code (Meeting Notes).
• Bootimage Feedback: Community input is requested regarding the creation of standard "bootimages" for bootc to lower the barrier of entry for new users exploring Image Mode without building their own containers first (Issue #77).

Learn more about the Atomic team.

CoreOS

This week, the CoreOS team officially announced that the Atomic Initiative will conclude on October 31st (following the Fedora 45 release), having successfully transferred ownership to the group. The community also approved migrating the automated engineering newsletter tool into the official CoreOS GitHub organization. A major deprecation was announced for the Linux community: the legacy quay.io/coreos/fcct container registry is now deprecated and will no longer receive updates; users must migrate to quay.io/coreos/butane.

Technically, the team is actively investigating a corrupt kernel file issue on ext4 /boot partitions linked to large-folio writeback bugs during upgrades. Other key initiatives include proposing poll-based Jenkins imports for Konflux-driven streams, syncing firmware updates to other ESPs in RAID setups, and adopting chunkah to split container images for enhanced layer reuse.

Decisions

• The legacy quay.io/coreos/fcct container registry is now officially deprecated. Existing users must switch to quay.io/coreos/butane to receive future updates.
• The community voted during the weekly meeting to migrate the Newsletter repository into the CoreOS organization to serve as the official tool for tracking and sharing updates.
• The Atomic Fusion team decided to start building the seed image with a strict minimal package set (kernel, systemd, SELinux policy, Podman, and bootc) without a bootloader, testing it via QEMU for internal foundational work.

Contribution opportunities

• A community member is preparing a pull request to add unit tests to Ignition's Azure logic to optimize and document its behavior.
• Following the migration of the Newsletter generator, there is an opportunity to rewrite the Python PoC tool into Golang to better match the CoreOS tech stack.
• Help is needed to configure Slack credentials and channel IDs to finalize the integration for publishing Konflux pipeline results to Slack and Matrix.

Learn more about the CoreOS team.

IoT

This week, the Fedora IoT Working Group reviewed the status of Fedora 44, 45, and Rawhide builds, noting a persistent greenboot issue across stable and freeze branches. A Go/No-Go meeting for Fedora 45 was anticipated to serve as a blocker review due to the lack of a release candidate. In parallel, the Bootable Image Unification ("Atomic Fusion") group discussed creating a monorepo for atomic images and shaping the architecture for a new baseline "seed" image to support layered products.

On the tracker, several older tickets were closed, notably confirming that the Fedora ROS2 testing repository is now available in the official ROS2 documentation, concluding collaborative work with the Robotics SIG. New spike tickets were also opened to evaluate device-specific ARM images and VM-based hardware testing, prompting active discussion about the necessity and implementation of these approaches compared to existing generic images and OpenQA tests.

Decisions

• The Bootable Image Unification initiative will officially conclude on October 31st, following the Fedora 45 release, with ownership transferring entirely to the working group (Bootable Image Unification Meeting Agenda).
• Base image work and continuous integration for Fedora 46 and onward will be migrated from GitLab to Forgejo to resolve long-standing workflow issues (Bootable Image Unification Meeting Agenda).
• A new atomic-seed repository was created on Forgejo to build a highly minimal image (containing only the kernel, systemd, SELinux policy, Podman, and bootc) without a bootloader, testing it directly via QEMU for internal foundational use (Bootable Image Unification Meeting Agenda).

Contribution opportunities

• The working group is requesting help to test the Fedora 45 nightlies and leave results on the wiki (Fedora IoT Working Group Meeting).
• Contributors are invited to share their feedback on the limitations of current generic ARM images to guide the evaluation of device-specific Fedora ARM images.
• Community members are asked to identify the value proposition and specific scenarios for VM-based hardware testing that are not already covered by central OpenQA VM testing.

Learn more about the IoT team.

ARM

The ARM group was notified of the Fedora 45 Blocker and Freeze Exception Review meeting, scheduled for October 12, 2026, at 16:00 UTC on Matrix. The agenda included reviewing 4 proposed blockers and 7 proposed freeze exceptions for the Final release to determine if they violate the Fedora Release Criteria.

Community members were encouraged to review the proposed blockers and cast their votes asynchronously before the meeting to help expedite the review process.

Contribution opportunities

• Evaluate and vote on proposed Fedora 45 Final blocker and freeze exception bugs ahead of review meetings. This can be done via the blockerbugs app or on Pagure tickets, as detailed in the meeting announcement.

Learn more about the ARM team.

Hummingbird

The Hummingbird group held two key meetings this week. The Bootable Image Unification meeting focused on defining a new architectural baseline via a minimal "seed" image and migrating base image repositories from GitLab to Forgejo. The group also announced the official sunsetting of the Atomic Initiative on October 31, 2026, as ownership successfully transfers to the community.

In broader Linux news, the Hummingbird Community Meeting highlighted that Fedora Hummingbird Linux is now powering Project Bluefin's new "Utah" alpha release and the upstream bootc-operator. Community discussions also explored practical applications of hardened images, bound images for specific workloads (such as PostgreSQL appliances), and new soft reboot capabilities for bootc-based artifacts.

Decisions

• The Atomic Initiative will officially shut down on October 31, 2026, transferring complete ownership to the unified group (Bootable Image Unification Meeting).
• A heavily minimized "seed" image will be created as an architectural foundation, containing only the kernel, systemd, SELinux policy, Podman, and bootc. It will be kept for internal and foundational use rather than direct general user consumption (Bootable Image Unification Meeting).
• The seed image will be tested using QEMU for direct kernel booting to avoid introducing unnecessary bootloader complexities or variant explosions (Bootable Image Unification Meeting).
• The new atomic-seed repository was created on Forgejo under an MIT license, and the team will target bootc directly without utilizing an rpm-ostree tree in the process (Bootable Image Unification Meeting).

Contribution opportunities

• Review and provide feedback on Architectural Decision Record 3 (ADR-0003) regarding the proposed monorepo for atomic images and Konflux CI/CD (Bootable Image Unification Meeting).
• Help identify gaps in the contribution ladder, including establishing and reviewing roles for Owners, Members, Contributors, and Reviewers (Bootable Image Unification Meeting).
• Contribute to initial container configuration tasks, documentation, and the setup of Konflux pipelines for the new atomic-seed repository (Bootable Image Unification Meeting).

Learn more about the Hummingbird team.

AI

This week, the AI/ML SIG reached a milestone by integrating ROCm 10.1 into Fedora Rawhide, closing gaps in older AMD GPU support and enabling better local AI testing. The infrastructure team successfully resolved network routing and SSL issues on the gpu01 hardware testing farm, ensuring CI pipelines for ROCm packaging remain functional. Additionally, contributors explored and packaged various local inference tools, including OpenClaw and Gufo, to optimize local model performance.

Strategically, the group participated in a cross-ecosystem leadership meeting to discuss AI model alignment with Fedora's open-source foundations. The consensus emphasized prioritizing model-agnostic tools and FOSS runtime engines over locking into specific models, while acknowledging the need for shared community inference infrastructure to ensure contributors with low-end hardware are not gated out of AI-augmented workflows. As a result of this strategy, proposals to exclusively deploy the fully-open but compute-heavy OLMo model were deferred until such shared infrastructure is realized.

Decisions

• The SIG decided to prioritize "tool freedom" by building model-agnostic, open-source contributor tooling (e.g., standard API endpoints and agent skills) rather than strictly mandating a specific LLM model for community infrastructure (Forum Discussion).
• Proposals to draft a broad Acceptable Use Policy for GPU hardware were closed as wontfix for now, as the current AMD hardware is reserved strictly for Continuous Integration (CI) workloads.
• The deployment of the OLMo LLM model on Fedora infrastructure was deferred due to its high compute overhead and lagging capabilities, pending the future deployment of shared contributor inference services.
• Automated bot alerts in Matrix have been moved out of the main SIG chat room to preserve human conversation readability. Notifications are now routed to a dedicated, opt-in #alerts-ai-ml:fedoraproject.org Matrix room (Ticket #42).

Contribution opportunities

• Help is needed reviewing the Gufo package for Fedora, which significantly speeds up local inference on specific AMD processors.
• Contributors with packaging expertise are invited to review and collaborate on AI agent skills Pull Requests, such as PR #18 and PR #25.
• The SIG is looking for a contributor to submit a Pull Request to list the AI-ML SIG on the Engineering Teams documentation page.

Learn more about the AI team.

RISC-V

The RISC-V group focused on finalizing Fedora 45 readiness, exploring kernel updates (including testing the 7.3 kernel), and advancing the Fedora ELN bootstrap for the RVA23 architecture. Contributors performed extensive debugging for various packages, successfully resolving LLVM 21.1.1 test suite failures, rebuilding Python packages for the 3.15 migration, and addressing nodejs, mysql, and cmake build issues.

Additionally, the team conducted build performance benchmarks comparing the SpacemiT K3 (RVA23) against older hardware like the P550, demonstrating significant speed improvements. Ongoing hardware stability investigations include debugging persistent glibc crashes on Milk-V Titan builders and testing transparent huge page (THP) disablement to fix GCC build failures on K3 boards.

Decisions

• The team decided to drop the VF2 PCIe patch from the kernel, shifting focus to the Omni kernel for users with older hardware.
• To mitigate GCC build failures on K3 boards, the group decided to disable transparent huge pages (THP) on affected builders as a non-invasive workaround.
• The weekly RISC-V SIG meeting has been rescheduled to Wednesdays at 18:00 CET.

Contribution opportunities

• Contributors with RISC-V hardware are invited to inspect mesa.spec to identify and enable missing hardware acceleration drivers.
• Help is requested to track down and permanently fix the underlying kernel issue requiring THP to be disabled on K3 boards.
• Assistance is needed to debug and resolve random glibc assertion failures (pthread_mutex_cond_lock) that are currently breaking builds on Milk-V Titan hardware.

Learn more about the RISC-V team.

NeuroFedora

This week, NeuroFedora officially closed its long-standing initiative to rethink its Python packaging strategy, as the new test-suite is now fully implemented and running regularly (Ticket #580). Following this strategy, the team is actively identifying leaf Python packages to orphan, such as python-interface-meta and potentially python-poetry-dynamic-versioning, while keeping others like python-dunamai until they are no longer required by the dependency chain (Matrix chat).

Additionally, the SIG is investigating packages that are failing to install in the test-suite for Python 3.14 and 3.15 (Ticket #588). Many of these failures are due to missing wheels for Python 3.15, which has sparked discussions on whether the test-suite should be limited to testing wheels only. The group also confirmed that they have provided all necessary approvals to be included in automated weekly reports (Ticket #587).

Decisions

• The initiative to rethink Python packaging and reduce the SIG's package count has formally concluded with the successful deployment of a regular test-suite (Ticket #580).
• python-interface-meta will be orphaned as it appears to be a leaf package, which may also allow python-poetry-dynamic-versioning to be orphaned (Matrix).
• python-dunamai will be retained by the SIG until it becomes a leaf package (Matrix).

Contribution opportunities

• Contributors are invited to review packages failing to install on Python 3.14 and 3.15 in the test-suite, and weigh in on whether the suite should be limited to testing binary wheels only (Ticket #588).
• Help is welcome to further improve the new package testing suite by implementing Forgejo actions (Ticket #580).

Learn more about the NeuroFedora team.

Gaming

This week, the Gaming group discussed the upcoming 64-bit Steam client beta and its impact on multi-lib support. A community member inquired whether the new client would resolve previous concerns that had sparked discussions about potentially dropping support for Steam. It was clarified that while the 64-bit client itself will not require 32-bit libraries—running instead inside the same runtime container used by the games—32-bit support (such as Mesa and glibc) will still be necessary for older 32-bit games to access graphics hardware.

Learn more about the Gaming team.

Perl

Between October 12 and October 18, 2026, the Perl group focused exclusively on routine package maintenance and version bumps. Contributors successfully updated several Perl packages to their latest versions across various branches, including perl-Net-CardDAVTalk, perl-ExtUtils-Typemaps-Default, and perl-CPAN-FindDependencies.

Additionally, there was minor ongoing coordination regarding disabling optional dependencies for perl-File-ShareDir on RHEL. Overall, the week saw smooth and rapid integrations of pull requests without any major disruptions or sweeping policy changes.

Decisions

• Merged pull requests to update perl-Net-CardDAVTalk to version 0.13 (PR #5 and PR #6).
• Merged pull requests to update perl-ExtUtils-Typemaps-Default to version 1.07 across multiple branches (PR #2, PR #3, PR #4, and PR #5).
• Merged a pull request to update perl-CPAN-FindDependencies to version 4.01 to address rhbz#2547436 (PR #3).

Learn more about the Perl team.

Python

The Python group's activity this week centered around a call for new maintainership for a highly utilized package. Miro Hrončok announced that he is seeking a new primary maintainer for python-hypothesis. Due to the upstream practice of releasing on every commit, keeping up with updates has become unmanageable for a single primary contact.

However, because python-hypothesis is a critical dependency required by over 100 packages (including pytest) during build time, it will not be orphaned. The current maintainer will remain available to assist whoever steps up to take over the primary duties.

Decisions

• It was decided that python-hypothesis will not be orphaned to avoid disrupting the builds of over 100 dependent packages in the broader ecosystem.

Contribution opportunities

• An experienced Python packager is needed to step up as the primary maintainer and main point of contact for python-hypothesis. The current maintainer will remain available to provide assistance and ensure a smooth transition.

Learn more about the Python team.

Ruby

Jarek Prokop announced the start of Ruby 4.1 development, beginning with a snapshot build based on upstream Git revision ad29ad7ad8. The initial Rawhide builds have completed successfully without any major surprises.

Continuous builds for Fedora are now available in a dedicated Copr repository, with the corresponding source code maintained in the 4.1 branch of Prokop's fork.

Decisions

• The Ruby group has initiated development on Ruby 4.1.
• Fedora gem ecosystem rebuilds will be performed periodically using a dedicated Copr repository, which will allow package maintainers to test compatibility as development progresses.

Learn more about the Ruby team.

Rust

This week, the Rust group focused heavily on resolving security advisories and cleaning up obsolete compatibility packages. Significant effort was directed toward addressing RUSTSEC advisories for crates like faster-hex (Issue 45), rustls (Issue 43), and ruzstd (Issue 42), which involved mass updates, creating side-tags, and coordinating rebuilds for dependent applications.

In addition, maintainers successfully concluded multiple package cleanups. Several old compat packages were officially retired, and progress was made on migrating applications away from unmaintained libraries like structopt, rustls-pemfile, and older versions of env_logger, itertools, and the gtk4-rs stack.

Decisions

• Rebuilds for specific packages affected by the faster-hex update (rust-cargo-semver-checks, rust-onefetch, and rust-cargo-c) will be delayed until the Fedora 45 Final Freeze lifts and side-tag updates stabilize (Issue 45).
• The rust-itertools0.11 compat package has been officially retired after backporting the final dependent package (Issue 11).
• The rust-signal-hook0.1 compat package was retired following the porting or retirement of its dependencies (Issue 23).
• The serial_test v0.5 compat packages were retired as their remaining dependencies were cleared (Issue 24).

Contribution opportunities

• Volunteer to package the qmassa GPU monitoring tool for Fedora, starting from the Non-crate Rust project spec file template (Issue 44).
• Assist with rebuilding dependent applications against the newly secured rustls v0.23.46 in the available Bodhi side-tags (Issue 43).
• Help port applications away from obsolete crates, such as moving structopt users to clap/derive (Issue 22), rustls-pemfile to rustls-pki-types (Issue 5), and bincode to modern serialization alternatives (Issue 6).
• Verify and rebuild stable branch applications (like akonadi-search, newsboat, or dnsdist) that may be affected by the cxx RUSTSEC-2026-0202 vulnerability (Issue 36).

Learn more about the Rust team.

Other Discussions

• In the Fedora Badges signed_fpca forum topic, a user inquired about gaining access to award badges. It was clarified that signing the Fedora Project Contributor Agreement grants visibility to the limited administrator frontend, allowing authorized users to hand out awards and create QR codes.
• A review of the Fedora-maintained hardening for general use cases documentation was posted on the forum. Users praised the thoroughness of the guide and debated whether permanent changes should overwrite or respect existing custom settings when implementing systemd-based hardening configurations.
• A thread explored whether packages would be easier to build by selecting specific dependency releases. The author proposed adding "upstream-release branches" in Fedora dist-git to help isolate complex application builds into containers or Flatpaks without bloating the traditional repository with parallel dependencies.
• Marián Konček shared the results of an Unused BuildRequires fields mass build using the unbreq Mock plugin on all Fedora packages. The report identified false positives related to hook ordering in %prep sections, which Konček plans to address in a future fix or through a new LD_PRELOAD implementation.
• The proposed Thin LTO Build Flag Change seeks to introduce an option to replace -ffat-lto-objects with thin objects (%global _lto_cflags %slim) to reduce memory exhaustion and build times on Koji. However, some developers doubted this would solve linking memory issues on 32-bit architectures like i686.
• A returning maintainer ran into authentication issues when trying to release a new version of the tss2 package. He was informed that his package had been orphaned and reassigned due to a period of inactivity, and he must now contact the current maintainer to be re-added to the package.
• The proposal to Relocate the SELinux policy store to /etc/selinux aims to unify standard, atomic, and ostree-based systems by storing policies outside of /var to assist with rollbacks. Reviewers pointed out that upcoming versions of libselinux will support loading policies from /usr, which is preferred by developers.
• A discussion about the present and future of Bodhi highlighted its unmaintained dependencies and UI freezes, sparking a conversation about whether to rewrite it or integrate it into larger Red Hat testing frameworks. QA members emphasized that Bodhi's tight integration with gating, package signing, and compose generation makes it difficult to easily replace.
• On the java-devel mailing list, Kenz S announced a New Fedora Forgejo repository for the Java Lounge matrix group. Maintainers are coordinating the addition of Java team members and planning to migrate documentation to Forge to improve integration with Fedora Docs.
• On the libteam mailing list, patches were successfully merged to factor out lacp_port_synced() and related functions in the teamd daemon.
• Other discussions included instructions on how to reach an inactive maintainer for a toxcore upgrade, a user reporting a damaged macOS DMG for Fedora Media Writer, the official deprecation of the quay.io/coreos/fcct Container Registry, a proposal to bump the Server aarch64 netinst image size limit, questions about outdated libicu timezone databases, and ongoing tracking of documentation pull requests and Design Suite documentation integration within the Fedora Docs Alerts matrix room.

Orphaning packages

• python-kerberos
• OpenImageIO2.5 compat package
• rubygem-ethon, rubygem-typhoeus, and rubygem-faraday
• python-proton-vpn-network-manager

Package updates

• SoapySDR (unannounced SONAME bump)
• uv 0.13 and ruff 0.17
• pygit v1.20.0
• z3 5.3.1
• ddcutil 3.0.2
• perl-SVK (license tag corrected)
• Imath 3.2
• perl-Gtk2-Notify (license tag corrected)
• aml v1.0.0, neatvnc 1.0.3, and weston 16.0.0

New contributor introductions

• Dawid Wrobel
• X. C.
• Nikita Sizikov

All contribution opportunities

For community members looking to jump right in, software testing and quality assurance offer immediate and highly impactful ways to contribute without requiring specialized group membership. Volunteers are urgently needed across multiple groups to review and vote on Fedora 45 blocker bugs via the blockerbugs app or through specific mailing lists for Desktop, Server, and ARM. Opportunities abound for general QA, including participating in the GRUB EFI and Podman Conmon-v3 Test Days, testing the KDE Plasma 6.8.0 and Apps 26.08.2 COPR release, and providing feedback on the new Fedora 45 nightlies for IoT. You can also help by testing the newly updated design-suite-docs locally, evaluating kiritan & subatomic as a performant alternative to createrepo_c, or investigating a keyring invalid content type bug.

If your strengths lie in communications, writing, or media, several teams are actively recruiting creative talent. The Fedora Magazine is seeking new writers, and FESCo specifically needs someone to draft an article explaining the migration away from vulnerable NetworkManager plugins. Documentation writers are invited to refine a Git cheat sheet for non-developers or assist with EPEL build-tagging instructions. On the design and media front, Mindshare is looking for volunteers to draft social media content and edit YouTube videos for the upcoming release party, as well as recruiting a brand new volunteer team dedicated to Fedora Badges. Those interested in community building can help brainstorm themes for Flock to Fedora 2027 or apply to organize and represent the project at the FOSSASIA 2027 Summit.

Developers looking to submit code patches have numerous approachable entry points. A great introductory task exists in the Infrastructure team to add error checking to the mote script, while the CoreOS team is looking for help rewriting a Python PoC newsletter tool into Golang and adding unit tests to Ignition's Azure logic. Web developers can assist by fixing a Wiki login loop UI bug, reviewing CSS for the WebUI installer, or submitting a pull request to the upstream ai-code-review tool to configure the verbosity of Forgejo LLM outputs. Additionally, Rust programmers are encouraged to help port applications away from obsolete crates.

For experienced contributors, there is a strong demand for package maintainers and architectural strategy reviewers. A large roster of orphaned packages needs adoption, and specific roles are open, such as primary maintainer for python-hypothesis, packaging the bup backup utility for KDE, or reviewing the Gufo AI package. Contributors are also invited to engage in package review swaps. Finally, at a higher structural level, members from any technical background are highly encouraged to review and comment on ADR-0003, which proposes a unified monorepo strategy for atomic image configurations and CI/CD pipelines.

Across the Fedora project this week, the primary focus is stabilizing the upcoming Fedora 45 release, which has officially entered its Final Freeze. Teams including Release Engineering, Quality, and various desktop and architecture groups are actively triaging blocker bugs, testing deliverables, and locking down infrastructure changes. Beyond the immediate release, a major collaborative focus is the newly named "Atomic Fusion" initiative, a strategic effort uniting the Atomic, CoreOS, IoT, and Hummingbird groups to design a unified, Konflux-built base image that minimizes attack surfaces by excluding tools like cloudinit and ignition. On the operational front, groups are heavily engaged in evaluating workflow tooling, marked by widespread assessments of a Bugzilla-to-Forgejo migration—which FESCo is currently pushing back against—and the rollout of LLM-powered community reporting tools, which prompted teams like Workstation and CoreOS to establish strict privacy and human-review boundaries. Finally, repository health remains a continuous cross-team priority, with FESCo, the Rust community, and NeuroFedora actively addressing orphaned packages and non-responsive maintainers to prevent downstream dependency breakages.

Announcements

On the development and infrastructure front, Fedora 45 has officially entered its final freeze, and an impact assessment for removing inactive packagers for the F45 release cycle lists potentially orphaned packages that currently need new maintainers. Infrastructure updates include detailed progress and plans for s390x improvements to address resource constraints, necessitating a planned s390x reboot. For QA and testing contributors, a Podman Test Week (also covered in a detailed Fedora Magazine article) invites help testing the Rust-based conmon v3, while community members continue to share advice on BTRFS system recovery methods.

Council

The Council held a bi-weekly meeting to discuss the F45 Final Freeze, finalize the new Decision Support Process, and begin brainstorming for Flock to Fedora 2027 Call for Proposals (CfP) themes. The Fedora Forge Usage Policy and Fedora Docs 2025 Initiative were formally closed following their approvals and updates, while @jflory7 was officially off-boarded from the Council following the end of his term as Fedora Community Architect.

New proposals were introduced regarding internal processes, including a non-binding "Sense of Council" vote process and making the Council Matrix channel publicly logged. A Bootable Image Unification Meeting also took place, where the team discussed Architecture Design Records (ADRs) and agreed on the project name "Atomic Fusion".

Decisions

• The Council finalized the conflict of interest discussions into a new Decision Support Process, deciding that the Fedora Operations Architect (FOA) will be the default owner to triage and action these requests.
• The Fedora Forge usage policy was officially approved and a request was made to add it to the official documentation.
• The Council voted to review and provide feedback on the Flock 2027 CfP themes via ticket comments, aiming for a usable draft by October 21, 2026.
• The external fundraising / Open Collective exploration ticket was closed to restart the effort properly with fresh, public discussion alongside the Mindshare Committee.

Contribution opportunities

• The Fedora Docs 2025 Initiative is requesting a six-month extension and is actively looking for a new executive sponsor to take over the role.
• Contributors interested in the "Atomic Fusion" Bootable Image Unification effort are invited to participate in consolidating the umbrella ADRs by joining the Bootable Image Unification Matrix channel.

Learn more about the Council team.

FESCo

FESCo addressed several critical governance, security, and infrastructure topics this week. The committee continued pushing back on the proposed migration from Bugzilla to Forgejo due to major feature regressions (e.g., cross-repo searches, bug relationships) and discussed exploring a self-hosted or consultant-supported Bugzilla instance instead. Additionally, FESCo processed multiple non-responsive maintainer tickets, notably prioritizing the retirement of vulnerable NetworkManager VPN plugins (NetworkManager-vpnc and NetworkManager-fortisslvpn) going back to Fedora 43. This obsoletion will impact existing users but was deemed an unavoidable security measure to prevent privilege escalation.

Other highlights include the nomination of a new FESCo member (maxamillion) to fill a vacant seat, progressing the change to use Sequoia (%openpgpverify) for post-quantum cryptography, and reaffirming strict boundaries for provenpackagers regarding mass package changes.

Decisions

• Retired and obsoleted NetworkManager-vpnc and NetworkManager-fortisslvpn across Fedora releases down to F43 due to unpatched privilege escalation vulnerabilities. (Ticket #3681)
• Elected to mark fedora-third-party updates as a blocker for Fedora Linux 45. (Meeting Log, Ticket #3682)
• Reaffirmed the provenpackager policy, specifically that provenpackagers must not perform mass cleanups or changes—such as converting to %autorelease or %autochangelog—without explicit maintainer permission. (Ticket #3687)
• Nominated maxamillion to fill the vacant FESCo seat left by duffy's resignation, which he accepted. (Ticket #3689)
• Processed non-responsive maintainer tickets for lkundrak, prarit, and gui1ty, resulting in the transfer to new volunteers or mass-orphaning of their respective packages. (Ticket #3681, Ticket #3665, Ticket #3678)

Learn more about the FESCo team.

Packaging Committee

This week, the Packaging Committee focused on two major themes: simplifying RPM snapshot versioning and updating Emacs packaging guidelines. Triggered by a recent versioning error in the bluez package that broke upgrade paths and caused openQA failures, the committee is heavily discussing a move to standardize snapshot versioning to a single, simpler format (<number>.<revision>) to prevent future mistakes (Issue #1570, Issue #1578).

Additionally, the group is modernizing its Emacs guidelines. This includes a new Work-in-Progress proposal to introduce RPM macros and dependency generators that natively support Emacs' built-in package management system, alongside finalized updates to existing Emacs packaging rules.

Decisions

• The pure GTK Emacs build is now explicitly packaged under the name emacs-pgtk (Issue #1575).
• The packaging guidelines were updated to clarify that Emacs 'compilation' refers strictly to byte compilation, distinguishing it from newer native compilation features (Issue #1574).

Learn more about the Packaging Committee team.

Mindshare

During the week of October 5 to October 11, 2026, the Mindshare committee actively cleared a backlog of event funding and swag requests while taking concrete steps to improve its own administrative efficiency. The committee successfully formalized a weekly meeting cadence—alternating between text and video formats—to curb previous delays in ticket resolutions.

Alongside standard event approvals, strategic discussions took place regarding the modernization of Fedora's physical event presence. This included plans to replace aging US and EU event boxes with new Pelican Air cases, the creation of a dedicated event box for India, and the production of localized tablecloths for EMEA events. Additionally, in response to persistently vacant seats on the committee, members proposed a structural change to allow rotating representation from active teams like Fedora Docs and Magazine, rather than static appointments.

Decisions

• Decided that the Fedora Design team will no longer supply custom artwork for event badges; event organizers must now design their own badges and submit them for Mindshare approval with a 30-day lead time (Ticket #145).
• Adopted a new weekly meeting cadence, alternating between text and video formats, to improve the committee's responsiveness to requests (Ticket #135).
• Approved producing an EMEA-specific event tablecloth first before expanding regional physical assets to APAC (Ticket #119).
• Maintained the current shared-responsibility model for Fedora's representation in the Digital Public Goods Alliance (Ticket #152).
• Approved regional swag and travel budgets for Texas Linux Fest 2026 (Ticket #148), LinuxDays 2026 (Ticket #149), IndiaFOSS 2026 (Ticket #147), and a Polish technical school (Ticket #138).

Contribution opportunities

• Provide feedback on the proposal to reconsider Mindshare Committee representation by rotating seats based on team activity and needs, potentially reallocating vacant CommOps or Marketing seats to the Fedora Docs or Magazine teams (Ticket #154, Ticket #145).
• Weigh in on the idea to create a DIY printable "Ask me about Fedora" t-shirt design (complete with a QR code) for community members to wear at conferences where Fedora lacks an official booth (Ticket #99).
• Mindshare Committee members are requested to pledge their timely availability to address recent delays in ticket voting and event curation (Ticket #153).

Learn more about the Mindshare team.

Fedora Join

This week, the Fedora Join group's primary focus was on addressing technical debt and improving the visibility of Fedora's web applications. Efforts are underway to update the outdated apps.fedoraproject.org directory. This exploratory project involves auditing existing applications, identifying unlisted infrastructure tools, and upgrading the web app's underlying Python software stack.

A community member has recently been assigned to take on this task as a "good first issue." The work will require collaboration with the broader Fedora Infrastructure team to ensure that the web directory accurately reflects the current state of active Fedora services.

Contribution opportunities

• The task to update apps.fedoraproject.org was identified as an excellent "good first issue." Although a community member has begun the initial exploratory work, the effort requires reviewing current infrastructure, discovering missing tools, and potentially upgrading the codebase to support modern software versions, which may offer further avenues for collaboration.

Learn more about the Fedora Join team.

Workstation / GNOME

The Workstation / GNOME group focused on preparations for the Fedora 45 release, evaluating blocker bugs and freeze exceptions as the Final Freeze begins. A major technical priority was fixing integration issues for the new oo7-daemon (which replaces gnome-keyring-daemon), specifically ensuring its portal component is correctly installed on Silverblue and GNOME systems. Additionally, developers are actively scripting the automation of appstream-data generation to prevent GNOME Software and KDE Discover metadata from becoming outdated between releases.

In other discussions, the Working Group addressed third-party software requests and clarified questions about dependencies. The group also provided feedback on these weekly reports, requesting that human review remain in place to filter out irrelevant or personal information before publishing chat summaries.

Decisions

• The Working Group rejected a proposal to include the proprietary, subscription-based LiveFaceSwap Desktop application in Fedora Workstation's third-party software discovery (Issue #530).
• To resolve missing dependencies during the transition to oo7-daemon, xdg-desktop-portal-gnome will now explicitly require oo7-portal to ensure it is installed by default on GNOME and Silverblue variants (Issue #506).
• The Working Group requested that human review of community posts and Matrix chat logs be required before including them in these automated weekly summaries, ensuring personal or irrelevant details are not broadcast (Issue #527).

Contribution opportunities

• Vote on Fedora 45 Blockers: Community members are encouraged to vote on proposed blockers and freeze exceptions for Fedora 45 in the blockerbugs app before review meetings. Voting in advance helps shorten the meetings (Meeting Announcement).
• AppStream Data Automation: There is ongoing work to automate the weekly generation of appstream-data. Contributors interested in packaging automation or verifying metadata diffs between Fedora versions can follow or assist in the progress (Issue #507).

Learn more about the Workstation / GNOME team.

KDE

The KDE group is preparing for the upcoming releases of KDE Plasma 6.8.0 and KDE Apps (Gear) 26.08.2. Due to the Fedora 45 final freeze, these major updates have already been pushed to Rawhide. For Fedora 44 and 45 users, the updates will be temporarily combined and made available via a COPR repository until the freeze is lifted and Fedora 45 is officially released.

In other news, the team is actively working on pulling the Union theme into Plasma Workspace, and preparations are underway for the Fedora 45 Blocker Review Meeting to finalize the upcoming OS release.

Decisions

• KDE Plasma 6.8.0 and KDE Apps 26.08.2 updates will be delayed for Fedora 44 and 45 until the F45 final freeze concludes; they will be provided via a COPR repository in the interim.
• The kgamma and kcm_wacomtablet packages will no longer receive updates and will be retired once Plasma 6.8 is released.
• Due to a libplasma soname bump in the Plasma 6.8 update, several dependent packages (including merkuro, kweather, kclock, kalgebra, kcm-fcitx5, kup-backup, and applet-window-buttons) will be rebuilt.
• The Union theme will be added to the KDE deliverables, starting with a recently rebased pull request for plasma-workspace.

Contribution opportunities

• Contributors and upstream community members are needed to help plan and participate in the KDE Plasma 6.8.0 Test Day, including exploring testing methods for Kinoite.
• Community members are encouraged to review and vote on F45 blocker bugs prior to the Fedora 45 Blocker Review Meetings using the blockerbugs app.

Learn more about the KDE team.

Server

The Server working group focused this week on F45 Beta release testing and advancing their Server Ansible support project. In F45 testing, initial-setup issues with the KVM image were successfully resolved, though some partition type issues with Kiwi persist. The group also briefly discussed aligning with the wider Fedora ecosystem by exploring a Borg-based backup solution, as backup coverage for F44 Server is currently lacking.

On the Ansible front, work is nearing completion to package the Server Ansible collection as an RPM, which will soon be released on Copr. Contributors identified idempotency and permission issues in the postinstall role, leading to plans to set up a molecule testing harness to test idempotence continuously. Finally, an announcement was shared on the mailing list regarding the upcoming F45 Blocker Review meeting for finalizing the release.

Decisions

• The group decided to hold off on immediately fixing the Kiwi partition type issue, as it is non-blocking and can be corrected during post-installation.
• Agreed to provision a dedicated VM for a molecule testing harness to ensure idempotence across the Ansible collection.

Contribution opportunities

• Contributors are asked to keep an eye on the F45 Beta testing tickets and claim tasks by leaving a comment.
• The working group is seeking help to draft the first versions of user documentation for their new Ansible support.
• There is a known gap in backup strategies and coverage for F44 Server; contributors familiar with backup tools (like Borg) have an opportunity to help shape Server backup documentation and defaults.

Learn more about the Server team.

Infrastructure

The Infrastructure group entered the Fedora 45 Final Infrastructure Freeze on October 6th, locking down system changes until after the release. Operations this week involved handling s390x hypervisor memory issues, replacing a failing RAID controller on a Copr builder host, and resolving an EPEL 10 repository access issue caused by version differences between RHEL and CentOS Stream. Additionally, discussions continued on migrating from Bugzilla to Forgejo, tracking AWS resource costs, and optimizing LLM code reviews on Forgejo.

The team welcomed several new contributors this week and processed multiple new tracking groups in FAS (including Fedora Java Lounge, dpdk, Regolith, and Free Explorers) alongside updates to mailing list ownerships and documentation fixes.

Decisions

• The Fedora 45 Final Infrastructure Freeze is in effect until at least October 20th. Frozen hosts should have no changes made to them without a sign-off from at least 2 sysadmin-main or rel-eng members.
• For CentOS 10 containers failing to install EPEL packages, a temporary workaround has been provided (dnf -y install epel-release && dnf -y upgrade epel-release) until RHEL 10.3 is released in November and the main epel-release-latest-10 symlink can be safely updated.
• Due to repeatedly failing disks on vmhost-p09-copr03, the host will be swapped out for a spare IAD2 Power9 host rather than reinstalling the existing faulty hardware.
• The Bugzilla to Forgejo migration assessment is underway; the team notes significant required workflow adaptations (e.g., losing global issue tracking and rewriting automated scripts like bugzilla2fedmsg and the-new-hotness).
• Documentation sources for the Fedora Design Suite Wiki are migrating directly to Forgejo instead of relying on a MediaWiki OIDC integration.

Contribution opportunities

• Review untagged AWS resources older than 24 hours. Owners must add the FedoraGroup tag to prevent automated deletion.
• Help is requested to create a playbook to automate the creation of tracking groups, which requires defining variables for description/display names and setting up FAS group configurations.
• The team welcomes newcomers! Interested contributors are encouraged to read the Infrastructure Join Guide and start with good-first-issues or small ticket requests in #noc:fedoraproject.org.

Learn more about the Infrastructure team.

Release Engineering

This week, the Release Engineering team successfully initiated the Fedora 45 Final Freeze. The team managed several critical build and infrastructure issues, including fixing a permissions bug that caused 403 errors on PXE boot images, resolving an AWS IAM role policy issue that broke Fedora CoreOS uploads, and mitigating an XML parsing failure on Koji builders triggered by a Python 3.14 update.

Looking forward, discussions and preparations have begun for a major system-wide change in Fedora 46 to switch to the RPMv6 package format. The team plans to test the rollout conservatively in a side-tag using a few select packages before considering broader implementation.

Decisions

• Fedora 45 officially entered its Final Freeze phase on October 6 (Issue #13544).
• Bug 2540692 (Cannot authenticate to secure wifi during gnome-initial-setup) was accepted as a Fedora 45 Final Blocker during the October 5 Blocker Review meeting.
• Bug 2545485 (Storage editor ignores BTRFS subvolumes under specific naming conditions) was rejected as a Final Blocker but accepted as a Freeze Exception during the October 5 Blocker Review meeting.
• The Fedora-ELN-NetworkInstaller package was created in the eln tag so Fedora ELN can transition to using image-builder for building artifacts (Issue #13547).

Contribution opportunities

• Community members are invited to review and provide feedback on the Fedora 46 change proposal to switch to the RPMv6 package format (wiki proposal here).
• Contributors can help streamline release efforts by voting on proposed blocker and freeze exception bugs prior to the upcoming Fedora 45 Blocker Review Meetings.

Learn more about the Release Engineering team.

Quality

The Quality team is highly focused on the final stages of the Fedora 45 release, which has officially entered the Final Freeze. Release validation is currently in progress, with strong test coverage and a relatively short blocker list. The team has been actively testing major new features, including kmscon userspace consoles and imagebuilder-built installer images, and recently discovered and fixed a longstanding bug affecting missing console keyboard layouts.

Test Days remain a major focus, with the Anaconda and CoreOS events concluding, and the Podman Conmon-v3 Test Days scheduled for mid-October. The team also conducted their weekly blocker review meeting, discussed streamlining predictable release chores by adding them to the automatic blockers list, and published the Q3 Heroes of Fedora Quality statistics to highlight and thank top community contributors.

Decisions

• It was generally agreed on the mailing list to add 'updates-testing repository still being enabled' and 'fedora-release package having a release number lower than 1' to the automatic Final release blockers list to save time during future blocker reviews.
• Bug 2540692 (Cannot authenticate to secure wifi during gnome-initial-setup) was officially accepted as a Fedora 45 Final Blocker.
• Bug 2545485 (Storage editor ignores BTRFS subvolume(s) if partition has the same filesystem label) was rejected as a Final Blocker but accepted as a Final Freeze Exception.
• Decision on Bug 2544626 (aarch Server DVD image install fails on RPi4 without network connection) was punted for a future meeting due to a lack of clear consensus.
• To resolve ongoing CI frustrations in dist-git PRs, rpmlint spelling checks will be downgraded to output warnings rather than errors (Issue #591).

Contribution opportunities

• Testers are needed for the upcoming Podman Conmon-v3 Test Days from 2026-10-12 to 2026-10-18.
• Contributors are encouraged to help improve the Heroes of Fedora Quality tools and workflows by automating the data collection and output generation for tester statistics.
• The team is seeking help to automate the mediakit checksums test case, which is currently performed entirely manually.
• Anyone with access to Beaker hardware is invited to help test F45 installations on bare metal and assist in writing a short guide for reserving machines.

Learn more about the Quality team.

Websites and Apps

The Websites and Apps team updated the Fedora download pages to visually highlight release-blocking deliverables with a star, clarifying for end users which images are fully tested by the Fedora Quality team versus those that are not. In the Fedora Websites Matrix room, the team discussed improving overall page load speeds by converting images to WebP format, bundling fonts, and downscaling new screenshots to 1360x768.

In the Fedora Apps Matrix room, a new build of Anitya was deployed to the staging environment for testing ahead of an upcoming release. The team also diagnosed a temporary rate-limiting issue with crates.io on release-monitoring, and clarified user confusion around the Badges admin interface, explaining that the UI remains visible but permission checks are safely performed retroactively when actions are attempted. Lastly, a forum discussion was started regarding the verbosity and excessive use of emojis in LLM-generated code reviews on Forgejo.

Decisions

• Release-blocking deliverables on the Fedora download pages are now explicitly marked with a star to distinguish them from non-blocking images that lack guaranteed testing.
• Secondary navigation bar logos on Fedora websites were updated to monochrome SVGs to improve visual consistency and reduce bandwidth.
• New website screenshots for the upcoming Fedora 45 release will be scaled down to a 1360x768 resolution to help optimize page load times.

Contribution opportunities

• Help is requested to update screenshots for Fedora 45 across all Editions, Spins, and Atomic Desktops.
• There is an open opportunity to remove outdated references to Zanata in the event CMS templates and replace them with references to Fedora Weblate.
• Contributors interested in website optimization can help investigate improving page load times by converting large images to the WebP format or bundling fonts.
• There is a long-standing wishlist item to create reusable event-specific page templates for major events (like FOSDEM, SCaLE, and DevConf), which currently rely on the Fedora Wiki.

Learn more about the Websites and Apps team.

Design

The Fedora Design team delivered promotional graphics and visual assets for the upcoming F45 Virtual Release Party, including social media banners and streaming templates. The team also concluded an investigation into Bugzilla workflow dependencies, confirming they exclusively use Forgejo and will be unaffected by Bugzilla's upcoming retirement. Additionally, a pull request was submitted to add CSS branding for the new WebUI-based installer to the fedora-logos package.

In their weekly meeting, the team reviewed CDUX logo mockups and managed their backlog by closing stale tickets. To improve workflows, they are restructuring their ticket queues to separate feature improvements from operational tasks. Ongoing open tasks include creating a high-resolution logo for GDM to fix fractional scaling blurriness, designing the F46 beta wallpapers, and crafting an avatar for the Matrix moderation bot.

Decisions

• Bugzilla Sunset Assessment: The team determined that the Bugzilla retirement will not impact their workflow, as they exclusively use Forgejo. No further migration planning is required for the Design group.
• Ticket Queue Restructuring: The group decided to establish a separation between standard operational tasks and feature improvements, planning to use a feature/improvements label.
• CDUX Logo Update: The team agreed to replace the fountain pen with a paintbrush in mockup 1C of the CDUX logo.

Contribution opportunities

• Design event-kit hex stickers for CentOS and EPEL, as requested in the Matrix chat.
• Provide a high-resolution (at least 600px width) SVG-derived Fedora logo to fix fractional scaling blurriness in the GDM greeter out-of-the-box experience (Issue #87).
• Create a new avatar for the Matrix Moderation bot (Issue #68).
• Help design the "Beta" wallpaper for Fedora 46 ahead of the mid-November deadline (Issue #77).
• Conduct initial user experience research on existing Fedora remix sites and Jekyll themes for Project Resistor (Issue #84).

Learn more about the Design team.

Docs

This week, the Docs team focused heavily on restructuring their Antora site architecture to allow for flexible module inclusion across different Special Interest Groups (SIGs). They decided to merge components under the ROOT namespace to shorten URLs and simplify maintenance, a massive change that will be tested incrementally on a newly configured staging instance. Furthermore, the team made progress integrating new AI/ML SIG and Security team documentation into the main user documentation structure.

Additionally, the team prepared the Beginner's Guide for the upcoming Fedora 45 release, resolved accessibility issues with image descriptions, and advanced collaborative writing efforts with a live CryptPad instance running in CommuniShift.

Decisions

• To accommodate cross-repository module inclusion (such as the new Security SIG user docs), all Docs repositories will transition to using ROOT as their antora.yml component name, which drops component names from the URLs altogether. This will be implemented and tested on a staging instance first, as discussed in Ticket #66 and the Oct 6 Meeting.
• The Security team's new user-facing documentation module will temporarily be included at the Fedora Linux latest index until the repository grows large enough to warrant its own dedicated space (Ticket #65).
• The obsolete prod branch in the builder repository will be renamed to main, pending successful testing on the staging Forge (Ticket #61).

Contribution opportunities

• Contributors are invited to provide feedback and suggest missing commands for a new WIP Git cheat sheet for writers.
• Reviewers are requested to proofread the Vorta backup section in the Beginner's Guide for typos before the Fedora 45 release.
• Community members can test the experimental Cryptpad instance in CommuniShift to evaluate its suitability for collaborative documentation drafting.

Learn more about the Docs team.

Legal

This week, the Legal group discussed the licensing of several projects and revisited existing policies. A significant portion of the conversation revolved around Fedora's policy on the CC0 license (also discussed here), which is currently restricted for software due to its explicit lack of patent grants. Despite user arguments to reconsider based on the license's "quiet enjoyment" waiver, legal experts maintained that the ban remains appropriate and aligns with both the license's original drafting history and current Free Software Foundation guidance.

Other discussions addressed specific packaging efforts. The Slint UI Framework was reviewed, and it was clarified that its GPL-3.0-only option is acceptable for packaging despite its broader dual-licensing and inbound MIT-0 contribution policy. Finally, a review of the koneko package determined that copyrighted third-party sprites must be removed at the source tarball stage to comply with distribution guidelines.

Decisions

• The koneko package's source tarball must be modified to remove copyrighted Cardcaptor Sakura artwork before it can be packaged.
• The Slint UI Framework is acceptable for packaging in Fedora under its GPL-3.0-only license option.

Learn more about the Legal team.

EPEL

This week, the EPEL team navigated tooling updates for the EPEL 10 transition, noting a bug in fedrq and a new mock release that simplifies repository configurations. In EPEL 9, Qt6 is being updated to version 6.10.3, which requires rebuilding a handful of dependent packages. Additionally, maintainers announced the retirement of several packages, and work continues on creating Koschei playbooks for minor End-of-Life and mass branching processes.

Decisions

• rust-libz-rs-sys is being retired from EPEL 9 and EPEL 10 by its maintainer, as it has been a leaf package for some time and is no longer useful for general development.
• singularity-ce will be retired from EPEL at the start of November, following the upstream project reaching End of Life / End of Engineering.
• python-sphinxcontrib-apidoc is being retired from EPEL 8 and EPEL 9 because it has been uninstallable. Maintenance will continue for EPEL 10, with a community member stepping up to help manage it.

Contribution opportunities

• Help is needed to fix obs-studio build failures against the new Qt 6.10.3 update in EPEL 9. The maintainer is open to suggestions and has provided a Copr repository for testing installs and builds.

Learn more about the EPEL team.

ELN

During the October 6, 2026 meeting, the ELN SIG discussed the transition to building boot.iso with image-builder. Minor OpenQA failures were noted in Rawhide, prompting the team to postpone the switch for a week to allow the changes to stabilize before being pulled into RHEL and CentOS Stream. The group also reviewed ELN Extras build failures (FTBFS), noting ongoing fixes for OpenSSL 4.0 compatibility (the_foundation and libesmtp) and resolving KDE issues caused by missed rebuilds. Finally, the team addressed Bodhi updates getting stuck due to planned outages and agreed on a procedural change to prevent this in the future.

Decisions

• The team decided to delay the switch to building boot.iso with image-builder until next week to let recent Rawhide changes stabilize (Releng Ticket #13547).
• Infrastructure documentation and procedures will be updated to automatically pause and unpause elnbuildsync (EBS) during future planned outages to prevent updates from becoming stuck (Meeting Log).

Learn more about the ELN team.

Atomic

This week, the Atomic group focused heavily on the unification of Fedora CoreOS and Atomic efforts under the new project name, "Atomic Fusion." The team held their first dedicated video meeting to discuss Architectural Decision Records (ADRs), specifically focusing on a unified base image architecture built with Konflux, which excludes cloudinit and ignition to minimize attack surfaces. They also established standard operating procedures for the project, including a weekly Thursday video meeting cadence, a "Doacracy" work prioritization model, and utilizing a renamed Matrix channel for communication.

In addition to unification planning, several technical issues were addressed for Fedora 45. The group merged a change to use kmscon as the default VT console in F45, resolving dependencies to bring it to bootc base images. A packaging bug causing COSMIC Atomic spin rawhide composes to fail was fixed in the latest compose, and an update was pushed to fix a missing public key error during system upgrades. The team is also actively investigating a boot failure and emergency mode issue affecting users who upgrade on non-BTRFS filesystems.

Decisions

• Fedora 45 will use kmscon as the default VT console for Atomic images (Source).
• The official project name for the CoreOS and Atomic unification effort is "Atomic Fusion" (Source).
• The team will prioritize work using a "Doacracy" model, meaning contributors who step up to do the work will set the immediate task priorities (Source).
• Unification meetings will be held weekly over video on Thursdays, as listed on the Fedocal SIG calendar (Source).
• The old initiative Matrix channel has been officially renamed to serve as the main workspace for unification discussions (Source).

Contribution opportunities

• Help is requested to consolidate the initial Architectural Decision Record (ADR) subdecisions for the unified base image into a single reviewable pull request. Interested contributors should join the Bootable Image Unification channel on Matrix to coordinate (Source).
• Community members are invited to participate in the CoreOS and Atomic Unification effort by joining the newly scheduled weekly video calls on Thursdays and assisting with the migration to the unified architecture.

Learn more about the Atomic team.

CoreOS

The Fedora CoreOS and bootc teams have officially begun merging their efforts, moving unification planning and architecture discussions to a dedicated Thursday video call, while leveraging the regular Wednesday meeting to handle current events, challenges, and tickets for both offerings. As the Fedora 45 Final Freeze is underway, several important fixes have successfully landed, including using kmscon as the default VT console, removing DTBs on aarch64 to save space in the boot partition, and officially declaring the composefs backend stable in bootc 1.17.0.

The community also addressed a slew of hardware and platform-specific pipeline issues this week. Notably, an AWS AMI import pipeline failure caused by a missing IAM role permission was resolved, and Azure Confidential VMs (CVMs) not picking up Ignition custom data was fixed via an upstream Ignition update. Meanwhile, the group agreed to use a build postprocess to patch dracut 111 errors on rawhide rather than continuing to wait on delayed upstream RPM backports.

Decisions

• Decided to unify CoreOS and bootc community meetings and outputs, establishing a regular Thursday video call for architecture and planning.
• Decided to remove Device Tree Blobs (DTBs) on aarch64 builds in Fedora 45 and later to save space in the /boot partition (#2222).
• Decided to manually patch a known failing file in dracut directly during the build postprocess for Fedora \<= 46 instead of waiting on upstream RPM updates (#2206).
• Decided to limit data collection for LLM-powered weekly reports strictly to official meeting logs and GitHub repositories, excluding raw chat conversations due to privacy concerns (#2223).

Contribution opportunities

• Volunteers are needed to help clean up FCOS manifest overrides, which largely involves following up with upstream package maintainers. Interested contributors can reach out in the CoreOS meeting channel.
• Contributors are invited to help write and consolidate Architectural Decision Records (ADRs) for the unified base image architecture. Interested parties should join the Bootable Image Unification channel on Matrix (as noted in the forum discussion).

Learn more about the CoreOS team.

IoT

This week, the IoT group focused on standardizing bootable image architectures and general repository housekeeping. The newly named "Atomic Fusion" project held a kickoff meeting for bootable image unification, proposing an Architectural Decision Record (ADR) that leverages container files and downstream variants while excluding cloudinit and ignition to minimize attack surfaces. They also recommended using Konflux as the standard build system for all Fedora bootable image outputs and systemd system extensions for platform-specific configurations.

In parallel, the team closed several long-standing tickets, highlighting that the Fedora ROS2 testing repository is now officially available in the ROS2 documentation as a result of collaboration with the Robotics SIG. Other closed trackers included updates for the deprecation of the Zezere provisioning tool, resolving Lua script upgrade errors, missing license files in osbuild installers, and initial bootc container builds.

Decisions

• The bootable image unification project was officially named "Atomic Fusion".
• Atomic Fusion's base image will exclude cloudinit and ignition to minimize attack surfaces, manage platform-specific configurations via systemd system extensions, and use Konflux as the standard build system for all Fedora bootable image outputs.
• The Fedora ROS2 testing repository was officially declared available for use in the ROS2 documentation, expanding Fedora's support for robotics and factory automation use cases.

Contribution opportunities

• Contribute to the Atomic Fusion image unification work by reviewing and consolidating Architectural Decision Records (ADRs) in the project's Forgejo repository.
• Join the Bootable Image Unification channel on Matrix to participate in ongoing discussions about unified base image architectures.

Learn more about the IoT team.

ARM

The ARM community was notified of the upcoming Fedora 45 Blocker Review Meeting, scheduled for October 12, 2026, at 16:00 UTC on Matrix. The meeting will focus on evaluating 4 proposed blockers and 7 proposed freeze exceptions for the Final release to determine if they violate any release criteria.

Participants were strongly encouraged to review the bug lists and cast their votes ahead of time using the blockerbugs app, which helps streamline the meeting and reduce its overall duration.

Contribution opportunities

• Review and vote on proposed blocker bugs and freeze exceptions for Fedora 45 prior to the meeting using the blockerbugs app or Pagure tickets.
• Attend the Fedora 45 Blocker Review Meeting on October 12, 2026, at 16:00 UTC via Matrix.

Learn more about the ARM team.

Alternative Images

The Alternative Images group met to discuss the upcoming quarterly image updates, which are targeted for release in roughly two weeks. A major highlight for this quarter's release will be the introduction of the project's first aarch64 raw images, generated using KIWI configuration.

In addition to the upcoming images, the team reported progress on building RISC-V packages for CentOS Stream 10 and processing Qt 6 updates for EPEL9. Testing for these alternative architectures has also improved, as team members noted that transitioning development laptops to Fedora CSB has successfully enabled multi-arch virtualization for local aarch64 and riscv image testing.

Contribution opportunities

• Help is needed to patch or update obs-studio for EPEL9; it is currently failing to build during the Qt 6 updates because GUI-Private was removed in Qt 6.10 (Meeting log).

Learn more about the Alternative Images team.

Hummingbird

The Hummingbird group kicked off its video meeting cadence for the bootable image unification effort, which aims to merge the CoreOS and Atomic Initiatives. During the October 8 meeting, the team reviewed a proposed unified base image architecture that leverages container files and downstream variants, excluding cloudinit and ignition to minimize attack surfaces. They also discussed handling platform-specific configurations via systemd system extensions and recommended Konflux as the standard build system.

The group established a formal process using Architectural Decision Records (ADRs) to track project decisions. Moving forward, the team officially adopted "Atomic Fusion" as the project name and began scaffolding an umbrella ADR to consolidate their initial architectural choices into a single reviewable document.

Decisions

• Accepted "Atomic Fusion" as the official project name for the bootable image unification effort (Original topic).
• Adopted a formal Architectural Decision Record (ADR) management process, utilizing sequential numbering and proposal PRs to review and ratify architectural choices (Original topic).

Contribution opportunities

• Contributors are invited to participate in consolidating the first round of unified base image architecture decisions on Forgejo Pull Request #2.
• Interested community members can join the discussion in the Bootable Image Unification Matrix channel (Original topic).

Learn more about the Hummingbird team.

Kernel

In a discussion regarding an RFC on splitting perf out of the kernel packaging, Fedora Python maintainers expressed a desire for the split. This separation would allow them to independently rebuild perf for Python packaging changes without requiring kernel-level signing permissions. However, other community members questioned whether this is a significant hurdle, noting that Rawhide kernels are already built almost daily to keep up with upstream changes.

Learn more about the Kernel team.

AI

The AI/ML SIG is making significant progress on the ROCm 10.1 stack, which is currently available in the preview COPR and compiling cleanly with downstream consumers like PyTorch. The updated toolchain introduces LLVM 24, preliminary support for the Khronos SPIR-V standard, and initial compiler support for the gfx1170 APU, with a multi-day Koji sidetag rebuild expected soon.

On the community front, the group agreed to enable an opt-in LLM summarization bot for the This Week in Fedora (TWIF) weekly reports to improve external visibility. Additionally, the SIG is debating a proposal to migrate documentation from the Fedora Wiki to Fedora Docs to align with standard project infrastructure, alongside discussions on authoring new beginner-friendly AI tutorials.

Decisions

• Allow the This Week in Fedora (TWIF) summarization bot to ingest the public SIG Matrix chat history on a trial basis to generate weekly reports for the wider community (Ticket #39).
• Relocate automated Forgejo bot notifications from the main Matrix room to a dedicated, opt-in alerts room to keep human discussions clear of clutter (Ticket #42).
• Grant forge-ai-ml-owners membership to @jflory7 to manage organization-wide labels and webhooks on the Fedora Forge repositories (Ticket #41).

Contribution opportunities

• Community members are invited to participate in the upcoming Fedora/RHEL/CentOS Leads (FRCL) open discussion on "Which LLM-gen-AI models are more aligned with Fedora?" scheduled for October 14 (Ticket #43).
• Contributors are welcome to help draft and shape beginner-friendly getting-started guides for Fedora Linux, focusing on topics like local AI inference (Ollama, RamaLama), GPU tuning, and AI coding agents (Ticket #6).

Learn more about the AI team.

RISC-V

This week, the RISC-V team focused heavily on preparing Fedora 45 (successfully testing Server, Cloud, and Container images) and progressing the Fedora 46 sync, analyzing the content-set diffs compared to the main Koji. Significant effort was directed toward bootstrapping Fedora ELN for riscv64, which involved configuring Koji tags, managing test suite failures in problematic packages, and successfully building LLVM from vanilla Fedora sources.

Kernel development centered on the Omni kernel, with maintainers preparing to adopt the upstream kernel 7.3 for F45. The team also investigated a persistent GCC build segmentation fault on K3 hardware and actively participated remotely in the Linux Plumbers RISC-V Microconference.

Decisions

• Disable the openmpi test suite on riscv64 due to persistent hardware-specific hangs to unblock the Fedora ELN bootstrap.
• Remove the VF2 PCIe patch from the unpatched Fedora 7.3 kernel for Fedora 45, steering users of older hardware toward the Omni kernel instead.
• Disable the MLIR execution engine in LLVM 21.1.1 for RISC-V to bypass unresolved test failures (Issue #2).
• Hold off on manually fixing empty debugsource packages caused by lack of LTO, as GCC 17 will naturally resolve this issue later this year.

Contribution opportunities

• Help is needed from compiler experts to debug and resolve a GCC build segmentation fault on K3 hardware.
• Contributors are invited to help test the Fedora 45 Server, Cloud, and Container RISC-V images.

Learn more about the RISC-V team.

NeuroFedora

The NeuroFedora group has successfully reached out to a non-responsive maintainer and consolidated admin rights for all neuro-packages to streamline review and cleanup efforts. This administrative update supports the team's ongoing initiative to reduce their Python packaging footprint by relying on direct installations from PyPI where appropriate. A dedicated test suite has been implemented to monitor the status of these packages and is now running regularly.

The group is currently reviewing packages that fail to install on Python 3.14 and 3.15 in the new test suite, and is considering limiting their automated tests strictly to pre-compiled wheels. Furthermore, team members have agreed to include their public activity in these weekly summaries for the Fedora community.

Decisions

• Admin rights for all neuro-packages were granted to active team members to facilitate the review and retirement of unneeded packages.
• The team finalized its strategy for reducing its Python packaging maintenance, replacing direct maintenance of some packages with a regular test suite to track compatibility.
• The group approved the collection of their public tracking and discussion data for automated weekly Fedora community reports.

Contribution opportunities

• Provide feedback on packages failing to install on Python 3.14 and 3.15 and discuss whether the test suite should be restricted to checking pre-compiled wheels only.

Learn more about the NeuroFedora team.

Perl

This week, the Perl group focused on maintaining and updating key packages, primarily resolving several lingering pull requests. Maintainers manually incorporated commits to update the rt (Request Tracker) package to version 5.0.10 after encountering merge conflicts, and a new draft pull request was recently opened to push rt further to version 6.0.3.

Additionally, housekeeping efforts led to the closure of older, redundant pull requests in rt and perl-Plack, while a dependency update was successfully merged for perl-Package-Generator to conditionalize Params::Util.

Decisions

• Merged a pull request to conditionalize the Params::Util dependency in perl-Package-Generator.
• Closed an outdated pull request intended to fix build-require paths for rt, as the necessary font build requirements (font(droidsans) and font(droidsansfallback)) had already been updated by maintainers.
• Manually incorporated commits to update rt to 5.0.10 due to merge and rebase conflicts, subsequently closing the original pull request.
• Closed a pull request to drop support for mod_perl in EL9 and later in perl-Plack because the author already possesses repository commit access.

Learn more about the Perl team.

Rust

This week, the Rust community was alerted to a looming issue affecting crun-vm builds. Fabio Valentini notified the maintainers that several of the project's dependencies are currently orphaned and are slated for removal from Fedora within the next one to two weeks. The affected packages include rust-rxml, rust-rxml_proc, rust-weak-table, rust-rxml_validation, and rust-minidom.

Contribution opportunities

• Maintainers are urgently needed to take ownership of five orphaned Rust packages (rust-rxml, rust-rxml_proc, rust-weak-table, rust-rxml_validation, and rust-minidom). Community members must step up to unorphan these packages to prevent crun-vm builds from breaking due to missing dependencies.

Learn more about the Rust team.

Other Discussions

• Shivank Sharma asked if signing the Fedora Project Contributor Agreement (FPCA) automatically grants access to award badges. Akashdeep Dhar clarified that while the admin frontend becomes visible, the user's authorizations dictate which badges they can actually award.
• Miroslav Suchý shared a list of newly added packages in Fedora Linux for September 2026, generated from the rawhide-changes script.
• Gordon Messmer inquired about how to contact the crypto team to add AWS s2n-tls to Fedora, noting that their mailing list is closed to non-members. Dmitry Belyavskiy offered to discuss the issue at the upcoming OpenSSL conference.
• Abdallah Shehawey proposed packaging a source-only version of whatsapp-desktop relying on a system-provided Electron runtime. The discussion highlighted the challenges of maintaining multiple Electron versions in Fedora and keeping dependent packages synced.
• Fabio Valentini reached out to find the maintainer of julia, noting that unmerged pull requests are causing FTBFS errors in Fedora 45 and that the non-responsive maintainer process has been initiated.
• Alejandro Lopez asked why rpminspect was reporting insecure mode failures for a sudo merge request on ELN. Dave Cantrell explained that the rpminspect environment lacked a product definition for ELN, leading to the creation of a new tracking ticket.
• Michel Lind proposed splitting the perf tool out of the kernel packaging to reduce build requirements, simplify the package spec, and avoid requiring kernel rebuilds when updating Python packaging.
• Julian Sikorski asked for advice on adding openh264 as a build requirement for MAME. Neal Gompa and Michael J Gruber recommended using the system package via pkgconfig and stripping the bundled source from the tarball during the prep phase to avoid patent issues.
• Chih-Tao Lee initiated a non-responsive maintainer check for python-authlib and successfully stepped up to co-maintain it alongside the RHEL Lightspeed group.
• Aoife Moloney shared the summary of the latest Fedora Council meeting, noting an agreement to implement a "Decision Support Process" instead of strict Conflict of Interest Guidelines, and starting discussions for Flock 2027 CfP themes.
• Other discussions included a reminder for the Fedora 45 Blocker Review Meeting, a review request for coconut-svsm for confidential computing, a non-responsive maintainer check for Luis Bazan, deleted branches and commits in the glibc-maintainer-scripts repo on the glibc mailing list, and updates in the Fedora Docs Matrix channel covering pull requests for image accessibility, rebuilding site scripts, and FIDO2 PIN commands.

Orphaning packages

• Michael Catanzaro announced he is orphaning WebKitGTK across all branches due to leaving his job, with Fabio Valentini volunteering to take over maintenance.
• Benson Muite announced the orphaning of python-proton-vpn-network-manager due to lack of time to maintain its required dependencies, which now involve Rust.

Package updates

• Richard Shaw updated OpenColorIO to version 2.6, handling an upstream SONAME bump and successfully rebuilding all dependent packages.
• Kaleb Keithley announced an update to Apache Arrow 26.0.0, which includes a libarrow SONAME bump and requires rebuilding dependent packages like ceph and gdal in a side tag.
• Antonio Trande announced that PETSc is being updated to 3.26 in Rawhide and F45, and listed the dependencies that require rebuilding.
• Stephen Gallagher warned of a backwards-incompatible update to python-openai 3.24.0 in Rawhide and F45, making HTTPX2 the default and removing deprecated CLI tools.

New contributors

• Andrew Heath introduced themselves, sharing a decade of enterprise Linux and infrastructure-as-code experience, and is looking for a sponsor to help with packaging, image building, and QA.

All contribution opportunities

Contributors with a passion for Quality Assurance and Testing have numerous accessible entry points to help ensure a stable release. Community members are highly encouraged to shorten review meetings by voting early on proposed Fedora 45 blockers and freeze exceptions for Workstation, KDE, ARM, and Release Engineering using the blockerbugs app. Hands-on testers can jump into the Podman Conmon-v3 Test Days or the KDE Plasma 6.8.0 Test Day. If you prefer trying out new builds, you can claim F45 Beta Server testing tickets, run bare-metal installations on Beaker hardware, or test upcoming RISC-V images.

Those skilled in Technical Writing, Community Feedback, and Documentation can make an immediate impact without deep technical onboarding. Writers and editors are needed to proofread the Beginner's Guide Vorta backup section, draft new AI getting-started guides, and create documentation for Server's new Ansible support. Reviewers can also provide valuable insights by suggesting missing commands for a Git cheat sheet, testing a collaborative Cryptpad instance, or weighing in on broad ecosystem changes like the RPMv6 format transition (feedback ticket) and AI model alignment. Additionally, contributors can help coordinate cross-team efforts by reviewing Bootable Image Unification ADRs or sharing thoughts on Mindshare's committee representation adjustments.

For contributors specializing in Design, Web Development, and Automation, several creative and structural tasks are open. Designers are invited to create CentOS/EPEL hex stickers, design the F46 Beta wallpaper, craft an avatar for the Matrix Moderation bot, and supply a high-resolution SVG Fedora logo for GDM. Web developers can help update apps.fedoraproject.org, replace outdated Zanata references with Fedora Weblate in CMS templates, and assist with website optimization and reusable event templates. Meanwhile, scripters and automation enthusiasts can improve infrastructure by automating AppStream data generation, tester statistics (Heroes of Fedora), mediakit checksums, and Infrastructure tracking groups.

Finally, experts in Software Packaging, Debugging, and Systems Engineering are in high demand to maintain the ecosystem's backbone. C/C++ developers can assist in resolving a GCC build segmentation fault on RISC-V K3 hardware or fixing obs-studio build failures against the new Qt 6.10 framework in EPEL. Maintainers are urgently needed to adopt five critical orphaned Rust packages to prevent VM build breakages, alongside other tools like julia and transifex-client. Systems engineers can make an impact by reviewing untagged AWS resources, evaluating Python test suite restrictions, or assisting with the CoreOS and Atomic unification migration. Members with strong leadership experience can also step up to sponsor the Fedora Docs 2025 Initiative.

Across the Fedora ecosystem this week, groups are heavily focused on stabilizing the upcoming Fedora 45 release, with teams like Quality, Release Engineering, and Workstation actively coordinating blocker reviews, test weeks, and freeze exceptions. Another major common thread is the ongoing modernization of project infrastructure, particularly the transition toward Forgejo—guided by the Council's newly approved Fedora Forge Usage Policy—and the strategic workflow planning for Red Hat's upcoming Bugzilla sunset, which is actively impacting discussions within EPEL and Design. Finally, navigating the integration of Artificial Intelligence has become a prominent focal point; the newly rebranded Fedora AI Working Group is establishing formal AI assistance disclosure policies, while several groups including Fedora Join, Diversity & Inclusion, and CoreOS are actively debating data privacy and opt-in boundaries regarding the collection of their communications for this report.

Announcements

The Fedora QA team is calling for community participation in the Anaconda F45 features Test Week, running through October 2, 2026. This is a highly focused opportunity for contributors to help shape the upcoming Fedora 45 installer by testing significant new capabilities, ensuring a smooth transition and avoiding disruptive surprises upon release. Key features needing real-world virtual or bare-metal testing include the modern WebUI for Atomic Desktops, browser-based remote installation support, and integrated Stratis storage configuration.

In broader ecosystem news, the Fedora Project recently supported a highly successful Software Freedom Day Bukidnon 2026 in the Philippines, bringing together students, educators, and professionals to celebrate open-source innovation with sessions ranging from automotive Linux to running local AI models. Meanwhile, on the technical discussion front, contributors are actively sharing best practices for installing the Navidrome music server on Fedora using Podman. Recent forum activity highlights how to optimize the setup using native systemd container files, rootless user namespaces, and automatic SELinux context tagging, providing a more robust, Fedora-native alternative to standard Docker configurations.

Council

During this period, the Council primarily focused on establishing clear governance for core project infrastructure and ensuring the continuity of Fedora's external partnerships. A key theme across both tickets was formalizing responsibilities and defining clear boundaries for project resources to maintain a sustainable ecosystem for all contributors.

Notably, the group concluded voting on the comprehensive usage policy for the Fedora Forge and successfully coordinated a transition plan for Fedora's ongoing representation in the global Digital Public Goods Alliance (DPGA).

Decisions

• Approved the new Fedora Forge Usage Policy by an 8-0 vote. This significantly affects the broader community by restricting the Forgejo instance strictly to Fedora-related work rather than serving as a general-purpose host. The policy mandates FAS authentication, establishes a soft repository size limit of 500MB, enforces a 10-minute timeout for shared CI runners, and outlines a formal exception process for ecosystem upstreams.
• Decided (by a 9-0 vote) to transition the responsibility of representing Fedora in the Digital Public Goods Alliance (DPGA) away from the Fedora Community Architect role. The Council agreed to formally request that the Fedora Mindshare Committee assume this long-term relationship, while immediate 2026 renewal tasks will be handled by current members. Documented in Issue 576.

Learn more about the Council team.

FESCo

This week, FESCo held one meeting but did not reach quorum, deferring formal votes. The committee briefly discussed the Forge Usage Policy and the process for appointing a new member. In the issue trackers, FESCo debated Koji build performance expectations for secondary architectures, analyzed requirements for the upcoming Bugzilla replacement, and tracked incomplete Fedora 45 Changes. Additionally, three new Change proposals (Crystal Language, Thin LTO Build Flag, and Libical4) were opened for voting, and community members discussed a proposal to preserve Git-derived modification timestamps for source packages.

Decisions

• Processed a non-responsive maintainer ticket, transferring ownership of actively maintained packages to new volunteers and orphaning the remainder.
• Authorized the retirement of the NetworkManager-vpnc and NetworkManager-fortisslvpn packages, intentionally using Obsoletes in the main NetworkManager package to forcefully uninstall them from user systems due to a critical privilege escalation vulnerability.
• Resolved the issue of kmscon breaking certain display managers after a workaround was pushed to stable for lightdm, noting that similar issues in other display managers should be handled as normal bugs.
• Confirmed the completion of the 'Filter Fedora Flatpaks for Atomic Desktop v2' Change and formally retargeted the 'Disable Vendor Change by Default' Change to Fedora 46.

Learn more about the FESCo team.

Packaging Committee

During its weekly meeting, the Packaging Committee processed multiple routine documentation updates and engaged in a lengthy discussion regarding a major simplification of snapshot versioning. Several minor updates concerning Emacs packaging and documentation restructuring were successfully merged.

The most significant ongoing topic is issue #1570, which proposes standardizing snapshot versioning to a single <number>.<revision> format to reduce complexities that have historically caused upgrade path breakages for packagers. While initial meeting votes favored the simplification, formal voting is continuing on the ticket to ensure the required committee majority is met.

Decisions

• Adopted a new fast-track rule allowing trivial or non-controversial pull requests to be merged before the next meeting if they receive two FPC member approvals.
• Approved and merged issue #1573 to move legacy complex versioning instructions into a separate versioning appendix page, streamlining the main versioning guidelines.
• Approved and merged issue #1574 to clarify that references to Emacs compilation in the guidelines specifically mean byte compilation.
• Approved and merged issue #1575 to reflect that the Pure GTK Emacs build is now provided by the emacs-pgtk package.
• Closed issue #1576 regarding the deprecation of the Group tag.

Learn more about the Packaging Committee team.

Mindshare

This week, Mindshare celebrated successful community events, reviewing reports and finalizing logistics for IndiaFOSS 2026, Data Con LA 2026, and Software Freedom Day Bukidnon 2026. Driven by the success of APAC events, the committee resolved to create a dedicated event box stationed at the Red Hat Pune office to streamline regional swag distribution and significantly reduce international shipping costs for local organizers.

Governance and activity levels were also a major focus, prompted by Ticket #153. To address recent delays in ticket triage and ongoing vacant representative seats (such as Comm Ops and Marketing), the committee discussed modifying its rules to formally reallocate representation to more active sub-teams, ensuring consistent and timely support for contributors and organizers across the broader Linux community.

Decisions

• Agreed to establish a new Fedora event box based in the Red Hat Pune office to better serve the APAC region without the prohibitive costs of international shipping from the US or EU. (Mindshare Meeting)
• Initiated a process to review and potentially change Mindshare representation rules, aiming to replace statically designated seats (like Comm Ops and Marketing) with flexible seats assigned annually to the most active community subgroups. (Mindshare Meeting)

Contribution opportunities

• Mindshare is seeking contributors to get involved with AI, documentation, and moderation efforts, providing opportunities for active individuals to eventually step into committee representative roles. (Ticket #153)
• Local event organizers in the Philippines (such as those behind SFD Bukidnon) are actively looking for resident Fedora Ambassadors to partner with for future open-source events. (Ticket #146)

Learn more about the Mindshare team.

Fedora Join

This week, the Fedora Join group welcomed two new contributors who introduced themselves via the forum and the mailing list, expressing interest in Docs, Python, and infrastructure. In the issue tracker, the group actively collaborated on shaping the new contributor experience by providing feedback for the Fedora Docs front page.

Additionally, the group approved the collection of their public activity for this report, explicitly exempting their Matrix chat to preserve a relaxed environment for newcomers. Work also began on auditing and updating the Fedora Apps directory.

Decisions

• The group decided to permit the collection of their mailing list, Discourse, and issue tracker data for the This Week in Fedora report, but explicitly excluded the Join Matrix channel from being scraped in order to protect it as an informal, friendly space for new members.

Contribution opportunities

• The Fedora Docs team is seeking time-sensitive feedback on adding a "Contribution" section to the Docs homepage. They are looking for ideas on which topics, SIGs, and non-technical contributions to highlight to attract newcomers.
• Exploratory work has started to update apps.fedoraproject.org. While a contributor has been assigned, the issue highlights ongoing infrastructure needs such as reviewing current web apps, finding unlisted services, and updating software stacks.

Learn more about the Fedora Join team.

Ambassadors

Planning for FOSDEM 2027 has officially begun, with Justin Wheeler and Daniel Mellado acting as event co-owners for Fedora. Applications for a Fedora stand and the Distributions DevRoom have already been submitted. Additionally, organizers are currently negotiating a single, larger hotel block for Fedora and CentOS contributors at the DoubleTree by Hilton Brussels City.

Decisions

• Applications for a Fedora stand and the Distributions DevRoom at FOSDEM 2027 have been officially submitted.
• A single, shared hotel block at the DoubleTree by Hilton Brussels City is being negotiated for Fedora and CentOS contributors attending FOSDEM 2027.

Contribution opportunities

• Contributors planning to attend FOSDEM 2027 are encouraged to monitor the mailing list and wiki for upcoming details on booking rooms within the Fedora and CentOS hotel block.
• Community members with questions or ideas about the event are invited to engage with the organizers by replying directly to the mailing list thread.

Learn more about the Ambassadors team.

Diversity & Inclusion

This week, the Diversity & Inclusion team resolved a discussion regarding the automated collection of group data for this weekly report. The team evaluated which communication platforms should be included in the data ingestion.

They concluded that while indexing asynchronous platforms like Discourse and the issue tracker is acceptable, the Matrix chat room should be excluded. This decision was made to ensure the chat remains a safe space for discussing sensitive and evolving topics without the risk of incomplete thoughts being broadcasted broadly.

Learn more about the Diversity & Inclusion team.

Workstation / GNOME

This week, the Workstation / GNOME group prepared for the upcoming Fedora 45 release by organizing Blocker Review Meetings to evaluate blocker bugs and freeze exceptions. On the issue tracker, members discussed a proposal to add LiveFaceSwap Desktop to Fedora's third-party software repositories and reviewed a request to include the group's communication channels in this weekly report.

Additionally, the group continued discussions on the need to automatically update the appstream-data package to ensure modern software store GUIs like GNOME Software and KDE Discover have up-to-date metadata. A community member volunteered to look into the current manual data update process to help move the automation effort forward.

Contribution opportunities

• Review and vote on proposed blocker bugs and freeze exceptions for the Fedora 45 release using the blockerbugs app prior to the weekly review meetings.

Learn more about the Workstation / GNOME team.

KDE

During the week, the KDE SIG focused on refining the default Fedora KDE Plasma installation and resolving release blockers. A major effort is underway to reduce the default installation footprint by transitioning Akonadi's default backend from MySQL to SQLite. Additionally, the group is modernizing the default application set by swapping out the K3b optical mastering tool in favor of Fedora Media Writer.

The team also investigated and implemented a workaround for a Fedora Kinoite login bug triggered during OS rebases, securing the fix in time for the Fedora 44 Beta. Routine Fedora 45 Blocker Review meetings were scheduled to evaluate and vote on outstanding final blockers and freeze exceptions.

Decisions

• Initiated a transition to replace k3b with Fedora Media Writer as the default image writer in the desktop comps (issue #729).
• Merged a change to the akonadi-server package alternatives priorities so new installations default to SQLite, while safely preserving the MySQL backend for existing users to avoid disruption (issue #730).
• Implemented and deployed a systemd service workaround for missing /etc/shadow entries during Kinoite rebases to unblock the Fedora 44 Beta (issue #684).

Contribution opportunities

• Community members are encouraged to vote on proposed blockers and freeze exceptions in the blockerbugs app prior to the weekly Fedora 45 Blocker Review Meetings.
• Testing and feedback are needed for developing an automated migration path or user alert strategy for existing Akonadi MySQL users transitioning to SQLite (issue #730).
• Developers can contribute to the long-term structural fix for user provisioning in atomic desktops by helping the project move away from nss-altfiles (issue #684).

Learn more about the KDE team.

Server

The Server Working Group focused heavily on Fedora 45 release testing and advancing the Ansible support project this week. Testing of the F45 20261003 build yielded successful results across various installation methods, while a critical blocker involving the Server KVM image and initial-setup hanging on the serial console was diagnosed and resolved via a patch to the systemd service.

In addition, the group continued to refine its Ansible support strategy. Members are finalizing continuous integration for the fedoraserver.general Ansible collection and are preparing to package it for Fedora once published on Ansible Galaxy. The group also discussed outreach strategies for upcoming conferences, such as FOSDEM and the Ohio Linux Fest, and prepared for the upcoming F45 Blocker Review meetings.

Decisions

• Decided to restore the quiet-console.conf drop-in lines for initial-setup.service to resolve the Server KVM image boot issue on serial consoles (Ticket #216).
• Agreed to develop a "turnkey solution" to simplify Ansible usage for end-users, consisting of a core fedoraserver.general collection to be published on Ansible Galaxy and a secondary management wrapper package (Ticket #194).
• Decided that Fedora 45 RC testing must be divided among working group members and completed within 1–2 days of a test release's availability (Meeting 2026-09-30).
• Decided to follow the US schedule for the upcoming winter time switch for meeting times (Meeting 2026-09-30).

Contribution opportunities

• Emmanuel Seyman requested testing for the experimental Wildfly RPMs available in their Copr repository before submitting them to Fedora proper (Meeting 2026-09-30).
• The group is seeking volunteers to help test the upcoming Fedora 45 Release Candidates, specifically requesting assistance with the default partitioning and remote install tests (Meeting 2026-09-30).

Learn more about the Server team.

Infrastructure

The Infrastructure group focused heavily on system maintenance this week, successfully executing a major planned outage to apply package updates, perform firmware upgrades, enable SecureBoot on x86 bare-metal hosts, and migrate several backend databases (including Koji and Datanommer). The team also actively troubleshot various access and system issues, such as clarifying that hardware security keys (ed25519-sk) will fail against legacy RHEL 8 systems, and resolving a configuration error that caused 403 errors on www.fedoraproject.org due to aggressive anti-scraper rules.

Additionally, the Forgejo migration continues to make progress, with MultiVM runnerhost support implemented on the distgit-staging environment. The team is also beginning a formal investigation to document workflow impacts and tooling requirements ahead of Red Hat's planned Bugzilla sunset and the proposed move to Forgejo.

Decisions

• The team confirmed that hardware-backed SSH keys (id_ed25519_sk) will remain unsupported on pkgs.fedoraproject.org. The server runs RHEL 8, which lacks the required OpenSSH 8.2+ package, and the team decided not to risk uplifting the OS or maintaining a custom OpenSSH fork prior to the upcoming Forgejo migration.
• Scraper-blocking rules that inadvertently returned 403 errors on www.fedoraproject.org have been narrowed in scope to only protect the wiki. This ensures regular users routed by search engines can view the site normally, and the www alias will now redirect 301 to the apex domain.
• The sysadmin-eln group has been granted permissions to execute the elnbuildsync.yml Ansible playbook on batcave, empowering the ELN team to trigger deployments without requiring manual intervention from Infrastructure team members.

Learn more about the Infrastructure team.

Release Engineering

The Release Engineering team focused heavily on stabilizing Fedora 45 ahead of its release, holding multiple blocker review meetings to evaluate and vote on blocker bugs and freeze exceptions. Alongside release preparations, the team addressed several Fedora 46 Rawhide compose breakages, resolving issues related to SELinux policy mismatches during offline labeling, oversized images on aarch64, and missing packages in the f46 tag. Additionally, a new community discussion was opened proposing the preservation of meaningful, per-file modification times for Git-derived source packages (such as linux-firmware) to improve traceability for users.

Decisions

• Accepted as a Final Blocker: Bug 2541402 - systemd-imds-early-network.service fails at boot with AVC denials.
• Accepted as a Final Blocker: Bug 2537341 - oo7-portal not installed by default after upgrading to F45.
• Accepted as a Final Freeze Exception: Bug 2536815 - dnf command not available in kickstart, f45 netboot installer (rejected as a hard blocker).
• Accepted as a Final Freeze Exception: Bug 2530897 - F45 grub boot fails with "invalid magic number" when installed to FW RAID multiple times from the GTK installer.
• Added Fedora-Server-NetworkInstaller and Fedora-Everything-NetworkInstaller to the f46 tag to fix broken Rawhide composes.
• Processed non-responsive maintainers lkundrak and gui1ty, effectively orphaning their unmaintained packages.
• Blocked and retired the Charliecloud repository for F46 onward to prevent it from triggering FTBFS errors during mass rebuilds.

Contribution opportunities

• Maintainers and community members are invited to provide input on a proposal to preserve meaningful per-file mtimes for Git-derived sources (such as linux-firmware), specifically regarding implementation methods and whether to use Git author or committer dates.
• Release Engineering assessment and coordination is requested on the F46 Change: LMDB 1.0 transition ticket to plan side-tag merging and potential rollback procedures before F46 branching.

Learn more about the Release Engineering team.

Quality

The Quality team is heavily focused on Fedora 45 Final release validation and blocker bug reviews. Testing activities are in full swing, with the CoreOS test days concluding and the Anaconda installer features test days (covering WebUI, Remote WebUI, and Stratis support) currently running. Additionally, the team successfully exported the results for the KDE Plasma 6.7 test days and is preparing for upcoming test days focusing on Podman Conmon-v3 and GRUB EFI for Confidential Computing.

In addition to release preparations, the team contributed their workflow requirements for the upcoming Bugzilla sunset and proposed transition to Forgejo, highlighting critical needs like Bodhi integration, anonymous access, and cross-component search capabilities. There is also an ongoing community discussion regarding a proposal to preserve meaningful per-file modification timestamps (mtimes) for Git-derived sources, which could significantly improve the inspectability of packages like linux-firmware.

Decisions

• It was decided to downgrade rpmlint spelling errors to warnings rather than turning them off globally across all packages (Ticket #591).
• Accepted Bug 2541402 as a Final Blocker due to systemd-imds-early-network.service AVC denials, noting that disabling the service by default would be an acceptable resolution (Blocker Review).
• Rejected Bug 2538553 (Czech keyboard layouts) as a final blocker due to the high risk of regressions and because the behavior only triggers on custom configurations rather than the default installer path (Blocker Review).
• Rejected Bug 2536815 (dnf not available in kickstart environment) as a Final Blocker, but accepted it as a Freeze Exception (Blocker Review).
• The _check_install_source test will no longer look for /tmp/syslog on network installers following the migration to image-builder (Ticket #948).
• The Podman Conmon-v3 test day is postponed by one week to 2026-10-12 to allow time for adjustments to a Podman PR (Ticket #941).

Contribution opportunities

• Testers are encouraged to participate in the Anaconda installer test days to evaluate WebUI for Atomic desktops, Remote WebUI, and Stratis support.
• Community feedback is sought on the proposal to preserve Git-derived per-file mtimes in RPM packages.
• A reviewer is needed for a pull request to fmf-tests to update Azure consumer cloud test results to the wiki (requested during the Quality Meeting).
• Help is requested to manually test SAS controllers and disks for F45 or to collaborate with the Server SIG for future automated testing (Ticket #946).

Learn more about the Quality team.

Websites and Apps

The Websites and Apps team implemented a clearer visual distinction on the Fedora download pages to highlight release-blocking deliverables. Star icons are now displayed next to images that have passed basic functionality tests performed by the Quality team, helping users identify the most stable and recommended installation options.

Other activities this week included identifying outdated references to Zanata on the Flock Call for Proposals template which need to be removed to avoid unnecessary work for translators. The team also fielded infrastructure meeting reminders and greeted new contributors offering UI/UX and web development help in the Websites chat.

Decisions

• A design change is now live on the Fedora download pages adding a star icon and a "Learn More" footnote to all release-blocking deliverables to clarify which images have guaranteed testing from the Fedora Quality team.

Contribution opportunities

• Contributors can help clean up outdated CMS templates (such as old Zanata references in the Call for Proposals page) to prevent translators from doing unnecessary work on disabled or obsolete text.
• New contributors looking to help with redesigns, UI/UX, bug fixes, or documentation are encouraged to read the room details in the Fedora Websites chat to discover current website projects and needs.

Learn more about the Websites and Apps team.

Design

This week, the Design team focused on creating initial concepts and technical specifications for the new CDUX logo, which will feature a duck incorporating UI elements and the Bezier tool. The team also began planning visual assets for the upcoming F45 Virtual Release Party and committed to providing a higher-resolution SVG Fedora logo for the fedora-logos package. This fix will address pixelation issues on the GDM login screen that occur when fractional scaling is enabled in Fedora 41 and later.

In the Design Matrix chat, team members discussed logo approval for Microsoft Ignite stickers and exchanged ideas with GNOME engagement members regarding Penpot automations and AI-assisted workflows. Finally, congratulations are in order for Emma, who recently began a part-time Masters in Service Design!

Decisions

• The Design team is no longer taking Fedora Badge requests in their main ticket queue; these must now be logged directly in the badges queue, which is currently facing a lack of dedicated designers. (Ticket #86)
• The official EPEL Steering Committee badge design was approved by the committee, finalized, and successfully published to the badges system. (Ticket #60)
• The team approved the inclusion of their public Matrix chat data for the collection of these weekly reports. (Ticket #83)
• The team confirmed they have no workflow dependencies on Bugzilla and are completely unaffected by its upcoming sunset, as they exclusively use Forgejo. (Ticket #88)
• The upcoming CDUX logo will be designed using simple black line art and solid colors without gradients to guarantee easy CMYK color conversion and sticker production. (Meeting Notes)

Contribution opportunities

• Anyone in the Fedora community is welcome and encouraged to contribute sketches and visuals inspired by the mindmap for the upcoming F46 Wallpaper.
• The Fedora Community Operations team is seeking design support and visual assets (thumbnails, Matrix room icons, Restream backgrounds) for the Fedora Linux 45 Virtual Release Party happening on October 30, 2026.

Learn more about the Design team.

Docs

This week, the Docs team implemented important changes to standardize contribution workflows. Direct pushes to main and prod branches have been disabled across all docs/* repositories; all contributors must now use forks and pull requests to submit changes. The team is also testing a new real-time collaborative writing tool via a CryptPad instance hosted in CommuniShift.

Additionally, discussions are ongoing regarding structural improvements to the Docs site. This includes evaluating whether to merge Antora components so content from different SIGs can be combined seamlessly, and determining the best way to consolidate scattered multimedia documentation. Finally, the team opted into having the "This Week in Fedora" summary bot monitor their ticket trackers to boost the visibility of their work.

Decisions

• Direct pushing to main branches is now disabled across all docs/* repositories. Non-admin contributors must fork the repository and submit a pull request, which now requires at least one approval before merging.
• The team agreed to let this weekly report collect the entire Docs organization's ticket trackers rather than summarizing their Matrix alert chat room.

Contribution opportunities

• The team is seeking volunteers for the Fedora Docs Captains pilot program to act as documentation liaisons for SIGs like Kernel, Multimedia, and AI/ML.
• Contributors are needed to write detailed image descriptions (alt text) for screenshots in the Beginner's Guide to meet accessibility standards.
• Help is requested to review, categorize, and organize scattered multimedia documentation across Quick Docs into a unified section.
• The team is looking for someone to help configure Zabbix monitoring for OpenShift Docs site builds to automatically track and report failures.

Learn more about the Docs team.

Legal

This week, a question was raised on the legal mailing list regarding the licensing of the Slint UI Framework. A contributor is looking to package the software and asked for clarification on whether utilizing the framework solely under the GPL-3.0-only option of its multi-license scheme is acceptable for Fedora. Additionally, they sought input on how the project's inbound MIT-0 contribution license interacts with its outbound licensing options.

Contribution opportunities

• Legal experts and community members can contribute by replying to the licensing inquiry regarding the Slint UI Framework, specifically confirming the viability of using the GPL-3.0-only option for Fedora packaging and explaining the compatibility of its inbound MIT-0 contribution policy.

Learn more about the Legal team.

COPR

Pavel Raiskup announced a planned Fedora Copr outage scheduled for October 1, 2026, at 06:00 UTC, lasting approximately two hours. During this window, build queue processing was paused and the frontend/web UI was unavailable to accept new tasks, though DNF packages and repositories remained accessible.

The purpose of this downtime was to deploy the latest development versions of the copr-* packages to the infrastructure machines, tracked under infrastructure ticket #13597.

Decisions

• The Copr team scheduled a two-hour infrastructure outage on October 1, 2026, temporarily halting build queues and web UI access to deploy package updates.
• It was decided to keep the Copr download server online during the update so that hosted DNF packages and repositories remained continuously available to external users.

Learn more about the COPR team.

EPEL

The EPEL team discussed the potential sunset of Red Hat's Bugzilla instance and its impact on EPEL's workflows, noting a strong preference for a Fedora Bugzilla instance over Forgejo due to the operational need to transfer issues between components. Maintenance efforts are currently heavily focused on an upcoming Qt6 update in EPEL9 to proactively handle llvm22 changes before the RHEL 9.9 release, alongside various CVE fixes for djvulibre and ffmpeg.

The release engineering team is preparing automation playbooks for koschei minor mass branching and minor EOL processes. They are also actively tracking infrastructure changes for the upcoming EPEL 9.8 archive snapshot and the complex EPEL 10.2 retirement / EPEL 10.3 switch.

Decisions

• Due to a lack of maintainer response, proven packager privileges were used to merge a fix for CVE-2025-53367 in djvulibre.

Contribution opportunities

• A community member is seeking a sponsor or an existing packager to co-maintain and branch autossh for EPEL 10.
• Contributors are needed to bring mailman3 to EPEL 10 to assist Releng with moving mailman to RHEL 10.
• Help is requested to get the incus package into EPEL 10 following its 7.0.0 LTS release on Rawhide.
• Assistance is needed to backport a fix for an ffmpeg heap-buffer-overflow CVE in EPEL 10 (version 8.1).

Learn more about the EPEL team.

ELN

The ELN SIG held a brief meeting on September 29. The main topic of discussion was a large Architectural Decision Record (ADR) pull request focused on the unification of bootc and CoreOS. Contributors discussed how ELN is envisioned to fit into this new structure as a layer built upon one of the proposed flavors.

Learn more about the ELN team.

Atomic

The Atomic group met to review the first draft of an Architectural Decision Record (ADR 002) proposing a unified strategy for Fedora CoreOS and Atomic. The draft outlines a three-tier architecture (base, flavor, and product) and standardizes on Konflux for image building; it is currently open for community review and feedback.

On the issue tracker, significant attention was given to improving the experience for downstream consumers building derived OCI images. This included discussions on how to handle Fedora trademark compliance (Ticket #125) and exploring ways to publish OCI images without Fedora-specific packages (Ticket #132). Other notable activities included a proposal to ship smartmontools for disk health monitoring (Ticket #135), fixing systemd checks that break the composefs backend (Ticket #133), and addressing package versioning and compose bugs across Fedora 45 and Rawhide.

Decisions

• It was decided that official Atomic Desktops images cannot use generic package replacements because Fedora branding is required. To aid downstream users, the team will instead focus on simplifying the package swap process and writing proper rebranding documentation (Ticket #125).

Contribution opportunities

• Reviewers and Subject Matter Experts (SMEs) are requested to provide feedback on the draft ADRs for unifying Fedora CoreOS and Atomic.
• Help is needed to identify which GUI applications can be included to display SMART data for users across the various desktop environments.
• A contributor is requested to submit a Pull Request removing the ConditionPathExists=/run/ostree-booted condition from specific systemd unit files to fix compatibility with the composefs backend.

Learn more about the Atomic team.

CoreOS

The CoreOS team successfully wrapped up the Fedora 45 Test Week, reporting that the F45 release schedule is on track without any failing packages requiring retirement. In infrastructure and pipeline matters, several issues were resolved, including failing kola-azure jobs, an insecureAcceptAnything policy block causing upgrade failures, and Vim installation conflicts on testing-devel. The team is actively investigating a new SELinux denial related to systemd 262 that breaks cloud tests on F45/F46, and working around dead AWS regions that caused garbage-collection job failures.

During their weekly meeting, the group discussed allowing this weekly report to gather data. They opted to pause Matrix channel data collection for the bot until the Fedora Council finalizes a formal opt-in policy, choosing to rely on GitHub repositories and meeting logs in the meantime. Additionally, members agreed to consolidate legacy meetings to improve cross-team collaboration.

Decisions

• Merge the legacy CoreOS Wednesday meeting and the legacy bootc Tuesday meeting into a single meeting to encourage cross-pollination between the communities. (Meeting log)
• Hold off on allowing LLM bot data collection in the CoreOS Matrix room until the Fedora Council establishes a formal opt-in privacy policy. (Meeting log)

Learn more about the CoreOS team.

IoT

The Fedora IoT Working Group reviewed their release status, noting that the Fedora 45 Beta freeze is complete and the final freeze begins next week. Both stable and Rawhide composes are currently healthy, and contributors are conducting hardware upgrade and installation tests leading into the final freeze.

In addition to routine release management, the team opened investigations into moving toward device-specific ARM images using arm-image-builder, assessing the impact of recent DNF repository path changes on image builds, and establishing a VM-based testing workflow to make hardware testing more accessible. The group also agreed to collaborate with the Fedora RISC-V Working Group to enable IoT support for RISC-V boards.

Decisions

• Drop support for Fedora 42 and older releases; any tracker issues related to these versions will be closed. (Meeting Log)
• Investigate transitioning from generic images to device-specific ARM images via arm-image-builder and IoT Compose. (Issue #141)
• Assess the impact of the new DNF .repo path configuration on bootc and Bootable Image Builder (BIB) workflows. (Issue #140)

Contribution opportunities

• Help is needed to run Fedora 45 nightly tests on any available physical hardware (especially aarch64 devices or modern hardware with accelerators like Orin) to assist with the final freeze.
• Community members with spare cycles are encouraged to review the Fedora IoT issue tracker to help close or fix open bugs.
• Contributors interested in QA can assist in evaluating VM-based hardware testing strategies to better share the validation workload across the team.

Learn more about the IoT team.

ARM

The ARM mailing list received announcements for two Fedora 45 Blocker Review meetings. The first meeting was held on September 28 to review four proposed blockers for the Final release. The second meeting was scheduled for October 5 to evaluate two proposed blockers and two freeze exceptions.

Contribution opportunities

• Review and vote on proposed blockers and freeze exceptions for Fedora 45 via the blockerbugs app prior to the review meetings to help shorten the meeting durations.

Learn more about the ARM team.

Cloud

The Cloud group's recent activities focused on refining image configurations to maintain feature parity and security alignment with upstream changes. A new request asks to add the SUSPEND_SAFE_FPR guest OS feature to Google Cloud Platform (GCP) images, specifically those patched for a page_reporting suspend Use-After-Free vulnerability (CVE-2026-74481). Additionally, a proposal was made to include the google-noto-sans-mono-fonts package in Cloud images to ensure the console appearance remains consistent with other Fedora editions following the recent kmscon update.

Contribution opportunities

• Provide feedback or assist with adding the SUSPEND_SAFE_FPR tag to GCP images containing the CVE-2026-74481 patch.
• Discuss the potential inclusion of google-noto-sans-mono-fonts to ensure consistent console rendering across editions by participating in Issue #448.

Learn more about the Cloud team.

Hummingbird

This week, the Hummingbird community saw ongoing forum discussions following the cancellation of their September meeting. A community member expressed enthusiasm regarding the project's use of superintelligence (SI) and container technology for building packages and customizing bare-metal systems.

Several inquiries were raised during the discussion, particularly regarding whether Fedora users have public access to this SI and any associated costs. The participant also asked about the feasibility of using SI agents to generate, lint, and highly optimize bootable container images—such as pruning irrelevant firmware or unused packages—based on specific hardware descriptions.

Learn more about the Hummingbird team.

Kernel

The Fedora kernel team discussed a proposal to split perf out of the kernel packaging and build it as a standalone package. Proponents noted that a standalone build would reduce BuildRequires (such as Java) for the kernel, lower the barrier to entry for new contributors intimidated by the massive kernel.spec file, and help resolve inconsistencies with perf headers.

However, reviewers raised concerns about the overhead of maintaining two separate packages, the risk of breaking user expectations if the perf version no longer perfectly matches the shipped Fedora kernel, and the potential disruption to vanilla kernel COPR builds that currently catch upstream bugs early. The primary blocker for the proposal is alignment with RHEL.

Contribution opportunities

• Contributors interested in the proposal to split perf out of the kernel packaging are welcome to join the effort to draft and submit a Change Proposal for Fedora 46.
• Community members and maintainers (specifically perf upstream maintainers) are encouraged to help advocate for this packaging split within RHEL, as their buy-in is a strict prerequisite for the change.

Learn more about the Kernel team.

AI & ML

During the week of September 28 to October 4, 2026, the AI & ML group focused on two major themes: group identity evolution and documentation modernization. The team successfully formalized its evolution into the Fedora AI Working Group (WG), reflecting a broader scope that encompasses both technical hardware enablement and community stewardship of open AI best practices.

On the documentation front, the group merged new issue templates that introduce lightweight bug reporting, structured content proposals, and a mandatory AI assistance disclosure checkbox. Furthermore, an active proposal was opened to migrate comprehensive packaging workflows and AI reference material from the legacy Fedora Wiki to the modern Fedora Docs platform to improve discoverability and maintainability.

Decisions

• The AI/ML SIG officially evolved into the Fedora AI Working Group (WG). This rebranding affects the broader community, as Matrix channels, Forgejo repositories, and the documentation site are being updated to reflect the unified identity.
• The group adopted structured issue templates containing an AI assistance disclosure checkbox for its documentation site to ensure all external community contributions comply with the Fedora AI policy.

Contribution opportunities

• An active project to migrate AI/ML content to Fedora Docs needs help converting legacy Wiki markup, structuring pages, and setting up :page-alias: redirects for existing Quick Docs.
• Contributors with automation experience are needed to help develop a new Fedora Agent Skill for reviewing Fedora Docs components and content.
• Help is requested to write automated ingestion scripts that pull build and release statuses directly from Koji and dist-git to maintain dynamic package tracking tables.

Learn more about the AI & ML team.

RISC-V

This week, the RISC-V group celebrated the release of the Fedora 45 RISC-V Beta images. Extensive testing on physical hardware—including Jupiter, P550, K3, and Titan boards—showed that the new images work smoothly. The group also made major strides preparing for Fedora 46, bringing the RISC-V content set almost fully into sync with the primary Fedora repositories, with over 19,000 packages now up to date.

Community members have been actively patching several packages that currently fail to build on the architecture, such as gdl, cmake, os-autoinst, and vxl. Meanwhile, kernel development continues for the upcoming 7.3 kernel, alongside stability improvements for the Omni kernel on ESWIN and P550 boards. Discussions in the Fedora RISC-V chat room and the fortnightly meeting confirmed that development is progressing well with no major blockers.

Decisions

• Users upgrading to Fedora 45 via dnf will need to manually install the fedora-repos-omni repository. The team decided to document this manual step on the wiki to assist users.
• The group agreed that removing board-specific kernel patches (such as the VisionFive 2 PCIe patch from the non-omni kernel) should only occur during major release transitions (like F45 to F46) to avoid disrupting existing users mid-cycle.

Contribution opportunities

• Assistance is needed to submit pull requests for fixing cmake tests on RISC-V.
• The group is looking for contributors to help test and maintain python-torch on the riscv64 architecture.

Learn more about the RISC-V team.

NeuroFedora

NeuroFedora contributors are preparing updates for the hdmf-common-schema, python-hdmf, and python-pynwb packages. During this process, the team noted that the listed maintainer has not performed a build or update in four years. These packages avoided the standard inactive packager flags because the broader NeuroFedora team has been keeping them up to date in the interim. A contributor has reached out directly and plans to initiate the nonresponsive maintainer policy if there is no reply within a few days. Further details can be found in the NeuroFedora Matrix room.

Learn more about the NeuroFedora team.

Gaming

This week, the Gaming group discussed packaging nbsdgames, a collection of 21 terminal-based games. The upstream maintainer reached out to the SIG to suggest its inclusion, noting it is easy to build and depends only on ncurses.

A packaging attempt revealed a binary name conflict between one of the games and the existing sos package. This was quickly resolved by building the games with an upstream option that prefixes all binaries with "nb" (e.g., nbsos). Additionally, the upstream maintainer noted that the games have been dual-licensed under Apache 2.0 to simplify the review process. An initial RPM is currently being prepared for official review.

Decisions

• To resolve a binary name conflict with the sos package, the upcoming nbsdgames package will use an upstream build flag to prefix all game binaries with 'nb' (e.g., nbsos).
• An initial RPM for nbsdgames was created and will be submitted for official Fedora package review.

Contribution opportunities

• Community members are encouraged to help review the upcoming package submission for nbsdgames once it is officially submitted.

Learn more about the Gaming team.

Perl

This week, the Perl group focused on routine package updates and minor configuration adjustments across several repositories. Maintainer Jitka Plesnikova successfully opened and merged pull requests to bump perl-Imager to version 1.037 and perl-DBI to version 1.654. Additionally, a change to the default fixed-width font in perl-podlators (switching from CW to CR) was implemented and merged into the project.

Decisions

• Merged a pull request to update perl-Imager to version 1.037 (Source).
• Merged a pull request changing the default fixed-width font from CW to CR in perl-podlators (Source).
• Merged a pull request to update perl-DBI to version 1.654 (Source).

Learn more about the Perl team.

Python

Miro Hrončok announced a plan to retire pypy3.10 from Fedora 46 and onwards, following the successful packaging of pypy3.12 and the cessation of upstream releases for pypy3.10.

To avoid disruptive surprises for existing contributors and users, pypy3.10 will be retained in Fedora 45 due to the proximity to the final freeze.

Decisions

• pypy3.10 will be retired from Fedora 46+ because upstream has stopped making releases and pypy3.12 is now available.
• pypy3.10 will remain in Fedora 45 since the release is very close to the final freeze.

Contribution opportunities

• Community members are asked to speak up and provide feedback if they have a compelling reason to keep pypy3.10 in Fedora 46+.

Learn more about the Python team.

Other Discussions

• In EPEL, ELN and Fedora packaging requirements, Jef Spaleta sparked a conversation about whether packages in the EPEL and ELN namespaces strictly adhere to Fedora packaging guidelines, which clarified that EPEL-only packages still must pass standard Fedora package reviews.
• A discussion regarding Bodhi: require_bugs and require_testcases have never been enforced - should they be? resulted in a consensus that previously ignored flags should default to off, and existing updates must be mass-edited to false before enforcing gating rules.
• Priscila Gutierres posted a Bioinformatics SIG Proposal to package essential genetics and computational biology tools, leading to cross-collaboration talks with the NeuroFedora SIG on the devel list.
• Christopher noted that GMail will remove ability to send email from @fedoraproject.org addresses soon, prompting contributors to seek alternative SMTP solutions and email clients for interacting with mailing lists.
• Miroslav Suchý asked contributors to Donate 1 minute of your time to test upgrades from F44 to F45 using an assumption-less dry run to preemptively catch and report package dependency issues.
• Gordon Messmer inquired about How can I contact the crypto team? to add AWS s2n-tls and AWS-LC; the thread detailed Fedora's crypto-policy constraints and concerns regarding AWS-LC's configuration format.
• Gordon Messmer also asked Would your package be easier to build if you could select specific releases of dependencies?, proposing upstream-release tracking branches in dist-git to build complex apps like vLLM as containers without hindering Rawhide maintenance.
• While coordinating an update of libxml2 and mini mass rebuild for F45, Zbigniew Jędrzejewski-Szmek prompted a side-debate over the etiquette of committing directly to branched package repositories without maintainer consultation.
• Julian Sikorski started a thread on the NTFS drivers situation, concluding that user-space tools and guestfs should continue relying on the mature ntfs-3g driver rather than the newer, less stable in-kernel ntfs3 driver.
• Several users reported Problems with https://koji.fedoraproject.org/ leading to 403 errors, which Kevin Fenzi attributed to temporary IP bans designed to block aggressive data scrapers hitting expensive endpoints.
• Other discussions included a proposal to pass --noclean to rpmbuild in Mock, a search for help for the Potentially non-responsive maintainer for julia, an RFC: splitting perf out of the kernel packaging, announcements for Fedora 45 RISC-V (non-official) Beta images and a Wiki resource for Fedora RISC-V + KVM, a scheduled Fedora Copr Outage on the buildsys list, the upcoming Fedora 45 Blocker Review Meeting, a warning about Package builds / updates accidentally missing from Fedora 45(+), and a request for IBus in update testing on the i18n list.

Package Orphaning

• Jakub Martisko gave a heads up about Deprecating and later Orphaning Atlas package (including the subpackages) due to upstream inactivity since 2018.
• Ben Beasley announced he is Orphaning python-fastapi and related packages due to the mounting maintenance burden caused by new opentelemetry dependencies.

Package Updates

• Yann Collette shared Some news about the Audinux activity for September, highlighting a successful F45 beta build, 16 new packages, and 336 updates.
• Pavel Raiskup announced the release of Mock v6.9 (cross-posted on the buildsys list), which introduces an unconditional --noclean flag to skip the obsolete %clean section during RPM builds.

All contribution opportunities

There are numerous highly accessible opportunities for community members to contribute to Quality Assurance, testing, and feedback, even without being part of a specific Special Interest Group (SIG). Anyone can help shorten review meetings by voting on proposed blocker bugs and freeze exceptions for Workstation, KDE, and ARM. Hands-on testers are needed to evaluate Anaconda F45 features, run IoT nightly tests, perform Fedora 44 to 45 upgrade dry-runs, and validate F45 Server Release Candidates. If you have specific hardware, testing is requested for SAS controllers and the new RISC-V Beta images. Furthermore, the broader community is encouraged to weigh in on structural proposals, such as keeping pypy3.10 in Fedora 46+, preserving Git-derived mtimes in RPMs, and resolving a GPL/MIT-0 licensing inquiry regarding the Slint UI Framework.

For contributors with skills in writing, design, and event coordination, there are excellent entry-level tasks available. Writers can help meet accessibility standards by authoring image alt-text for the Beginner's Guide, organizing scattered multimedia documentation, or structuring migrated AI/ML Wiki content. The Docs team is also recruiting Fedora Docs Captains to act as liaisons and seeks feedback on building a "Contribution" section for their homepage. Designers are invited to contribute visual assets for the F45 Virtual Release Party, sketch ideas for the F46 Wallpaper, or tackle UI/UX projects in the Websites chat. On the community front, Mindshare is seeking moderators, and open-source event organizers in the Philippines are looking to partner with local Fedora Ambassadors.

Contributors with backgrounds in packaging, development, and automation can assist several teams with critical maintenance and coding tasks. The EPEL group urgently needs packagers to branch autossh, bring mailman3 and incus to EPEL 10, and patch an ffmpeg heap-buffer-overflow CVE. Developers can also help maintain python-torch on RISC-V, rescue the julia package from retirement, or review the nbsdgames submission. Those with DevOps or automation experience are encouraged to update apps.fedoraproject.org, configure Zabbix monitoring for OpenShift Docs, write automated ingestion scripts for AI/ML tracking, or submit pull requests fixing systemd units for Atomic desktops.