Finding My Way into Fedora, One Tab at a Time

Source: Dev.to

I just wrapped up an internship—the kind where you’re heads‑down for months, learning fast, shipping things, and barely coming up for air. When it ended, I sat back and thought, “Okay, what now?”
That’s when Outreachy found me—or maybe I found it. Either way, the timing felt right. I applied with little expectation, honestly not thinking much would come of it. Then I was selected for the contribution round and suddenly it was real. While browsing the projects, the Fedora Badges revamp clicked for me. Not because it looked good on a résumé, but because it felt like real work on a real system that real people use.

Wait, What Even Is Fedora?

I’ll be honest: before this, I had absolutely no idea Fedora existed. I’m a Windows user through and through, but Linux was always something I genuinely wanted to get into. It lived on my “someday” list for the longest time, but I never had a real reason to dive in until now. So Fedora wasn’t just a new project for me; it was finally that door I’d been meaning to walk through.

Fedora is a free and open‑source Linux operating system, but more than that it’s a global community of developers, designers, translators, writers, and many others building something together. It was born in 2003 as a collaboration between Red Hat and volunteers, and has since grown into one of the most innovative Linux distributions. New technologies, kernel features, and desktop environments often land in Fedora first before anywhere else. It’s where things get tried, tested, and refined.

What surprised me most is how much of what we use in enterprise Linux today started as an experiment inside Fedora. Fedora is upstream for Red Hat Enterprise Linux, meaning things proven here eventually make their way into production systems used by companies worldwide. There’s something quietly powerful about that.

The First Few Days, Finding My Footing

The first few days after joining were honestly just me trying to figure out where I even was. Sign up here, join this channel, that mailing list, this Matrix room, that repository. The Fedora community is vast—impressively so, but also quietly overwhelming when you’re standing at the door with no map.

I spent more time than I’d like to admit just navigating between tabs, trying to understand which space was for what and who I was supposed to talk to. Nobody tells you that the first step in open source isn’t writing code; it’s figuring out where the conversation is happening.

Once things started clicking—once I found the right channel, read the right thread, sat in the first meeting—it began to feel less like a maze and more like a neighbourhood I was slowly learning my way around.

The Badges Project and Why It Matters

One of the first things I explored was Fedora Badges, a platform that recognises and rewards community contributions:

• Packaging code? Badge.
• Attending an event? Badge.
• Helping someone in the forums? Badge.

It sounds simple, but the idea behind it is genuinely thoughtful. Open source can feel invisible sometimes; you contribute and nothing really acknowledges it. Fedora Badges tries to change that. It makes contribution visible, tangible, even a little fun.

The current project I’m applying to work on is a complete revamp of this system: modernising the backend, rebuilding the frontend in React, and adding MCP support, which means AI assistants will be able to interact with the badges system directly. It sits at the intersection of community, infrastructure, and modern AI tooling—exactly where my interests lie.

Being an AI Developer Walking Into This

I work with AI. Python is my comfort zone. So when I read through the project and saw the MCP server architecture planned—a way for AI assistants to query and interact with badge data—I felt like I already had a language to speak in here.

The mentors made something very clear in our first meeting: using AI to write your contributions is not allowed. You can use it to understand things, the way you’d use a dictionary to look up a word, but the actual work, the thinking, the implementation, and the decisions have to come from you.

As someone who works in AI, I respect that stance a lot. It’s easy to let a tool do the thinking for you; it’s harder—and more valuable—to understand something deeply enough that you could explain it to someone else. That’s what this project is asking for, and I think it’s the right ask.

What’s Ahead

I’m still early in this journey. I’m going through the codebase, understanding how the Flask backend and the React frontend talk to each other, looking at open issues, and getting familiar with how contributions work in a community this size. It’s a lot to take in, but I haven’t felt stuck—just curious, which is a different thing entirely.

• If you’re curious to explore Fedora yourself, the best place to start is the Fedora Project website.
• To get involved with the Badges project specifically, the main conversation is happening on Matrix at #badges:fedoraproject.org (chat.fedoraproject.org).
• The codebase lives on GitHub under the fedora-infra organization and is open for anyone to explore.

Don’t overthink the entry point. Just show up, read for a bit, and say hello. I’ll be sharing more as I go—there’s a lot more to learn, and I’m just getting started.