From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f171.google.com (mail-yw0-f171.google.com [209.85.161.171]) by dpdk.org (Postfix) with ESMTP id 37BDAFA37 for ; Fri, 2 Dec 2016 10:00:45 +0100 (CET) Received: by mail-yw0-f171.google.com with SMTP id i145so215221876ywg.2 for ; Fri, 02 Dec 2016 01:00:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=rFy+D/icCJ9ws3ybzXRc/yul1tce/bwoswXiNPBbTeM=; b=g5ONiEg+NV18r/GDILJ6+dFI7d3y9YXA0DfDpqxIN5XKXGdU6lPPDiPw+tF5H3aDkl QpGBuuxNeN1VpqQMj+W9uuDC97UFQw3my0XKUPYZTr1hzkHWqy4zKuA+CiG+bU4sclUg s1Vd1IO5d1/LDjK9ZYT/nI/GM+pLtEKqrI9nM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=rFy+D/icCJ9ws3ybzXRc/yul1tce/bwoswXiNPBbTeM=; b=Cf5MVoOPQnAOXC/jj6zk8jME9AOAoRtnSvHz2PyK49QrYv45t3gp090H8whogq0eoC vPgUa4AnB1aCPJTyyugOTpxcyJqH5vtYFSlup3z17CRfwYGcoyLOih5Gpp/qb7p8k/uO /YayBPr1vihmFLYksCULBkY5Sw9lcWcxT4E5a8Q2euO3m/EtRkFd6lFOmjqy5UvdV6gG 3drCfFGEL7bEGYTFQbXkrmp2vTF7D3uL0ffjDEkGurfaZBqpDSNiFesFf6SrMRshsKHR qrxHaYkizWuDeci7dyT3cRM00XWr7PxXYIxfLfABatJmINvxe/NopRnSBohTJY4j+vIT eYkA== X-Gm-Message-State: AKaTC036r9dnOTApACO+6Jd6RgAn+RwO9NqGl/LA7Psot4FWJzRhVpVH5aP2XA0vw4Jc84zB9kK4BWyDV5bko8ut X-Received: by 10.129.168.131 with SMTP id f125mr51379516ywh.215.1480669244608; Fri, 02 Dec 2016 01:00:44 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.164.99 with HTTP; Fri, 2 Dec 2016 01:00:43 -0800 (PST) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA6762794B@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA67626AEE@IRSMSX108.ger.corp.intel.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA676277F4@IRSMSX108.ger.corp.intel.com> <58406EC0.7000904@redhat.com> <584070FA.30606@redhat.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA6762794B@IRSMSX108.ger.corp.intel.com> From: Francois Ozog Date: Fri, 2 Dec 2016 10:00:43 +0100 Message-ID: To: "O'Driscoll, Tim" Cc: Dave Neary , Michael Dolan , "moving@dpdk.org" Content-Type: multipart/alternative; boundary=94eb2c13cbe25afdbf0542a92c26 Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, November 29th X-BeenThere: moving@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK community structure changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 09:00:45 -0000 --94eb2c13cbe25afdbf0542a92c26 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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! Cordially, Fran=C3=A7ois-Fr=C3=A9d=C3=A9ric On 1 December 2016 at 22:33, O'Driscoll, Tim wrote: > > > From: Francois Ozog [mailto:francois.ozog@linaro.org] > > Sent: Thursday, December 1, 2016 7:09 PM > > To: Dave Neary > > Cc: O'Driscoll, Tim ; 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, H= P > 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 overhea= d > 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 fo= rm > of patent protection. Looking at the list of LNG members, many of them ar= e > already significant contributors to DPDK, so that statement doesn't make > sense to me. Can you perhaps clarify what exactly the problem you're tryi= ng > to address is, just to make sure we all understand it properly? > --=20 [image: Linaro] Fran=C3=A7ois-Fr=C3=A9d=C3=A9ric Ozog | *Director Linaro Networking Group* T: +33.67221.6485 francois.ozog@linaro.org | Skype: ffozog --94eb2c13cbe25afdbf0542a92c26 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Tim,

First, thank you for bein= g 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 s= elling products that include DPDK. DPDK can be/become a playground to learn= about userland network IO while products are built on derived proprietary = technology.=C2=A0


Let's rephras= e: I am not mandating a CLA, I just stress that intellectual property and l= icensing 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 DPD= K with its counsel.

When you say "Depending on their company's legal policy, that m= ay slow down or block contributions.": hopefully you don't think t= here is a need for legal intervention for each contribution. right? there i= s just one CLA to be established at the first contribution.
And I hope you don't mean that peopl= e 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 re= sponsability behavior!

Cordially,

Fran= =C3=A7ois-Fr=C3=A9d=C3=A9ric


<= div class=3D"gmail_extra">
On 1 December 2016= at 22:33, O'Driscoll, Tim <tim.odriscoll@intel.com> wrote:

> 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 fo= r IP:=C2=A0http://opendataplane.org/contributor= /individual/
>
> Compnies that already signed it (not all are listed): ARM, Broadcom, C= anonical, Cavium, Cisco, Comcast, Ericsson, ENEA, Facebook, Hisilicon, HP E= nterprise, Huawei, MontaVista, Nokia, NXP, Qualcomm, RedHat, Samsung, Socio= next, Spreadtrum, ST microelectronics, Texas Instruments, Wind River, ZTE >
> I wonder how to read "Need for a CLA is a problem for some contri= butors due to the need to get legal approval."
>
> Is it: "let's mask the problem to lawyers because they may NO= T 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 ov= erhead for contributors to the project. If somebody wants to contribute, th= ey 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 b= efore 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 wou= ld not be able to contribute to DPDK and/or use it in production without so= me form of patent protection. Looking at the list of LNG members, many of t= hem are already significant contributors to DPDK, so that statement doesn&#= 39;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 proper= ly?



--
3D"Linaro"<= td style=3D"font-family:Arial,Helvetica,'Sans Serif';white-space:no= wrap;font-size:9pt;padding-top:2px;color:rgb(87,87,87)" valign=3D"top">T:= =C2=A0+33.67221.6485
francois.ozog@linaro.org=C2=A0|=C2=A0Skype:=C2=A0ffozog
Fran=C3= =A7ois-Fr=C3=A9d=C3=A9ric Ozog=C2=A0|=C2=A0Director Linaro Networking Group

--94eb2c13cbe25afdbf0542a92c26--