How I Started Contributing to Open Mercato
Open source can feel intimidating when you're starting out.
You see large repositories, experienced contributors, long issue discussions, and public pull requests where anyone can review your code. For a while I kept thinking I should “learn more first” before trying to contribute.
Eventually I decided to just try.
I chose Open Mercato and approached it in a simple way — explore the project, understand how it works, and start with something small.
This is roughly how that process looked.
Why I Chose Open Mercato
I didn’t pick a repository randomly.
While browsing GitHub projects, Open Mercato stood out for a few reasons:
- The repository was active — there were recent commits and pull requests.
- Maintainers were responding to issues.
- The documentation was detailed enough to understand what the project does.
That last point helped a lot. When documentation is decent, it removes a lot of the friction that usually stops people from getting started.
Spending Time Reading the Repository
Before writing any code, I spent some time just exploring the project.
I read through the README.md and the CONTRIBUTING.md, and then started looking around the repository structure. I opened a few different folders and files just to see how things were organized.
I also checked:
- open issues
- recently merged pull requests
Looking at merged PRs was particularly useful. It gave me a better idea of what maintainers expect from contributors and how changes are usually structured.
Instead of trying to guess how things worked, I tried to observe how the project was already evolving.
Looking for a Small First Contribution
At first I thought about trying something more ambitious, but I quickly realized that probably wasn’t the best way to start.
So I deliberately looked for something small.
Things like:
- minor bugs
- small improvements
- documentation updates
- small refactoring opportunities
The goal wasn't to make a big change. I mainly wanted to understand the workflow and see how contributions are reviewed.
Starting small made the whole process feel much less intimidating.
Opening the Pull Request
Once I found something I could improve, I followed the usual GitHub process:
- fork the repository
- create a separate branch
- implement a small change
- write a clear commit message
- open a pull request
When creating the PR, I tried to explain clearly:
- what the change does
- why it improves the project
- whether it might affect anything else
Maintainers review a lot of contributions, so clear explanations make that process easier.
Feedback From Maintainers
After opening the pull request, I received some feedback.
It wasn’t really criticism — it was mostly suggestions to make the change align better with the existing code style and structure.
This part was actually very helpful. Seeing how maintainers think about code quality and consistency gave me a better understanding of how the project is maintained.
I updated the PR based on the comments and continued the discussion there.
What I Learned From the Process
One thing that stood out to me is that contributing to open source involves a lot more than just writing code.
You spend a lot of time:
- reading other people's code
- understanding design decisions
- communicating clearly in pull requests and discussions
Another thing I realized is that you don't need to be an expert to start contributing. Even small improvements can be valuable, especially in active projects.
If You're Thinking About Contributing
If you're considering contributing to open source but aren't sure where to begin, a few things helped me:
- choose a project that actually interests you
- spend time reading the repository before coding
- start with small, manageable changes
- don't worry too much about making everything perfect
Once you go through the contribution process once, it becomes much easier the next time.
Final Thoughts
My first contribution to Open Mercato was relatively small, but the experience was valuable.
It helped me understand how open source collaboration works in practice — from exploring a repository to discussing changes in a pull request.
If you're thinking about contributing to a project, it's worth trying. The first step is usually the hardest part.
Top comments (0)