-
Notifications
You must be signed in to change notification settings - Fork 37
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
License question #29
Comments
Thanks @g3n35i5. First of all I'm really open to put pysoem under a more permissive licence. But as SOEM itself is under a GPL-2.0 licence, and the wrapper directly compiles SOEM code, I decided to put pysoem also under GPL-2.0. Thus I don't get into trouble. And for the ease of use, it is really good to compile SOEM directly into pysoem, thus one dose not need to compile SOEM separately in order to use pysoem. However SOEM has a special exception in it's licence terms. I'm not good with leagel issues. Somehow it reads as it would be okay to put pysoem under another licence. But I'm not sure. That is also because I use a slightly patched version of SOEM. |
Thanks @bnjmnp for your quick answer! I totally understand from this aspect why you chose the same license. To make it as transparent as possible: I want to use pysoem in my company in a commercial project. We already have a license to use SOEM. I will have a closer look at the license terms on monday and get back to you as soon as possible! Best regards and many thanks! |
Hello @bnjmnp! I'm sorry that I didn't manage to get back to you until yesterday. Your fork of SOEM uses the same license as SOEM without modifications. The GPLv2 License allows you to do so as long as you're publishing it. So your fork is safe. As you've mentioned correctly, the SOEM license (which inherits from the GPL2.0 license) and thus the license of your fork
So let's have a look at the corresponding section in the GPL2 license:
So far so good, you've published the pysoem code, so i think you can put pysoem under a more permissive license, e.g. Apache/MIT/BSD. Another useful comment which underlines my point of view can be found here: OpenEtherCATsociety/SOEM#44. Disclaimer: I am not a lawyer, just a programmer, and as such none of the above should be construed as legal advice. |
Thank you for your research, this all sounds plausible to me. I'll think through this a one or two more days. |
So, it's done, I made the change. |
Great thank you! |
Dear @bnjmnp,
thank you very much for this great wrapper! I would like to know why you chose a GPL-2.0 licence, which allows commercial use, but only under the condition that the source code must be published.
Therefore I have two questions:
Many greetings and many thanks
The text was updated successfully, but these errors were encountered: