[OpenSIPS-Users] [OpenSIPS-Devel] [HELP] Advising on GPL license issue

[Binan AL Halabi]

Hi Bogdan,

I think Opensips modules are considered derivative to the core ( OpenSIPS module needs "help"
from the core. It is not stand alone  ). 


Special exception clauses can only be applied to an original  work and never a 
derivative. If the core is linked to the lib then all the copyright 
holders of the core states the exception.

You can go around this by considering this module as part of original work not derivative. In this case we backed to above (All must state the exception).


This must be confirmed by IP lawyer.
// Binan.



________________________________
 Från: Bogdan-Andrei Iancu <bogdan at opensips.org>
Till: Binan AL Halabi <binanalhalabi at yahoo.com> 
Kopia: OpenSIPS users mailling list <users at lists.opensips.org> 
Skickat: måndag, 3 december 2012 13:05
Ämne: Re: [OpenSIPS-Devel] [HELP] Advising on GPL license issue
 

Hi Binan,

And this exception clause (btw, found something similar here
      http://lists.debian.org/debian-legal/2004/05/msg00595.html), needs
      to be stated by the copyright holders of this new opensips module
      (that will link to the lib) or by all copyright holders from core
      + module ? This is the tricky part :)

Thanks and regards,
 
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 12/01/2012 02:11 AM, Binan AL Halabi wrote: 
Hi Bogdan.
>
>Yes .
>Special exception clauses allows this combination (linking).
        This is what i know.
>
>
>// Binan
>
>
>
>________________________________
> Från: Bogdan-Andrei Iancu <bogdan at opensips.org>
>Till: Binan AL Halabi <binanalhalabi at yahoo.com> 
>Kopia: OpenSIPS users mailling list <users at lists.opensips.org> 
>Skickat: fredag, 30 november 2012 17:57
>Ämne: Re: [OpenSIPS-Devel] [HELP] Advising on GPL license issue
> 
>
>Hi Binan,
>
>Already when through that page, but not 100% clear.
>
>As I understand it, to make it possible you should :
>    1) the copyright holders of the GPL code should
                  agree on an exception to link against the non-GPL lib
>    2) owner of the non-GPL lib you give you the
                  permission to use it (if not fully public).
>
>?
>
>Regards,
> 
>Bogdan-Andrei Iancu
OpenSIPS Founder and Developer http://www.opensips-solutions.com
>On 11/30/2012 06:25 PM, Binan AL Halabi wrote: 
>Hi Bogdan,
>>See this : "GPL-incompatible libraries with GPL
                    software"
>>http://www.gnu.org/licenses/gpl-faq.html#GPLIncompatibleLibs 
>>
>>
// Binan 
>>
>>
>>
>>________________________________
>> Från: Bogdan-Andrei Iancu <bogdan at opensips.org>
>>Till: "users at lists.opensips.org" <users at lists.opensips.org>; "devel at lists.opensips.org" <devel at lists.opensips.org> 
>>Skickat: fredag, 30 november 2012 14:39
>>Ämne: [OpenSIPS-Devel] [HELP] Advising on GPL license issue
>> 
>>Hi all,
>>
>>As I'm not an expert in this, I'm looking for
                        someone to advise on a more complex issue
                        regarding GPLv2 license.
>>
>>Shortly - developing an opensips module that
                        needs to link to a non-GPL (and not compatible)
                        library (available for public in binary format,
                        with proprietary license).
>>
>>For details or whatever feel free to contact me
                        offline, not a problem.
>>
>>Help will be highly appreciate not only be me,
                        but by the project and community (as a really
                        nice feature depends on finding a solution
                        here).
>>
>>Regards,
>>
>>-- Bogdan-Andrei Iancu
>>OpenSIPS Founder and Developer
>>http://www.opensips-solutions.com
>>
>>
>>_______________________________________________
>>Devel mailing list
>>Devel at lists.opensips.org
>>http://lists.opensips.org/cgi-bin/mailman/listinfo/devel
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20121203/a29b37b7/attachment-0001.htm>