DPDK community structure changes
 help / color / mirror / Atom feed
From: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
To: Francois Ozog <francois.ozog@linaro.org>, Dave Neary <dneary@redhat.com>
Cc: 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: Thu, 1 Dec 2016 21:33:32 +0000	[thread overview]
Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA6762794B@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAHFG_=UzcianJfFp-221m5kXtTfZY1SSzu8HwYde25whFmAeiw@mail.gmail.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, ZTE
> 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?

  parent reply	other threads:[~2016-12-01 21:33 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 [this message]
2016-12-02  9:00             ` Francois Ozog
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=26FA93C7ED1EAA44AB77D62FBE1D27BA6762794B@IRSMSX108.ger.corp.intel.com \
    --to=tim.odriscoll@intel.com \
    --cc=dneary@redhat.com \
    --cc=francois.ozog@linaro.org \
    --cc=mdolan@linuxfoundation.org \
    --cc=moving@dpdk.org \


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