Re: [tools-pmc] PMC Approval for libwebsockets usage in TCF agent

["Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>]

Hi Tools PMC,

 

To be clear, as the TCF project we’ll only request a WORKWITH for libwebsockets-2.0,

just like the iot pmc approved workswith for libwebsockets-1.3 before:

https://dev.eclipse.org/mhonarc/lists/iot-pmc/msg00170.html

 

That said, can you approve and pmc+1 the CQ?

http://dev.eclipse.org/ipzilla/show_bug.cgi?id=11843

 

Once we are clear on the workswith, we can work with the IP team on

whether our build can also link it statically (thanks to the LGPL exceptions)

or only dynamically.

 

Thanks,

Martin

--

Martin Oberhuber, SMTS / Product Owner – Development Tools, Wind River

direct +43.662.457915.85  fax +43.662.457915.6

 

 

From: <tools-pmc-bounces@xxxxxxxxxxx> on behalf of "mike.milinkovich@xxxxxxxxxxx" <mike.milinkovich@xxxxxxxxxxx>
Organization: Eclipse Foundation
Reply-To: "mike.milinkovich@xxxxxxxxxxx" <mike.milinkovich@xxxxxxxxxxx>, "tools-pmc@xxxxxxxxxxx" <tools-pmc@xxxxxxxxxxx>
Date: Friday 19 August 2016 at 04:21
To: "tools-pmc@xxxxxxxxxxx" <tools-pmc@xxxxxxxxxxx>
Subject: Re: [tools-pmc] PMC Approval for libwebsockets usage in TCF agent

 

On 2016-08-17 11:17 AM, Brachet, Didier wrote:

1 - The license of the library is not LGPL, it is "LGPL with exceptions" (exceptions are listed at https://github.com/warmcat/libwebsockets/blob/v1.7-stable/LICENSE). Does this impact: "The APIs cannot be obtained under a more permissive open source license (e.g., the BSD)."?

 

Those permissions are quite significant and alter  a number of the terms of the LGPL which have been problematic for us in the past. At this point I would ask that we follow David's advice: open a CQ making it clear the license is LGPL *with additional permissions* and see what the IP team has to say. Please cc me on the CQ, and provide a pointer to this thread on the PMC list.

Thanks.

--
Mike Milinkovich
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223