Skip to main content

Command Palette

Search for a command to run...

My Fedora Contributions

Updated
3 min read
My Fedora Contributions
A

Hey there! Welcome to TechWordCraft! I'm Amarachi, a passionate technical writer on a mission to make complex concepts simple and enjoyable. I enjoy demystifying technology for everyone. Join me on this journey as we explore the endless possibilities that the tech world has to offer, one word at a time!

When I first heard about the Fedora Project I did not really understand what contributing to an open source community even meant in practice. I had read about it, seen it mentioned in tech spaces, nodded along like I understood. But I did not.

That changed in June 2025.

The Task That Looked Simple

I joined the "Easy local testing of Fedora packages" project and was assigned what looked like a straightforward task on the surface. A minor change involving accepting root directory. I thought it would be simple until I actually sat down to do it.

I had never written testing code for a contribution before. Not in any real meaningful way. I had written code before, but writing tests for a specific change in someone else's project, in a codebase with structure I was still figuring out, was a completely different thing. I remember staring at my screen for a longtime trying to understand where even to begin.

The Failing Part (Which Nobody Talks About Enough)

The tests failed several times. Not in a dramatic way but in that quiet uncomfortable way where you run something and it does not work and you are not entirely sure why and you start wondering if you are even cut out for this.

I think that is the part of open source contribution that people leave out of their blog posts because it is not a fun thing to admit. But I genuinely think it is the most important part of the story. Because what happened after the failing is what actually mattered.

What the Mentors Did

Matej Focko was one of the mentors on the project and honestly I do not think I would have made it through without that kind of guidance. Every time I got stuck there was always a clear and patient response on the other end. Not just "here is the answer" but the kind of explanation that actually helped me understand what I was doing wrong and why. I felt like giving up countless times but the support from the mentors kept me going.

What I Actually Learned

By the time the contribution was accepted, I had learned things I did not expect to learn. Not just technical things though, I did pick up a lot about how package testing works in a Linux environment. I learned how to read errors more carefully instead of panicking at them. I learned how to ask for help in a way that is specific enough to actually get useful feedback. I learned that open source communities are not as intimidating as they look from the outside.

I also learned something about myself, I can push through something even when I am scared of looking incompetent. That first contribution was uncomfortable from start to almost finish. But I finished it. And it was accepted. And that felt like something real.

Why I Came Back

That experience is the reason I am here again for this Outreachy cycle. I already know what it feels like to be in a Fedora contribution space. I know what the community feels like when it is actually working the way it is supposed to work, which is people helping people without making anyone feel small for not knowing something yet.

If you are reading this as someone thinking about applying, that is the honest version of what it looks like. It is not smooth. You will probably fail at something. But the people are good, and the learning is real and by the end of it you will know you actually did something.