Thanks for signing up.
We'll see you soon 👋
We'll see you soon 👋
So you've decided you're gonna dive into the world of Open Source as described previously and you hear terms like "PR", "repo", "commits" etc. You also get to hear about "issues", "merging" or "branching". Well, other terms can wait but in this article, I'll tell you all about what an issue is and how you can take advantage of this nifty feature of the open-source environment to start learning a new programming language! Who's excited?
Whenever you visit a project on an open-source platform like GitHub, you are presented with it's 'homepage' called the repository or simply a repo. Next to that, you can see a few other tabs, the first one being labelled as "Issues". You see a list of different issues that exist in the project currently.
Issues are one of the best ways to pitch your idea to start an open-source contribution to a project.
It can be anything from a feature request, giving your idea, adding a bug report or advising an enhancement to the repo owner. As you can see, issues can have several aspects to them. One may be of really low importance, the other a 'critical' one which should be fixed ASAP. Therefore, they're marked with 'labels' so that other people contributing can know the importance of each issue.
Issues can simply be used to kick off a conversation or discussion. Did you get an idea? Unable to understand how a specific module works? Open an issue and talk about it. This is one of the great ways to take your idea and making it a 'move' towards a contribution.
Having an issue tracker in an open-source project helps a lot. Its main aim is to manage and maintain lists of issues. Let's see how much value they provide with their important features:
As you may see, it's an issue tracking system built within the WorksHub platform. Let's open an issue and see what we get.
We have the following important things to look in this issue:
And most importantly, you can see the programming language required to work on this. WorksHub is built upon the listed language i.e. Clojure so it's obvious that this issue is also available on GitHub.
To start working on an issue, you must know what's required and what the issue is about. We know two things are required here, first the Clojure programming language and second, the issue is about the image upload failure.
If you don't know these, you can not solve this issue. Let's imagine you're new to Clojure, you've never worked on it before. Here are some steps you can take to learn it and then implement in an open-source issue:
Engineers who find a new job through WorksHub average a 15% increase in salary.Start with GitHubStart with TwitterStart with Stack OverflowStart with Email