Do you want to join us for our annual contributor conference? We want to see you there! However, we know that traveling to a global event is a big trip. It costs real money. To help out, the Flock Organizing Team offers Flock 2026 financial assistance. We want to make sure money does not stop our active contributors from attending.

This is your final reminder. You must submit your form by Sunday, March 8th, 2026. The organizing team starts looking at the data on Monday morning. Because of this fast timeline, we cannot accept any late forms. Sunday is a hard stop.

What does this funding actually cover? We can help you pay for your travel. This includes your airfare or train tickets. We can also help cover your hotel room at the main event venue. We have a limited budget. Because of this, we cannot fully fund every person who applies. Your peers on the organizing team review all the forms. They look at your community impact to make these tough choices.

Note for Flock 2026 speakers

Are you giving a talk this year? We are excited to hear from you! But please remember one important rule. Being an accepted speaker does not give you guaranteed funding. You still need to ask for help. All speakers must fill out the Flock 2026 financial assistance form if they need travel support.

Apply for Flock 2026 financial assistance

Applying is easy. Just follow these steps:

1. Open the Google Form application.
2. Fill in your travel details and your estimated costs.
3. Explain your recent work and your impact in the Fedora community.
4. Submit the form before the end of the day on Sunday, March 8th.

We want to bring as many builders and contributors together as possible. Please do not wait until the last minute. If you need support to join us, fill out the application today!

The post Final Reminder: Flock 2026 Financial Assistance Applications Close Sunday, March 8th appeared first on Fedora Community Blog.

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: 02 – 06 March 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

• Migrated remaining pagure.io repositories, there is one remaining, but needs to have private issues implemented
• Provide DNS domain name for konflux (ticket)
• Meeting with the IPA-tuura team to move forward with the Ipsilon replacement project

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

• investigate jenkins repo gpg key change
• zabbix agent fails to load on rhel 10.1 due to selinux policy mismatch
• Podman/crun issue on ansible ARA host
• Enable side tag feature
• Add AIE to sigs.centos.org
• Enable draft builds in CBS
• [spike] verify how to prevent self-registration on mailman3 instance (outside of allowing FAS/ACO accounts)
• Update pungi for CentOS Stream

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

• Still in Beta Freeze, we have had a couple of release candidate composes for Fedora 44 Beta.
• GO/NO-GO call for the Beta Release is tentatively scheduled for Thursday, March 5th.

RISC-V

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

