Hello travelers!

Loadouts for Genshin Impact v0.1.20 is OUT NOW with the addition of support for recently released characters like Vesna and Vodyanitsa and for recently released weapons like Beyond the Chrysalis, Breezeborne Refrain, Hymn of the Maelstrom, New Bough, Silver Light and Winter's Heavy Heart from Genshin Impact v7.1 Phase 2. Take this FREE and OPEN SOURCE application for a spin using the links below to manage the custom equipment of artifacts and weapons for the playable characters.

Resources

• Loadouts for Genshin Impact - GitHub
• Loadouts for Genshin Impact - PyPI
• Loadouts for Genshin Impact v0.1.20
  • Executable for GNU/Linux distributions
  • Executable for Microsoft Windows

Installation

Besides its availability as a repository package on PyPI and as an archived binary on PyInstaller, Loadouts for Genshin Impact is now available as an installable package on Fedora Linux. Travelers using Fedora Linux 42 and above can install the package on their operating system by executing the following command.

$ sudo dnf install gi-loadouts --assumeyes --setopt=install_weak_deps=False

Changelog

• Automated dependency updates for GI Loadouts by @renovate[bot] in #676
• Automated dependency updates for GI Loadouts by @renovate[bot] in #683
• Automated dependency updates for GI Loadouts by @renovate[bot] in #693
• Automated dependency updates for GI Loadouts by @renovate[bot] in #695
• Add additional description in weapon Sapwood Blade by @gridhead in #677
• Add additional description in weapon Moonpiercer by @gridhead in #678
• Add additional description in weapon Forest Regalia by @gridhead in #679
• Correct the alphabetical order of workspace artifacts listing by @gridhead in #680
• Introduce the recently added character Vesna to the roster by @gridhead in #691
• Introduce the recently added character Vodyanitsa to the roster by @gridhead in #692
• Automated dependency updates for GI Loadouts by @renovate[bot] in #698
• Automated dependency updates for GI Loadouts by @renovate[bot] in #708
• Update dependency python to 3.13 || 3.14 || 3.15 by @renovate[bot] in #707
• Update Python to >=3.12,<3.16 by @renovate[bot] in #709
• Replace CharName StrEnum with __charmaps__ dict by @gridhead in #694
• Add the recently added weapon Breezeborne Refrain to the GI Loadouts roster by @sdglitched in #700
• Add the recently added weapon Winter's Heavy Heart to the GI Loadouts roster by @sdglitched in #701
• Add the recently added weapon Silver Light to the GI Loadouts roster by @sdglitched in #702
• Add the recently added weapon New Bough to the GI Loadouts roster by @sdglitched in #703
• Add the recently added weapon Hymn of the Maelstrom to the GI Loadouts roster by @sdglitched in #704
• Add the recently added weapon Beyond the Chrysalis to the GI Loadouts roster by @sdglitched in #705
• Reconfigure ascension asset for Cashflow Supervision by @sdglitched in #706
• Stage the release v0.1.20 for Genshin Impact v7.1 Phase 2 by @gridhead in #710

Characters

Two characters have debuted in this version release.

Vesna

Vesna is a sword-wielding Anemo character of five-star quality.

Vodyanitsa

Vodyanitsa is a catalyst-wielding Hydro character of five-star quality.

Weapons

Six weapons have debuted in this version release.

Beyond the Chrysalis

Dance of Wings Unbound - Scales on Crit DMG.

Breezeborne Refrain

Viper's Ballad - Scales on Crit Rate.

Hymn of the Maelstrom

Rondo of Slumber - Scales on HP%.

New Bough

Wildgrowth - Scales on Crit DMG.

Silver Light

Radiance on the Water - Scales on ATK%.

Winter's Heavy Heart

Secrets of Frost - Scales on Crit DMG.

Appeal

