License Type (which license to use and why?)

Choosing the right license for your GitHub repository is like choosing the rules of a game: it defines who can play, how they can play, and if they can take the board home. Without a license, your code automatically falls under standard copyright law ("all rights reserved"), which ironically prevents others from legally contributing to or using your project.

Here is a practical guide to help you decide which license to use and why.

1. Why is a license fundamental?

In the Open Source world, a license is what differentiates "public code" from "free software." It serves to:

• Protect you: It exempts the author from liability (warranty) in case the code causes issues.

• Grant permission: It explicitly authorizes the use, modification, and distribution.

• Set limits: It establishes whether the code can be used in commercial projects or if modifications must also be kept open.

Choosing the right license for your GitHub repository is like choosing the rules of a game: it defines who can play, how they can play, and if they can take the board home. Without a license, your code automatically falls under standard copyright law ("all rights reserved"), which ironically prevents others from legally contributing to or using your project.

Here is a practical guide to help you decide which license to use and why.

1. Why is a license fundamental? In the Open Source world, a license is what differentiates "public code" from "free software." It serves to:

Protect you: It exempts the author from liability (warranty) in case the code causes issues.

Grant permission: It explicitly authorizes the use, modification, and distribution.

Set limits: It establishes whether the code can be used in commercial projects or if modifications must also be kept open.

2. Most Common License Types

We can divide licenses into two major categories: Permissive and Copyleft.

Permissive Licenses (Total Freedom)
These focus on simplicity. You allow others to do almost anything with your code, as long as they give you credit.

• MIT: The darling of GitHub. It’s extremely short and says: "Do whatever you want, just don't sue me and keep my name in the credits." It is ideal for libraries that you want everyone to use, including companies in closed-source products.

• Apache 2.0: Similar to MIT, but offers extra protection regarding patents. It is the default choice for large corporate projects (like Android).

Copyleft Licenses (Reciprocity)
These focus on preserving software freedom.

• GPLv3: If someone modifies your code and distributes it, they must release those modifications under the same license. This ensures the software stays free forever.

3. Quick Comparison

4. Which one to choose? (Decision Guide)

1. "I want it to be as simple as possible": Go with MIT.

2. "I want my code used by companies without fear of lawsuits": Go with Apache 2.0.

3. "I want to ensure that whoever improves my code shares those improvements": Go with GPLv3.

4. "I don't care about anything, do whatever you want": Use Unlicense (Public Domain).

Golden Tip: How to apply it on GitHub

GitHub makes this process very easy. When creating a repository or adding a new file named LICENSE, it offers a selector with summaries of each license.

Remember: Choosing a license is not just bureaucracy; it is a statement of intent about the future of your community.

Source: Guide