Closed thorade closed 6 years ago
When choosing a license for my Modelica library, I found @dietmarw's and @mtiller's Where impact got Going helpful.
So what should the library developer do? The simplest solution is to not use the “Modelica License Version 2.0” for libraries but rather go for standard licenses that are more compatible with open source, community driven development (e.g., MIT or BSD licenses). Interestingly, the old “Modelica License Version 1.1” is still suitable for user libraries since it does not contain the restrictions of having to change the package name.
@raulrpearson Thanks. Also, one can find a lot of related issues here on github: https://github.com/search?q=license+language%3Amodelica&type=Issues&utf8=%E2%9C%93
The MSL is now licensed under BSD-3 https://github.com/modelica/Modelica/issues/2320
The corresponding IBPSA issue is here: https://github.com/ibpsa/modelica-ibpsa/issues/890
MSL and IBPSA are now under BSD3, so that we can also switch any time now.
The Modelica Association seems to be switching to the BSD-3-Clause license (instead of Modelica license) for the Modelica Standard Library: https://github.com/modelica/Modelica/issues/2320 https://github.com/modelica/Modelica/pull/2373 Once that is completed and released, we should consider switching to BSD-3-Clause as well.
https://choosealicense.com/licenses/bsd-3-clause/ https://opensource.org/licenses/alphabetical