17 Feb
2013
17 Feb
'13
12:44 p.m.
Hello Olle,
A very interesting and important question.
As maintainer and developer of app_python (and upcoming app_java), I'm a
very interested in this question.
I just looked for python's licenses (http://docs.python.org/3/license.html).
Since app_python offers a correct work >= 2.4.3 (at least was tested a week
ago), it's should be licensed under PSF license.
PSF is also GPL-compatible license.
...
GPL-compatible doesn’t mean that we’re distributing Python under the GPL.
All Python licenses, unlike the GPL, let you distribute a modified version
without making your changes open source. The GPL-compatible licenses make
it possible to combine Python with other software that is released under
the GPL; the others don’t.
...
2013/2/17 Olle E. Johansson <oej(a)edvina.net>
Hello from North Carolina where SIPit starts tomorrow!
Reading through the docs on the app_* modules I wonder how the GPLv2 is
handled here. By default, GPL is sticky, so any module linked in to
Kamailio will be GPL-licensed.
With app_mono, precompiled binaries are executed within Kamailio, but not
"linked in" to the core. The question here is if we have a clear
distinction here. If someone developes a Kamailio-based appliance and sells
it - would the customer have the right to app_mono modules under the GPL?
What about python, java and Lua? I don't think these environments
precompile, but they still execute within a GPL environment.
I think we need a clear statement about this in the README, like Asterisk
has for AMI/AGI applications.
Greetings!
/O
_______________________________________________
sr-dev mailing list
sr-dev(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev