The Fedora Project is proposing a new contributor status called “Fedora Verified” to better recognize all forms of community contribution, and we need your feedback. Following the Fedora Council 2026 Strategy Summit, Fedora leadership is reflecting on how we recognize, support, and empower the people who make Fedora possible. Please read through our proposal below and share your thoughts in the Fedora Verified community survey.
Continue readingPrague 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.
Continue readingArtificial Intelligence is a transformative technology, and as a leader in open source, the Fedora Project needs a thoughtful position to guide innovation and protect our community’s values.
For the past year, we have been on a journey with the community to define what that position should be. This process began in the summer of 2024, when we asked for the community’s thoughts in an AI survey. The results, which we discussed openly at Flock and in Council meetings, gave us a clear message: we see the potential for AI to help us build a better platform, but we also have valid concerns about privacy, ethics, and quality.
The draft we are proposing below is our best effort to synthesize the Fedora community’s input into a set of clear, actionable guidelines. It is designed to empower our contributors to explore the positive uses of AI we identified, while creating clear guardrails to protect the project and its values from the risks we highlighted.
Continue readingThe Fedora Council is considering a change to our policy for promotion of a Fedora deliverable to “Edition” status. Please read that entire document for context before commenting.
This change is being made to reflect actual practice. For example, there is clear overlap between the use-cases and potential user-bases for the current Server, Cloud, and CoreOS Editions, but each takes a different approach. We are currently considering adding an exception for a KDE Desktop Edition, which would overlap with Fedora Workstation.
Currently part of the policy currently reads in a way that prevents this exception from being possible:
A Fedora Edition:
- addresses a distinct, relevant, and broad use-case or user-base that a Fedora Edition is not currently serving;
- is a long term investment for the Fedora Project; and
- is consistent with all of Fedora’s Four Foundations.
We propose an additional line:
The Council may make exceptions to the “distinct” rule when we determine that doing so best fits the Project’s Mission and Vision.
This topic is open for community discussion, following our Policy Change Policy. After two weeks, the Council will vote in a new ticket, and if approved, the policy will be updated.
Approval of this change would not automatically mean the approval of a KDE Desktop Edition, but would allow that possibility.
We’re excited to unveil the Fedora Community Operations initiative, an endeavor to boost community engagement, support everyone with more events and contribution points, and build on our amazing culture.
At its heart, the Community Operations Initiative is all about making Fedora an even better place to collaborate and connect. We’re focusing on two main contribution areas: Contributor Experience and Community Social Analytics. Contributor Experience means working on unified documentation, improving onboarding processes, and organizing fantastic virtual events like the Fedora Linux 40 and 41 Release Parties. Community Social Analytics will explore data from our infrastructure tools, applications, and services to help Fedora leadership and the community make smarter decisions, ultimately making Fedora an even more welcoming and efficient community for everyone.
Continue readingAs described in Fedora Strategy 2028: April 2024 Update, we came out of our annual face-to-face meeting with a new presentation for our strategy for the next five years. That article gave the background — this is the high-level strategy itself.
We’re going to double the number of contributors who are active every week.
Our goal is to ensure that Fedora is healthy and sustainable. As a project, we’re generally in great shape. However: there are many areas where everyone feels under-resourced, and we have too many places where we have a very poor “yak farm factor” — if one or two people are ready for a change and go off to start new lives, will the areas they’re working in collapse? Plus, there’s always so much more exciting new stuff that we could be doing, and maybe need to do to remain relevant as the computing landscape changes.
We can measure aspects of this in many different ways: interconnectedness, onboarding, burnout, team resilience, and so many more. But, the weekly-active-contributor number gives us a simple, basic check. If that number is going up, we must be doing something right.
The metric itself isn’t the goal in itself.. We don’t want to merely inflate a number, after all. So, we also plan to watch those other community health metrics, and we’ll adjust as needed to make sure that the Guiding Star is really leading us to the right path.
This means different things to different people and is often different across projects. However, for this purpose, we’re using a broad definition.
A Fedora Project contributor is anyone who:
Fedora has numerous already-public data sources for activity, and we plan to use those as widely as possible. Unlike smaller projects, we can’t simply count commits in a git repo — and, I think that’s a good thing, because in order to get a meaningful number, we need to count more than just code and other technical contributions.
Upcoming posts:
from Fedora Project Leader Matthew Miller, on behalf of the Fedora Council
First, a personal note! As you may have seen, I was out sick with Covid for a month after getting home from our annual Council face-to-face meeting. It’s not been fun — some respiratory symptoms, but primarily, overwhelming fatigue. Somewhat ironically, the timing suggests that I managed to avoid catching anything at FOSDEM itself (where I wore a mask most of the time), or at the Council meeting, but rather on the plane or in the airport on the way back. Although emergency measures have been lifted, there really is still a pandemic going on. Be careful, everyone, especially when traveling! In any case, I’m back to myself now, and am excited for Fedora’s next big steps.
So! I’ve been talking about “Strategy 2028” for a while — we started this effort seriously about a year ago. If you’re just joining in, or want a refresher, Fedora Strategy 2028: a topic index for our planning process is a great place to start. I won’t rehash all of that here.
The important thing is: 2023 was kind of a hard year, and although we made some progress, we lost momentum. The Council hackfest helped get things back on track, and we’re moving forward now. We’re not making any fundamental changes, but we are restructuring how we present things — and we’re moving on from theory to practical work.
Continue readingDuring the Council’s February 2024 hackfest, we discussed the future of Fedora’s git forge – that is, the platform Fedora uses for version control and tracking for packages, source code, documentation, and more. This topic has been around for quite some time. If you are just coming into this conversation, or would like a refresher, #git-forge-future is a good place to start.
Instead of one huge post, the Fedora Council divided the follow-ups from our hack-fest into a mini-series of posts throughout April that will cover all the topics we discussed and made decisions on. In each post, we will walk through one core topic, and share our discussion and thought process on how we reached our outcomes. The first in this series, because why not start strong 🙂 , is an update on our git forge evaluation. Read on for important information.
Continue readingWe updated the “How is Fedora Organized?” page on Fedora docs with the org chart below. This chart shows governing bodies, teams, editions, spins/labs, and initiatives. Is your Fedora thing missing? Feel free to comment on this Discussion post to ask for an update.
The Fedora Council wants to hear what you have to say! Take the anonymous survey now.
As before we are interested in the usage of tools and communication channels, your roles, your favorite apps and programming languages. This year we also specifically ask about the development mailing list.
Continue readingCopyright © 2026 Fedora Community Blog
This work is licensed under a Creative Commons Attribution 4.0 International License.
Theme by Anders Noren — Up ↑
Recent Comments