• Continue to comb through the list of Fedora packages that need work —  submit changes to Fedora / upstream, review patches from others, and submit builds as needed.
• Build/test the RISC-V unified kernel.
• Figured out logistics for 24-h remote access to SpacemiT ‘K3’ hardware (based on RVA230
• Discussed with the RISC-V SIG and Fedora docs about migrating the Fedora RISC-V docs from the wiki to forge.
• Figure out the prerequisites for F44 builds — toolchain dependencies are being sorted out.

AI

This is the summary of the work done regarding AI in Fedora.

• Aurelien Bompard Worked on the AI-powered This Week in Fedora.
• Claude helped Gordon Messmer develop an extension to glibc’s malloc API to solve a common problem with memory inflation, and produced some illustrations of the problem and solution.  The write-up will be posted shortly. Draft at:  https://codeberg.org/gordonmessmer/dev-blog/src/branch/main/memory-efficiency-with-arena-allocators.md
• Quality Team workflow for AI code review in Forgejo — easily reused if you’re interested! https://forge.fedoraproject.org/quality/workflows/src/branch/main/.forgejo/workflows/ai-review.yml

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.

• Fedora 44 RCs are now available and under heavy testing. The Go/NoGo is scheduled in a few days. Lots of blocker (and not blocker) bugs were discovered, discussed, voted on and resolved. 
• Kernel 6.19 test days are complete and Podman 5.8 test days are under way.
• A new version of BlockerBugs bot was implemented and deployed to staging, which should allow us to migrate blocker voting repository from Pagure to Forge (ticket).
• Our cloud automation now reports results to the production wiki for each new compose.
• The refactoring of Fedora Easy Karma was merged to the main branch. All places with links were also updated wrt the recent transition to Forge, and the migration is now done for this repo.
• Forge QA repos now has a reusable workflow for an AI review.
• More bugs hitting OpenQA automated testing were resolved, some some particular ones are very hard to debug, e.g. an ibus hang or an xdg-desktop-portal crash.

Forgejo

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

• [Forgejo] New Organization and Teams Request: Fedora KDE [Followup]
• [Forgejo] Participated in the Forge review, planning and retrospective meet with Rodney, Nils, Ryan and David [Board]
• [Forgejo] New organisation for Fedora Code of Conduct committee + migration [Followup] [Namespace] [Followup]
• [Forgejo] New repo for Security SIG [Followup] [Namespace] [Followup] [Followup]
• [Forgejo] New Organization and Teams Request: Fedora Btrfs [Followup] [Namespace]
• [Docs] Will be migrating Release Notes imminently + branching for F44, contributions welcome once the repo appears on Forgejo
• Forgejo runners added for orgs mindshare and apps
• Private Issues
  • Unit tests for code ⇔ DB boundary (Issue & PrivateIssue: done, related types: ongoing)
  • Verify, debug and fix DB migration

UX

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

• Updated all references to Fedora Design ticket tracker to point to Forgejo [ticket], migration of tickets still wip, but significant progress made.

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

The post Community Update – Week 10 2026 appeared first on Fedora Community Blog.

Fedora Documentation translations will be put on hold from March 4th as the Fedora Localization Team has started the process of migration from pagure.io to the Fedora Forge. From the date, translation projects of the documentation (with ‘fedora-docs-l10n’ in name) will be gradually locked on the Fedora translation platform. Translation automation of the Docs website will also be stopped in the Fedora infrastructure. Consequently, there will be no translation updates available in the language versions on the Fedora Documentation.

The migration involves all repositories which support and ensure the availability of translations of the Fedora Documentation. There is no possibility the migration can be performed ‘on the fly’ as changes in the repositories, related scripts and continuous integration with the translation platform cannot be dealt with independently. Therefore the translation process of the Fedora Documentation is kept on hold.

We regrettably ask the Fedora contributors, our translation community, to pull back from translating of the Fedora Documentation and wait till the translation automation of the documentation is resumed again.

The progress of migration can be followed in the localization tracker as issue #52.

The post Fedora Documentation translations not available from March 4th, 2026 appeared first on Fedora Community Blog.

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

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

• Migration of pagure.io repositories continues
• Ansible repository now has CI running in runner
• Resolved errors on dist-git that were spamming sysadmin-main mailbox – ticket

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

• Fix `automotive10s-packages-main-el10s-build` inheritance to inherit from `autosd10s-packages-main-release`
• Extend underlying storage for OKD/SCoS deliverables
• Add kernel-rpm-macros to the buildroot of automotive10s-packages-main-el10s-build
• Rebase/align mailman3 packages stack for el 9.7
• Clarify debuginfod.centos.org Stream 8 usage (and take action)
• Investigate current hardware situation

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

• Release engineering is currently in Beta Freeze.
• Releng has provided the first beta release candidate after the QE request.
• Request for creating detached signature has been handled by Samyak for ignition 2.26.0 release.

RISC-V

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

• Continued to go through the list of packages to investigate (failing to build; requires patching, and more).
  • Got a PR merged for ‘libkrunfw’ (a low-level library for process isolation) and built it in RISC-V Koji; Marcin (“hrw”) also got a couple more merged.
• Work is progressing well on Fedora RISC-V unified kernels (Jason Montleon is doing most of the heavy-lifting here).  Currently hosted in Copr.

AI

This is the summary of the work done regarding AI in Fedora.

• Worked on the AI-powered This Week in Fedora.
• Updated ai-code-review to use Gemini 3.1 Pro by default
• Nexus team: interesting experience using Claude to refactor fedora-easy-karma, on review we found it made multiple unrequested functionality changes which complicated the review, after discussion decided to re-prompt it to avoid functionality changes

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.

• Fedora 44 Beta testing in full swing
• Kernel 6.19 test week in progress, please contribute
• Help wanted: if anyone can help figure out why F44 boot occasionally just hangs for no very obvious reason that’d be great (details in bug)

Forgejo

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

• Create and present Fedora -> Forgejo efforts during FOSDEM 2026 Distributions Devroom [Video] [Followup]
• Pagure migration doc: add follow-up checklist based on Nexus team’s [Review]
• Create new organisation and namespace on Fedora Forge for Fedora Join [Followup] [Namespace]
• Rename “translations” into “localization-docs” [Followup][Namespace]
  • Remedy mapping after renaming translations to localization-docs [Commit]
• Migrating NeuroFedora SIG [Followup][Namespace][Update]
  • Perform mapping for NeuroFedora SIG teams and groups [Commit] [Followup]
• New Organization and Teams Request: Fedora KDE [Followup][Triaged]
  • Perform mapping for Fedora KDE teams and groups [Commit]
• REST API: Create private issue & foundational work [Followup]
• Runner for forge organization [Followup]
• Refactor the ansible-role-forgejo-runner role task now configured and deploy the runners using ansible-pull 
• Clean out the spam from Pagure.io [Followup]
• Refactor internal APIs for public vs. private issue identity [Followup][Feature]

EPEL

This team is working on keeping Epel running and helping package things.

• Completed EPEL 10.2 mass branching in preparation for the upcoming RHEL 10.2 release (announcement)

UX

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

• Madeline’s  F45 Wallpaper Process Update:  blog post / discussion post
• The Fedora Design Team has switched to using Google Meet for our weekly meetings to utilise Gemini for note-taking. Discussion took place on this ticket and on our weekly call. Updated Fedocal entry can be found here. 
• Forgejo migration: Sprint board created, tickets currently being imported, remaining assets currently being imported / reorganised.

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

The post Community Update – Week 9, 2026 appeared first on Fedora Community Blog.

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: 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

• lack of ipv6 on some sponsored servers
• New Build Target and Tags for the Kmods SIG (kernel-6.18)
• Extend maximum build time for CS10 Risc-v
• Spam on the automotive-sig mailing list
• Move Hyperscale SIG docs source from pagure to gitlab
• Request: Add new SSH key for OKD / SCOS bootimage sync to cloud.centos.org
• mirror request
• Setup BuildRoot for CS10 risc-v
• allow rsync for 2 fedoraproject mirrors
• Need more disk space on Gitlab Runners
• Ensuring that gen2 images are also deleted/cleaned up from koji (through koji-gc)

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.

The post Community Update – Week 8 2026 appeared first on Fedora Community Blog.

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.

What is new?

• Faster Downloads: Try optimized “parallel pulls” to get your images in seconds.
• Setup: Test the new “automatic database creation” for a smoother start.
• Expert Skills: Learn how to use latest container environments before they go mainstream.

Why join?

Your setup is unique. By running Podman 5.8 on your machine, you make sure the final version works perfectly for everyone. It is a great way to learn by doing and to see how top-tier open-source software is made.

Start here

We have prepared easy-to-follow steps for you here: https://fedoraproject.org/wiki/Test_Day:2026-02-27_Podman_5.8

The post Master Podman 5.8: Join Fedora Test Week appeared first on Fedora Community Blog.

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: 09 – 13 February 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

• Ported bugzilla2fedmsg to use Red Hat’s Kafka servers, since UMB will be decommissioned. The code with Kafka support is currently in staging but requires firewall ports to be opened (ticket 13133)
• Resolved outage of stg.pagure.io caused by anubis (ticket 13128)
• Few more repositories migrated to forge.fedoraproject.org from pagure.io
• Resolved pushing issues on to src.stg.fedoraproject.org, caused by wrong permissions (ticket 13096)
• [Tahrir] Add PUT endpoint for updating for USER relation and integrate it with the frontend [Review] [Merged]
• [Tahrir] List profile invitations when the user has logged in [Pull request]

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

• Update Gitlab Runners to v18
• Spam on the automotive-sig mailing list

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 Mass Branching was successfully completed last week!
• Beta Freeze is tentatively scheduled to begin next week, Tue 2026-02-17.

RISC-V

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

• Fedora RISC-V “unified kernel” work in progress (Jason Montleon): targeted for F44.  Right now they’re being built in Copr.  Will move to Koji once the F44 buildroot is populated.
• Work by Fabian Arrotin RISC-V builders in CentOS Build System (CBS) now can build from official sources (git+https from CentOS Stream)

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.

• Co-ordinated with releng team on branching as it involves openQA, critical path and the gating policies – things went much smoother this time but still lots of lessons learned and SOP improvements drafted and suggested
• Work ongoing to port the blockerbugs tool to forgejo , nearly complete but may be delayed as jgroman will be on PTO
• Multiple enhancements to testdays-web, see merged PRs
• Updated openQA packages deployed to production
• Another heavy week of openQA catching bugs, mostly plasma-setup and GNOME 50, details here

Forgejo

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

• Forgejo backup pruning solved
• Staging runner going offline issue fixed
• A lot of new organizations created, repo migrations
• Private Issues: Make tests succeed, ongoing: tidy up commits for PR

EPEL

This team is working on keeping Epel running and helping package things.

• EPEL 11 early planning at CentOS Connect, FOSDEM, and CentOS Docs Day

UX

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

• Started migrating Fedora Design to Forgejo! 
• The F45 wallpaper inspiration is officially Alan Turing!

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

The post Community Update – Week 07 2026 appeared first on Fedora Community Blog.

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: 02 Feb – 05 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

• [Matrix] Insert 2025 Matrix Dragon Slayers badge artwork [Commit] [Request] [Followup] [Badge]
• [FOSDEM] Insert Sprouting Strategy badge artwork [Commit] [Issue] [Followup] [Badge]
• [FOSDEM] Insert FOSDEM 2027 Attendee badge artwork [Commit] [Request] [Followup] [Badge]
• Fixed permission on staging dist-git [ticket]
• Fixed failed disk on bvmhost-x86-02 [ticket]
• Fixed network card issues on copr VM hosts [ticket]
• Mass updates and reboots [ticket]
• Continue on pagure.io to forgejo migration [ticket]
• Continue on registry.fedoraproject.org to quay.io migration [ticket]
• Look at adapting bugzilla2fedmsg for the migration to Kafka
• Work with GNOME Damned Lies for their migration to Fedora’s OIDC

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

• [CentOSConnect] Worked on fixing the CentOS Connect 2026 attendee badge [Invitation]
• CBS s390x builder offline?
• mirror request
• Spam on the automotive-sig mailing list

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 mass branching preparation [ticket]
• Mass resigning [ticket]
• Creating Bugzilla component [ticket]
• Day to day tickets [ticket]

RISC-V

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

• Fedora RISC-V kernel situation: work on a unified kernel is in-progress for F44 that will work across different boards.
  • Copr RISC-V chroots are being used for kernel builds
• In the RISC-V SIG meeting, agreed to work on a formal “community initiative” for RISC-V
  • Much of the real work has already been going on w/o a “formal” process — Koji server running on Fedora Infra, FAS integration, RISC-V in Copr, etc.
• State of RISC-V on Fedora talk at FOSDEM was well received.  Slides [PDF] and video are available.
• F43: the difference between the packages in primary Koji and the RISC-V Koji is very little now (i.e. the gap is being closed).

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.

• KDE Test Days going on now (Feb 2 to Feb 9), please help out! Jgroman publicized this and the GNOME Test Day in Fedora Magazine and Community Blog
• Finally merged the automated test for openQA for Fedora Media Writer
• Settling into Forge and discovering some paper cuts – Sprint search, duplicated priority labels
• Work ongoing to port blockerbugs to Forge
• Heavy week of openQA catching bugs in Rawhide changes – see ticket for details (more shadow 4.19 stuff and plasma-login-manager feature heavily)

Forgejo

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

• [Forgejo] Create a localization-docs namespace and group mapping for specific requirements [Followup] [Resolved]
• [Forgejo] Migrate Weblate translations/internationalization tooling from Pagure/GitLab/GitHub to Forgejo [Followup] [Resolved]
• [Forgejo] Verify if the milestone dates are set correctly in the production deployment of Fedora Forge [Followup] [Resolved]
• [Forgejo] Create and present Fedora -> Forgejo efforts during FOSDEM 2026 Distributions Devroom [Followup] [Followup] [Resolved]
• Image build automation pull request
• Fedora-based runner image built, tested and deployed to staging for further testing (under the playground org), definition
• Private Issues: Debug failing tests, tidy up accrued changes and cope with nullable public/private issue ID fields

UX

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

• Artwork for Sprouting Strategy badge.
• Slideshow template for FOSDEM conference booth complete. Comment with slideshow private due to badge claim link. 
• FOSDEM swag survey uploaded to LimeSurvey – next step is analysing results.

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

The post Community Update – Week 6 appeared first on Fedora Community Blog.

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.

The post Flock CFP Extended to February 8 appeared first on Fedora Community Blog.

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.

The post Desktop Test Days: A week for KDE and another for GNOME appeared first on Fedora Community Blog.

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: 26 – 30 January 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

• Migration of tickets from pagure.io to forge.fedoraproject.org 
• Dealing with spam on various mailing lists
• Dealing with hw failures on some machines
• Fixed IPA backups
• Fixed retirement script missing some packages
• Another wave of AI scrapers
• Quite a few new Zabbix checks for things (ipa backups, apache-status)

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

• Setup BuildRoot for CS10 risc-v
• New group: sig-automotive-copr
• Onboard risc-v architecture into infra for bootstrap
• [Messaging SIG] Messaging tags for CentOS Stream 10 in CBS
• Access to jenkins-nfs-ganesha – member add request to ocp-cico-nfs-ganesha.
• Access to jenkins-nfs-ganesha – member add request to ocp-cico-nfs-ganesha
• Setup for the new Accelerated Infrastructure Enablement SIG
• [dc move] – reprovision local internal mirror
• Racking RISC-V machines in rdu3
• Enable native RISC-V builds in CBS Koji

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 Mass Rebuild resulted in merging approx 22K rpms into the F44 Tag

RISC-V

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

• Relative good news: Mark Weilaard managed to get a fix for the ‘debugedit’ bug that was blocking Fedora.  We now have a build that has unblocked a few packages. The fix has some rough edges. We’re working on it, but a big blocker is out of the way now.
• We now have Fedora Copr RISC-V chroots — these are QEMU-emulated running on x86. Still, this should give a bit more breathing room for building kernel RPMs.  (Credit: Miroslav Suchý saw my status report a couple of months ago about builder shortage. He followed up with us to make this happen with his team.)
• Fabian Arrotin racked a few RISC-V machines for CBS.  We (Andrea Bolognani and Fu Wei) are working on buildroot population

AI

This is the summary of the work done regarding AI in Fedora.

• awilliam used Cursor to summarize several months of upstream changelogs while updating openQA packages (still one of the best use cases so far)

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.

• Forgejo migration continuation and cleanup – we’re now nearly 100% done
• All generally unhappy about the CSB policy and communication
• Prepared some upcoming Test Days: KDE Plasma 6.6, Grub OOM 2: Electric Boogaloo
• Dealt with a couple of issues caused by the mass rebuild merge, but it was much smoother this time 
• Psklenar signed up for the Code Coverage working group thing
• Set up sprint planning in Forgejo
• Added a Server build/install test to openQA to avoid reoccurrences of Server profile-specific issues like https://bugzilla.redhat.com/show_bug.cgi?id=2429501
• Did some testing on new laptop HW provided by Lenovo

Forgejo

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

• More repo migrations,  creating new Orgs and Teams, creating Org requested runners,  solving reported issues
• Staging instance of distgit deployed
• Performance testing of the forge instances, storage increase, maintenance

UX

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

• Looking for people to vote for F45 Wallpaper Inspiration!
• Final wallpaper for F44 complete.
• Wrapping up last design bits for FOSDEM.
• Fedora Design Team docs revamp starting this sprint.

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

The post Community Update – Week 05 2026 appeared first on Fedora Community Blog.

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

The post Packit as Fedora dist-git CI: final phase appeared first on Fedora Community Blog.

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.

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.

Important Dates & Travel Info

• CFP Deadline: Monday, February 2, 2026 (23:59 UTC)
• Travel Assistance Deadline: March 8, 2026
• Event Dates: June 14–16, 2026
• Location: OREA Hotel Andel’s

If you require financial support to attend, please remember that the Flock 2026 CFP submission is separate from the Travel Subsidy application, but speakers are prioritized. Make sure to apply for the Travel Subsidy by March 8.

How to Submit to Flock 2026 CFP

Don’t let the deadline slip past you. Head over to our CFP platform and draft your proposal today.

Submit to the Flock 2026 CFP

See you in Prague!

Note: AI (Google Gemini) edited human-generated content first written by me, the author, to write this article. I, the author, edited the AI-generated output before making this Community Blog article. If you notice mistakes, please provide a correction as a reply to this topic.

The post 2 Weeks Left: The Flock 2026 CFP Ends Feb 2 appeared first on Fedora Community Blog.

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: 12 Jan – 16 Jan 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

• [FMTS] TLS certificate for zodbot service is about to expire in 30 days
• [FMTS] TLS certificate for logging service is about to expire in 30 days
• Disabled branch: python-plotly + stats-collect
• History of a file on src.fp.o returns HTTP/403 Forbidden
• FAS account mail modified but alias still forward to the old one
• proxy05 outage 2026-01-06
• Fedora Messaging certificate for logdetective-packit
• wiki, cannot edit via python script, mwclient.errors.APIError: (‘internal_api_error_Error)
• [Forgejo] New Organization and Teams Request: Konflux Integration Team
• `fedpkg new-sources` is failed with server error 502
• Upgrade proxies from f42 to f43
• maubot-meetings bot multi line paste is cut

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

• Add back ppc64le composes tests on testing.stream.centos.org
• CS image and runroot server is broke
• Create internal nginx cache for stream infra

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

• Mass Rebuild is GO for Wednesday, January 14th.

QE

This team is working on day to day business regarding Fedora CI and testing.

• Multi-signed shim Test Day is live
• The OpenQA needly editor Needly from Lukas Ruzicka is now packaged on Flathub
• An OpenQA test for Fedora Media Writer is mostly done, now testing on staging

Forgejo

This team is working on deployment of forge.fedoraproject.org.
Ticket tracker

• Fedora Localization migration – Groups [A] [B] [C], teams and namespaces created
• Konflux integration organisation and groups created 
• Forge action runner for quality organization
• Konflux pipelines for distgit added – images for distgit instance ready on quay. Work in progress for fedora-rawhide based images.

RISC-V

• We’re still blocked by a complex in potential both binutils and debugedit  We have a reproducer and some leads, but no clear “chain of blame” yet. We’re still actively working on this with several folks.
  • (Details: We have about 1433 packages that build something that include `*.a` (archive file).  We know the affected packages are roughly <200 packages , but that’s likely because we’re just shipping the static libraries.  The count of 1433 drops to 440 if we exclude OCaml, GHC, and MinGW.)

UX

• We have a new teenage contributor in Fedora Design! He has completed his first ticket
• Logo variations for Project Hummingbird have been uploaded.
• All files for printed materials created for Fedora at FOSDEM have been sent to stakeholders.
• Held an initial brainstorming session for revamping the Fedora Design docs [epic].

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

The post Community Update – Week 03 2026 appeared first on Fedora Community Blog.

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: 05 Jan – 09 Jan 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

• [FESCo] Five badges for F43-F47 changes have been pushed [A] [B] [C] [D] [E]
• Cannot send emails via smtp-auth server for orphaned packages process
• error 500 on cgit hosted on fedorapeople.org
• new group for Universal Blue

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

• Create internal nginx cache for stream infra
• EL 9 / 10 oVirt Tags
• One sponsored server (hosting services like website) is flapping
• [virt-sig collab] : rebase qemu-kvm pkg for ppc4le

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

• Preparatory steps for the next Mass Rebuild which is currently scheduled for next week, Wednesday January 14th.

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

The post Community Update – Week 02 2026 appeared first on Fedora Community Blog.

The tmt web app is a simple web application that makes it easy to explore and share test and plan metadata without needing to clone repositories or run tmt commands locally.

At the beginning, there was the following user story:

As a tester, I need to be able to link the test case(s) verifying the issue so that anyone can easily find the tests for the verification.

Traceability is an important aspect of the testing process. It is essential to have a bi-directional link between test coverage and issues covered by those tests so that we can easily:

• identify issues covered by the given test
• locate tests covering given issues

Link issue from test

Implementing the first direction in tmt was relatively easy: We just defined a standard way to store links with their relations. This is covered by the core link key which holds a list of relation:link pairs. Here’s an example test metadata:

summary: Verify correct escaping of special characters
test: ./test.sh
link:
  - verifies: https://issues.redhat.com/browse/TT-206

Link test from issue

The solution for the second direction was not that straightforward. Thanks to its distributed nature, tmt does not have any central place where a Jira issue could point to. There is no server which keeps information about all tests and stores a unique id number for each which could be used in the link.

Instead of integers, we’re using the fmf id as the unique identifier. It contains url of the git repository and name of the test. Optionally, it can also define ref instead of using the default branch and path to the fmf tree if it’s not in the git root.

The tmt web app accepts an fmf id of the test or plan or both, clones the git repository, extracts the metadata, and returns the data in your preferred format:

• HTML for human-readable viewing
• JSON or YAML for programmatic access

The service is currently available at the following location:

• https://tmt.testing-farm.io/

Here’s an example of what the parameters would look like when requesting information about a test in the default branch of a git repository:

• https://tmt.testing-farm.io/?test-url=…&test-name=…

By default, a human-readable HTML version of the output is provided to the user. Include the format parameter in order to choose your preferred format:

• https://tmt.testing-farm.io/?test-url=…&test-name=…&format=yaml

It is possible to link a test, a plan, or both test and plan. The last option can be useful when a single test is executed under several plans. Here’s how the human readable version looks like:

Create new tests

In order to make the linking as smooth as possible, the tmt test create command was extended to allow automated linking to Jira issues.

First make sure you have the .config/tmt/link.fmf config prepared. Check the Link Issues section for more details about the configuration.

issue-tracker:
  - type: jira
    url: https://issues.redhat.com
    tmt-web-url: https://tmt.testing-farm.io/
    token: ***

When creating a new test, use the --link option to provide the issue which is covered by the test:

tmt test create /tests/area/feature --template shell --link verifies:https://issues.redhat.com/browse/TT-206

The link will be added to both test metadata and the Jira issue. Just note that the Jira link will be working once you push the changes to the remote repository.

Link existing objects

It’s also possible to use the tmt link command to link issue with already existing tests or plans:

tmt link --link verifies:https://issues.redhat.com/browse/TT-206 /tests/core/escaping

If both test and plan should be linked to the issue, provide both test and plan as the names:

tmt link --link verifies:https://issues.redhat.com/browse/TT-206 /tests/core/escaping /plans/features/core

This is how the created links would look like in Jira:

Closing notes

As a proof of concept, for now there is only a single public instance of the tmt web app deployed, so be aware that it can only explore git repositories that are publicly available. For the future we consider creating an internal instance in order to be able to access internal repositories as well.

We are looking for early feedback. If you run into any problems or any missing features, please let us know by filing a new issue. Thanks!

The post Improve traceability with the tmt web app appeared first on Fedora Community Blog.

The Fedora Linux 43 (F43) election cycle has concluded. In this election round, there was only one election, for the Fedora Engineering Steering Committee (FESCo). Congratulations to the winning candidates. Thank you to all candidates for running in this election.

Results

FESCo

Five FESCo seats were open this election. A total of 214 ballots were cast, meaning a candidate could accumulate a maximum of 1,498 votes. More detailed information on the voting breakdown is available from the Fedora Elections app in the Results tab.

The post Fedora Linux 43 (F43) election results appeared first on Fedora Community Blog.

Voting is currently open for the Fedora Engineering Steering Committee (FESCo). You have approximately 2 days and 9 hours remaining to participate.

DEADLINE: 2026-01-07 at 23:59:59 UTC
VOTE HERE: https://elections.fedoraproject.org/about/f43-fesco

Please ensure your ballot for the Fedora Linux 43 FESCo Elections is cast before the cutoff.

The post DEADLINE 2026-01-07: Fedora Linux 43 FESCo Elections appeared first on Fedora Community Blog.

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

Week: 15 – 19 December 2025

Forgejo

This team is working on deployment of forge.fedoraproject.org.
Ticket tracker

• [Ansible] Attachments redirect config changes merged – Now being tested in staging
• [Design] Design and Translation floating migration from GitLab to Forgejo in progress
• [Upstream] Extended support for milestones to support YYYY-MM-DD on QE request
• [FOSDEM] “Forging Fedora Project’s Future with Forgejo” selected for Distro Devroom
• Staging forgejo distgit deployment complete but for a netapp volume. Waiting on access to the netapp to get this created.
• Forgejo runner to be added to the Infra org on production.
• Private Issues: Refactoring of internal APIs (ongoing)

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

• DC Move (rdu-cc to rdu3/rdu3-iso) outage completed.
  • Some hosts still having issues, see ticket
• Zabbix moving forward as our main monitoring tool.
• Updates+uptimes tool now removes hosts as they are removed from  ansible inventory.
• Dealt with HW warranties that need/not-need renewing for next year.
• Docs are now migrated to https://forge.fedoraproject.org/infra/docs

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

• Reconfigure machines moved to RDU3
• CBS tagBuild tasks stuck in open state
• Prepared hardware that will move to RDU3 (dc-move)

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 41 is now END OF LIFE.

QE

This team is working on day to day business regarding Fedora CI and testing.

• Kernel 6.18 test days and GRUB Out of Memory Verification test days are now in progress
• Fedora QE is now blocked on broken attachments in migrated tickets, paused migrations for now
• Lruzicka rewrote the new basic networking test case to be simpler and more human-friendly
• Caught a significant bug in passt (podman networking component): “Thanks a lot for all the support. This was an actual and serious issue that was prevented” (maintainer)
• Revitalized maintenance of testdays webapp with help from new member jgroman
• Multiple issues in Firefox 146 update: crashed on aarch64 (that was fixed), breaks Cockpit Services page (not yet fixed)
• Set up a test day at request of bootloader folks to get broad testing on a specific change
• Quarterly connections and reward zone nominations

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

The post Community Update – Week 51 2025 appeared first on Fedora Community Blog.

This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.

Interview with Máirín Duffy

• FAS ID: duffy
• Matrix Rooms: My long-term home has been Fedora Design, but I also hang out in Podman, Fedora Marketing, and Fedora AI/ML.

Questions

Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?

I have used Fedora as my daily driver since 2003 and have actively contributed to Fedora since 2004. (Example: I designed the current Fedora logo and website design.) I am very passionate about the open source approach to technology. I first started using Linux as a high school student (my first Linux was Red Hat 5.1) and being able to use free software tools like Gimp when I couldn’t afford Photoshop made an outsized impact on my life. (I explain my background in Linux and open source in-depth in this interview with Malcolm Gladwell: https://youtu.be/SkXgG6ksKTA?si=RMXNzyzH9Tr6AuwN )

Technology has an increasingly large impact over society. We should have agency over the technology that impacts our lives. Open source is how we provide that agency. We’re now in a time period with a new disruptive technology (generative AI) that – regardless if you think it is real or not, is having real impact on computing. Fedora and other open source projects need to be able to provide the benefits of this new technology, the open source way and using open source software. Small, local models that are easy for our users to deploy on their own systems using open source tooling will provide them the ability to benefit AI’s strengths without having to sacrifice the privacy of their data.

There is a lot of hype around AI, and a lot of very legitimate concerns around its usage including the intellectual property concerns of the pre-trained data, not having enough visibility into what data is part of pre-trained data sets, the working conditions under which some of the data is labeled under, the environmental impact of the training process, the ethics of its usage. Open source projects in particular are getting pummeled by scraping bots hungry to feed coding models. There are folks in the tech industry who share these legitimate concerns that prefer to avoid AI and hope that it the bubble will just pop and it will go away. This strategy carries significant risks, however, and we need a more proactive approach. The technology has legitimate uses and the hype is masking them. When the hype dies down, and the real value of this new technology is more visible, it will be important for the type of community members we have in Fedora with their commitment to open source principles and genuinely helping people to have had a seat at the table to shape this technology.

(You can see a short video where I talk a bit more indepth about the pragmatic, privacy and open source-focused approach I take to AI here: https://youtu.be/oZ7EflyAPUw?si=HSbNhq_3NelXoX2J)

In the past I have been quite skeptical about generative AI and worried about its implications for open source. (I continue to be skeptical and annoyed by the hype surrounding it.) I’ve spent the past couple of years looking at open source licensed models and building open source generative AI tooling – getting hands on, deep experience to understand it – and as a result I have seen first hand the parts of this technology that have real value. I want FESCo to be able to make informed decisions when AI issues come up.

My background is in user experience engineering, and I am so excited about what this technology will mean for improving usability and accessibility for users of open source software. For example, we never have enough funding or interest to solve serious a11y problems; now we could generate text summaries of images & describe the screen out loud with high-quality audio from text-to-voice models for low vision users! I want open source to benefit from these and even more possibilities to reach and help more people so they can enjoy software freedom as well.

I have served in multiple governance roles in Fedora including time on the Fedora Council, the Mindshare Committee, lead of various Fedora Outreachy rounds (I have mentored dozens of interns in Fedora), and founder / lead of the Design team over many years. More importantly, I have deep Linux OS expertise, I have deep expertise in user experience, and I have a depth in AI technology to offer to FESCo. I believe my background and skills will enable FESCo to make responsible decisions in the best interest of open source and user agency, particularly around the usage of AI in Fedora and in the Fedora community. We will absolutely need to make decisions as a governing group in the AI space, and they should be informed by that specific expertise.

How do you currently contribute to Fedora? How does that contribution benefit the community?

I founded and ran the Fedora Design Team for 17 years. It was the first major Linux distribution community-lead design team, and often as a team we’ve been asked by other distros and open source projects for help (so we expanded to call ourselves the “Community Design Team.”) Over the years I’ve designed the user experience and user interfaces for many components in Fedora including our background wallpapers, anaconda, virt-manager, the GNOME font-chooser, and a bunch of other stuff. I moved on from the Fedora Design role to lead design for Podman Desktop and to work more with the Podman team (who are also part of the Fedora community) for a couple of years, and I also led the InstructLab open source LLM fine-tuning project and corresponding Linux product from Red Hat (RHEL AI.) For the past year or so I have returned to working on core Linux on the Red Hat Enterprise Linux Lightspeed team, and my focus is on building AI enhancements to the Linux user experience. My team is part of the Fedora AI/ML SIG and we’re working on packaging user-facing components and tooling for AI/ML for Fedora, so folks who would like to work with LLMs can do so and the libraries and tools they need will be available. This includes building and packaging the linux-mcp-server and packaging goose, a popular open source AI agent, and all of their dependencies.

My career has focused on benefiting Fedora users by improving the user experience of using open source technology, and being collaborative and inclusive while doing so.

How do you handle disagreements when working as part of a team?

Data is the best way to handle disagreements when working as part of a team. Opinions are wonderful and everyone has them, but decisions are based made with real data. Qualitative data is just as important as quantitative data, by the way. That can be gathered by talking directly to the people most impacted by the decision (not necessarily those who are loudest about it) and learning their perspective. Then informing the decision at hand with that perspective.

A methodology I like to follow in the face of disagreements is “disagree and let’s see.” (This was coined by Molly Graham, a leadership expert.) A decision has to be made, so let’s treat it like an experiment. I’ll agree to run an experiment, and track the results (“let’s see”) and advocate for a pivot if it turns out that the results point to another way (and quickly.) Being responsible to track the decision and its outcomes and bringing it back to the table, over time, helps build trust in teams like FESCo so folks who disagree know that if the decision ended up being the wrong one, that it can and will be revisited based on actual outcomes.

Another framework I like to use in disagreements is called 10-10-10, created by Suzy Welch. It involves thinking through: how will this decision matter in 10 minutes? How about 10 months? How about 10 years? This frame of thought can diffuse some of the chargedness of disagreement when all of the involved people realize the short or long term nature of the issue together at the same time.

Acknowledging legitimate concerns and facing them head on instead of questioning or sidelining others’ lived experience and sincerely-held beliefs and perspectives is also incredibly important. Listening and building bridges between community members with different perspectives, and aligning them to the overall projects goals – which we all have in common as we work in this community – is really helpful to help folks look above the fray and be a little more open-minded.

What else should community members know about you or your positions?

I understand there is a campaign against my running for FESCo because myself and a colleague wrote an article that walked through real, undoctored debugging sessions with a locally-hosted, open source model in order to demonstrate the linux-mcp-server project.

I want to make it clear that I believe any AI enhancements that are considered for Fedora need a simple opt-in button, and no AI-based solutions should be the default. (I’ve spoken about this before, recently on the Destination Linux Podcast: https://youtu.be/EJZkJi8qF-M?t=3020) The user base of Fedora and other open source operating systems come to their usage in part due to wanting agency over the technology they use and having ownership and control over their data. The privacy-focused aspects of Fedora have spanned the project’s existence and that must be respected. We cannot ignore AI completely, but we must engage with it thoughtfully and in a way that is respectful of our contributors and user base.

To that end, should you elect to grant me the privilege of a seat to FESCo this term:

• I intend to vote in opposition to proposals that involve bundling proprietary model weights in Fedora.
• I intend to vote in opposition to proposals that involve sending Fedora user data to third party AI services.
• I intend to vote in opposition to proposals to turn AI-powered features on by default in any Fedora release.
• I intend to vote in favor of proposals to enact AI scraper mitigation strategies and to partner with other open source projects to fight this nuisance.

My core software engineering background is in user experience and usability, and I believe in the potential of small, local models to improve our experience with software without compromising our privacy and agency. I welcome ongoing community input on these principles and other boundaries you’d like to see around emerging technologies in Fedora.

The post F43 FESCo Elections: Interview with Máirín Duffy (duffy/mizmo) appeared first on Fedora Community Blog.

This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.

Interview with Timothée Ravier

• FAS ID: siosm
• Matrix Rooms: Fedora Atomic Desktops, Fedora CoreOS, Fedora bootc, Fedora KDE, Fedora Kinoite, Fedora Silverblue

Questions

Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?

I want to be a member of FESCo to represent the interests of users, developers and maintainers of what we call Atomic, Bootable Container, Image Based or Immutable variants of Fedora (CoreOS, Atomic Desktops, IoT, bootc, etc.).

I think that what we can build around those variants of Fedora is the best path forward for broader adoption of Fedora and Linux in the general public and not just in developer circles.

I thus want to push for better consideration of the challenges specific to Atomic systems in all parts of Fedora: change process, infrastructure, release engineering, etc.

I also want to act as a bridge with other important communities built around this ecosystem such as Flathub, downstream projects such as Universal Blue, Bazzite, Bluefin, Aurora, and other distributions such as Flatcar Linux, GNOME OS, KDE Linux, openSUSE MicroOS, Aeon or ParticleOS.

How do you currently contribute to Fedora? How does that contribution benefit the community?

I primarily contribute to Fedora as a maintainer for the Fedora Atomic Desktops and Fedora CoreOS. I am also part of the KDE SIG and involved in the Bootable Containers (bootc) initiative.

My contributions are focused on making sure that those systems become the most reliable platform for users, developers and contributors. This includes both day to day maintenance work, development such as enabling safe bootloader updates or automatic system updates and coordination of changes across Fedora (switching to zstd compressed initrds as an example).

While my focus is on the Atomic variants of Fedora, I also make sure that the improvements I work on benefit the entire Fedora project as much as possible.

I’ve listed the Fedora Changes I contributed to on my Wiki profile: https://fedoraproject.org/wiki/User:Siosm.

How do you handle disagreements when working as part of a team?

Disagreements are a normal part of the course of a discussion. It’s important to give the time to everyone involved to express their positions and share their context. Limiting the scope of a change or splitting it into multiple phases may also help.

Reaching a consensus should always be the preferred route but sometimes this does not happen organically. Thus we have to be careful to not let disagreements linger on unresolved and a vote is often needed to reach a final decision. Not everyone may agree with the outcome of the vote but it’s OK, we respect it and move on.

Most decisions are not set in stone indefinitely and it’s possible to revisit one if the circumstances changed. A change being denied at one point may be accepted later when improved or clarified.

This is mostly how the current Fedora Change process works and I think it’s one of the strength of the Fedora community.

What else should community members know about you or your positions?

I’ve been a long time Fedora user. I started contributing more around 2018 and joined Red Hat in 2020 where I’ve been working on systems such as Fedora CoreOS and RHEL CoreOS as part of OpenShift. I am also part of other open source communities such as Flathub and KDE and I am committed to the upstream first, open source and community decided principles.

The post F43 FESCo Elections: Interview with Timothée Ravier (siosm/travier) appeared first on Fedora Community Blog.

This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.

Interview with Daniel Mellado

• FAS ID: dmellado
• Matrix Rooms: #ebpf, #fedora-devel, #rust, #fedora-releng, and a lot of #fedora-*

Questions

Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?

I accepted this nomination because I believe FESCo would benefit from fresh perspectives, and I think that these new perspectives will also help to lower the entrance barriers for Fedora.

Governance bodies stay healthy when they welcome new voices alongside experienced members, and I want to be part of that renewal.

Technologies like eBPF are redefining what’s possible in Linux–observability, security, networking–but they also bring packaging challenges that we haven’t fully solved, such as kernel version dependencies, CO-RE relocations, BTF requirements, and SELinux implications.

On FESCo, I want to help Fedora stay ahead of these challenges rather than merely reacting to them. I want to advocate for tooling and guidelines that will help make complex kernel-dependent software easier to package.

How do you currently contribute to Fedora? How does that contribution benefit the community?

I founded and currently lead the Fedora eBPF Special Interest Group. Our goal is to make eBPF a first-class citizen in Fedora, improving the experience for the developers who are building observability, security, and networking tools and figuring out how to package software that has deep kernel dependencies.

On the packaging side, I maintain bpfman (an eBPF program manager) and several Rust crates that support eBPF and container tooling. I’ve also learned the hard way that Rust dependency vendoring is… an adventure.

Before Fedora, I spent years in the OpenStack community. I served as PTL (Project Team Lead) for the Kuryr project, the bridge between container and OpenStack networking and was active in the Kubernetes SIG. That experience taught me a lot about running open source projects: building consensus across companies, mentoring contributors, managing release cycles, and navigating the politics of large upstream communities.

I try to bring that same upstream, community-first mindset to Fedora. My hope is that the patterns we establish in the eBPF SIG become useful templates for other packagers facing similar challenges.

How do you handle disagreements when working as part of a team?

I start by assuming good intent. If someone is in the discussion, it’s because they do also care about the outcome, even though they may have another point of view.

I also try not to speculate about why someone holds a particular view. Assigning motives derails technical conversations fast. Instead, I focus on keeping things facts-driven: what does the code actually do, what do users need, what are the real constraints? Egos don’t ship software, and sticking to concrete data keeps discussions productive.

When disagreements persist, I find it helps to identify what everyone does agree on and use that as a new starting point. You’d be surprised how often this unblocks a stalled conversation.

Also, I think that it’s important to step back. It’s tempting to want the final word, but that can drag things on forever without real progress. Miscommunication happens and not every discussion needs a winner.

What else should community members know about you or your positions?

I believe in Fedora’s Four Foundations: Freedom, Friends, Features, First. What draws me to this community is the “Friends” part: there’s a place in Fedora for anyone who wants to help, regardless of background or technical skill level. Open source is at its best when it’s genuinely welcoming, and I want FESCo to reflect that.

From my time in the OpenStack community, I learned that healthy projects focus on protecting, empowering, and promoting: protecting the open development process and the values that make the community work; empowering contributors to do great work without painful barriers; and promoting not just the software, but the people who build and use it. I try to bring that mindset to everything I do.

I also believe strongly in working upstream. The changes we make should benefit not just Fedora users, but the broader open source ecosystem. When we solve a hard problem here, that knowledge should flow back to upstream projects and other distributions.

I’ll be at FOSDEM 2026. FOSDEM embodies what I love about open source: a non-commercial space where communities meet to share knowledge freely. If you’re there, come say hi.

The post F43 FESCo Elections: Interview with Daniel Mellado (dmellado) appeared first on Fedora Community Blog.

This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.

Interview with Kevin Fenzi

• FAS ID: kevin
• Matrix Rooms: I’m probibly most active in the following rooms. I’m available and answer notifications and watch many other channels as well, but those 3 are the most active for me:
  • noc -> day to day infra stuff, handling alerts, talking with other infra folks
  • admin -> answering questions, helping fix issues, some team discussions
  • releng -> release engineering team discussions, answering questions, handling issues, etc.

Questions

Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?

I think I still provide useful historical information as well as being able to pull on that long history to know when things are good/bad/have been tried before and have lessons to teach us.

Based on the proposals we approve or reject we can steer things from FESCo. I do think we should be deliberate, try and reach consensus and accept any input we can get to try to come to good decisions. Sometimes things won’t work out that way, but it should really be the exception instead of the rule.

How do you currently contribute to Fedora? How does that contribution benefit the community?

I’m lucky to be paid by Red Hat to work on infrastucture, I like to hope it’s useful to the community
In my spare time I work on packages, answering questions where I can, unblocking people, release engineering work, matrix and lists moderation.

I really hope my contributions contribute to a happier and more productive community.

How do you handle disagreements when working as part of a team?

I try and reach consensus where possible. Sometimes that means taking more time or involving more people, but If it can be reached I think it’s really the best way to go.

Sometimes of course you cannot reach a consensus and someone has to make a call. If thats something I am heavily involved in/in charge of, I do so. I’m happy that we have a council as a override of last resort in case folks want to appeal some particularly acromonious decision. Also, as part of a team you have to sometimes delegate something to someone and trust their judgement in how it’s done.

What else should community members know about you or your positions?

I think there’s been a number of big debates recently and probibly more to come. We need to remember we are all friends and try and see things from other people’s point of view.

My hero these days seems to be treebeard: “Don’t be hasty”

My matrix/email is always open for questions from anyone…

The post F43 FESCo Elections: Interview with Kevin Fenzi (kevin/nirik) appeared first on Fedora Community Blog.

This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.

Interview with Fabio Alessandro Locati

• FAS ID: fale
• Matrix Rooms: I can be easily found in #atomic-desktops:fedoraproject.org, #bootc:fedoraproject.org, #coreos:fedoraproject.org, #devel:fedoraproject.org, #epel:fedoraproject.org, #event-devconf-cz:fedoraproject.org, #fedora:fedoraproject.org, #fedora-arm:matrix.org, #fedora-forgejo:fedoraproject.org, #fosdem:fedoraproject.org, #flock:fedoraproject.org, #golang:fedoraproject.org, #iot:fedoraproject.org, #meeting:fedoraproject.org, #meeting-1:fedoraproject.org, #mobility:fedoraproject.org, #python:fedoraproject.org, #rust:fedoraproject.org, #silverblue:fedoraproject.org, #sway:fedoraproject.org, #websites:fedoraproject.org

Questions

Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?

I have been part of the Fedora community for many years now: my FAS account dates back to January 2010 (over 15 years ago!), and I’ve contributed in many different roles to the Fedora project. I started as an ambassador, then became a packager and packaging mentor, and joined multiple SIGs, including Golang, Sway, and Atomic Desktop. For many years, I’ve been interested in immutable Linux desktops, Mobile Linux, and packaging challenges for “new” languages (such as Go), which are also becoming more relevant in the Fedora community now. Having contributed to the Fedora Project for a long time in many different areas, and given my experience and interest in other projects, I can bring those perspectives to FESCo.

How do you currently contribute to Fedora? How does that contribution benefit the community?

Currently, many of my contributions fall in the packaging area: I keep updating the packages I administer and exploring different solutions for packaging new languages and maintaining the Sway artifacts.
My current contributions are important to keeping Fedora first, not only in terms of package versions but also in terms of best practices and ways to reach our users.

Additionally, I served for the last two cycles (F41/F42) as a FESCo member, steering the community toward engineering decisions that were both sensible in the short and long term.

How do you handle disagreements when working as part of a team?

I think disagreements are normal in communities. I have a few beliefs that guide me in entering and during any disagreement:

1. I always separate the person from their argument: this allows me to discuss the topic without being influenced by the person making the points.
2. I always keep in mind during disagreements that all people involved probably have a lot of things they agree on and a few they don’t agree on (otherwise, they would not be part of the conversation in the first place): this allows me to always see the two sides of the disagreement as having way more in common than in disagreement.
3. During a discussion, I always hold the belief that the people arguing on the opposite side of the disagreement are trying to make sure that what they believe is right becomes a reality: this allows me always to try to see if there are aspects in their point of view that I had not considered or not appropriately weighted.

Thanks to my beliefs, I always manage to keep disagreements civil and productive, which often leads to a consensus. It is not always possible to agree on everything, but it is always possible to disagree in a civil, productive way.

What else should community members know about you or your positions?

Let’s start with the fact that I’m a Red Hat employee, though what I do in my day job has nothing to do with Fedora (I’m an Ansible specialist, so I have nothing to do with RHEL either), so I have no ulterior motives for my contributions. I use Fedora on many devices (starting from my laptop) and have done so for many years. I contribute to the Fedora Project because I found in it and its community the best way to create the best operating system :).

I’ve been using Sway exclusively on my Fedora desktop since I brought it into Fedora in 2016. On the other systems, I use either Fedora Server, Fedora CoreOS, or Fedora IoT, even though lately, I prefer the latter for all new non-desktop systems.

I see the Fedora Community as one community within a sea of communities (upstream, downstream, similarly located ones, etc.). I think the only way for all those communities to be successful is to collaborate, creating a higher-level community where open-source communities collaborate for the greater good, which, in my opinion, would be a more open-source world.

The post F43 FESCo Elections: Interview with Fabio Alessandro Locati (fale) appeared first on Fedora Community Blog.

This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.

Interview with Dave Cantrell

• FAS ID: dcantrell
• Matrix Rooms: Looking right now it appears Fedora Council, FRCL, Introductions, Announcements, Fedora Meeting, and Fedora Meeting 1. I tend to go to rooms that people ask me to join. I also use it a lot for DMs and people find me that way. For me primarily I rely on Matrix for our online meetings and DMs with people. Email continues to be the most reliable way to reach me and have a conversation.

Questions

Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?

I have been a member of FESCo for a while now and enjoy doing it. Fedora is really good at bringing in new technologies and ensuring that we minimize disruption for users. I enjoy the technical discussions and working together to ensure that changes account for everything before we bring them in. Making and having a plan is often difficult and requires a lot of coordination.

I am also interested in mentoring people interested in running for FESCo and introducing some changes to how we staff FESCo. There are discussions going on right now for that, but an important thing for me is ensuring we have a succession plan for FESCo that keeps Fedora going without burning people out. If you are interested in being on FESCo, please reach out to me!

Lastly, I feel very strongly about open source software and the licenses we have around it. I believe that it has fundamentally changed our industry and made it a better place. We continue to see changes come in to Fedora that bring challenges to those ideas and I want to ensure that Fedora’s position around open source, creator rights, and licensing are not lost or eroded.

How do you currently contribute to Fedora? How does that contribution benefit the community?

My job at Red Hat is working on the Software Management team. The two big projects on that team are dnf and rpm. But we also have a lot of dnf and rpm adjacent software. I am upstream for or contribute to numerous other projects. I also maintain a variety of packages in Fedora and EPEL as well as RHEL (and by extension CentOS Stream).

I am a sponsor for new contributors and I help mentor new developers in both the community and at Red Hat (that is, developers at Red Hat wanting to participate more in Fedora).

I am a member of the Fedora Council where I focus on engineering issues when we discuss large topics and strategy.

How do you handle disagreements when working as part of a team?

Communication has always been a challenge in our industry and community. We have language differences, cultural differences, and communication medium differences. One thing I notice a lot is that some discussions lead to people taking things personally. Often the root cause of that is people feeling like they are not being heard. A solution I have found is to suggest changing the communication medium. I am perfectly fine communicating over email, or chat, or other online methods. But talking in person can go a long way. We know the value of having in-person events and a lot of people find that their interactions with people in the community improve simply because they finally met someone in person at an event. While that is not always possible, we do have video conference capabilities these days. I do use that in Fedora and it helps quite a bit.

For everyone, if you find yourself in a frustrating situation, I recommend first stepping away and collecting your thoughts. Then remind yourself why everyone is involved in the first place. We all want to achieve the same things, so let’s try to work towards that and find common ground. And if necessary, suggest an alternate communication mechanism.

What else should community members know about you or your positions?

Most people are surprised to learn that I support protons more than electrons. I like being positive in everything I pursue. It’s ok for us to disagree. It’s ok to have a position, learn something new, and then change that position. The important thing to me is that Fedora ultimately remains a fun project.

My favorite color is orange. I use an Android mobile phone. I do not use current Apple hardware, but I am a big fan of the Apple II series and 68k Macintosh series. If you corner me, I will likely talk your ear off about the Apple IIgs or any Macintosh Quadra (particularly the various crazy and horrible operating systems Apple made for the platform).

The post F43 FESCo Elections: Interview with Dave Cantrell (dcantrell) appeared first on Fedora Community Blog.

This is a part of the Fedora Linux 43 FESCo Elections Interviews series. Voting is open to all Fedora contributors. The voting period starts today, Wednesday 17th December and closes promptly at 23:59:59 UTC on Wednesday, 7th January 2026.

Interview with Zbigniew Jędrzejewski-Szmek

• FAS ID: zbyszek
• Matrix Rooms: #devel:fedoraproject.org, #reproducible-builds:fedora.im, #jenkins-coreos:fedoraproject.org, #coreos:fedoraproject.org, #quality:fedoraproject.org

Questions

Why do you want to be a member of FESCo and how do you expect to help steer the direction of Fedora?

I think Fedora as a project is in a good place. Our core responsibility is to put out a new release every six months, and we are doing that on schedule and with high quality. But there are always new challenges and issues that need to be solved. As a member of FESCo, I take the Change process seriously, trying to work with submitters to improve their proposals before they are approved, and keeping track of what remains to be done. I do my best to move the things I’m personally working on in the right direction, and I try to help others move the things they are working on.

Most of the proposals that FESCo gets to vote on are obvious. But every once in a while there are proposals which are a mistake. The tough part of the job is to distinguish between something that is risky but will be good for the project if done correctly, and ideas that are a mistake and should be rejected. FESCo is in the position to push back, and needs to do that with enough strength and visiblity to be effective.

The part of being in FESCo that I (and everybody else) likes the least is the slow-as-molasses tickets that get stuck on infrastructure changes or other external constraints. FESCo should do a better job of regularly returning to those, pushing for updates, and figuring out how to finally solve the problem. I like the idea of introducing the limits on consecutive terms of FESCo members
to bring in new people and hopefully use this energy to tackle some long-standing issues.

How do you currently contribute to Fedora? How does that contribution benefit the community?

I maintain systemd and a bunch of other packages in the python scientific stack,
a bunch of tools related to installing Linux (mkosi, pacman, archlinux-keyring), and
tooling for reproducibile builds (add-determinism).

I’m active in FESCo and I contribute to the Packaging Guidelines and in various other places that need help. Over the last year I worked on build reproducibility (https://fedoraproject.org/wiki/Changes/Package_builds_are_expected_to_be_reproducible), bin-sbin unification (https://fedoraproject.org/wiki/Changes/Unify_bin_and_sbin), and helped with introduction of nix (https://fedoraproject.org/wiki/Changes/Nix_package_tool).

How do you handle disagreements when working as part of a team?

Discuss. Evaluate. Discuss again. Reach a compromise.

Rarely there is an issue where compromise is not possible. If the issue is worth fighting for, agree to disagree, try to convince everyone else.

What else should community members know about you or your positions?

n/a

The post F43 FESCo Elections: Interview with Zbigniew Jędrzejewski-Szmek (zbyszek) appeared first on Fedora Community Blog.