GitHub’s Guide to Open source

There are thousands of open source projects in GitHub and a number of people working on them. As deduced from the issues or the state of the project, they need help. On the other hand, people are looking for projects to improve themselves, just like me looking for, when I was a first grade bachelor student. To match the demand and supply, GitHub released a guide to contribute to an open source project. You can find the link, here.

By contributing to an open source project, people could gain variety of skills. As mentioned in the guide, there are examples like @errietta. One does not need to be a coder to work on such a project, there is room for different talents or interests like designers, organizers, or just helpers(who helps people having hard time when installing the software, for example). Contributing to projects, actually, creates a portfolio for the people, which could be shown as a proof of skills and dedication in professional life. Another benefit is that it gets the people ready for a team environment, which is, I think, the most important one.

In GitHub’s guide, different types of roles in a project mentioned, each of them has a value to add to the project.

One of which is event planners, where people could set up team meetings to collaborate and interact better.

The other one is designers. There is always a need for usability improvements, and designers are the solutions to it. A nice user interaction or interface could kick a project to the top.

Organizers could arrange the issues of the project. A lot of projects have duplicate issues which messes with the issue system, and finally reduces the performance of the team. By helping them organizing the issue system, or even structuring it, a great contribution could be made.

Today, projects consist thousands lines of code, and it is very hard to read and understand for a starter. In this scene, documentation comes into the game. Writing documentation for even small part of project, helps each person trying to understand what is happening in that part, which expedites the progress a lot.

Of course coders are welcomed, too :) After finding an open issue or a bug and talking to the team, one could start fixing the code or even implementing a new feature. At the end, this is a win-win situation, and for my case, to help makes happy :)

I wish I would have known such opportunities years ago, but it is never late. Why not find a project and start working on it? After finding one, I will be writing under this post as comment.