We updated the “How is Fedora Organized?” page on Fedora docs with the org chart below. This chart shows governing bodies, teams, editions, spins/labs, and initiatives. Is your Fedora thing missing? Feel free to comment on this Discussion post to ask for an update.
What changed?
There were some significant changes to the chart, including:
- Adding CoreOS & Cloud to Editions
- Additions to and definition between Spins and Labs
- Closer link between Infrastructure and Release Engineering
- Refinement of Alternate Architectures
- Reorganization of bubbles to reflect the merge of Ask and Discussion
- Redo of color scheme from a variety of Fedora colors to a combo of the Fedora blues
- Rework of composition to make things less cluttered and more readable
- Use of different colored bubbles to denote hierarchy while keeping the horizontal organization reflecting how Fedora operates
My process
I designed and published the previous revamped version of the Fedora Org Chart in 2021. A lot has changed in two years — it was time for an update! I opened a Discussion post earlier this year to gather feedback from the community, such as:
- What’s missing
- What’s outdated (teams or projects that are retired or inactive for the foreseeable future)
- Any updates on naming (teams, variants, etc)
- Readability (is it easy to understand? how could that be improved?)
- Color scheme, format, composition (refresh to match our updated brand)
After gaining some insightful first responses, I got to work on the redesign. I published the first draft to the Discussion thread and also brought it the Fedora Design Team Sessions. I wanted to ensure the new chart reflected Fedora’s updated brand and I wanted to collect specific feedback related to the design aspects such as composition, color scheme, and overall look and feel.
A couple of rounds of significant feedback later, as well as lots of small changes and suggestions, I was excited to call the redesign complete(for now)! I opened a ticket on the Council Docs repo to request publishing of the new org chart.
But Fedora is always changing!
Some pointed out that the org chart won’t be 100% accurate pretty shortly after it gets redesigned. I think that’s okay. The idea is that the org chart is a “snapshot” and that it will naturally become somewhat inaccurate after some time has passed from the latest version. The chart’s main purpose to give an overview of Fedora: how we organize the project, how far spread the work we do is, and a way for newcomers to get an idea of that scope. To quote the “How Fedora is Organized” page:
Since many groups are rather informal, don’t take the chart as written in stone. Also, if it is a little overwhelming, don’t worry. Fedora is a friendly project — just pick an area you’re interested in, introduce yourself to the people involved, and get started. Or, if you don’t know where to start, see how to get involved.
This is amazing. Will someone talk about it during Flock. It will be interesting to walkthrough this org chart during Flock.
Not that I’m aware of. But you can check the talks on:
Now, we need to make sure key people from each of the higher level groups here are participating on Discourse.
Hey @riecatnor, @jflory7, @mattdm, @duffy what do you think if we pack this org-chart as part of the extra wallpapers each release?
I love it, and thinking that this could and would change in time, we can update it on each release if necessary.
I am open to the idea, although we likely need our resident Fedora wallpaper experts to weigh in on what the technical requirements are to make this happen.
CC: @madelinepeck @duffy
I think that if it’s own package, it can exist independently — it just needs to put the right files into the right place.
I’m looking forward to the
fedora-one-chart-to-rule-them-allRPM.I said that I’ll print it in large format. I did it with three pieces of A4 sized paper and stitched them. I just need to find a proper wall to hang it.
Here’s the pic: