Fedora Community Blog

News and updates for and about the Fedora Project community that develops, supports, and promotes Fedora. For more information, and to download the Fedora OS head to Get Fedora. For general news about the Fedora OS, check out the Fedora Magazine

Community Update – Week 9, 2026

February 27, 2026 / jnsamyak / Comments Off

This is a report created by CLE Team, which is a team containing community members working in various Fedora groups for example Infrastructure, Release Engineering, Quality etc. This team is also moving forward some initiatives inside Fedora project.

Week: 20 Feb – 27 Feb 2026

Community Update – Week 8 2026

February 20, 2026 / lenkaseg / Comments Off

Week: 16 Feb – 20 Feb 2026

Fedora Infrastructure

This team is taking care of day to day business regarding Fedora Infrastructure.
It’s responsible for services running in Fedora infrastructure.
Ticket tracker

[GSoC Project Idea 2026] Revamp Fedora Badges project with modern fullstack architecture and dedicated MCP support [Ticket] [Followup]
[Infra] Added package and installed size to package metadata [Review] [Lint]
[Infra] Improve vagrant setup instructions and add container-based setup [Followup A] [Followup B]
Migration of pagure.io repositories to forge.fedoraproject.org continues (9 more repositories migrated)
Resolved authentication issues with wordpress instances (thanks to misc)
Fixed database connection issues on Dist-Git
Dep updates and CI fixes for our apps in Github
Worked on the port of bugzilla2fedmsg to Kafka (since the UMB deprecation), deployed it to staging, asked RHIT for firewall ports.

CentOS Infra including CentOS CI

This team is taking care of day to day business regarding CentOS Infrastructure and CentOS Stream Infrastructure.
It’s responsible for services running in CentOS Infratrusture and CentOS Stream.
CentOS ticket tracker
CentOS Stream ticket tracker

Release Engineering

This team is taking care of day to day business regarding Fedora releases.
It’s responsible for releases, retirement process of packages and package builds.
Ticket tracker

Fedora 44 Beta Freeze is now in effect.

RISC-V

This is the summary of the work done regarding the RISC-V architecture in Fedora.

(Not a lot to report this week, besides the routine on-going work.)
Started a discussion with the RISC-V team about RHEL builders for Konflux. (This is not about general Konflux support, that’s out of scope)
Continued to investigate Fedora 44 build failures and all that entails — working with relevant upstream maintainers to get changes reviewed, merged, etc.
Sorted out a build-timeout issue with Copr upstream. (Jason Montleon is currently used to build some board-specific kernels.)

QE

This team is taking care of quality of Fedora. Maintaining CI, organizing test days
and keeping an eye on overall quality of Fedora releases.

TestDays App was updated in production.
Anubis no longer breaks actions in Forge thanks to our debugging (and Infra fixing it, of course).
Blockerbugs meetings and the whole blocker review process has started since this week.
Ran test days: Grub OOM fix, GNOME 50

Forgejo

This team is working on introduction of https://forge.fedoraproject.org to Fedora
and migration of repositories from pagure.io.

Spike of zabbix installation for ansible-role-forgejo-runner researched
Forge image build and versioning fully automated
Runners updated to use image version 12
More migrations from pagure and troubleshooting
Private Issues: Fixed tests, tied up loose ends and consolidated feature branch.
Packit team got access to staging distgit deployment
Create new organisation and namespace on Fedora Forge for Fedora Join [Followup] [Namespace]

UX

This team is working on improving User experience. Providing artwork, user experience,
usability, and general design services to the Fedora project

CLE logo complete!
F45 wallpaper mindmap session took place. Mindmap created can be found here.
Continuing Forgejo migration.

If you have any questions or feedback, please respond to this report or contact us on #admin:fedoraproject.org channel on matrix.

Master Podman 5.8: Join Fedora Test Week

February 19, 2026 / Petr Sklenar / Comments Off

Want to learn the latest container tech? From February 27 to March 6, 2026, you can join the Podman 5.8 Test Day. It is the perfect time to explore new features and see how the future of Fedora is built.

Community Update – Week 07 2026

February 13, 2026 / zlopez / Comments Off

Week: 09 – 13 February 2026

Community Update – Week 6

February 6, 2026 / lenkaseg / 0 Comments

Week: 02 Feb – 05 Feb 2026

Fedora Design Team © CC BY-SA 4.0

Flock CFP Extended to February 8

February 4, 2026 / Shaun McCance / 0 Comments

The deadline for the Flock 2026 CFP has been extended to February 8.

We are returning to the heart of Europe (June 14–16) to define the next era of our operating system. Whether you are a kernel hacker, a community organizer, or an emerging local-first AI enthusiast, Flock is where the roadmap for the next year in Fedora gets written.

If you haven’t submitted yet, here is why you should.

Why Submit to the Flock 2026 CFP?

This year isn’t just about maintenance; it is about architecture. As we look toward Fedora Linux 45 and 46, we are also laying the upstream foundation for Enterprise Linux 11. This includes RHEL 11, CentOS Stream 11, EPEL 11, and the downstream rebuilder ecosystem around the projects. The conversations happening in Prague will play a part in the next decade of modern Linux enterprise computing.

To guide the schedule, we are looking for submissions across our Four Foundations:

