Closed AnHeuermann closed 2 years ago
We need to sort out the license before merging this.
Should we merge this? I don't have the rights to do so. Not sure about the license, though.
I think we can merge it so we are making some progress, otherwise this PR risks getting stale. It is always possible to make other ones in the future. @sjoelund are you fine with that?
Regarding the license, I would use OSMC-PL as for the OMC source code. Which means, GPL v3 if you're not a Consortium Member, can do modifications and redistribution without GPL v3 conditions if you are a Level 2 member. I see no reason to do differently.
@sjoelund, @adrpo what do you think?
Some things, like OMPython, are using the OSMC-PL runtime license (BSD3)
The runtime, of course we want people to be able to run OMC-generated code without any license issues, otherwise we'd become almost like any other commercial vendor. I'm not 100% sure why this would apply to OMPython's source code.
In any case, this is a separate tool for testing of libraries, that we developed, and can probably be further improved. I guess the regular OSMC-PL suits better, because it forces people to either share the improvements they may make to it, or at least to join the OSMC if they don't want to.
GPLv3 doesn't require them to publish changes to the source code unless they publish the changed software. And given that it's Python code, if they do you pretty much get the changes.
Okay, I have added OSMC-PL to this PR.
Related Issue
13, #14