We’re developing a high-level strategy for Fedora for the next five years. This post serves as an index to various posts about this — both existing and planned. (It’s everything in strategy2028, with context.)
- From the State of Fedora 2022: strategic plan high-level goals
- Theory of Change: how we plan (and explain our plans!)
- Fedora Strategy 2028: February/March Planning Work and Roadmap 'til Flock
- Fedora Strategy 2028: What is a contributor? What is a contribution?
Current Topics: Objective & Impact feedback and Discussion
Please start with Fedora Strategy 2028: Focus Area review guidelines, and then dive into the individual Focus Areas:
Theme: Fedora is for everyone
Focus Area: Reaching the World (February 27 – March 27)
- Fedora Strategy 2028: Focus area review (Reaching the World)
Theme: Fedora leads in Linux distribution development.
Focus Area: Community Sustainability (March 13 – April 13)
- Fedora Strategy 2028: Focus area review (Community Sustainability)
Focus Area: Technology Innovation & Leadership (March 20 – April 20)
Fedora Strategy 2028: Focus area review (Technology Innovation & Leadership)
- Objective Review: Fedora is a popular source for containers and Flatpaks
- Objective Review: Immutable variants are the majority of Fedora Linux in use
- Objective Review: We integrate programming language stack ecosystems
- Other proposals:
- Fedora Strategy 2028: Focus area review (Technology Innovation & Leadership)
Rough Schedule for Future Posts
Upcoming Objective & Impact feedback and discussion
Timeframe: February, March, and April
Each topic will give a little more explanation into what each means, and then … we’ll talk. I’m planning on just one post for the a11y topics, because I think they’re connected particularly tightly. The rest will three separate topics — if things go as planned, I’ll schedule them for Monday, Tuesday, and Wednesday each week. We’ll have a month of discussion for each topic and then two weeks for the Council to create a final version.
When the following posts are available, I’ll move them to the section above.
Theme: We build on the success of Fedora.next.
Focus Area: Editions, Spins, and Interests (Posts planned for week of March 27)
- Each Edition has a story for each release.
- It’s trivial to create and maintain a new Fedora Spin or Remix.
- More (active) SIGs, fewer images.
Focus Area: Ecosystem Connections (Posts planned for week of April 3)
- Better collaborative workflow with CentOS Stream and RHEL.
- Get people working on Amazon Linux directly involved in Fedora as an upstream.
- Collaborate on tooling, practices, and offerings with peer distros and upstream projects.
We plan to find a specific person to be responsible for each Objective, as well as an Executive Sponsor from the Council for each. We’ll talk about this more as we get to May… probably not a topic for each, but… maybe! We will also think about the initiatives, projects, and programs that each Objective will require — the Outputs and Activities columns in the Logic Model. Those probably will be individual topics. (I’ll update this section as we get closer.)
Completing the Model
Council approval of Outputs and their links to the Objectives.
Complete definition of Activities and Resources for each Output.
Outlines for expected projects, programs, and initiatives related to all of this.
Announcing the Plan
Matthew’s Keynote at Flock
- Fedora in 2025: what do we want, and how will we get there?
- Fedora 2025 strategy: Improving Fedora mindshare in the Linux ecosystem
- Fedora 2025 strategy: accessiblity improvements in support of our vision?
Completed Focus Area Reviews
Theme: Fedora is for everyone
Focus Area: Accessibility (February 17 – March 17)
- Fedora Strategy 2028: Focus area review (Accessibility)
- Fedora websites and docs use the current best-practices for a11y.
- Fedora Linux Editions use the best-available open source a11y tech.
- Our project tooling follows best a11y practices.
- Logic models vs. OKRs (Logic models give a better picture and are more useful!)
- I let chatgpt have a go at creating our project strategy
Each will be set to close automatically — if you have something to add after that point, create a linked topic as followup ↩︎
As noted in the Roadmap post, “final” in the sense of “this is the plan we’re deciding on now” — of course we’ll adjust over the next five years ↩︎