From: Vincent Jardin <vincent.jardin@6wind.com>
To: Ed Warnicke <hagbard@gmail.com>
Cc: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
Matt Spencer <Matt.Spencer@arm.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
Dave Neary <dneary@redhat.com>, <moving@dpdk.org>
Subject: Re: [dpdk-moving] Reminder on Today's Meeting and Updated Charter
Date: Thu, 24 Nov 2016 20:05:32 +0100 [thread overview]
Message-ID: <15897ba8060.27fc.bb328046f2889bc8f44aafa891a44dd2@6wind.com> (raw)
In-Reply-To: <CAFVSqg25W_fjrCJFykt1LXFhyoy5jLgWh8hM-7WTfJjDzbPBhA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1198 bytes --]
Again: please explain in case of *BSD OSes ?
Le 24 novembre 2016 19:20:03 Ed Warnicke <hagbard@gmail.com> a écrit :
> Speaking as someone who's been involved in thousands of discussions over
> more than a decade evaluating issues like patent risk in consuming open
> source software, I don't see a patent clause in a CLA offering any
> realistic assurance to a downstream consumer.
>
> Were I involved in a discussion around patent risk in DPDK, I would point
> to its license.
>
> That said (and keeping in mind that IANAL), I do *not* see any patent
> protection in the BSD license similar to what one sees in the Apache 2
> license, or the Eclipse Public License. Please note: I am not advocating
> here for a license change, just drawing attention to my perspective as
> someone who's been deeply involved in such things for a long time.
>
> Ed
>
> On Thu, Nov 24, 2016 at 12:07 PM, Vincent Jardin <vincent.jardin@6wind.com>
> wrote:
>
>> Matt,
>>
>> Please explain why you think that contributions under BSD licenses are not
>> proper contributions for patents. For instance, Free/Net/OpenBSD do not
>> require any CLA so contribution process remains smooth.
>>
>> Thank you,
>>
>>
>>
>>
[-- Attachment #2: Type: text/html, Size: 1991 bytes --]
next prev parent reply other threads:[~2016-11-24 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 11:08 O'Driscoll, Tim
2016-11-22 14:47 ` Vincent JARDIN
2016-11-23 22:26 ` Dave Neary
2016-11-24 12:46 ` O'Driscoll, Tim
2016-11-24 13:26 ` Thomas Monjalon
2016-11-24 14:16 ` Matt Spencer
2016-11-24 17:27 ` O'Driscoll, Tim
2016-11-24 18:07 ` Vincent Jardin
2016-11-24 18:20 ` Ed Warnicke
2016-11-24 19:05 ` Vincent Jardin [this message]
2016-11-24 18:13 ` Ed Warnicke
2016-11-29 13:20 ` Francois Ozog
2016-11-29 13:50 ` Thomas Monjalon
2016-11-29 14:25 ` Francois Ozog
2016-11-29 14:50 ` Vincent JARDIN
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15897ba8060.27fc.bb328046f2889bc8f44aafa891a44dd2@6wind.com \
--to=vincent.jardin@6wind.com \
--cc=Matt.Spencer@arm.com \
--cc=dneary@redhat.com \
--cc=hagbard@gmail.com \
--cc=moving@dpdk.org \
--cc=thomas.monjalon@6wind.com \
--cc=tim.odriscoll@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).