Licences#

Licences ensure that communities behind many of today’s most innovative technologies can protect their creations in whatever way they see fit. The open source licence determines how openness is defined from a legal perspective. Depending on whether one wants to license a small software tool, a larger framework, datasets or an internet service, the choice of licence can determine the long-term strategic direction. In this way restrictions, conditions and guarantees are defined by the authors under which use and derivations are possible. Especially for commercial use, licensing criteria play an important role. Websites like ChooseALicense can help you choose the right licence. The distribution of licences reveals the orientation of the open source ecosystem towards more permissive licences or copyleft licences.

data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7

Fig. 29 - Distribution of licences#

Permissive licences like BSD, Apache and MIT are the most popular in the field of sustainability. The MIT licence was the top choice, used in ~26% of the projects. MIT is a short and simple permissive licence. Permissive licences are easier to use in commercial products, and unlike the copyleft licence, they do not enforce the release of all code under a similar licence. Permissive licences like MIT create many opportunities for the reuse and commercialisation of OSS projects within proprietary software. Projects under this licence, on the other hand, may be jeopardised by the use of proprietary products. Companies are not required to release bug fixes or enhancements, so improvements cannot be contributed back to the open source project. In some cases, this can lead to developers losing motivation to contribute over time as it becomes apparent that the capacity for the overall development effort is diminishing.

The second most used licence was a Custom licence, used in 24% of the projects. All projects that could not be mapped to standard open source licences based on the SPDX License List are considered custom licences. Licences with modifications from the original open source licences also fall under this category.

GPL 3.0 is the third most popular licence used by 17.3% of all projects. Permissions under this strong copyleft licence require licensing the entire source code of the licenced works and modifications. GPL was created to protect software from becoming proprietary, or private. Copyright and licence notices must be preserved and contributors provide an express grant of patent rights. Copyleft licences are more prevalent in business models that rely on direct monetisation of the core project.