From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f177.google.com (mail-yw0-f177.google.com [209.85.161.177]) by dpdk.org (Postfix) with ESMTP id AFCC1106A for ; Tue, 29 Nov 2016 14:20:12 +0100 (CET) Received: by mail-yw0-f177.google.com with SMTP id i145so137600790ywg.2 for ; Tue, 29 Nov 2016 05:20:12 -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=wdwhVaSX3O4Aeiv+t9GM/auCZ4cdfGYlKtYNgiKEXks=; b=eyHpxOBBtHlRfLSoQexHQjg8+yKMCwpdxDbo0so/V34rPGCgIHTX0jYcDxTDUWiL9N JjhUIQGBpM7lZgvoW55rA8kG17DBcBvBYubvOcwIj2YhhpT1GB1r9j18/BRWazMIaR66 by/H9nn8hMSOpvyAR39lGehPyIJhUA+1X7rDg= 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=wdwhVaSX3O4Aeiv+t9GM/auCZ4cdfGYlKtYNgiKEXks=; b=YgfMyOaKdv7nZTMqOSkHDDjNA7ZS7DXXw8krdb4VBM4Dz3Zr7/FnQHb49JRjEIemr/ yXtKXJMd/9Qao2YHUoymC0YHAEWRR4eHrlFT7Zgytuc9P0tYNtN8WhfE2a/wQO3PwAFz kD01fyHWtnr5m/qINeetBgrBgRtobzOqZCSRk3bK/Vz5VdkdurjbcfrcAZo3i2IOHtAA gA7jCQpP2+Dh9FDzg/BwciU8GxJK0Phvf1CDo3Euub6k6Iflov8t2BfxHyL4Fefj+JgM gphj1rNSUD9yyMwqUPjQpSIoqJwysy8WidCq7Mw5k8STslgGIloj5lbzKSvmSuhDpvn8 xFmA== X-Gm-Message-State: AKaTC02MsZKNFwvxeEeOj4oiDbHpVz4AKmaPMpdX82/zQltEtvYXXiHLrn3sW5kPpSgpZl4i9JmsB3P+eXIg2RwW X-Received: by 10.129.111.2 with SMTP id k2mr30891248ywc.335.1480425612082; Tue, 29 Nov 2016 05:20:12 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.164.99 with HTTP; Tue, 29 Nov 2016 05:20:08 -0800 (PST) In-Reply-To: References: <26FA93C7ED1EAA44AB77D62FBE1D27BA67622717@IRSMSX108.ger.corp.intel.com> <583617A4.4000400@redhat.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA67623D9E@IRSMSX108.ger.corp.intel.com> <1540534.G53vByIeVs@xps13> From: Francois Ozog Date: Tue, 29 Nov 2016 14:20:08 +0100 Message-ID: To: Matt Spencer Cc: Thomas Monjalon , "O'Driscoll, Tim" , Dave Neary , "moving@dpdk.org" Content-Type: multipart/alternative; boundary=001a1149001ab9c01305427072c0 Subject: Re: [dpdk-moving] Reminder on Today's Meeting and Updated Charter 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: Tue, 29 Nov 2016 13:20:12 -0000 --001a1149001ab9c01305427072c0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Matt, I coy/paste Mike Dolan's comment on CLA: "Most of our projects use the Apache CCLA if a CLA is required. We have a fully automated e-signature management system for CLA signings. You can see the CCLA for Kubernetes for example here: https://identity.linuxfoundation.org/content/cncf-corporate-contributor-lic= ense-agreement " I had Linaro member companie lawyers have a look at it and they said it is fine. So it should be nice to have such CCLA in place in DPDK. FF On 24 November 2016 at 15:16, Matt Spencer wrote: > I think I suggested a Contributor level member so that they could be > allocated official positions in the charter. > > > It was also to track who had signed up to the CLA (or similar). > > At the time we were discussing Silver member access to the Governing Boar= d > (in a 5-1 ratio, maximum 2 if I remember). The Contributor level member > was there to allow Contributor access to the board at a suggested 20-1 > ratio with some maximum, voted for by their peers. > > > I think this level of membership is needed to track CLA? > > > /Matt > > ------------------------------ > *From:* moving on behalf of Thomas Monjalon < > thomas.monjalon@6wind.com> > *Sent:* 24 November 2016 13:26 > *To:* O'Driscoll, Tim; Dave Neary > *Cc:* moving@dpdk.org > *Subject:* Re: [dpdk-moving] Reminder on Today's Meeting and Updated > Charter > > 2016-11-24 12:46, O'Driscoll, Tim: > > From: Dave Neary [mailto:dneary@redhat.com ] > > > Fourthly, do we need to make a distinction between DPDK the software > > > project and the DPDK Project, the entity which will come into being > > > under the LF? I ask, because participation in the DPDK software proje= ct > > > is clearly not to be limited to paying members, while participation i= n > > > the DPDK Project under the LF is limited to paying companies, for the > > > most part. > > > > The aim was that this was clear from point 4.a in the Membership > section. At last week's meeting somebody (Matt I think) suggested adding = a > membership category of Contributor to make this clearer, but most people > felt this was over-kill. > > > > Do you think this is clear from point 4.a, or do you still think > something further is required? > > I think the membership section must be part of the governing board sectio= n. > So it makes clear that we are talking about members of the governing boar= d. > IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy th= e > information in any medium. Thank you. > --=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 --001a1149001ab9c01305427072c0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Matt,