While allowing you to experiment with various builds and share them for later, Loadouts for Genshin Impact lets you take calculated risks by showing you the potential of your characters with certain artifacts and weapons equipped that you might not even own. Loadouts for Genshin Impact has been and always will be a free and open source software project, and we are committed to delivering a quality experience with every release we make.

Disclaimer

With an extensive suite of over 1626 diverse functionality tests and impeccable 100% source code coverage, we proudly invite auditors and analysts from MiHoYo and other organizations to review our free and open source codebase. This thorough transparency underscores our unwavering commitment to maintaining the fairness and integrity of the game.

The users of this ecosystem application can have complete confidence that their accounts are safe from warnings, suspensions or terminations when using this project. The ecosystem application ensures complete compliance with the terms of services and the regulations regarding third-party software established by MiHoYo for Genshin Impact.

All rights to Genshin Impact assets used in this project are reserved by MiHoYo Ltd. and Cognosphere Pte., Ltd. Other properties belong to their respective owners.

23 Oct 2026 6:30pm GMT

RPMs of PHP version 8.5.12 are available in the remi-modular repository for Fedora ≥ 43 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.4.27 are available in the remi-modular repository for Fedora ≥ 43 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.3.36 are available in the remi-modular repository for Fedora ≥ 43 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

RPMs of PHP version 8.2.35 are available in the remi-modular repository for Fedora ≥ 43 and Enterprise Linux ≥ 8 (RHEL, Alma, CentOS, Rocky...).

ℹ️ These versions are also available as Software Collections in the remi-safe repository.

ℹ️ The packages are available for x86_64 and aarch64.

⚠️ PHP version 8.1 has reached its end of life and is no longer maintained by the PHP project.

🛡️ These Versions fix 2 critical security bugs (CVE-2026-109618, CVE-2026-109619), so the update is strongly recommended.

Version announcements:

• PHP 8.5.12 Release Annoucement
• PHP 8.4.27 Release Annoucement
• PHP 8.3.36 Release Annoucement
• PHP 8.2.35 Release Annoucement

ℹ️ Installation: Use the Configuration Wizard and choose your version and installation mode.

Replacement of default PHP by version 8.5 installation (simplest):

On Enterprise Linux (dnf 4)

dnf module switch-to php:remi-8.5/common

On Fedora (dnf 5)

dnf module reset php
dnf module enable php:remi-8.5
dnf update

Parallel installation of version 8.5 as Software Collection

yum install php85

Replacement of default PHP by version 8.4 installation (simplest):

On Enterprise Linux (dnf 4)

dnf module switch-to php:remi-8.4/common

On Fedora (dnf 5)

dnf module reset php
dnf module enable php:remi-8.4
dnf update

Parallel installation of version 8.4 as Software Collection

yum install php84

And soon in the official updates (thanks to Jitka Plesnik for the updates):

• Fedora Rawhide now has PHP version 8.5.121
• Fedora 45 - PHP 8.5.12
• Fedora 44 - PHP 8.5.12
• Fedora 43 - PHP 8.4.27

⚠️ To be noticed :

• EL-10 RPMs are built using RHEL-10.2
• EL-9 RPMs are built using RHEL-9.8
• EL-8 RPMs are built using RHEL-8.10
• intl extension now uses libicu74 (version 74.2)
• mbstring extension (EL builds) now uses oniguruma5php (version 6.9.10, instead of the outdated system library)
• oci8 extension now uses the RPM of Oracle Instant Client version 23.26 on x86_64 and aarch64
• A lot of extensions are also available; see the PHP extensions RPM status (from PECL and other sources) page

ℹ️ Information:

• Migrating from PHP 8.2.x to PHP 8.3.x
• Migrating from PHP 8.3.x to PHP 8.4.x
• Migrating from PHP 8.4.x to PHP 8.5.x

Base packages (php)

Software Collections (php83 / php84 / php85)

22 Oct 2026 12:58pm GMT

22 Oct 2026 7:22am GMT

21 Oct 2026 6:22am GMT

