When I asked people, "Hey, what's Github?", the usual reaction was :- (•ˋ_ˊ•)
So I decided to explore this all-mighty God named Github, for whom there's love in every developers' hearts.
I only knew a bit of frontend and CP and so I decided to " contribute to the open-source projects".
I was damn sure that I would fix (if not all) some of the issues and bugs and make Github a better hello world.
But 5 minutes into it and I gave up. I couldn't understand what's going on.
All the issues labeled as "Good-First" are going over my head and I felt like a failure.
After that, I kinda avoided Github and got a bit demotivated too.
Now after a few months, I am back and this time I wanna atleast try to get started with open-source contributions.
But I donno where to start from. It's soo overwhelming.
Can anyone tell me(or rather fix my bug ;) regarding this issue?
(Also sorry for my boring jokes, this is my first post in dev.to,so yeah kinda nervous)
Also before you go, let me show you this meme:
Top comments (4)
Following. This is an issue I notice personally as well. One time I noticed a bug in a project and decided to just fix it really quick (it was a css issue) but I couldn't for the life of me figure out where the change needed to be made. I think most maintainers have a deep knowledge of the project so it seems like an easy fix but to someone who doesn't understand and structure of the project it's a huge task.
ikr....So how can we start as a beginner to contribute to open-source?
Do we have to be like a pro at whatever technologies are being used in the project that we contribute to?
You can make documentation contributions at first -- those totally count!
My colleague has a course for navigating a new codebase that you might find helpful if you happen to use TS typescriptcourse.com/navigate-a-ty...
Sounds good... I'll definitely try this, thnkx