The results of the initiative to change the LLVM project from the BSD-like UIUC/NCSA license to the Apache 2.0 license, with exceptions added for compatibility with GPLv2 and to address licensing issues when incorporating parts of the compiler and runtime libraries into executable files, have been summarized. Since developers in the LLVM project do not sign an agreement transferring ownership rights to the code, explicit consent from all participants is required to change the license. The re-licensing process began in 2018, and over the course of 8 years, consent for the license change has been obtained from more than 1,300 developers and around 100 companies.
Code added after January 19, 2019, was accepted under the new license, so the main objective of the initiative was to obtain consent from the developers of previous changes. Currently, 99.5% of the project's codebase is covered by the new license or is not subject to copyright (changes in fewer than 10 lines of code). The continued search for developers to cover the remaining 0.5% is considered pointless. Those who disagree with the license change can contact project representatives, and their code will be appropriately marked in the SPDX metadata.
Following the release of LLVM 24, scheduled for early 2027, the next LLVM 25 branch will come with updated LICENSE files and relevant licensing information in the code files. Third-party libraries integrated into LLVM will retain their own licenses.
The primary reason for changing the license to Apache 2.0 is to protect users and development participants from patent lawsuits and relieve companies wishing to participate in development from the complexities of transferring patented technologies. The Apache 2.0 license requires granting rights to use patents related to the open source code and includes provisions to minimize risks from patent litigation (the license is revoked in the event of a patent lawsuit against the creator of the open source code).
The license change also helped eliminate inconsistencies in the licenses for runtime libraries and other compiler components that hindered code exchange with runtime (compiler_rt was supplied under the UIUC/NCSA and MIT bundle, while the compiler was only under UIUC/NCSA). One of the advantages of Apache 2.0 is its one-way compatibility with the GPLv3 license, allowing the use of code under the Apache 2.0 license in GPLv3 licensed projects.
Incompatibility with GPLv2 has been overcome by adding a special exception that discards certain sections of the Apache 2.0 license when using code in GPLv2 licensed applications, in the event of a licensing conflict or litigation. The exception applies only to combined products that incorporate LLVM code with GPLv2 licensed code. The added exception also includes a clause that waives the requirement of the Apache 2.0 license to retain copyright notices, attach the license text, and note modifications for the compiler and runtime libraries included in object and executable files.
Source: opennet.ru
