There's more than one type of open source license. Here, we break down your open source licensing options.
Open source licenses are licenses that comply with the terms of open source software.
Open source licenses set the conditions of how software code can be shared and the level to which the authors are protected. All software (even open source software) that is going to be public needs to be governed by a license that protects the copyright holders of the code. The Open Source Initiative (a non-profit organization) determines licenses have authority. There are almost 100 licenses that the Open Source Initiative has approved.
Organizations often utilize several types of open source software with different types of licenses. If you’re already running open source, run an audit of your running projects and determine which licenses you’re currently under before adding another.
With all this in mind, which open source license is right for your organization?
Permissive licensing is a form of open source licensing that allows a person or company to use that software to create products that require a paid license. An example of this type of license is the Apache 2.0 license by the Apache Software Foundation. It is the most popular and widely used permissive license.
Under this license, people change the code, rebrand it, and never have to give attribution to the software provider. An organization that uses permissive-license open source in a product could deploy that software behind some form of digital rights management (DRM) regulation. What this means is that no one outside of the company can access the “open source” software, so it is essentially closed source software.
Software that comes with nonpermissive licenses enforces freedom with software. An example of a nonpermissive license is the General Public License (GPL) that ensures users have the freedom and responsibility to share their changes with the community. It is the most widely used nonpermissive license. Nonpermissive licenses guarantee the freedom of developers and end-users. When you improve upon the source code and it benefits your company, you have to give it back to the community. This level of sharing is required to ensure the openness of the software. It is not for the developer who’d rather keep their changes within their organization.
The State of Open Source ReportFind out what you need to know about open source. This report provides data on the most popular open source technologies used today, and sheds light on the barriers and benefits teams experience when adopting open source technologies.GET THE REPORT
Find out what you need to know about open source. This report provides data on the most popular open source technologies used today, and sheds light on the barriers and benefits teams experience when adopting open source technologies.
GET THE REPORT
The answer to this question it depends on your use case within your open source software stack. Are you needing to solely use the software or are you creating software? The type of use has various considerations when deciding what license to be under:
Consider what does your organization needs to protect. If your organization has sensitive information, you’ll want to be careful that your software license will protect your information. Choosing a nonpermissive license may force you to share information. If you are not going to be making changes to the source code of the software, permissive licensing should serve you well.
Examine why you’re creating the software in the first place. Thinking about why you’re doing what you’re doing to help you choose the type of license that suits you best.
Yes, open source is free for commercial use. However, commercial is not the same as proprietary.
Take the time to consider what license makes sense for you based on the value you need to get from it. If your organization is going to use any open source software, be aware of the liabilities you will be held to:
Do you have questions on how open source licensing works, or which one is right for you? OpenLogic by Perforce has a team of expert architects ready to help you navigate what is best for you.
TALK TO AN EXPERT
Ex-Chief Evangelist - OSS & API Management, Perforce Software
Justin has over 20 years of experience working in various software roles. He is an outspoken free software evangelist, delivering enterprise solutions, technical leadership, and community education on databases, architectures, and integration projects.