20 Oct 2026 7:02am GMT

19 Oct 2026 9:00am GMT

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.

19 Oct 2026 8:46am GMT

For decades, the Linux virtual console has relied on the kernel fbcon driver, to draw the framebuffer, to manage fonts, and to handle keyboard layout. Starting with Fedora 45, we're switching to a userspace utility called kmscon. Depending on your usage of virtual console, this may impact your workflow.

If you're not a developer or a system administrator, chances you probably never heard about fbcon or virtual terminal (VT), in this case you're probably not impacted.

You can still read the rest if you're curious about minimal text interfaces, and maybe you'll start using it.

How to use the virtual console

Most of the graphic sessions runs in tty1 or tty2. So press Ctrl+Alt+F3 to switch to tty3, and you will get a login prompt. This is the virtual console we're talking about. To go back to your graphic session, press Ctrl+Alt+F1 (or F2 or F7 depending on your desktop environment).

Why is kmscon replacing fbcon ?

The legacy fbcon driver runs directly in the kernel space, and has significant drawbacks:

• Security: Each bug in fbcon can be exploited in the kernel directly, and each crash is a kernel panic.
• Keyboard layout: The keyboard layouts supported by the kernel are different from what userspace is using. So when you choose the keyboard layout in the anaconda installer, it tries to find the kernel layout that is as close as possible to the chosen layout.
• Fonts: fbcon only uses bitmap fonts, which look small on a High DPI display, and you can't resize them at runtime. They have limited unicode support. Kmscon can use freetype, and render all monospace fonts.
• Scrolling: fbcon does not support scrolling anymore, due to a CVE.
• Mouse: fbcon does not have mouse support, it can be added with gpm, but is a bit clumsy. Kmscon uses a transparent hardware cursor when available, and has basic mouse support.
• Fbdev: fbcon relies on the old fbdev interface, but all GPU drivers are now using drm. Switching to kmscon allows dropping the fbdev emulation layer in the kernel.

What this will change for users and administrators ?

• Kmscon uses pseudo-tty (pts) devices. So when you run tty it returns /dev/pts/0 instead of /dev/tty1, like when you use a graphic terminal. So you will need to update all scripts or configuration that use this information.
• Kmscon uses the exclusive drm interface to the GPU to draw the terminal. If you want to run a graphic session or a program that wants to use the GPU, it won't work like it used to with fbcon. The reason is that fbcon runs in the kernel and can let any userspace application take the GPU. Kmscon can't do that, so you have to tell it to release the GPU. This is done with a script called kmscon-launch-gui. For example, to start a graphic session you can run
  kmscon-launch-gui kmscube -c 100
  or
  kmscon-launch-gui startx
• Kernel messages: By default the kernel error/warning messages are visible in tty1. It can be annoying when it mixes with what you are typing. You can read the messages with dmesg -w, or have a dedicated tty that runs
  kmscon --vt=%I --no-switchvt --oneshot --login -- dmesg -w
• Kernel fonts: The setfont command has no effect on kmscon. Kmscon uses the built-in unifont or freetype if it's available. You can read below how to configure it. kmscon can also use psf fonts, if you want the exact same looking as fbcon.
• Keyboard layout: The loadkeys command has no effect on kmscon. Instead, kmscon listens to localectl dbus, and updates the keyboard layout accordingly. So, to change layout, run
  localectl set-keymap us
• Kmscon replaces the default console in F45, for tty1-6. If you want to keep a tty using fbcon, just in case, you can run
  sudo systemctl mask kmsconvt@tty5 && sudo systemctl enable --now getty@tty5
  Then pressing Ctrl+Alt+F5 switches to your good old fbcon console.

Default kmscon shortcuts

