-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Relicensing project to Apache License 2.0 #114
Comments
|
Please check with Gerald Spreitz as he has done some similar investigation for other COVESA repos, and I guess it should be synched with at least COVESA technical Steering Team. As I understand it all contributors must agree to the license change. Could be feasible for ifex/vsc-tools as there are a limited set of contributors involved. |
These are all the Author name/email of commits in the current master branch: NOTE: To reduce email-harvesting for spam the "@" will be replaced by "##" here and in later comments.Adrien Leravat Pixep##users.noreply.github.com Every contribution (each commit) will get individual approval for relicensing from the respective author or copyright-holder, and it will be documented here. |
I personally approve the license change for all commits where Novaspring AB (@novaspring.eu) has copyright. |
All commits done by Michael (Mikhail) Tsukerman (Tcukerman) using this author-address: miketsukerman##gmail.com 38d28a9 Michael Tsukerman miketsukerman##gmail.com Each commit is also signed off by a second MBition employee: |
We had an internal discussion at Bosch. Concerning the Bosch contributions we are willing to accept a license change if COVESA TST approves/recommends a license change. |
The default COVESA license is Mozilla Public License v 2.0 (MPLv2) because it provides a good balance between wide adoption and a copyleft effect that reduces risk of privatization of the code base by any party at a later time (see COVESA license policy).
There are however occasionally concerns when tools perform some sort of code-generation. There may be implementation choices that includes some part (or derivative thereof) of the tool source code in the generated result. Even if MPLv2 is generally considered a weak copyleft license, and seems unlikely to intend to have that effect on generated code, it is still desirable by some companies to see a permissive license for tools of this nature.
The Apache License v2.0 is a popular permissive license alternative, because of the other conditions that are included.
Therefore, the IFEX project is now exploring the possibility to relicense the project. This ticket tracks the progress.
The text was updated successfully, but these errors were encountered: