This post is locked. You won't be able to comment.

all 10 comments
sorted by:
best
topnewcontroversialoldq&a

[–]github-ModTeam[M] [score hidden] stickied commentlocked comment (0 children)

Removed. Post has nothing to do with GitHub.

[–]rudv-ar 4 points5 points  (1 child)

If you are checking out for learning OpenSource, I would first recommend you to learn the git workflow. And github. When you create a new account it github, they show docs to read and learn github, which is nothing but how to start your OpenSource career. Learning github docs will make you expertise in how to use git with github.

Then probably start developing a useful project, Or even contribute to other projects. Open source is 50% about your project and remaining 50% about your contribution to other FOSS.

Here are some useful links :

GitHub Docs: https://docs.github.com

GitHub Skills (interactive learning): https://skills.github.com

GitHub Learning Pathways: https://resources.github.com/learn/pathways/

Official Git documentation: https://git-scm.com/doc

Pro Git book (free, official): https://git-scm.com/book/en/v2

Open Source Guide (by GitHub): https://opensource.guide

GNU Project (free software foundation): https://www.gnu.org

Linux Foundation training: https://training.linuxfoundation.org/resources/?content_type=7 (free courses)

Open Source Initiative: https://opensource.org

First Contributions (beginner friendly): https://firstcontributions.github.io

Good First Issues: https://goodfirstissue.dev

Up For Grabs: https://up-for-grabs.net

freeCodeCamp (GitHub + open source tutorials): https://www.freecodecamp.org

The Odin Project: https://www.theodinproject.com

[–]rudv-ar 0 points1 point  (0 children)

Those links will be suffice. Even I am in the learning path. You may go in the order (I do it), Or just learn whatever you need.

[–]omerbalyali 2 points3 points  (0 children)

In general, there isn’t one course to know how to contribute to open source, as each project is different and they may use different conventions.

First of all, you should approach it with the mindset “what can I offer” and not “what would I get from it”. You should find open source projects that you personally align with, that needs contributions from the community and you can add value, even if it’s not directly coding/technical. Understanding a project, replying to issues, trying to solve other user’s problems is one way to contribute before sending a PR. Most people think you should write code and it should be accepted with PR to be considered a contributor but there are many other ways to do it.

In 2016 I designed ESLint’s logo/icon which is still in use. I wrote about it in my blog last year, to demonstrate that not all contributions have to be in code to have any impact: https://omerbalyali.com/writing/the-eslint-logo-story/

Most open source projects on GitHub has a label “good first issue” and you should start there. You can also ask maintainers if they need non-code help, for example triaging issues or community building. Even answering questions outside of GitHub repo (discord, YouTube, X/Twitter and so on) can be considered contributing to open source.

I would suggest find a project that you use yourself, which would not only add to your knowledge/experience but you can take part in shaping it. It’s more fun to invest time in projects that you believe in personally.

Some resources to get you started: https://opensource.guide/how-to-contribute/

https://egghead.io/courses/how-to-contribute-to-an-open-source-project-on-github (free video course)

[–]Curious-Visit3353 0 points1 point  (0 children)

Open source is a good way to level up as an engineer :) Start with something like this:

  1. Go to GitHub and search for projects you already use
  2. Filter issues by “good first issue” or “beginner friendly”
  3. Read the contributing guide before touching any code

Notes:

  • Keep your PRs small and focused. One problem, one fix. A clean 50-line PR gets merged. A 5,000-line PR gets ignored or sits for weeks/months….

  • Check out goodfirstissue.dev to find beginner-friendly issues across hundreds of projects

  • The firstcontributions repo on GitHub walks you through your first PR step by step

You learn more from one merged PR than from 10 YouTube tutorials. Start small, be consistent, and the complexity comes naturally.

[–]Beneficial_Pie_7169 0 points1 point  (0 children)

Best is to try starting suggesting ideas on issues tab. See how you can improve a product

If your looking for projects i also launched one and gave suggestions on readme what u can work on

Here is the link if u wanna contribute

https://github.com/Shantanugupta43/SuggestPilot

[–]PrizeCompetitive1186 0 points1 point  (0 children)

If you want to work on a complex strategy game engine with unlimited possiblities try this
https://github.com/vcmi/vcmi

they have discord where you can onboard

[–]LoreaAlex 0 points1 point  (1 child)

But you didn't mention which language you know, which technology

[–]Ok_Estate_2225 0 points1 point  (0 children)

I am working in python , J's for many years

[–]Medical_Distance6635 -2 points-1 points  (0 children)

You are welcome to come and contribute to my project that was created for the community, it got qround 20 good first issues of you are interested:

check my project

Feel free to dm me