Please join us tomorrow for our bi-weekly call. As usual, this meeting is
open to everybody and completely optional.
You might be interested to join if:
You want to know what is going on in BPF land
You are doing something interesting yourself with BPF and would like to share
You want to know what the heck BPF is

=== IO Visor Dev/TSC Meeting ===

Every 2 weeks on Wednesday, from Wednesday, January 25, 2017, to no end date
11:00 am | Pacific Daylight Time (San Francisco, GMT-07:00) | 30 min

https://bluejeans.com/568677804/

https://www.timeanddate.com/worldclock/meetingdetails.html?year=2018&month=9&day=5&hour=18&min=0&sec=0&p1=900

Hi,

Link regarding using LGPL with Apache licensed software, (from,
https://www.apache.org/legal/resolved.html#category-x)

`
WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?¶

GNU LGPL
The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion.
`

Because we have a specific warning on the apache license site
it seems best to get libbpf dual licensed. We would happily
start using it in cilium[1] for example after the dual license was
in place.

Thanks,
John

[1] https://cilium.io

On Wed, Sep 5, 2018 at 11:51 AM John Fastabend <john.fastabend@...> wrote:

Hi,

Link regarding using LGPL with Apache licensed software, (from,
https://www.apache.org/legal/resolved.html#category-x)

`
WHICH LICENSES MAY NOT BE INCLUDED WITHIN APACHE PRODUCTS?¶

GNU LGPL
The LGPL is ineligible primarily due to the restrictions it places on larger works, violating the third license criterion.
`

Because we have a specific warning on the apache license site
it seems best to get libbpf dual licensed. We would happily
start using it in cilium[1] for example after the dual license was
in place.

Here is good summary of why using lgpl in apache product is not a great option:
https://issues.apache.org/jira/browse/LEGAL-192?focusedCommentId=13907462&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-13907462
"These are not LEGAL restrictions. They are POLICY restrictions. They
impact the downstream, not the ASF."
My understanding that cilium and bcc legally can use existing libbpf,
but they would have
to provide non standard redistribution policy (apache2 plus lgpl 2.1
wording) which I suspect
is not something cilium or bcc projects would want to do.
So the best way forward is to dual license libbpf as lpgl 2.1 and apache2