Fedora Community Blueprint: All you need to know

Project Discussion
1

This is a blueprint from my point of view, based on the things I’ve learned and what I think might help Fedora local communities grow.

For me, it started back when I joined Outreachy and planned and executed an event at Murang’a University: We’re in Kenya: Fedora at Murang’a University.

So, I’ll be referencing that experience from a local perspective - which I believe might also apply to other regions.

At the back of our minds, Fedora is trying to get more contributors from different regions all over the world.

Blueprint

If you’re interested in helping out or organizing events in your region, go for it. Running local events is enjoyable and fun. You just need to show interest — and if you have a unique idea, even better.

Note: Anyone is welcome to help organize events at any time.

Even small awareness sessions are enough to kickstart your first event. My event at Murang’a University spread widely, introduced Fedora to new people, and even opened opportunities for me. I was invited to speak at OpenInfra because of that event. Government officials also reached out - so the work is seen, and it matters.

Things I’d suggest in regions where open source is less visible

  • Outreach/info sessions (universities/high schools)

  • Install parties (helping new people install Fedora, sharing tips)

  • Pull request parties (fix bugs together in person/online)

Such events build awareness and catch attention first. This is different from regions where contributors already exist and just need more engagement. In those regions, you can focus on more advanced/engaging events like PR parties or workshops.

What really are the steps to do it right?

To make things easier, always engage with the current Fedora Community Architect - they’ll guide you further.

Some key steps:

  • Plan early and draft your event idea in writing (e.g. Fedora DEI & Docs Workshop (wiki page)).

  • Involve your team - events are stronger when you collaborate.

  • Inform the Community Architect.

  • If you need funds, open a ticket at least one week before the event. Small events usually get quicker approval.

  • Keep all receipts for swag and expenses to get a full refund. (See the Reimbursement Policy)

Examples from my Fedora Docs Workshop (June 21, 2025):

Framework for regional support

The Fedora DEI team is trying to support regional communities. I came up with a framework (with feedback from the community too) to guide this effort - see the [discussion thread] (link once ready).

From my Murang’a University event and reviewing Hackfest notes from Flock 2024, I gathered activities and ideas that can make an impact.

I drafted an initial mind map, shared it for feedback (thanks MatH and Jona Azizaj for brainstorming with me), and am finalizing a structured version here (this will be disabled after 6 months of post but you can find the pdf/image below)

If you have comments, please reply to the discussion thread on supporting regional communities.

Images:

(Initial mindmap)

1600×757 283 KB

(final mindmap)

1424×908 84.5 KB

If the images aren’t clear enough, you can download the pdf below:

first draft: https://drive.google.com/file/d/18ArY5cMTbAK921riwiD0Qd4hg_7qYVpg/view?usp=sharing (might not be clear enough but the final has all the content except a few changes)

final draft: https://drive.google.com/file/d/1V8yRbLu_mTsh5r_vvzANIFLrKGF5pMKc/view?usp=sharing

2 Likes
2

My rant;

I also think a lot of current contributors are really getting old. We need to build the future generation of open source contributors.

From what I’ve seen (reading old blogs and past community activities), things used to be different back then. You could easily hear about open source, which is why we had a large number of contributors who are still around today. But is that still the case for this generation?

You might think: that’s fine, because you’re here. But what if you’re not here anymore (say you’ve decided to become a farmer? xD)? Do you know someone who would replace you? Yes, we have mentored projects like Outreachy and GSoC - and I was an Outreachy intern in summer 2025 - but will I still be here contributing years from now?

Maybe ask yourself this: Are there people in your region actively pushing open source? We’re pushing Fedora - are you?

In my region, I don’t hear much. Among the younger generation, there are no open source tech clubs. I’m not sure if it’s too late for them to realize there’s always been an open source alternative to proprietary software, but often they only discover this after campus.

For most, getting a job to pay bills comes first, and open source becomes secondary. Opportunities in open source aren’t many, and often only a few benefit. So where do the rest go? That’s why we need to start earlier - high school, university, and local outreach.

By the way, in my upcoming OpenInfra talk, I’ll be speaking about how we need to nurture contributors in open source - not just focusing on those already contributing, but showing ways to bring new people in.

One last thought: Do you think Fedora users will automatically become contributors? Maybe - but it could take 5-10 years. Do we even have that time with the young generation today?

Whoahh, rant over!

1 Like
3

I think there’s a lot of things I’ve wondered about this as I’ve heard from different stakeholders. Food for thought, but Open Source as an ecosystem can mean that if we’re connecting people to contribute in some way - that’s a successful activity! As a distribution on the Fedora Linux side, we partner with our upstreams to package, test, and deliver software to end users. But if we get someone on the upstream side contributing, or downstream enabled to do something in Open Source because of what Fedora can do for them as the foundation, I think that’s a win either way. Like you’re saying above, there’s a lot to talk about in different communities.

I would also say it would be exciting to see more of “we’re doing this with Fedora” with the downstreams in the hobbyist spaces (Bazzite being one of those that comes to mind). People who take Fedora and make cool things with it are contributing IMO to the broader what can be with the base of the distribution.

One thing for Fedora is to figure out more and more as software changes, how the distribution is packaged and delivered, what even is the software people use day to day (I use a lot of “desktop apps” that are just electron wrappers I find), and then what can people do with a solid / forward driven OS like this community has.

Either way, I’ll echo what you’re saying above - enabling more people means also bringing back the local engagement. I’ve been trying to find Amsterdam Linux groups and am sadly feeling like I missed out on the events of the past.

/endrant

2 Likes
4

Quoting this part for transparency for future local community organizers.

This is crucial. Don’t try to act cheap, this is likely the case in some countries in Africa where you might want to do a cheaper way and couldn’t get a receipt just to cut cost. Don’t do it. Make sure you have all the receipts at hand.

Another thing to point out: the Fedora reimbursement policy stresses on receipts, and not transactions(either mobile money/bank proofs) - is this crucial? (@jflory7).

And how long does it take for a reimbursement to be processed after someone has submitted a reimbursement ticket?

1 Like
5

Yes, it really does need to be receipts. In general, receipts need to have a transaction date, the name of the vendor, the payment method used (i.e. cash, card, check, or something else), and a clear total amount paid.

This is required for Red Hat to complete reimbursements, as we have to comply with international anti-bribery and anti-corruption laws as an American company.

In a best case scenario, when all the documents are provided and the banking proof is sufficient, I have seen some reimbursements paid out as early as two days after the reimbursement is submitted.

Sometimes, there are issues that require some back-and-forth, but when everything is correct, the reimbursements can happen pretty quick.

1 Like