We’re creating a more connected travel industry, underpinned by sustainability and long-term investor relations.
An OSS license typically grants the user/licensee a non-royalty right to use, modify and re-distribute the OSS. The OSS license also provides the OSS “as is”. There may be additional obligations to be fulfilled depending on the specific license such as attribution notices.
We’ve discussed the many benefits of using Open Source Software (OSS) previously on this blog and in our landmark Open for business report, but we should also be mindful of the various implications and obligations imposed by OSS licenses.
OSS licenses can be generally categorized into two broad categories:
Copyleft/GPL is one of the most popular OSS licenses and there is already a huge pool of codes released under GPL. Therefore when you release your software under GPL, you can easily find many available libraries and codes to use without worrying about the compatibility of the license with your chosen GPL license.
Permissive/Apache licenses are beneficial due to minimal restrictions. You are therefore able to attract both OSS developers and proprietary software developers to develop software released under the permissive license. Hence you can grow your community in a fast manner.
The license we’ve chosen for our ARIA Templates is the Apache License v2.0. The Apache License is a permissive license, and is very widely known and used in the software industry. It will also help us grow the developer community surrounding ARIA Templates.
We know that this can be a confusing topic – so be sure to let us know if you have any questions below!