• Zoom in: Ctrl++, Ctrl+WheelUp
• Zoom out: Ctr+-, Ctl+WheelDown
• Rotate the terminal: Super++, Super+-
• Scroll up: Shift+UpArrow, Shift+PageUp, Mouse Wheel Up
• Scroll down: Shift+DownArrow, Shift+PageDown, Mouse Wheel Down
• Copy/paste: select with the mouse, or select a word with double click, and MiddleClick to paste
• Switch to ttyX: Ctrl+Alt+FX
• Restart kmscon on ttyX: sudo systemctl restart kmsconvt@ttyX
• To know on which VT you are using, echo $XDG_VTNR

How does it look ?

Previous experience, Fedora 45 with fbcon:

Fedora 45 with kmscon (unifont)

Fedora 45 with kmscon (freetype) and some customization (fish, Hack Nerd Font)

How to configure kmscon the way you like

Plugins

kmscon is split into multiple subpackages, so you have a minimal installation without graphic/font dependencies for servers, and optional packages for more features.

• kmscon: main package, contains the unifont font, for good unicode support without additional dependencies.
• kmscon-freetype: Use the freetype library to render the fonts.
• kmscon-pango: Uses the pango library to render the fonts, it is deprecated in favor of kmscon-freetype.
• kmscon-gl: This is an opengl renderer. This might be faster but also a bit blurry. You need to add hwaccel to your configuration file to actually use it.

Configuration file

The configuration file for kmscon is /etc/kmscon/kmscon.conf
you can copy the example with this command:
sudo cp /etc/kmscon/kmscon.conf.example /etc/kmscon/kmscon.conf

Here are the most common options to change:

verbose: enable more logs, if you have issues with kmscon. To get the logs, use
journalctl -u kmsconvt*

font-engine: defaults to freetype (if available) or unifont (fallback). You can also use pango, or psf (the format used by the kernel fonts)

font-name: The name of the font (for pango, freetype, and psf). As kmscon runs as root, the font must be installed in /usr/share/fonts, not in your home directory. You can find the exact name to use with fc-list. You can install Cascadia fonts, that are good for non-latin languages with
sudo dnf install cascadia-fonts-all
If you want fancy icons, Nerd fonts are good, but not available in the default Fedora repository. For psf font, font-name is the path to the font file.

font-size: The font height in pixels. By default kmscon tries to scale the font to have about 120×40 characters.

multi-monitor: multi-monitor configuration, the terminal is the same on all monitor. The default is scaled which will scale the font to avoid too much black border. Other options are clone, which will center the terminal on each monitor, and largest which will only use the largest monitor.

dpms-timeout: The timeout (in second) after which the monitor will be turned off. default to 600 (10 minutes). 0 means disabled.

no-mouse: This disable the mouse support. It can be useful to disable touchpad on some laptops.

palette: Change the default color palette for your terminal. You can define each color if none of the provided default palette suits you.

Conclusion

We hope you will enjoy using kmscon in Fedora 45. You may use it occasionally, or use it as your main session for some specific usage, like Veronica Explains for a writerdeck https://www.youtube.com/watch?v=E7vFdy4BEAY.

If you encounter any bugs, have feature ideas, or want to contribute to development, the upstream repository is at https://github.com/kmscon/kmscon.

19 Oct 2026 8:00am GMT

19 Oct 2026 12:00am GMT

It's October, and you know what that means…Its Hallow…. no… its the start of curling season!!!!!!!!!

Jef, what does this have to do with the scope of this blog? Well at the start of curling season, back in Alaska I'd always get together with my other sort of technology nerdy friend Jon and we'd nerdsnipe each other. We'd talk about cool little curling use case technology projects we'd like to try to build. I'm in the headspace right now thinking of small silly curling projects I could start ( I'm not promising to finish them) and in doing so learn more about the local language model as a technology.

Now the obvious thing to do isn't even really LLM relevant, its vision machine learning. I've sort of already explored that topic when I was learning about machine vision so it's not an interesting problem space for me right now. But if you want to know sort of the state of the art of DIY curling rock detection, check out the codetrick blog series. If I'm reading the blog correctly he's making use of a variety of tools licensed under a mix AGPL BSD and Creative Commons. If you are interested in visual machine learning and not "chatbot" style LLMs, it's a really good read as a blog series.

