From the State of Fedora 2022: strategic plan high-level goals

As we work on the next big Fedora strategy, I wanted to pull a relevant section from my keynote at Nest with Fedora this year into non-video form. The video is on YouTube if you want to watch the whole thing:

but here are the relevant points. I decided to illustrate these with MidJourney AI because it’s very good at making mystical, weird-looking things. It likes to make people staring into the distance, which seems appropriate. Many of the slides reproduced below have an image generated with its headline as the prompt.

Let’s start with some context. The “” strategy started with proposals at Flock to Fedora in 2013. Its goal was to plan the second decade of the Fedora Project. One of the key features was a switch from “Fedora Linux is everything!” to deliverables focused on specific use cases. We started with three Editions: Workstation, Server, and Cloud.

The idea behind Editions was to reduce user confusion. Instead of a single ISO that you had to customize at install time, users could pick an opinionated, curated experience. (Of course, if you love customizing your package set, that’s still an option.) This has been incredibly successful, and I think it’s a big part of the improved reputation and technical quality we’ve enjoyed. And the fact that we’ve added IoT and CoreOS as Editions proves that this works.

But that was a five-year plan that we started eight-ish years ago. As we prepare to enter the third decade of Fedora, how do we build on the success of


I talked about this a little bit last year, and kind of started on “where we’re going”, and I called it That is a terrible name. Please help me come up with a better name for this, because if we don’t, it’s going to stick. It’s a bad name.

slide text

