The first time I opened the Firefox codebase, I had no idea where to start and that was exactly the point.
I remember opening one of the sidebar test files and just staring at it. The structure was unfamiliar, the naming felt different, and I wasn’t sure what I was even looking at. I knew my task involved reorganizing some of these files, but at that moment, I didn’t fully understand how everything connected. Still, I started.
Figuring Things Out as I Went
In these first few weeks, I didn’t try to understand everything at once.
Instead, I focused on small things reading through files, comparing similar ones, and trying to understand how the project was structured. I began to notice patterns in how tests were written and organized, and that helped me make sense of what I was working on.
It became clear that contributing wasn’t just about making changes it was about fitting those changes into an existing system.
When Things Didn’t Click Immediately
There were moments where I felt stuck.
I would move between files, reread sections, and still feel unsure if I was doing the right thing. Even running commands like ./mach lint and ./mach test was confusing at first. Sometimes I didn’t understand what the output meant or what exactly needed to be fixed.
But instead of stopping, I kept trying.
Over time, I started to recognize patterns in the feedback from these tools. The errors became less intimidating, and I got better at figuring out what needed to change.
Working Through the Task
My contribution involved reorganizing existing sidebar test files and making sure everything still worked after the changes.
This included moving the tests into a more appropriate structure and updating the related configuration so they could still be discovered and run correctly.
It wasn’t complicated in theory, but it required attention. I had to make sure I wasn’t breaking anything and that the structure stayed consistent with the rest of the project.
That was the part that surprised me the most how something that seemed small still required careful thinking.
Looking Back
Over these first few weeks, I’ve become more comfortable navigating the codebase and using the tools involved.
I’m still learning, but I now approach unfamiliar parts of the project with more confidence. What once felt confusing now feels like something I can break down and work through.
Final Thoughts
Contributing to open source for the first time can feel intimidating.
But you don’t need to be an expert. You just need to be willing to learn, try, and keep going.
This experience showed me that I can contribute to complex systems and more importantly,
I belong in spaces like this.
