< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate-users] Recon and LGPL sipXtapi license


License issues aside, we created a branch some time ago that decoupled recon 
from all of the sipX dependencies -- meaning that you would need to implement 
your own media library to the (newly defined) media interfaces we contributed 
on the branch.

The branch is at 
https://svn.resiprocate.org/rep/resiprocate/branches/cp-recon-contrib-20100125

If anyone else is interested in investing the time, it would be nice to see 
this branch collapsed back to trunk, but with a default sipX media 
implementation of the interfaces.  This has been on my list of things to do for 
quite some time, but there is currently no timeline.

Jeremy

-----Original Message-----
From: resiprocate-users-bounces@xxxxxxxxxxxxxxx 
[mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Adam Roach
Sent: September-02-10 6:25 PM
To: Eric Cozzi
Cc: resiprocate-users
Subject: Re: [reSIProcate-users] Recon and LGPL sipXtapi license

  This email is not legal advice and I am not a lawyer.

The LGPL isn't incompatible with use in a closed source system. All it 
does is place restrictions on how you use the code covered by the LGPL. 
In a nutshell: you have to make the source code to the LGPL library 
available. This is true regardless of whether you have made changes to 
the library. The LGPL does not obligate you to make other parts of your 
application source available.

http://www.gnu.org/licenses/gpl-faq.html#LGPLv3ContributorVersion

I encourage you to consult with a lawyer if anything is unclear.

/a


On 9/2/10 19:19, Sep 2, Eric Cozzi wrote:
> Has there been any discussion on this list of the ability to use Recon in a 
> closed source commercial product? I am not a lawyer, but from my review of 
> the code and the various project licenses that make up Recon, it appears that 
> since (if I'm not mistaken) Recon statically links to sipXtapi, the sipXtapi 
> LGPL license prevents Recon's use in a closed source commercial product. Is 
> my read of this true? Or, am I missing something (completely likely!).
>
> Thanks,
> Eric
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/

_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/