1. 🚀 Freedom (The Open Frontier)

How are we pushing the boundaries of what Open Source can do? We are looking for Flock 2026 CFP submissions covering:

Open Source AI: PyTorch, vLLM, and the AI supply chain.
RISC-V: Enabling Fedora on the next generation of open silicon.
Open Hardware: Drivers, firmware, and board support. GPU enablement?

2. 🤝 Friends (Our Fedora Story)

Code is important, but community is critical. We need sessions that focus on the human element:

Mentorship: Case studies on moving contributors from “Lurker” to “Leader.”
Inclusion: Strategies for building a more globally-inclusive project.
Community Ops: The logistics and operations of running a massive global project.

3. ⚙️ Features (Engineering Core)

The “Nitty-Gritty” of the distribution. If you work on the tools that build the OS every six months, we want you on stage:

Release Engineering: Improvements to Dist-git, packager tools ecosystem, and the build pipeline. Distribution security. Konflux?
Quality Assurance: Automated testing and CI/CD workflows.
Packaging: Best practices for RPM, Flatpak, and OCI containers.

4. 🔮 First (Blueprint for the Future)

Fedora is “First.” This track is for the visionaries:

Strategy: What does Fedora look like in 2028?
Downstream Alignment: How upstream changes flow downstream.
New Spins: Atomic Desktops, Cloud Native innovations, and new Editions.

Desktop Test Days: A week for KDE and another for GNOME

February 2, 2026 / Petr Sklenar / 1 Comment

Desktop Test Days: A week for KDE and another for GNOME

Two Test Days are planned for upcoming desktop releases: KDE Plasma 6.6 on 2026-02-02 and GNOME 50 on 2026-02-11.

Join the KDE Plasma 6.6 Test Day on February 2nd to help us refine the latest Plasma features: https://fedoraproject.org/wiki/Test_Day:2026-02-02_KDE_Plasma_6.6

Help polish the next generation of the GNOME desktop during the GNOME 50 Test Day on February 11th: https://fedoraproject.org/wiki/Test_Day:2026-02-11_GNOME_50_Desktop

You can contribute to a stable Fedora release by testing these new environments and reporting your results.

Community Update – Week 05 2026

January 30, 2026 / zlopez / 0 Comments

Week: 26 – 30 January 2026

Packit as Fedora dist-git CI: final phase

January 27, 2026 / Laura Barcziová / 3 Comments

Hello Fedora Community,

We are back with the final update on the Packit as Fedora dist-git CI change proposal. Our journey to transition Fedora dist-git CI to a Packit-based solution is entering its concluding stage. This final phase marks the transition of Packit-driven CI from an opt-in feature to the default mechanism for all Fedora packages, officially replacing the legacy Fedora CI and Fedora Zuul Tenant on dist-git pull requests.

What we have completed

Over the past several months, we have successfully completed the first three phases of this rollout:

Phase 1: Introduced Koji scratch builds.
Phase 2: Implemented standard installability checks.
Phase 3: Enabled support for user-defined TMT tests via Testing Farm.

Through the opt-in period, we received invaluable feedback from early adopters, allowing us to refine the reporting interface and ensure that re-triggering jobs via PR comments works seamlessly.

Users utilising Zuul CI have been already migrated to using Packit. You can find the details regarding this transition in this discussion thread.

The Final Phase: Transition to Default

We are now moving into the last phase, where we are preparing to switch to the default. After that, you will no longer need to manually add your project to the allowlist. Packit will automatically handle CI for every Fedora package. The tests themselves aren’t changing – Testing Farm still does the heavy lifting.

Timeline & Expectations

Our goal, as previously mentioned, is to complete the switch and enable Packit as the default CI by the end of February 2026. The transition is currently scheduled for February 16, 2026.

To ensure a smooth transition, we are currently working on the final configuration of the system. This includes:

Opt-out mechanism: While Packit will be the default, an opt-out mechanism will be available for packages with specialised requirements. This will be documented at packit.dev/fedora-ci.
Documentation updates: Following the switch, we will also adjust official documentation in other relevant places, such as docs.fedoraproject.org/en-US/ci/, to reflect the new standard.

We will keep you updated via our usual channels in case the target date shifts. You can also check our tasklist in this issue.

How to prepare and provide feedback

You can still opt-in today to test the workflow on your packages and help us catch any edge cases before the final switch.

While we are currently not aware of any user-facing blockers, we encourage you to let us know if you feel there is something we have missed. Our current priority is to provide a matching feature set to the existing solutions. Further enhancements and new features will be discussed and planned once the switch is successfully completed.

Bugs/Feature Requests: Please use our issue tracker.
Discussion: Join the conversation on discussion.fedoraproject.org.
Chat: Reach out to us in the #packit:fedora.im channel on Matrix.

We want to thank everyone who has tested the service so far. Your support is what makes this transition possible!

Best,

the Packit team

2 Weeks Left: The Flock 2026 CFP Ends Feb 2

January 20, 2026 / Justin Wheeler / 0 Comments

Prague is calling! The deadline for the Flock 2026 CFP (Call for Proposals) is fast approaching. You have until Monday, February 2nd to submit your session ideas for Fedora’s premier contributor conference.