We’re working on Fedora Strategy 2028 — our next five-year plan. We are now reviewing those Objectives and their associated Impact. Read this guide for details on the current planning phase.
This Objective is part of the Theme “Fedora leads in Linux distribution development” and the Focus Area Technology Innovation & Leadership. For general discussion of this focus area, please see the topic Fedora Strategy 2028: Focus area review (Technology Innovation & Leadership).
Objective and Impact
Objective: Immutable variants are the majority of Fedora Linux in use
Impact: New way of doing things brings excitement and new energy.
There is a strong trend towards “immutable” or “image based” Linux systems. In fact, Linux Weekly News went so far as to predict that 2023 will be “the year of the immutable distribution”:
The classic Linux distribution follows in the footsteps of the Unix systems that came before; a suitably privileged user can change any aspect of the system at any time. For a few years now, though, we have seen movement away from that model toward a system that is, at least in part, immutable. Android is arguably the most prominent example of an immutable system; the Android core can only be changed by way of an update and reboot — and the previous version is still present in case the need arises.
Distributions like Fedora’s Silverblue have been exploring the immutable space as well. The upcoming SUSE Adaptable Linux Platform (ALP) is based on an immutable core, as is the just-released, Ubuntu-based Vanilla OS system. It seems likely that others will follow, perhaps using the blueprint that was laid out at the 2022 Image-Based Linux Summit. By the end of the year, there may be a number of immutable alternatives available to play with — and to use for real work.
Fedora has long been a leader here (Fedora Atomic Host was an F22 feature!), and Fedora CoreOS is currently our fourth most-popular variant (after Workstation. Cloud, and Server). Silverblue (and Kinoite and friends) have smaller numbers, but a definite outsized impact in terms of press and enthusiast excitement.
Meanwhile, though: our traditional system works quite well. This puts us in a “local maximum” situation — it’s hard to get to something new. (See also: the Innovator’s Dilemma.) With this Objective, the Fedora Council would like to explicitly commit to investing in the immutable approach, with an eye towards making it the default for most use cases.
Our goal now
For this Objective and related Impact, validate that:
- If the Impact is achieved, it’s reasonable to expect an increase in active Fedora contributors.
- Success in the Objective logically results in the intended Impact.
- That link is reasonably sufficient — that is, it represents everything needed to have the Impact.
- While there might be other ways to have similar Impact, the chosen Objective is the right one for Fedora right now.
- The wording is precise and clear. The Objective is concrete, and the Impact is (at least a little bit) inspirational. Together, they fit into this Focus Area.
Bonus. If you can improve the longer explanatory paragraphs at the top of this post, that’s helpful too!
As outlined in the roadmap, this post will close in one month.
link is broken in the LWN article — see https://documentation.suse.com/alp/micro/html/alp-micro/concept-alp.html and The SUSE ALP Bedrock Guide | General description ↩︎