Recently, I was in a group that was talking about personal projects and growing your developer skills. Nick made a good point when he said that you...
For further actions, you may consider blocking this person and/or reporting abuse
Before contributing to open source, you should really understand what you are doing and why. Blindly participating in open source because 'it will be great for your career' isn't really a great thing to do - and the advice to do so is flawed...
This is a great read on the topic, that gets it right:
💡What contributing to open-source is, and what it isn't.
Samuel-Zacharie FAURE ・ Apr 19
Hey Jon Randy can you please suggest that how can I find best repository for open source.??
My post next week is going to talk about that too. But I don't necessarily disagree with Jon.
That's just the point - you shouldn't really go actively looking for projects to contribute to. It should be something that happens organically, and something you feel you want to do. Ideally it should be a project/library/document/whatever that you've already used and are working with, and can see something you could fix/improve/add.
I am glad I found this! Thanks a lot for the effort and such detailed self-assessment check list. I started my open source journey with a very supportive organisation. Now thanks to you, I get to explore more 🙂
Congratulations! What project are you contributing to?
Thanks! Started with an organisation called Savvato.
Planning to contribute to OpenSauced as soon as I my skills pass the assessment👍🏾
Hi BekahHW,
Top, very nice !
Thanks for sharing
Really useful post. This help's me a lot....
To assess your skill level before contributing to open source, consider the following steps:
Review project documentation: Check the README, contribution guidelines, and issue tracker to understand the project's complexity and requirements.
Evaluate your experience: Reflect on your familiarity with the project's technology stack, coding standards, and similar past projects.
Start small: Begin with minor issues like documentation updates, bug fixes, or small feature enhancements to gauge your comfort level.
Seek feedback: Submit your contributions and request feedback from maintainers to identify areas for improvement.
By following these steps, you can better understand your readiness and grow through practical experience.
Unpopular opinion: Just start. Yes, it's important to pause and reflect what you are doing and why. Yet for starters, the open source projects you are interested are likely to have a large code base and you will never feel good enough to contribute. What most open source newbies don't recognize is that you don't have to make big contributions. Making a PR to correct a typo is a valid contribution. It's easy to get approved, and it's a good way to get the ball rolling because it boosts your motivation.
Amazing post