I also mostly contribute on a project that I use or have impact in my productivity as long as it's quick to patch.
For big projects, the goal is different. It's more like self-learning on how it works. A PR can take very long and might require constant merge conflict with the upstream. Also, you might forgot that PR because it takes very long to review caused by other PR/features need to be merged/implemented first before moving on. Asking the community manager or do extensive research first might be necessary before contributing.
It probably makes the most sense to contribute to something that you know and use because you can improve exactly what's missing for you personally and reward yourself with enjoying the benefit of your contribution.
That said you could also have a look at github.com/trending for inspiration.
Personally, I started out with contributing to projects I currently use, whenever I found an unmet need. This will look different for everyone - what languages/frameworks are you currently using?
I do this from time to time as well, but with quite small projects where I need a hotfix or some simple feature to be quickly added, but I've never done it for big projects.
I'm currently focusing all my resources on Flutter and Dart, both at work and on my free time. I'm also quite experienced in JS, TS, and anything web. I've also done quite a bit of Java over the years.
HTML, CSS, Bootstrap, XML, ajax, react js, WordPress, Magento, Shopify, Photoshop, Camtasia, SEO & learning new skills every moment 👨🏼💻 | I believe in learning and sharing with others 🛴
Top comments (9)
I also mostly contribute on a project that I use or have impact in my productivity as long as it's quick to patch.
For big projects, the goal is different. It's more like self-learning on how it works. A PR can take very long and might require constant merge conflict with the upstream. Also, you might forgot that PR because it takes very long to review caused by other PR/features need to be merged/implemented first before moving on. Asking the community manager or do extensive research first might be necessary before contributing.
It probably makes the most sense to contribute to something that you know and use because you can improve exactly what's missing for you personally and reward yourself with enjoying the benefit of your contribution.
That said you could also have a look at github.com/trending for inspiration.
Personally, I started out with contributing to projects I currently use, whenever I found an unmet need. This will look different for everyone - what languages/frameworks are you currently using?
I do this from time to time as well, but with quite small projects where I need a hotfix or some simple feature to be quickly added, but I've never done it for big projects.
I'm currently focusing all my resources on Flutter and Dart, both at work and on my free time. I'm also quite experienced in JS, TS, and anything web. I've also done quite a bit of Java over the years.
Have you tried looking into Flutter itself? That ecosystem is moving quickly, and they do use a good first contribution label.
Interesting, I have not actually. I'll check it out, that might be a good starting grounds
There is lots of open source projects available on GitHub
I also have open source projects 😁
Check out this
GitHub.com/atulcodex
Join on our OSS Project SleekwareDB
Cool, I'll take a look!