Getting to a plan for the next five years!

  • Kicked off with my State of Fedora
    last year
  • Threads on Fedora Discussion (see #council topics in particular)
  • Covid makes this hard.
  • Finally, Marie, Ben, and I sat down with the ideas from the discussion threads and came up with a skeleton
  • Now, it’s time to fill that out

We kicked this off at Nest with Fedora last year, and we’ve been working on it since. We’ve had some threads and some conversation on Fedora Discussion already. But COVID made the next steps really hard.

In the past, the Fedora Council has worked on our strategy and direction by getting together in a room several times a year. Usually we have a meeting that is just the Council in one physical location for a few days. We also got together around DevConf.CZ and Flock. With those meetings, we have higher bandwidth conversations, which really help with this kind of deep thought work. We’ve tried to do that virtually, and it just isn’t the same as getting people in the room together, so this has been a way slower than I’d have liked.

Marie, Ben, and I were able to get together for a few days over the summer. We took ideas from the discussion so far, and put together a skeleton for what we think we’re kind of coming together on collectively for this strategy.

We think these ideas are the direction we’re going. If you think I’m missing something, join the discussion and make sure that that gets included. If you think something’s the wrong direction, this is the time to say something.

slide text

The guiding idea

In five years, double the number of Fedora Project contributors actively involved every week.
But… how?

So here’s the guiding idea!: In five years, I want to have twice as many people who are working actively every week in Fedora as there are today. Right now that number is around 300 or so. I’d like to see that number be 600 or 700 people who are active and really involved every week.

That’s going to be the key tracking metric for this. I know we also want user growth, and the number of systems going up in my charts, but the really big thing is we want to see the project feel really healthy and vibrant. So that’s the headline thing. Besides, user and contributor growth feed each other. A vibrant and welcoming community produces a better product, which grows the user base. When you have more users, that’s a bigger pool of potential contributors.

But how are we going to take this guiding idea and make it into reality?

Three big goals

slide text

Three big goals

We think these things will help us grow — but not just that.

We think they’re necessary.

  1. Accessibility for Everyone

  2. Innovation and leadership in the Linux distro space

  3. Grow from “3 Editions” to “multi-project”

We came with three big topics: the overall goals, the main areas, the focus areas. They are: accessibility for everybody, innovation and leadership in the Linux distro space, and growing from the five Editions to being a “multi-project”…um…project (in a big-umbrella kind of way).

Accessibility for Everyone

slide text

Accessibility for Everyone

  1. Practical a11y — improve our software

    a. Websites
    b. Docs (the content)
    c. The Fedora Linux OS
    d. Fedora Project tooling

  2. Remove other limits

    a. More preinstalled systems
    b. Improve help and docs
    c. Better support our global communities

We’ve had a number of people who are blind or who have other accessibility issues come to us and tell us we’re doing a terrible job. We hear that, and we can do better. We should do better. It goes directly to our vision. How can everyone benefit from free and open source software if they can’t use it?


To start off, there’s the practical accessibility — what you probably think of when someone says “accessibility” (or a11y). We need to improve our software, our website could be better (Discourse is really good for this — it uses modern web standards and accessibility tags, while some of our older sites don’t), improve the content of our documentation to be more inclusive for people using our software in different ways. We want to improve the OS itself — for example, to make sure that the installer works with text-to-speech.

And it can’t just be the software and OS — we have our own tooling for packaging, docs, design, and more, and we need all of those project tools to be inclusive as well. This will be a lot of work!

One nice thing is Red Hat has hired someone to work on the desktop team for some of this stuff. That’s a step, but it’s going to require work from all of us to make it really happen.

For everyone

But accessibility is about more than that. It’s also about availability. We want to make sure that we have Fedora Linux and the Fedora Project available to everybody in the world. This is part of our Fedora Vision overall — that we are making a better world for everybody, building open source software together as communities. We want to share that vision.

There are some simple things we can do, like making it easier to get Fedora Linux pre-installed from hardware vendors. I think that’s part of making it available for everyone. This goes for IoT devices as well.

We want to make sure that our help is better — that people are able to get the support they need, and that it is friendly — that when they get into IRC, they don’t get chewed up by not understanding the norms of the channel. We want people to have a friendly experience in getting support. We need better documentation — again, a continuing theme.

And we want to make sure that we are supporting people in Fedora communities around the world. We need more people sharing Fedora and spreading it in their local communities — both local meetups & conferences and localization & translations kind of work. We want to make sure that that is really getting the support that it needs. I think that we used to be better about this in the past, and we have kind of fallen. We need to build it back up again.

Innovation and leadership in the distro space

slide text

Innovation and leadership in the Linux distro space

  1. … in Community

    a. Mentorship

    • Onboarding
    • Growth
    • Continuity
    • Connections

    b. More work on DEI and positive community norms
    c. Measurable community health

Next up: innovation and leadership in the distro space. For this one, I had to break it into two slides. (Aside: it’s impressive to me that Midjourney somehow found a consistent — and even Fedora-friendly! color scheme throughout these.)

Leadership in community

First, we want to focus on leadership in the practice of community and how we run our project.

One of the big themes here is mentorship — we have the idea that everyone in Fedora should both be a mentor and have a mentor. Vipul, Jona and other folks worked on a Mentor Summit last year, and that was a huge success. I want to expand that.

There are a whole number of reasons we want to do this.

First, it will make the onboarding experience better.

Second, we want to help people already in the project grow. Being a mentor to someone else is one of the best ways to learn new things yourself.

Finally, we want to ensure that we have continuity. We want to make sure you’re not just sharing your knowledge, but also making sure that what you’re doing will survive even when you win the billion-dollar lottery and go off to build an alpaca farm somewhere. You can be sure that what you’re working on is going to continue. We need to move from the pride of “I’m the person who does this one thing” to the pride of “I’m part of this team and I’ve helped this team be successful in doing something I really care about.”

To do this. we need to build connections — particularly, from the non-engineernig or “mindshare” parts of the project. In open source, there’s often the assumption that contributing is all about coding. While that’s important, for any project needs more than that to be successful. We need all of these different skills. And we need connections between people working these things and those doing engineering. Mentoring doesn’t need to be just focused on the deep technical work you may be doing.

Fedora also needs to work more on diversity and inclusion, and on positive community norms. This is a big focus, and an area where Fedora has already shown leadership. A lot of communities have codes of conduct inspired by or based on our work in this area. And we have practical experience in this area from doing this for a long time. We really wanted to believe that “be excellent to one another” was a sufficient code of conduct, but we learned that there’s got to be more, that there has to be standardization around it — and, our leadership around this also needs to show that it’s not just about hard rules — it’s about how we all treat each other.

Innovation in technology

slide text

Innovation and leadership in the Linux distro space

  1. … in Technology

    a. Beyond RPM!

    • Direct to Flatpak
    • Direct to containers
    • Native language stacks
    • rpm-ostree

    b. Containerize all the things

    • Ship containerized services
    • podman :heart: systemd
    • Consider CentOS and UBI as part of 2 Fast 2 Slow solution?

Much to my surprise, I talked about this the least in my keynote. That’s not because it’s unimportant, I think it’s just self-evident. Advancing the state of the Linux distribution is sort of what we do around here, you know? It’s embedded in our “First” and “Features” foundations.

Some people think distros don’t matter anymore, that it’s just the language stack. And, sure, Linux distros have become reliable so that people don’t have to think about them as much these days. But distros still matter! Curated repositories are very important for reliable and secure development. And there’s still plenty of room for improving the user experience.

We can make Fedora Linux safer and easier to use. Part of this will involve expanding and improving our rpm-ostree variants — this model is the future of the OS. But it also includes other technical changes, some of which I can’t suggest because they haven’t been invented yet.

Growing beyond Editions worked. It made our offerings more clear and gave folks something to come together around. So now we have the opportunity to build on that momentum.

slide text

Grow from “3 Editions” to “multi-project”

  1. Spins, remixes, and downstreams

    a. Build more connections to CentOS, RHEL, Alma, Rocky, Amazon Linux, etc, etc.
    b. Smaller projects too!

  2. Curated areas that aren’t boot media

    a. Astronomy, design, comp-neuro, gaming…
    b. Preserve team identities where things are working!

You shouldn’t need to build a distro to showcase your awesome idea or new technology. We have one of those already. Fedora should be the place where you can build your cool thing on top of a great distro. Even if your big new idea is a change in how distros are built, Fedora should be the place for you.

We have to make Spins, remixes, and downstreams easier to build and distribute. I want these sorts of things to be done inside the project whenever possible, but downstreams and remixes should be easy if that’s what you need. We want to encourage and empower people to experiment.

In addition to that, we need to move beyond the idea of creating new ISO images. A lot of our deliverables are currently designed around boot media. We want to be able to present those curated software sets, like for graphic design or astronomy, in ways that are easy to get without having to make dedicated ISOs.

slide text

Forum discussions! (Please participate!)

Logic model all of the things!

Next steps…

This is the part where I have homework! In the next month or so, there will be more Discussion threads on each of the areas here I covered today. Look for these upcoming topics in the council tag. We’re going to build a Logic Model bringing these high-level ideas down to practical steps.

As you know, we don’t do top-down dictation in Fedora. The Council’s job is to find where the community wants to go and build consensus around that. The only way this works is if you participate. I look forward to seeing what you have to say and working with you to build a strategy for the future of Fedora.


When I was watching the full-length video, came to my mind. Other options that are succinct and intentional:

  • Fedora.together (I like this with the emphasis on mentoring in the new plan)
  • Fedora.more (more people/contributors?)
  • Fedora.lead (leading the way into the third decade of Fedora?)
  • Fedora.future

Assuming we like the whole “Fedora dot ” nomenclature…

Yes, this makes sense and seems like a good goal! When people say “accessibility,” I think this is the place where they start thinking from.

But I worry that we are grouping too many things together under one high-level goal. One thing I was looking for was the emphasis on mentoring and mentorship that we have discussed informally since Nest 2022. Grouping this kind of “project accessibility” together with “system/technology accessibility” feels like we are doing too many things under one umbrella. Also, the success metrics for both of these look very different.

What if we split out this “community accessibility” thing into something else, like “improved community onboarding”? I feel like a goal dedicated to onboarding pairs well with the high-level goal (doubling # of contributors) and gives us space to have conversations about how people on-ramp into the community. Grouping it with technology accessibility feels like we are blurring two different things together in one, and I feel that tracking and measuring success will be harder for this reason.

I have the same feeling here, that grouping “community leadership” and “technology innovation” together are two separate things that are both measured very differently. What if we split off the community leadership piece of this goal and combined it into a new goal, together with the “community accessibility” piece of the first goal?

I want to make sure we are identifying the mentoring and onboarding goals clearly and succinctly, without them getting “lost” in the details of other goals.

1 Like

This is fantastic. I love the variety of the things that need focus and how they act as multipliers for each other.


@ekidney - here is our mission definition for the A11y working group ^^

1 Like

But what happens when “now” becomes “then”?

I’m fine with something like “Fedora 2028” (or whatever year we set as the goal). It’s not very exciting, but it’s much easier to understand, particularly 15 years from now when we’re working on our next-next-next strategic plan.

That makes a lot of sense.

1 Like

While we keep on maintaining the status quo for the offerings of Fedora Linux that we have had so far, we would want to enhance them further to suit better the needs of the specific purposes of the offerings. It is a catch-22 kind of problem, I know, but the technical quality and superior polish would help convince people to use, it and (very possibly) give back by contributing to the community. Two of the ways that I can think of (off the top of my head right now), are to take measures to improve the contributor’s quality of life and recognize their efforts. If people find it convenient to contribute and are appreciated for those efforts, we can let their word of mouth do the magic.

Haha agreed! Almost looks like I am being dragged back to my college, taught about pointer arithmetic and asked how I can remove an element from a singly linked list. I am gonna say a +1 to @jflory7’s suggestions though.

To understand people’s ideas, one must comprehend where they are coming from and their perspective on the things. A lot many time, an hour long call is not just enough to go to those parts, so +1.

Circling back to the the points I have stated before, one thing (of many thousand other things) that really helps establish such a community is direction. Some kind of goal[1] that resonates through the most, added to the enhancements to ensuring that contributions are done easily and are recognized/rewarded appropriately. We have been doing that to some extent but it always helps to step up those efforts.

Couldn’t have said any better myself! One of the takes that I have on accessibility is that, it is less about the act of giving space and more about empowering the ones (with accessibility issues) so that they feel comfortable in making their own space, the way they want. Easier said than done, I understand but with a direction to go to and some initial groundwork, I see people following us through and helping us create a lot more inclusive ecosystem, both in desktop/web technologies and tooling.

One of the things that I seem to have noticed from the Ask Fedora forums, is that a lot many people come to ask questions and some of them stay back too (to help others or facilitate answering etc.), when they are subjected to the sense of belonging by the Q&A regulars there. This[2] also becomes a prime location for folks who want to get started with their baby steps on their journey from being “Fedora Linux users” to “Fedora Project contributors”.

Hatch was one of the fun events that happened across the world throughout the Fedoraverse, last year. A proxy event of sorts for those who are either not active contributors, cannot make it to Flock or are simply users - these events let people connect on a more human level that is simply not possible to that extent on virtual conferences. We would definitely want to take more strides to ensure that the contributors feel empowered/resourceful[3] that they would organize these events, wherever they belong.

+100. Being someone who was mentored by other experienced contributors throughout this “fedorable”[4] journey, the importance of mentorship and (possibly) being able to mentor others in turn is unparalleled. The very experience of reaching out to universities and art schools, teaching them the technologies they need for their careers and letting them test their skills on real-world projects like those in Fedora Project, has been slowly picking after the COVID-19 situation became less serious but admittedly, the level[5] isn’t just there yet. Unless, of course, if we make it.

Yep, “the bus factor” (or like Justin says it, “the lottery factor”) but it does not really have to be the case only for the leaders, representatives or maintainers of their own small worlds[6] within the Fedora Project community. People have been falling off the face of the earth in the past as they continue to do so now, just because they could not find something that they would want to work on[7]. It is an issue I resonate with and yet, something that we most definitely would want to find a solution to.

+100. We should take strides to ensure people feel the same way[8] we do about rpm-ostree based variants.

To everything else, I didn’t quote you on. I agree on those and the fact that we have a task at hand.

P.S. Ok, maybe I used too many footnotes.

  1. tangible enough to move grassroots contributors but effective enough to describe strategy ↩︎

  2. being one of the places where I started contributing from ↩︎

  3. and most importantly, know whom to reach out to in case they need assistance ↩︎

  4. We should get this trademarked, I am telling you. ↩︎

  5. with colleges more focussed on making industrial connections rather than upskilling in these dire times of technological recessions - or so they say ↩︎

  6. SIGs, subprojects, subcommunities etc. ↩︎

  7. or even if they did, they could not make enough contributions to make their stay warranted ↩︎

  8. or at least, be open to trying it out on a VM - that’s a good enough of a start to (probable) contributions ↩︎

1 Like

In the way this came together, the three top-level focus areas all are a little abstract. And I agree, the more-specific goals under each of those don’t necessarily share the same success criteria. We don’t necessarily have to organize them like that. Let me start with putting these two levels in outline form:

  • Accessibility for Everyone
      1. a11y
      1. community access
  • Innovation and leadership in the distro space
      1. in community (mentorship, dei + community health, community metrics)
      1. in techology (containers, immutable OS, native language stacks)
  • Growing beyond Editions[1]
      1. make things better for our “flavors” and remixes
      1. provide distro value for special interests beyond specialized boot media

We could reorganize this as something like:

  • Improved Community Stuff
    • community onboarding and mentorship
    • dei + community health, community metrics
    • make things better for our “flavors” and remixes
  • Techy stuff
    • a11y
    • containers, immutable OS, native language stack
    • provide distro value for special interests beyond specialized boot media

… but I don’t think that actually makes the top levels any more unified. In fact, I really prefer the first, where both engineering/technical and community/social goals are part of each high-level focus area.

  1. This might also be called “Building on” — we actually want to make thing better for the Editions, too! ↩︎

1 Like

To elaborate further: I think the second-level goals we’ve identified are all reasonably actionable and coherent, regardless of how we group them, and I think that’s the level that really matters. Under that, there are a number of probable initiatives:

    1. a11y
    • websites and docs
    • Fedora Linux improvements
    • Fedora Project tooling improvements
    1. community access
    • pre-install vendor outreach
    • better end-user docs and communications tools
    • local user groups, globally
    1. leadership in community
    • mentorship
    • dei & community norms
    • community metrics
    1. leadership in techology
    • containers
    • immutable OS
    • native (programming) language stack support
    1. make things better for our “flavors” and remixes
    • easier / better spins
    • better downstream relationships
    • grow Fedora Editions to the next level
    1. provide distro value for special interests beyond specialized boot media
    • curated content for special interests (rather than just install media)
    • more support for these teams and communities
1 Like

I give props to @bcotton since he was the first person I heard use the “lottery factor” to describe this phenomenon.

My first read of the top post was that these are three well-defined goals with a clear, unifying mission. It may be abstract to an extent, but the picture here of the strategic plan also deserves credit as an already-refined vision. Additionally, it comes with good supporting documentation (e.g. link-outs to the prior strategy and the 1-hour video presentation from Nest 2022).

What is drafted out in this topic is abstract enough to allow for additional feedback, but detailed enough where we can scrutinize what gets attention as a headlining goal for the next five years.

If we did not organize them that way, how do we better distinguish mentorship and onboarding experiences in other high-level goals? These two topics feel underrepresented in the five year view, given their importance. I also want mentoring and improved onboarding highlighted in accessibility-related work. I also want mentoring and improved onboarding in growing beyond the Editions.

It might be inherent that mentoring and improved onboarding go naturally with these goals. However, I want to deliberately underline them as a high-level goal. In 2023, I intend to explore interest in a Council Objective for community onboarding. Additionally, It aligns to places I want to spend more time in with my role in Fedora.

To be fair, “techy stuff” doesn’t sound nearly as inspiring as “Accessibility for everyone”. :smiley:

In either case, I am skeptical whether splitting the high-level goals into two different “tech” and “community” goals is the right approach either. I think it oversimplifies what we want to do, when we have the ability to be more specific.

I understand the intent to group both engineering/technical and community/social things together. Every tech goal should have a community component. For example, if an outcome of Goal 3 were to deliver a new way of building Remixes, we should also pair that with a metric like “Support the rollout of three new community Remixes during a two-release cycle period.

But a community lens in all goals should not reduce the necessity for a high-level goal that looks closely at topics like mentoring and onboarding. Separating them out further into more defined subject areas gives them more weight and space from each other, so they are distinct and easier to plan around.

Here is a counter-proposal:

Accessibility for Everyone

  1. Distribution a11y: Making sure we build an operating system that works for everyone, so people who have disabilities or other challenges using conventional interfaces can access and connect to a free & open operating system.
  2. Community a11y: Building our websites, infrastructure, and community tools in a way that enables a wider group of people than before to access the things we build together as a community.

Innovation and leadership in the distro space

  1. Storytelling: Helping to tell our story and share the message about what Fedora is, what we do, and how to be a part of the Fedora story. Highlighting and communicating more about the Fedora contributor experience.
  2. Metrics: Using our rich data to better understand how our community works, to know both our strengthes and weaknesses as supported by tangible data from our infrastructure.
  3. Technology: Containers, immutable operating system, native language stacks.

Growing beyond Editions

  1. Remixes: Improve the contributor experience and quality of life for people rebuilding Fedora in new and interesting ways. Make it easier for people to test out new ways to build Fedora together in an open way.
  2. provide distro value for special interests beyond specialized boot media [1]

Friends means Together [2]

  1. Mentoring: Build up our capacity to mentor as a community so we can build connections between different generations of contributors and enable diverse participation in Fedora leadership.
  2. Onboarding experience: Make it easy for anyone to discover what they can do in Fedora, why they should do it, and how they can get started as a new contributor.

  1. I kept this one as written in the original outline because I realized I did not fully understand it. But I wanted to know the context because it sounds nice. :smiley: ↩︎

  2. Or some other name. I was riffing on the Friends Foundation, but it might be better to come up with a high-level title that is more concrete and tangible. ↩︎

It’s part of “what should we do with Labs and Spins?” — specifically, the Labs part. “Spins” are basically desktop-environment technology showcases. “Labs” are use-focused. And, fifteen years ago, “Labs” was literal — take some LiveCDs (or later, USB sticks) to a computer lab, boot up Fedora Design Suite on twenty computers, teach a class on using Inkscape and other open source tools.

But now, that boot-to-a-specialized-selection-of-software case is much less relevant. But, we’ve still got something neat with Fedora Design Suite, Fedora Jam, Fedora Robotics Lab, Compneuro. How can we present these curated selections of open source software in a way that’s useful and relevant?

More on the rest tomorrow. Still thinking about it. :classic_smiley:

I would like to ask that people think about the following in order to ‘grow’ beyond the Editions would be to actually ‘shrink’ or ‘simplify’ the build system. It has a very large ‘lottery’ factor and it also has a lot of things which have been glued in over 2 decades which make adding more things much harder to impossible.

If the build structure and things like spins and labs could be ‘decoupled’ from the main system, I think it would allow for growth and remove large number source of daily failures.

1 Like

Okay, I am following you! And when you say distro value, do you mean value for the Fedora Linux distribution offerings? Value for the Lab/Solution/Thingie developers who use Fedora to build their thing? Or something else?

Yes, this is actually something I’d really like as part of that. I’d like this kind of media to be generated by ImageBuilder (or similar), decoupled from The Compose.

I mean: the kind of value we provide by putting it into a distro: consistency, maintenance, trust, collective community, etc.

So, I’ve been thinking about this:

  • Accessibility for Everyone
      1. Distribution a11y
      1. Community a11y
  • Innovation and leadership in the distro space
      1. Storytelling
      1. Metrics
      1. Technology: Containers, immutable operating system, native language stacks.
  • Growing beyond Editions
      1. Remixes
      1. provide distro value for special interests beyond specialized boot media
  • Friends means Together
      1. Mentoring
      1. Onboarding experience

I’m not opposed to reorganizing the levels, but this also drops a number of things which I think are important.

I don’t see a place for any of the items from “For everyone” — Fedora Linux pre-installed from hardware vendors, easier access to support and help, and probably most important, better supporting our regional / local communities aruond the world.

And, I know I didn’t talk about it as much, but I don’t think all of the “improve the distro itself” parts can be compressed into one item.

In the other direction, having Onboarding and Mentoring as one

Finally, I’m really uncertain about the addition of “Storytelling”. I don’t mean that that’s not important, and it may well be something that we missed overall. However, I don’t think it is really " Innovation and leadership in the distro space" — in fact, some other distros do this kind of stuff really quite well. Contrast that to the big goal with a comprehensive distro-wide mentoring program — I think that is really something new. There are also a lot of untapped areas in community metrics for a large project like ours. [1]

I can see a case for highlighting Storytelling as an initiative,[2] but I don’t think this is the right grouping.

Going back to your original concern about “Accessibility” being not-the-right-thing for what was under it, maybe something like this (with all three levels!)

  • Fedora for Everyone!
    • Accessibility (a11y)
      • websites and docs
      • Fedora Linux improvements
      • Fedora Project tooling improvements
    • Reaching the World
      • more preinstalled systems
      • dei + community health
      • rebuilding our local communities and connections worldwide
  • Distro Innovation and Leadership
    • In Community
      • mentorship (onboarding, growth, continuity)
      • community metrics (contributor and user)
      • move to modern tooling for communications
    • In Technology
      • containers / flatpak
      • immutable OS
      • native programming language stacks
  • Building on Fedora Next
    • All of the Flavors
      • easier, better, more lightweight spins
      • collaborate with active downstreams [3]
      • bridge to rebuilld-downstreams [4]
    • Fedora for Your Interests
      • move beyond boot/install media for “labs”
      • connect Fedora with other “maker” communities
      • [5]

  1. Most of the CHAOSS metrics tools and even concepts target projects which can be represented as a gitlab repo, or maybe several such repos. ↩︎

  2. the counter argument is: it’s fundamental to everything and therefore shouldn’t be separated out ↩︎

  3. CentOS Stream + RHEL, Amazon Linux, and smaller ones too ↩︎

  4. AlmaLinux, Rocky Linux, etc. ↩︎

  5. And I’m still struggling for a third option for this one, which is really painful for my desire for perfect symmetry ↩︎

I was thinking about this yesterday, and wondered if we knew who our ‘customers’ are for Fedora. I expect in some ways it is ‘everyone’ but do we have an idea of who our ‘vital’ few customers are from a Pareto-Juran view (10% of your audience are a vital few and 90% are a useful many. Both need to be looked at but you tend to see things which help the 10% getting the most ‘bang’ for the vital resources you put in it.)

1 Like

Thanks for sharing the strategic plan.

For the accessibility, we have at least 2 places to communicate. One place is mailing lists such as devel@, and another place is Fedora Discussion forum. And to have twice as many people, I think both 2 places need to thrive. Because some people like email, and some people don’t.

Bridging the 2 places or filling a gap between 2 places is important for that. It’s like thinking about how to share the info of the Fedora mailing list to the people on the Fedora Discussion forum, and polishing HyperKitty.

Here’s my take: each of the Editions has its own answer to this. That is part of what makes them “Editions”. Focusing on this more clearly — and expanding into potential audiences that aren’t currently served — is one of the “whys” behind my third focus area (what I’d called “Beyond Editions” and is “Building on” in the latest iteration above. Thanks for bringing this up, because I see that while I had that in mind, it isn’t communicated clearly and needs to be.

At a higher level, the “10% audience” we are looking for in this overall plan is _those users who might become highly-active contributors". That should be a guiding principle when looking at which possible outputs we want to prioritize — @bex has something about Fedora Linux for Alpaca Farmers that fits here.

We don’t resources to polish HyperKitty. I wish we did, but it’s been the hard fact since it was launched. I don’t say this to knock it at all — I just wish we’d planned it differently. (Same goes for Pagure.) But here we are now.

I know many people like tradional email lists, but I think we need to consolidate here. I’m going to write a separate post about this soon… stay tuned for that drama!


That’s fine. The consolidated community could be better if it is possible. We will see the drama!

1 Like

How about Fedora.evolution or Fedora.ascends?