11. Solving licensing issues of contributed code¶
Note: the author is not a lawyer and the contents in this section may not be legally complete. Ask lawyers for the legal advices.
11.1. License of Erlang/OTP: Apache License 2.0¶
Rami Sass explains the summary of how Apache License 2.0 works in the blog entry Top 10 Apache License Questions Answered. Some of the points are quoted here as follows:
- Apache License 2.0 is a permissive open source license.
- You can freely use, modify, distribute and sell a software licensed under the Apache License without worrying about the use of software: personal, internal or commercial.
- If you redistribute software with any Apache licensed components, you must include a copy of the license, provide a clear Apache License attribution, and add modification notices to all the files that you modify.
- You can choose to release the modified or derived products under different licenses. The unmodified parts of the software, however, must retain the Apache License.
- You cannot name your modified version in any way that suggests that the final product is endorsed or created by the Apache Software Foundation.
- Every licensed file must contain any original copyright, patent, trademark, and attribution notices in its redistributed code.
- Each modified file must also contain a notice about all the changes made to the original file.
11.2. Compatibility of Apache License 2.0 with other licenses¶
Mixing source code which has other licenses than Apache License 2.0 should be done carefully.
11.2.1. GPL version 2 and 3¶
Software under GNU Public License (GPL) cannot be directly linked to Erlang/OTP, due to the license compatiblity with Apache License 2.0.
According to the document of Apache Software Foundation about Apache License 2.0 and GPL compatibility, the following issues must be considered:
- Software with Apache License 2.0 is compatible with GPL version 3 (GPLv3), but the derived product must be licensed under GPLv3.
- Software with GPL version 2 (GPLv2) is incompatible with Apache License 2.0, citing the patent termination and indemnification provisions as restrictions not present in the older GPL license.
11.2.2. MIT and BSD licenses¶
Including MIT and BSD license code in Erlang/OTP does not require any special process, because both license allow relicensing of the software, under the restriction of keeping the original notices.
11.3. Relicensing your code to Erlang/OTP¶
When OTP Team decides to include your code as a part of OTP, you need to comply the following rules:
The code is relicensed as Apache License 2.0, and no other licenses are allowed in the code.
The copyright notice in the code must be a simple one like this:
Copyright (c) 2017 by Kenji Rikitake.
Note that the notice has no “All Rights Reserved” or other words except the year and the name.
OTP Team will let you know the details on the exact conditions before merging your code, so that the legal issues will be cleared.
If you are using other authors’ algorithms and code, they must be compatible with Apache License 2.0 of Erlang/OTP. You may need to obtain written permissions from the original algorithm authors for specific relicensing to Erlang/OTP.
|||On versions 17.x and before, Erlang/OTP was licensed under Erlang Public License 1.1, a modified license from Mozilla Public License. This is no longer applicable.|