How Junior Developers Can Contribute to Open-Source Projects
How Junior Developers Can Contribute to Open-Source Projects
One of the best ways to improve your skills is by contributing to open-source projects. Read on to learn more about how.
Join the DZone community and get the full member experience.Join For Free
It's never been easy to learn programming, but one of the best ways to improve your skills is by contributing to open-source projects.
The open-source community provides a great opportunity for aspiring programmers to distinguish themselves. By contributing to open-source projects, developers can improve their skills and get inspiration and support from like-minded people. Most importantly, they can prove that they can build fantastic experiences that people love.
Previously, we have discussed why open source is good for your business. In this article, we'll explain why you should contribute to open-source projects, how to contribute, and what projects to choose. This article is geared towards developers who are just starting their career and would like to get involved with the open-source community (and maybe become a coding genius).
Why Contribute to Open-Source Projects?
There are a number of reasons to contribute to open-source projects. Let's see what motivates developers to contribute.
First, there are a lot of enthusiasts who simply believe that code should be open. They're idealists who want to make the world a better place and it drives them to contribute code. The desire to share can be a powerful motivator.
Second, open-source projects give you a great start. Beginners might start by fixing minor things, such as a bug in a library, sending a pull request, or even writing a piece of documentation. However, beginner developers can also learn to write so-called "clean code" – code that is readable and maintainable – while contributing to open-source projects. When developers realize that their code is exposed to the world, it makes them focus on making that code easy to understand and support. Programmers stick to generally accepted rules within a team, which include norms for indents, descriptions of methods and classes, variable names, and following the don't-repeat-yourself rule. In a nutshell, when contributing to open-source projects you're obliged to conform to the norms of a project.
Third, you get the chance to be part of an active open-source community where you can meet like-minded people and supporters. Moreover, if you're a freelancer and actively contribute to open-source projects, you increase your chances of being noticed by potential employers.
The main reasons why developers go open source are to be recognized, to sharpen their programming skills, and to become part of the vibrant open-source community. Now let's look at what you should consider before you start contributing.
What to Consider Before You Go Open Source
Okay, so you can't wait to start your first open-source project. Let's go through a few tips that might help you choose what to work on.
Type of Project
After you've chosen the language you want to work in, you need to choose the type of project you prefer. Github projects are categorized into folders called Showcases. Here are some examples of Showcases: "security," "virtual reality," "text editors," and "CSS preprocessors." Just choose a topic that interests you.
However, we do recommend paying extra attention to those projects that would be used by a broad spectrum of people so you'll have the chance to test your code on a large real-world audience. For example, the "Emoji" Showcase contains 25 repositories that represent its popularity. Another tip on how to choose an open-source project is to start working on software you already use or software you're interested in using. This will keep you motivated to keep on working.
Large software projects like VLC Media Player or Spree – with thousands of lines of code – aren't the best choice for a beginner. When you contribute to open-source projects of this scale, you're expected to meet the established requirements within that team. A here's another small tip: pay attention to issue labels. Some issues are labeled as "first-timers-only," "beginner," "easy," and so on. You can also find a list on GitHub with collections of projects that suit newcomers.
Consider these tips when choosing a project to contribute to. And always remember to choose the software you're interested in and allocate time in advance.
How to Contribute to Open-Source Projects
When we speak about open source, we can't avoid talking about GitHub and related tools. Let's see what GitHub is and how it helps you participate in open-source projects.
Get to Know GitHub
GitHub is the most popular platform for open-source collaboration, so you'll probably use it when exploring the open-source world. First, you need to create a GitHub account and read the guide that helps you get started. On GitHub, you can contribute to projects by submitting issues and contributing code. Submitting issuesmeans sending messages about errors in applications and suggesting ways to fix them. Contributing code involves sending pull requests with your corrections and improvements.
Learn the Basics
When working with GitHub, you should know how to use Git – one of the most popular version control tools (also known as revision control tools). Because developers constantly make changes to their code, they need a system that can manage those changes in a central repository. In this way, everyone involved in the development process can download a given piece of software, make changes, and submit updates.
Besides being comfortable with revision control tools, essentials skills include being able to clone a repository and send pull requests. Pull requests inform code maintainers about changes made to the code; they can then review these changes, start a discussion about them, or assign them to a further commit.
Join the Community
You can easily join an open-source project by subscribing to the mailing list for that project. You can find mailing lists on official websites or on GitHub pages. After being accepted to the list, you can communicate with team members and get support if necessary. Thanks to the vibrant communities present in nearly every open-source project, you are likely to get quick replies to your questions.
All Skills Are Welcomed
Even non-programmers can contribute to open-source projects! Documentation is needed for all projects, and sometimes this is poorly written and maintained. Thus, you can help by writing, updating or even translating documentation. Also, your design skills might come in handy: every application needs an interface, after all. Finally, you can contribute by managing a community by replying to questions and guiding newcomers.
Ways to Contribute to Open-Source Projects
Let's highlight the most common ways to contribute to open-source projects.
1. Create Your Own Open-Source Project
Every project should start with an identified need. If you feel that existing projects on GitHub or Bitbucket don't offer the functionality you would like to build, then create your own open-source solution. Besides an initial project draft, you should consider the following set of questions:
- What skills do you need for your project?
- How much time are you willing to spend on your project?
- What problem(s) does your software solve?
- How many potential users are there for your product?
2. Create Open Source Alternatives to Commercial Software
Today's commercial projects actively engage open-source solutions. Many companies base their projects on open-source tools. When there's a huge selection of software, you don't need to reinvent the wheel. This is why it's useful to play around with open-source software that can replace similar proprietary software, or that fixes an issue you've recently faced.
Another reason for replacing commercial solutions with open-source software is an eagerness for real innovation and growth. Commercial software claims to be innovative, but its final goal is turning a profit. Open-source software unites best practices, great quality of code and passionate developers willing to code just because they like to.
3. Contribute to Existing Open-Source Projects
You can find many projects you are free to participate in on Github – a developer-oriented platform with a simple but essential set of functionality. GitHub attracts developers with public APIs, a sleek and frequently updated UI, gists (Git repositories) that allow you to share pieces of code or even whole applications, and much more. You can contribute to open source in many ways. Developers can fork projects, make changes to code, and send pull requests. And quality assurance is always appreciated. Sometimes developers are too busy or too lazy to check the quality of their code. So go ahead and report a bug or try to fix it – your help is appreciated.
You can reach the hottest GitHub projects by following the "Trending" link. And in order to make your search more relevant, use advanced search: select the language you would like to code in and choose "best match" criteria. Best match ranks projects according to relevance, taking into account the number of forks (which represents how actively the project is updated) and stars ("likes," in the language of Facebook). Most projects have known issues (however, some don't) with labels like "bug," "discussion," "security," or "refactor," or other labels according to the level of difficulty: "easy," "medium," "hard."
Open-source projects bring many benefits to those who participate in them, and such experience is great for your CV. By joining a community of like-minded people and polishing up on your skills, you can give yourself a step up as an aspiring developer. We've listed common reasons why people contribute to open-source projects and described various ways to get started. If you would like to read more about contributing to open-source projects, check out our previous articles about how open-source projects penetrate the IT market and about the security of open-source software.
Originally published at https://rubygarage.org/blog/how-contribute-to-open-source-projects
Published at DZone with permission of Ievgen Cherkashyn . See the original article here.
Opinions expressed by DZone contributors are their own.