I however am currently interested in learning LLMs, so I'm trying to figure out some curling related silliness that will let me explore the LLM inference technologies I can run locally. I've thought up some vibe coding projects that I can hopefully build a prompt for and compare the outputs of different models with. But I'm also interested to see if I can do any interesting boutique small language training with the small iron I have sitting under my desk. Can I describe curling games in a compact "language" similar to how chess games (hey they call curling chess on ice) and train a curling strategy bot and have it call strategy during a real game? I don't expect it to be good. In fact I definitely want it to be not good…because it'll be funnier. But I do want to understand the training process first hand and this fits my idiom.

What I don't know how to do is create enough real world training material to sufficiently train such a thing. How many different curling games do I need to describe in a compact language of my own design? Can I simulate games using a simplistic Markov process and train with that? Can I train from real games? And how would I actually automate the transcript of games into my language? Which brings me back to the rock detection blog series I pointed out earlier. If I could point that vision system not at live games, but at the video recordings on youtube of all the livestream cameras from clubs that livestream their leagues and events and have it provide compact language descriptions of the evolution of the games… I might have a lot of low quality training data…to create my low quality strategy bot..and I can have a ton of fun with that during the wacky rules social spiel later in the season.

Anyways… like I said, it's that time of year when I think about stuff like this. First curling game of the season is Monday.

18 Oct 2026 1:02pm GMT

18 Oct 2026 12:00am GMT

Hello again to any readers out there. Its been a bit.

Last week I was out going to a concert ( rush, they were great! ) and next week I am going to be out again ( visiting friends in New Mexico ). So, today, lets go over a few things from the last two weeks and look ahead to next week.

17 Oct 2026 6:52pm GMT

Building zellij

Just a small one for myself (and anyone else looking to build the zellij terminal multiplexer on Fedora 44).

During the build of zellij, cargo will try to build openssl-sys. I always end up adding the required operating system packages one by one in a repeating trial and error to make the build work. So for the next time I (or someone else) runs into this:

sudo dnf install openssl-devel perl-Time-Piece perl-File-Copy \ 
    perl-File-Compare perl-IPC-Cmd perl-FindBin

Then cargo build zellij should just work. Enjoy ;-)

17 Oct 2026 2:34pm GMT

Fedora Linux 45 is almost here! Developers, packagers, and quality assurance engineers are hard at work putting the remaining polish on Fedora 45, which means it's time for our Global Virtual Release Party! It is almost time to celebrate! If all goes according to plan, we will celebrate Fedora 45 just after its actual final release.

To mark the occasion, we are hosting the Fedora Linux 45 Virtual Release Party on Friday, October 30, 2026.

Regardless of the final calendar date of any Fedora Linux release, every release represents months of hard work, testing, and collaboration from our global community. Whether you are a long-time package maintainer, a dedicated documentation writer, a creative graphic artist, or a brand-new user, this release belongs to you.

Join us for a half-day of live sessions, recorded deep-dives, and community socialization. We're busy filling the upcoming schedule with updates from the Fedora Project Leader and behind-the-scenes looks at new features.

How to Attend

The event is 100% free and open to everyone, but registration is required to access the virtual venue. We will continue using Element, our chat communication platform, as the virtual venue for the Global Virtual Release Parties. Thanks Element & Matrix.org for providing us the great tools to bring our global community together!

Register for the Fedora Linux 45 Release Party live event on Matrix!

See you there!

Don't miss out on the chance to connect with the people who build Fedora. Grab your ticket, share the link with your friends, and get ready to celebrate Fedora Linux 45.

16 Oct 2026 4:06pm GMT

15 Oct 2026 10:00pm GMT

15 Oct 2026 8:23pm GMT