Bits and Pieces
7 min read Jan 4, 2021As software developers, all of us are aware of the two types of licenses available for software. They are,
In this article, I’ll mainly focus on open-source licensing models and explore what they offer.
All of these licenses fall under two categories; Copyleft and Permissive. We’ll find out what each of these means and categorize them as we explore each of the licenses.
Let’s have a look at what each of these licenses offers.
This particular license implements the concept: copyleft. As the name suggests, it is the opposite of copyright. When software is released under this license, the recipients are granted the following benefits.
This enables the collaborative development of software projects but offers high protection for the author of the software.
Even though this looks like a lot of freedom compared to copyrighted software, out of the open-source licenses set, this is one of the most restrictive licenses as it enforces the condition where a source code with GPL can only include a composition of GPL code.
The latest release of GPL is GPLv3, which includes patent indemnity, internationalization, and remedies for license infringement as upgrades from GPLv2.
To use GPL, you have to include certain information in the source code and a copy of the license. The practical usage of this is not as easy as it sounds. If you want to know more about the practical usage of GPL, refer to this practical guide.
Further, if you release a source code under GPL, you cannot revoke this right you gave to the community. However, you can choose to redistribute it under a different license. But, even if you decide to change the type of license, other developers who already obtained your source code under this license can choose to continue distributing it under GPL.
Say goodbye to monolithic applications and leave behind you the tears of their development.
The future is components; modular software that is faster, more scalable, and simpler to build together. OSS Tools like Bit offer a great developer experience for building independent components and composing applications. Many teams start by building their Design Systems or Micro Frontends, through shared components. Give it a try →
LGPL is another GNU license which grants fewer rights than GPL. It is suitable for software that requires linking from non-GPL and non-open-source software.
For example, if you are releasing a library which is meant to be used in many software, if you release it under GPL, the software which uses it is also required to be released under GPL. This is a massive problem as commercial software also use a lot of third-party libraries. Therefore, it is best to release a library under LGPL, which avoids the above problem. This is a weak copyleft license.
LGPL consists of the following conditions in comparison to GPL,
The Apache license is a permissive license. Unlike copyleft licenses, a permissive license does not require software applications that re-use code with Apache license to be released under the same terms.
It does not require any derivative work to be distributed under the same license. Therefore, non-copyleft.
Work under the Apache license has the following benefits.
The Spring Framework, the Android OS are some of the software and technologies that use the Apache License.
The BSD license has two main versions: 2-clause (Simplified BSD license) and 3-clause (New BSD license). This is a permissive license.
The benefits provided by them are as follows.
The primary difference between 2-clause and 3-clause is that 3-clause includes a specific rule about endorsements. It says that the names of the contributors cannot be used for endorsement without obtaining special permission.
Popular projects such as Redis, Ruby, Nginx use BSD licensing.
The MIT license is the least restrictive permissive license out of the open-source licenses.
Anyone can do anything with the work as long as the license is included along with it.
The only restriction this has it to accompany the work with the MIT license. As long as that condition is met, you can use, copy, modify the software and distribute it for free or even sell it. There are no restrictions on distribution.
This license can be combined with any other license. Therefore, it is suitable for commercial purposes.
Now that we’ve learnt about a few open-source licensing models, then comes the next question.
In order to understand the correct license to use, the following questions need to be answered by you.
Likewise, based on your requirements, the license you have to choose would differ. After some research about similar software to yours, you will be able to decide which license to go with. The insights provided in this article about each license will help you make that decision better.
Open-source licensing is a massive topic. In this article, I have discussed and compared a few but popular open-source licenses. But there are many more out there. Once you’ve decided on the best license for your open-source project you can add it to your GitHub repository using a LICENSE.txt file.
In order to summarize the permissions and conditions provided by open-source licenses, refer to the chart below.
Hope you got some insight about open-source licensing models and what they offer. Let me know if you need more information about how to choose a licensing model for your software too.