Cover image is from-> Image by magnific
I've always admired people who contribute to open source.
Every time I use a library, read its documentation, or find a solution on GitHub, I've realized that someone took the time to build it, improve it, and share it with the community.
The truth is, I honestly don't know where to begin. 🧐
It's not that I'm afraid of writing code. I've spent years building web applications, fixing bugs, and learning new technologies as a software engineer. But open source feels like a different world.
Questions keep coming to mind:
- How do people choose their first project?
- Is improving documentation enough for a first contribution?
- How do you avoid breaking someone else's project?
- What's the proper etiquette when opening an issue or a pull request?
- How do I figure out what a project actually needs?
The more I think about it, the easier it becomes to postpone taking that first step. So instead of waiting until I have everything figured out, I've decided to make this one of my goals.
My Open Source 101 plan 📅
- Find a project I actually use.
- Read its documentation, issues, and commit history.
- Look for beginner-friendly issues.
- Submit my first pull request, even if it's just a documentation improvement.
- Learn from the review process instead of trying to be perfect.
I know my first contribution won't be groundbreaking 😃, and that's okay. Every experienced open source contributor started with a first pull request, right?
If you've been contributing to open source for a while, I'd love to hear your advice.
What was the first project you contributed to, and what helped you get started?
And if you're in the same position as me, maybe this is the sign that we should both stop waiting and start contributing..
Note: My goal is to submit my first open source pull request before the end of this month. I'll come back and share what I learned whether it succeeds or fails.
Top comments (0)