Hello there!
TL;DR
In this article, we’re going to see how open-source can change your career for the better and get you out...
For further actions, you may consider blocking this person and/or reporting abuse
I think docs contributions are often looked down on, but they mean a ton.
Hack for first time contribution:
This is a thing that makes everyone's docs more high quality, but usually it's overlooked.
I can definitely see how docs contributions could be looked down upon in our circles. However to our organization, and many others, developers that write great documentation are worth their weight in gold. One of the highest costs we have is the slow ramp of developers into our ecosystem.
Personally, I see it as a sign of maturity.
Love this hack!
oh this is a great idea :)
100% percent :)
heh, now I want to write automation for this. project for this weekend? 😅
This is an amazing tip actually, typos are easy to fix and really bad for documentations. Perfect for the first issue since you generally have to read the docs to do it hahaha
I think I love this. How do I get started with this kind of contributing to open source
Great hack 😀
An amazing write-up, Lucas! I especially like that you selected Wasp as an example for OSS contributions :).
My 2c - even if you find an issue that sounds interesting to you and somebody else has already expressed interest in solving it, IMHO it's often still worth it to ask what the status is and that you would be interested as well. Oftentimes the original assignee didn't have enough time to start/finish, or he could use some help!
It's a great way to start the discussions and meet people along the way - that's often how the best contributions and features are made :).
100% agreed, Matija! It's a win-win situation where you meet new people and potentially make some even greater contributions!
Thanks for the comment!
I have seen it many times!
Contribute a valuable contribution to open-source, and wait for companies to offer you a job!
The most common point of failure for new contributors that I noticed is taking a too big bite -> they jump on a feature that is harder than they predicted, give it a try a bit, spend some energy on it and give up. While this is sometimes unavoidable, there are two things that we can do about that:
detailed explanation.. and it's true in my case.
I am maintaining the forked version of Django JET (original maintainers archived it). then I updated jQuery and jQuery Ui library and synced with every django upgrade.
i am getting calls from companies whoever see my profile on LinkedIn.
Wow! That's so good to hear! Keep it up with the good work and thanks for sharing your experience on this!
But how do we get acknowledgement and recognition for our skills and contributions? What if it was as easy as editing the CHANGELOG.md? Namely, repository owners could add a machine-readable file (e.g., yaml, json) to denote the different contributions of direct or indirect contributors. WDYT?
That's a great idea! For smaller repos I think that's perfect actually, now, for larger repos with thousands of contributors I think it can be a little impratical though.
A similar way to showcase that could be approached from the POV of a repository owner is to reference the people that helped in the release tag too!
Here's an example.
I'll edit the post to add this info because I think it's super relevant! Thanks for the comment @alenhorvat!
By reading your post and doing some research I also found github.com/all-contributors/all-co...
We're also discussing with skills recognition/HR communities about adding skills acknowledgements: github.com/skillJot/git-recognise
git and git platforms represent a new opportunity to acknowledge skills and contributions in a transparent and verifiable manner. Does any of this make sense? :)
Nice article! It's great to see that people are realizing that open-source has so many benefits, including helping you level up your skills and land you sweet jobs :)
Being proactive in general will lead to success. Especially contributing, you're showcasing your skill, and more importantly, determination.
Determination is totally the keyword here! Thanks for the comment!
I love this article
I used to think making contributions to open source had to be code only
Thanks for the tips
Nice stuff!
I can relate!
Great article 💯
This PR landed me on the desk of a Facebook recruiter. Nearly five years on I'm over in the US, still working here. Contributions count!
That is so awesome to hear! Awesome comment @hsimah!