In my contributor guidelines, I usually include the tip:
commit often commit early. Open a draft pull request in the early development stage so you can recieve feedback (and some hints around potential pifalls) about your approach.
I build practical applications that save time, improve workflows, and turn ideas into real products. I believe in learning, sharing real lessons, and building tools that create real-world impact.
This is super helpful! 👏 I’ve always wanted to contribute to open-source AI projects but didn’t know how to begin. The step-by-step guide makes it seem much more manageable. Thank you for simplifying it!
Focused on practical web solutions and online utility platforms. I work with real-world data, usability, and performance to build simple and reliable digital tools. Learning and improving every day.
Such a detailed guide, I really love it!
I actually published a post on this topic today as well, where I cover the broader why and how of contributing to open source.
100% agree with that you wrote there @alikhil ! It's definitely quite helpful for learning and networking!
In my contributor guidelines, I usually include the tip:
+1
I'd usually ask contributors to first describe what they are planning to do and get the okay from the team before assigning the issue.
Loved your detailed 30-day action plan.
Thanks @abdullahjan !
Informative
This is super helpful! 👏 I’ve always wanted to contribute to open-source AI projects but didn’t know how to begin. The step-by-step guide makes it seem much more manageable. Thank you for simplifying it!
I’ve always wanted to contribute code, but I never really knew how to do it.
Now I finally understand. Thank you so much for your guidance!
Informative