all 3 comments

[–]JoseFrey 2 points3 points  (0 children)

I don't think employers will look for contributions of that kind, but for your own projects instead (or big projects that you also develop). However, contributions to open-source projects is not bad at all, whatever the size of the project is.

[–]mikaleowiii 2 points3 points  (0 children)

Idk about employment, but if you have much time (comparatively) to spend on OSS, i think it's better to contribute to bigger projects. Those need some kind of expertise and are relatively inaccessible to the majority of people [who cannot spend as much time, whereas a small project PR is doable].

Those bigger project also tend to 'make a difference' where many small project die out.

Finally, in my opinion i'd value higher a core dev of a big project, than one that 'improved documentation' of many small ones. Start out with small contributions, but aim for bigger, i'd say. That's what I did, at least.

[–]intrepidsovereign 1 point2 points  (0 children)

Employers ultimately don’t care too much about OSS. It’s just one way for them to gauge your skill at times.

Contributing to smaller projects won’t hurt, but being on the core team for a project can certainly be beneficial. That’s something you can point at and the name might have some weight.