It took me some time to write this post, but now it says exactly what I wanted to say.
When people talk about open source contributions, we usually think about code.
You organize your repository, improve the documentation, create issues, and over time you hope someone will contribute.
But this wasn't what I expected.
One person helped my project without writing a single line of code.
We met here on DEV, and later continued our discussions on Discord.
He shared useful resources, gave organizational advice, introduced me to Conventional Commits, and helped me think more seriously about the long-term direction of the project.
The most surprising part is that this happened at a very early stage.
When your project is new, you're still trying to validate the idea itself and understand whether you're building something people actually find useful.
Then he spent hours reviewing the project and wrote a roadmap that aligned almost perfectly with what I wanted the project to become.
What's funny is that we hadn't even discussed many of the future ideas yet.
That roadmap is still one of the most valuable contributions the project has received so far.
Because of that, I decided to invite him as a member of the DebugProbe GitHub organization.
@gimi5555, thank you for allowing me to mention you here.
Thank you for the time, the advice, the honest feedback, and for becoming part of the DebugProbe journey so early.
Even with a 7-hour time difference and living on different continents, we connected through the same thing:
Building software.
And that's one of the things I like most about open source.
Thank you, man 🙏
The roadmap is 🔥
Discord: georgidhristov
Final Words
Open source contributions are not only about code.
Sometimes advice, feedback, organization, documentation, and simply helping someone stay on the right path can have an even bigger impact.
And those contributions deserve recognition too.
Top comments (0)