DPDK community structure changes
 help / color / mirror / Atom feed
From: Francois Ozog <francois.ozog@linaro.org>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: Dave Neary <dneary@redhat.com>,
	Michael Dolan <mdolan@linuxfoundation.org>,
	"moving@dpdk.org" <moving@dpdk.org>
Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, November 29th
Date: Fri, 2 Dec 2016 10:00:43 +0100	[thread overview]
Message-ID: <CAHFG_=XiWKfMvP7t=Wizv1OUijnr-r1ZKohm4wqeowgDt_==ew@mail.gmail.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA6762794B@IRSMSX108.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 3760 bytes --]

Hi Tim,

First, thank you for being so patient. As per LNG members, you have silicon
vendors, distro vendors, NEPs. I am sure you saw that not all NEPs are
contributing. Some may, some are not contributing code at all even if they
active in the community.

More importantly, contributing does not mean building and selling products
that include DPDK. DPDK can be/become a playground to learn about userland
network IO while products are built on derived proprietary technology.

Let's rephrase: I am not mandating a CLA, I just stress that intellectual
property and licensing aspects are better off handled at the bengining. As
per Mike Dolan, Apache 2 is also a good approach. I hope every contributor
have gone (or are going to go) through due dilligence about selling
products based on DPDK with its counsel.

When you say "Depending on their company's legal policy, that may slow down
or block contributions.": hopefully you don't think there is a need for
legal intervention for each contribution. right? there is just one CLA to
be established at the first contribution.
And I hope you don't mean that people don't go to legal because they know
they will block contributions so they keep low profile and contribute: that
would be a very bad corporate responsability behavior!



On 1 December 2016 at 22:33, O'Driscoll, Tim <tim.odriscoll@intel.com>

> > From: Francois Ozog [mailto:francois.ozog@linaro.org]
> > Sent: Thursday, December 1, 2016 7:09 PM
> > To: Dave Neary <dneary@redhat.com>
> > Cc: O'Driscoll, Tim <tim.odriscoll@intel.com>; Michael Dolan <
> mdolan@linuxfoundation.org>; moving@dpdk.org
> > Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux
> Foundation" call, November 29th
> >
> > Hello,
> >
> > please find the Linaro CLA that passed many large companies lawyers for
> IP: http://opendataplane.org/contributor/individual/
> >
> > Compnies that already signed it (not all are listed): ARM, Broadcom,
> Canonical, Cavium, Cisco, Comcast, Ericsson, ENEA, Facebook, Hisilicon, HP
> Enterprise, Huawei, MontaVista, Nokia, NXP, Qualcomm, RedHat, Samsung,
> Socionext, Spreadtrum, ST microelectronics, Texas Instruments, Wind River,
> >
> > I wonder how to read "Need for a CLA is a problem for some contributors
> due to the need to get legal approval."
> >
> > Is it: "let's mask the problem to lawyers because they may NOT allow us
> to continue our technical fun?" or is it "this is just a burden that may
> take long and I don't want to lose time".
> >
> The concern that several people have expressed is that a CLA adds overhead
> for contributors to the project. If somebody wants to contribute, they
> would need to go through the extra step of getting the CLA reviewed and
> approved by their legal department. Depending on their company's legal
> policy, that may slow down or block contributions.
> Mike is correct that the legal details are better handled by lawyers, but
> before that it would be good to make sure we're clear on the problem you're
> trying to address. You said on Tuesday that some Linaro members would not
> be able to contribute to DPDK and/or use it in production without some form
> of patent protection. Looking at the list of LNG members, many of them are
> already significant contributors to DPDK, so that statement doesn't make
> sense to me. Can you perhaps clarify what exactly the problem you're trying
> to address is, just to make sure we all understand it properly?

[image: Linaro] <http://www.linaro.org/>
François-Frédéric Ozog | *Director Linaro Networking Group*
T: +33.67221.6485
francois.ozog@linaro.org | Skype: ffozog

[-- Attachment #2: Type: text/html, Size: 6257 bytes --]

  reply	other threads:[~2016-12-02  9:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 16:01 O'Driscoll, Tim
2016-11-30 17:10 ` Thomas Monjalon
2016-11-30 22:08   ` O'Driscoll, Tim
2016-12-01  9:20     ` Thomas Monjalon
2016-12-01  9:40       ` O'Driscoll, Tim
2016-11-30 17:39 ` Michael Dolan
2016-11-30 20:55   ` Dave Neary
2016-12-01 17:40   ` O'Driscoll, Tim
2016-12-01 17:46     ` Ed Warnicke
2016-12-01 18:01     ` Michael Dolan
2016-12-01 18:41     ` Dave Neary
2016-12-01 18:50       ` Dave Neary
2016-12-01 19:09         ` Francois Ozog
2016-12-01 19:44           ` Michael Dolan
2016-12-01 20:20             ` O'Driscoll, Tim
2016-12-01 20:47               ` Wiles, Keith
2016-12-01 21:33           ` O'Driscoll, Tim
2016-12-02  9:00             ` Francois Ozog [this message]
2016-12-01 20:33       ` O'Driscoll, Tim

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAHFG_=XiWKfMvP7t=Wizv1OUijnr-r1ZKohm4wqeowgDt_==ew@mail.gmail.com' \
    --to=francois.ozog@linaro.org \
    --cc=dneary@redhat.com \
    --cc=mdolan@linuxfoundation.org \
    --cc=moving@dpdk.org \
    --cc=tim.odriscoll@intel.com \


* 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).