Friction in Fedora over AI developer desktop initiative
A push by Red Hat employees to create a Fedora "AI Developer Desktop" with support for out-of-tree kernel drivers and AI toolkits has been met with objections from some long-time members of the Fedora community. After more than a month of sometimes heated discussion, the Fedora Council had voted to approve the initiative; however, a last-minute change to vote against the proposal by council member Justin Wheeler has (at least temporarily) sent it back to the drawing board.
The proposal
On March 31, Gordon Messmer, a senior software engineer at Red Hat, proposed
the AI Developer Desktop initiative on the Fedora discussion forum. The aim of
the initiative is to "build a thriving community around AI
technologies
" within Fedora. The initiative would focus on the
technical hurdles in the way of shipping AI developer tools, enabling
hardware; more than that, though, Messmer's proposal is meant to make
AI development a major priority for Fedora as a project.
Community
initiatives are projects that do not fit "neatly into the
biannual Fedora Linux release cycle
" and may span several
releases. Initiatives are also meant to be goals for the entire
project that align with Fedora's mission
statement. One example of an initiative is the work to replace
Bugzilla and Pagure with Forgejo as Fedora's "Git forge"; the
Fedora wiki has a list of
completed initiatives as well. Note that initiatives were
previously called "objectives", which is the term that Messmer
uses. For consistency, we'll stick with "initiative", as that is the
current terminology.
Messmer said that much of the work Fedora does is to package applications so
that the software requires minimal post-installation configuration to
be usable; however, AI tooling often requires more than minimal setup
on Fedora. He wants to make things easier for users who wish to work
with AI tools by minimizing the amount of post-installation hassle
required to get them up and running on Fedora. The platform
deliverables he identifies to provide "an operating system
image that would improve Fedora as a platform for AI software
"
would require Fedora to accommodate, if not actually include,
out-of-tree kernel modules (NVIDIA's OpenRM, "until the
Nova
driver is ready
") and support for NVIDIA's proprietary CUDA Toolkit. He
was clear that there was no plan for adding "applications that
inspect or monitor how users interact with the system or otherwise
place user privacy at risk
", or applications pre-configured to
connect to remote AI services.
Fedora's rolling-release kernel, Messmer said, is not well-suited
for "the AI space
", and called for a Fedora long-term-support
(LTS) kernel to avoid problems with out-of-tree kernel software and
user-space components that "can be impacted by the changes typical
of a kernel minor release
". The Fedora project follows the
upstream Linux kernel closely and has policy against maintaining
multiple kernels. A Fedora release will usually receive many kernel updates, including
major versions, during its release cycle. For example, Fedora 42 shipped
with the 6.14.0 kernel in April 2025; the current updated kernel for
that release (which is almost at the end of its life) is
6.19.14. Fedora's kernel
policies currently discourage, but do not entirely prohibit,
out-of-tree modules. He said that the initiative would require asking
the Fedora
Engineering Steering Committee (FESCo) to "revisit policies
that prohibit the option of a stable Fedora kernel
".
Additionally, he wanted to publish Fedora
Atomic variants to support AI workloads, with the CUDA toolkit,
around the same time as the Fedora 45 release scheduled for
October 2026. "If Fedora cannot distribute this image due to
license or policy issues that we can't resolve, I'd like to ask NVIDIA
if they would publish the image we build
". The Atomic desktops are
image-based, which means that it is more complicated for users to
install NVIDIA's CUDA package separately. Including the package when
the image is built would be much simpler. He linked to a preview
build of the desktop along with the configuration
files used to build it, as well as a Copr
repository with a 6.12 Linux kernel for Fedora 43 containing
the out-of-tree NVIDIA module. He proposed himself as the lead of the
initiative.
Discussion
Fedora's initiative process requires a discussion phase, which Messmer had initiated with his post on Fedora's forum; if the proposal is well-received by the community, then its lead can proceed to opening a ticket with the council for consideration. So far, the conversation has generated more than 140 comments from more than 30 participants; whether it has been "well-received" has been called into question.
Steve Milner said
he liked the idea and proposed plan overall. He wondered if the LTS
kernel would be specific to the AI desktop, or if it would be
available to other Fedora variants. Messmer replied
that he thought it would be useful for many people, not only AI
desktop users. He said he often heard complaints about
hardware-support regressions after kernel upgrades, and that a
stable kernel could also benefit users who needed other out-of-tree
modules for VirtualBox or ZFS. He admitted that an additional
kernel would present more work for Fedora's quality team,
but argued that "the testing process around Fedora kernels today
has serious flaws
" because the rolling-release kernel "does not
align well with the concept of a stable release
". Even if users
participate in testing days and report regressions, "there just
isn't any realistic alternative to shipping the new release series as
an update
".
Neal Gompa had
a number of thoughts to share. He objected to changing Fedora's
policy around supporting out-of-tree kernel modules: "the
likelihood our user's systems will be considered tainted and
ineligible for support from upstream kernel developers goes up
significantly.
" Kernel developers prefer Fedora, he said, because
it does not currently support out-of-tree modules.
He had reservations about equating AI specifically with CUDA; Fedora
initiatives should encourage a fully open-source-software stack, not to
endorse a proprietary one. Building it around CUDA would send "a
dark signal that we don't care enough to push for open source driven
AI technology stacks
". He added that, with his FESCo hat on, he
would be strongly against a policy change in favor of a stable Fedora
kernel: "your rationale for this is rather weak, since it isn't
even needed for OpenRM
".
Messmer responded
that the OpenRM module works well today, "but there is no guarantee
that will be the case at any given point in time
". That was the
reason he was given for why OpenRM would not be built in Fedora's
kernel package. NVIDIA, he said, was mentioned specifically in the
proposal because there was work needed to enable NVIDIA hardware, not because
the initiative was intended to be CUDA-specific. Other vendors had
already provided "more active support or better aligned
support
". Gompa had also complained that Red Hat was not allocating
kernel developers to do significant development of Fedora's kernel;
Messmer said that was a reason why the stable kernel was needed.
I'm actually quite surprised to see anyone argue simultaneously that there are not enough developer resources assigned to the rolling kernel release and that the stable kernel isn't useful or desirable. Those seem like contradictory points of view, to me. The latter is the solution to the former.
The Gompa-and-Messmer discussion went on for some time; Gompa
continued
to emphasize that, unlike the openSUSE and Ubuntu distributions, which had similar
corporate sponsorship, Fedora had a single kernel maintainer who is
"massively overworked and isn't able to engage on Fedora kernel
bugs
". It did not matter what kernels Fedora had because
Fedora does not have people to fix the problems that users
discover: "it doesn't matter if the problem is in 7.0-rc6,
6.19-stable, or 6.18-longterm. They are still not getting
fixed
". The additional complexity of the packaging, installation,
and bootloader infrastructure for multiple kernels did not make sense,
he said. "I'm saying this as someone who is maintaining kernel
trees and alternative kernel flavors for Fedora Asahi Remix and CentOS
Stream Hyperscale: it's a bad place to be, and I would rather not be
here if it wasn't absolutely required.
".
Clement Verna said
that there would be a lot of overlap between Messmer's proposal and
what the Universal Blue
community was already doing. That project develops Fedora-based images
custom-tailored for specific use cases; for example, the Bazzite gaming
distribution and Bluefin
workstation distribution are part of the project. He said that Fedora
could learn a lot from the automation tools being used by Universal
Blue, and there could be an "opportunity to consolidate the
maintenance effort for an LTS build
" as well.
FESCo member Kevin Fenzi asked
why Messmer would not do the entire project as a Fedora Remix. Projects
can use the "Fedora Remix" branding while shipping third-party
software, even proprietary software, so
long as the remix does not use official Fedora branding
packages. He added that the reason Fedora had a "'one
kernel only' rule
" was to reduce the maintenance burden. Messmer
said
that a remix was considered, but he wanted Fedora as a project to take
part in community building around AI. "I believe that the
communities we promote will promote the project in return.
"
Philosophical objections
Fabio Valentini, who is also a FESCo member, spoke
up on April 27. He apologized for "arriving a bit late to
the party
", and said that he was not sure he wanted Fedora to make
an AI desktop initiative. Fedora is "already being
perceived as 'tainted by AI'
" due to the council's decision
to approve an AI-assisted
contributions policy, which was "driving users and contributors away to distributions which are perceived as not drinking the AI Kool-Aid
". (LWN covered the discussion in
October 2025, prior to the council's decision.) He said an LTS
kernel might be interesting, but did not agree with making
"anything with 'AI' in its title
" an official initiative, and
worried that it would further alienate users.
Messner argued
that it would call into question whether Fedora was really an
open-source project if Fedora decided to nix the project because it
had "AI" in the title, rather than due to policies about proprietary
software: "that would actually be bad for our
reputation
". He cited the Open Source Initiative's Open Source Definition (OSD),
which requires that a license "must not restrict anyone from making
use of the program in a specific field of endeavor
". Valentini said
that did not make sense: Fedora has to make decisions "of the 'we
could do this, but will not / do not want to do it' kind
" if for no
other reason than to limit the scope of the project. Choosing not to
do something for ethical or philosophical reasons must be a valid
reason not to do something.
Fernando Mancera replied
that the OSD did not require a project to adopt specific technologies
to be considered open source. The decision would be whether Fedora
wanted to align itself with and promote a specific use, not about
restricting others from pursuing the AI use case. Making something a
Fedora initiative implied the project, as a whole, would be focused on
its success. "The question is whether Fedora, as a project, should
associate its identity and priorities with that field.
"
Reputational damage
Fedora Project Leader (FPL) Jef Spaleta entered
the discussion with a lengthy reply. He said that he had "zero
evidence in front of me
" that people were avoiding Fedora due to
AI, and asked to be shown metrics that would support that
claim. Fedora has to be "out in front of conversations
" even on
controversial technologies, and it could not influence conversations
it was not part of. He claimed he was "genuinely concerned about
the ethical use of AI
", but said the best possible future required
the Fedora community to be part of the conversation about ethical use
of AI.
The people who are going to get us to the better AI future are the people at the start of their journey and see value in the technology and Fedora needs to be influencing those people so they take the technology into an ethical direction that is most congruent with our shared ideals.
He added that, as FPL, he was "absolutely not concerned about
the reputational damage to this project that comes with setting up an
entirely new output attractive to developers who want to make use of
AI tools
".
Valentini replied
that Spaleta had missed his point; the whole effort could happen
without being an official Fedora initiative. There is no mechanism to
prevent someone from working on an AI desktop, he just thought it
would be better if Fedora did not promote technology that was
"deeply problematic
", in its current form, as a project
initiative.
After taking a week away to let his thoughts settle, Mancera responded
again; he agreed that Fedora should let data guide its decisions, but
that went both ways. "Otherwise, we risk holding different
arguments to different standards.
" He said he was struggling with
Spaleta "expressing no concern about potential reputational
impact
"; that could be read as dismissing an issue that some
Fedora contributors care deeply about. "Even if the change is
non-disruptive in a technical sense, it can still influence how the
project is perceived and what it signals about Fedora's
priorities.
"
Spaleta responded,
in part, that he was not dismissing anyone's concerns, he disagreed
with what to do with those feelings. He said he lived in an area that
had "the highest density of data centers
" and was directly
impacted by their power and water usage. But, telling people not to
use the technology was not going to work. "Offering people a more
ethical version, which they can actively contribute to making better,
may help.
" Mancera replied:
I do not think we can move this forward in a community way. I am withdrawing all my activities in Fedora project starting right now. The present situation in Fedora is clearly not for me.
There was no need, Simon de Vlieger said,
for the AI desktop to be an initiative right now. Instead, he
suggested, it should be a remix with a special-interest group
that built up a community before making it an initiative. If it turned
out to be popular and sustaining, then it could become an
initiative. He felt that it was being treated as "a train that
must leave the station
" to the disregard of community
members and their concerns.
Spaleta continued
to argue that an AI developer desktop was strategically important
to Fedora. "I believe that the base image that comes out of this
work needs to be an edition with its own working group in the 2028
timeframe.
"
Council
While the discussion raged on, Wheeler announced
that the council had discussed
the initiative on May 6. The council had
voted to approve it (six in favor, none opposed) as a 12-month
initiative led by Messmer with Spaleta as its executive sponsor. Gompa
was
unhappy with the council "essentially ignoring the
community discussion
", and said that the proposal was not
acceptable to the community to approve as-is. "I'm especially
disappointed at how we're being told that as our opinions and
interests in the project as highly engaged contributors do not
matter.
"
On May 8, Wheeler changed
his vote to -1. The council requires full consensus to pass
significant decisions, which means that a council member can halt the
process and require discussion. Based on "recent
public and private feedback, we do not yet have the necessary
consensus to proceed
". He said that feedback from Fedora's kernel
experts had not been sufficiently integrated into the plan. "I am
casting this vote to ensure we build a structurally sustainable
initiative that succeeds without alienating or burning out our core
experts.
"
Wheeler changed the date for the council
ticket to May 22, and said that he was optimistic that the
council could come to a decision "without a deadlock and FPL
override
" before then. According to the council's charter, the FPL
can "'unstick' things if consensus genuinely cannot be reached
"
and a decision must be made.
Spaleta has firmly planted a stake in the ground that Fedora should be involved in the "AI conversation", as it were. It does not seem to be enough to do the technical work to make Fedora suitable for working with AI technologies; the project has to send a message that it's in favor of such things.
There is clearly a top-down push from Fedora's corporate sponsor to
be AI-friendly, which is not surprising since the company is all-in on AI. Last
year, Red Hat vice president of core platforms, Mike McGrath, weighed
in on the AI-assisted contributions discussion to complain about
Fedora's governing bodies being well-known for what they do not
want. He wanted to see Fedora "leading and shaping the future and
saying 'AI, our doors are open, let's invent the future
again'
".
Ultimately, it seems likely this initiative will be approved in some form. The pressure for Fedora to accept and embrace AI as part of its identity seems destined to continue until the project moves in the direction its sponsor wants—or until the winds change, bubble pops, or AI becomes yesterday's news. Since the AI craze is probably not going to go away soon, odds are Fedora will be making room for it sooner than later.