I coy/paste Mike Dolan's c= omment on CLA:

"Most of our projects use the Apache CCLA if a CLA is required. We= have a fully automated e-signature management system for CLA signings. You= can see the CCLA for Kubernetes for example here:=C2=A0https://identity.linux= foundation.org/content/cncf-corporate-contributor-license-agreement&quo= t;

I had Linaro member companie lawyers have a loo= k at it and they said it is fine.

So it should be = nice to have such CCLA in place in DPDK.

FF
<= /div>

On 24 Novemb= er 2016 at 15:16, Matt Spencer <Matt.Spencer@arm.com> wro= te:

I think I suggested a Contributor level member so that they could be all= ocated official positions in the charter.


= It was also to track who had signed up to the CLA (or similar).


At the time we were discussing Silver member access to the Governing Boa= rd (in a 5-1 ratio, maximum 2 if I remember).=C2=A0 The Contributor level m= ember was there to allow Contributor access to the board at a suggested 20-= 1 ratio with some maximum, voted for by their peers.


I think this level of membership is needed to track CLA?


/Matt


From: moving <m= oving-bounces@dpdk.org> on behalf of Thomas Monjalon <thomas.monjalon@6wind.c= om>
Sent: 24 November 2016 13:26
To: O'Driscoll, Tim; Dave Neary
Cc: moving@dpdk= .org
Subject: Re: [dpdk-moving] Reminder on Today's Meeting and Updat= ed Charter
=C2=A0
2016-11-24 12:46, O'Drisc= oll, Tim:
> From: Dave Neary [mailto:dneary@redhat.com]
> > Fourthly, do we need to make a distinction between DPDK the softw= are
> > project and the DPDK Project, the entity which will come into bei= ng
> > under the LF? I ask, because participation in the DPDK software p= roject
> > is clearly not to be limited to paying members, while participati= on in
> > the DPDK Project under the LF is limited to paying companies, for= the
> > most part.
>
> The aim was that this was clear from point 4.a in the Membership secti= on. At last week's meeting somebody (Matt I think) suggested adding a m= embership category of Contributor to make this clearer, but most people fel= t this was over-kill.
>
> Do you think this is clear from point 4.a, or do you still think somet= hing further is required?

I think the membership section must be part of the governing board section.=
So it makes clear that we are talking about members of the governing board.=
IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease notify the sender immediately and do not disclose the contents to any= other person, use it for any purpose, or store or copy the information in any medium. Thank you.



--
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

--001a1149001ab9c01305427072c0--