Hi Fedora folks! 👋🏻
Software Freedom Conservancy (SFC) honored *Mark J. Wielaard* (mjw) with
the second annual Distinguished Service Award in Software Freedom at *FOSSY
2026*. This award recognizes decades of dedicated service to software
freedom in both volunteer and professional capacities.
Within Fedora, Mark plays a critical role in maintaining the foundation of
our development and debugging stack. He is the package maintainer for
several core packages, including:
* debugedit
* dwz
* elfutils
* rpm
* systemtap
* valgrind
Beyond his essential packaging work for Fedora, Mark's broader impact on
the FOSS ecosystem includes:
* *Tooling & Standards*: Long-time maintainer of the Valgrind and elfutils
projects, and member of the DWARF Debugging Standard Committee.
* *Securing Open Java*: Led the IcedTea project to bridge core Java
libraries with free software alternatives.
* *Critical Infrastructure*: Voluntarily maintaining Sourceware, a
developer hosting platform.
Please join in congratulating Mark on this outstanding and deeply deserved
recognition! 👏🏻🎉👏🏻
You can read the full SFC announcement and celebration remarks here:
https://sfconservancy.org/news/2026/aug/12/mark-j-wielaard-receives-2-annua…
--
*Justin Wheeler* (*he/him*) || 📧 jwheel(a)redhat.com || 🔗 jwheel.org
*Formerly Justin W. Flory*
*AI Alignment* Community Architect, *Fedora*
TZ=America/Atlanta (UTC-4) 🕗
*Fedora is a registered Digital Public Good
<https://app.digitalpublicgoods.net/a/12003>*
While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
*Originally posted on Fedora Discussion
<https://discussion.fedoraproject.org/t/fedora-council-statement-on-the-futu…>.*
*TL;DNR: Effective immediately, the Fedora Council is proposing we pause
the Community Initiatives process as an official project process. A
replacement process will need to be designed, in time, with community
input. Existing approved Initiatives will continue to run their scheduled
term.*
The Fedora Council would like to close the discussion regarding the AI
developer desktop proposal, as we have come to the conclusion that the
current community initiatives process is ineffective and therefore this
work should not be proposed through this mechanism.
When/if the AI Desktop work matures, it can follow our current path to
becoming an official offering, whether through a proposal as a Remix or
otherwise, namely first filing a Council ticket for trademark/branding
approval followed by a Change Proposal for FESCo technical review. Until
those steps occur, this remains an independent exploration rather than an
official Fedora offering. We would like to encourage the proposer and those
interested in this work to consider working on this anyway in and for
Fedora. This includes having an open space to talk about the work, holding
meetings, and collaborating with other groups, such as the AI/ML SIG, that
have similar or the same interests.
Fedora is such a wonderful project *because* we have so much choice. Should
we someday add an AI developer desktop as a Fedora offering, we expect it
will be inline with the project's Four Foundations
<https://docs.fedoraproject.org/en-US/project/#_what_is_fedora_all_about>.
This would certainly add another interesting flavour to our already diverse
ecosystem.
The Fedora Objectives/Initiatives framework was never intended as a
mandatory prerequisite to do the work in Fedora. It supposed to help by
focusing the community on a certain work when needed, not to decide what is
allowed.
The AI developer desktop initiative proposal highlighted that the Community
Initiatives process has failed to serve as a good framework in Fedora where
new ideas can surface, receive respectful feedback, and gain Council
support for work that fits the project's present and/or future. This is
something that the Council must address.
As a first step, we would like to halt the community initiative process
immediately. Existing initiatives in flight (Fedora Forge, Atomic, and
Fedora Docs 2026) will continue with full Council backing. Their underlying
work will be completed as planned in their current timeboxed state, though
the administrative framework around them may evolve.
As a second step, we would like to work out a new mechanism to allow
Council to set strategic direction in an open, transparent way that more
intentionally includes the community voice. We recognise that we have to be
better at being more open in our discussions and decision making.
Part of this work will involve addressing our implict social norms.
Currently, a lot of great work, happens under the radar before official
approval processes kick in. While our current approval pipeline (Council
trademark review, then FESCo change proposal) works well, we are missing
early and inclusive discussion for everyone across the project. We want to
bring these ideas and this work to light at the beginning, where the
community can discuss them, so they can be championed earlier (and attract
more contributors!).
To that effect, Council will be looking at the Initiatives Lifecycle or
'sandbox' proposal
<https://discussion.fedoraproject.org/t/a-modest-proposal-a-technology-innov…>
closely, as this may have potential to be either a better way, or be
complimentary to another process we may develop, that can surface these
initiative-style ideas and work items in Fedora early. Your feedback on
this proposal is most welome so we can try to understand how the Fedora
Community needs these kinds of processes to behave to be successful.
Council intends to return to the conversation of whether Community
initiatives should be retired or revamped once this discussion has reached
some kind of conclusion.
— Aoife, on behalf of the Fedora Council.
--
*Justin Wheeler* (*he/him*) || 📧 jwheel(a)redhat.com || 🔗 jwheel.org
*Formerly Justin W. Flory*
*Fedora* Community Architect
TZ=America/Atlanta (UTC-4) 🕗
*Fedora is a registered Digital Public Good
<https://app.digitalpublicgoods.net/a/12003>*
While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
Hello all,
Fedora 42 has reached end of life for updates today, 2026-05-28. It was
originally supposed to happen yesterday but there was a slight delay.
Apologies.
No more updates of any kind, including security updates or security
announcements, will be available for Fedora 42 after this date. No pending
updates will be pushed to stable.
Fedora 43 will continue to receive updates until approximately one month
after the release of Fedora 45. The maintenance schedule of Fedora releases
is documented here [1]. The documentation also contains instructions [2] on
how to upgrade from a previous release to a version receiving updates.
Best regards,
Patrik Polakovic
Fedora Release Engineering
[1]
https://docs.fedoraproject.org/en-US/releases/lifecycle/#_maintenance_sched…
[2]
https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-releas…
The Fedora Project is now accepting nominations for all elected bodies
until May 21, 2026. Candidates can self-nominate or be nominated by others
with prior consent. Interviews are mandatory and must be completed by May
28, 2026. Elected members serve a two-release term.
https://communityblog.fedoraproject.org/f44-election-nominations-now-open/
--
*Justin Wheeler* (*he/him*) || 📧 jwheel(a)redhat.com || 🔗 jwheel.org
*Formerly Justin W. Flory*
*Fedora* Community Architect
TZ=America/Atlanta (UTC-4) 🕗
*Fedora is a registered Digital Public Good
<https://app.digitalpublicgoods.net/a/12003>*
While I may be sending this email outside my normal office hours, I have no
expectation to receive a reply outside yours.
Hello all,
Fedora Linux 42 will go end-of-life for updates and support on
2026-05-13.
No more updates of any kind, including security updates or security
announcements, will be available for Fedora Linux 42 after this
date. No pending updates for Fedora Linux 42 will be pushed to stable.
Fedora Linux 43 will continue to receive updates until approximately
one month after the release of Fedora Linux 45. The maintenance
schedule of Fedora Linux releases is documented here[1]. The docs also
contain instructions[2] on how to upgrade from a previous release of
Fedora Linux to a version receiving updates.
Regards,
Samyak Jain
Fedora Release Engineering
[1] https://docs.fedoraproject.org/en-US/releases/lifecycle/#_maintenance_sched…
[2] https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-new-releas…
Hello everyone,
We’re excited to announce that Fedora Linux 44 is now officially available!
This release continues Fedora’s tradition of delivering the latest
open-source innovations, bringing together updated packages, improved
performance, and enhancements across the desktop, server, and cloud
ecosystems. Whether you’re a developer, system administrator, or
open-source enthusiast, Fedora Linux 44 offers a refined and reliable
experience built on cutting-edge technology.
To get started:
- Read the official announcement and release highlights:
https://fedoramagazine.org/announcing-fedora-linux-44/
- For a fresh installation, download the installer images from:
https://fedoraproject.org/
- If you encounter any issues or have questions, visit:
https://ask.fedoraproject.org/
- Upgrade your existing Fedora system using the standard upgrade
process: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/
Thanks to all contributors who made this release possible.
Regards,
Samyak Jain
Fedora Project
Planned Outage - fedora.im / matrix - 2026-04-06 11:15 UTC
There will be an outage starting at 2026-04-06 11:15 UTC,
which will last approximately 30 minutes.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2026-04-06 11:15 UTC'
Reason for outage:
Element matrix services is performing scheduled maintenance on our matrix server (fedora.im).
Affected Services:
chat.fedoraproject.org
fedora.im
matrix services
Ticket Link:
https://forge.fedoraproject.org/infra/tickets/issues/13247
Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix.
or add comments to this ticket for more information or feedback.
Updated status for this outage may be available at
https://www.fedorastatus.org/
Planned Outage - fedora.im / matrix - 2026-03-26 11:50 UTC
There will be an outage starting at 2026-03-26 11:50 UTC,
which will last approximately 30 minutes.
To convert UTC to your local time, take a look at
http://fedoraproject.org/wiki/Infrastructure/UTCHowto
or run:
date -d '2026-03-26 11:50 UTC'
Reason for outage:
Element matrix services is performing scheduled maintenance on our matrix server (fedora.im).
Affected Services:
chat.fedoraproject.org
fedora.im
matrix services
Ticket Link:
https://forge.fedoraproject.org/infra/tickets/issues/13213
Please join #admin:fedoraproject.org / #noc:fedoraproject.org on matrix.
or add comments to this ticket for more information or feedback.
Updated status for this outage may be available at
https://www.fedorastatus.org/