From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f42.google.com (mail-vk0-f42.google.com [209.85.213.42]) by dpdk.org (Postfix) with ESMTP id EBA293989 for ; Wed, 30 Nov 2016 18:39:09 +0100 (CET) Received: by mail-vk0-f42.google.com with SMTP id 137so114332336vkl.0 for ; Wed, 30 Nov 2016 09:39:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=P9B+c3f834ARP0LYmiJi8LSyzOzlZgb1TT4t8eAx7MY=; b=CAlSzTgDQ7m2hJ8U9pI5ju6xxvTc7+6g72CAKvBAlPjweShc+dRvaqgX7kT5n8xzbC C9lovUzjIdAzqFMKGqwKNUHJlpiLTVlTlld0di3IndlWNNw6/pEMlP9zUJmqdkcUxLsG JYns+TkIXIf1cbiJ9NtjeSFkXnqVOAOpYcU60= 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=P9B+c3f834ARP0LYmiJi8LSyzOzlZgb1TT4t8eAx7MY=; b=J49mRl/R4qEBtf/AwTR9JXpTUsWdqKUYCqp32q5uSKwdSH+krh2RMZ5RF7byW/tFEO DEBO1yH47te/QCC0gK/zokn+JLvVg9bDrcN0yJhn07AqGy0O/Xf6XPd993/X6YWfvZuX oiViNZI7M9Lq4ha9iG+kopxrXAbmRuD4GTzSzrM8bWX2V4hyDtR2igKPALJemSLejxeO wIBXtHxpUwCo/1+4S1ihx5oLuZwsbelA8PVkDhXDvsebZGQ7OUGR6T3rTEArXJz5Uvo7 bHDnzJytnnFnSLlCu8HaP8ACt6VCXHK82BVpQYCiOz1vmO8l/9mfRbd6iua9baLK4m6G O/+g== X-Gm-Message-State: AKaTC00yiB8fezMWvaZ8V57BPsUR58pOfprBIoXdpKj7rgsW/bs/QTJrVW5usqVp3SJRsHv+I1y2KFOSIpdd7CGR X-Received: by 10.31.149.138 with SMTP id x132mr12218962vkd.86.1480527549223; Wed, 30 Nov 2016 09:39:09 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.3.79 with HTTP; Wed, 30 Nov 2016 09:39:08 -0800 (PST) In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA67626AEE@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA67626AEE@IRSMSX108.ger.corp.intel.com> From: Michael Dolan Date: Wed, 30 Nov 2016 10:39:08 -0700 Message-ID: To: "O'Driscoll, Tim" Cc: "moving@dpdk.org" Content-Type: multipart/alternative; boundary=001a1141003aa705da0542882e78 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: Wed, 30 Nov 2016 17:39:10 -0000 --001a1141003aa705da0542882e78 Content-Type: text/plain; charset=UTF-8 Hi Tim, sorry I couldn't make it with a LF Board meeting conflict yesterday. As for 1), most/all of our projects facing this issue decide to go Apache 2. A CLA is less preferably particularly with the BSD license. Where we do use a CLA on a project it's usually the same as the Apache CCLA/ICLA and that combined with the BSD license will I'm fairly certain not achieve what Linaro legal is probably concerned about. My guess is the members here are 90% or more of the contributors and a relicensing effort could be done within a reasonable timeframe. The project could also start under the LF with all new contributions under the Apache 2 license which is compatible with all prior BSD contributions. Or you could just required Apache 2 on any future contributions and keep the prior BSD if the relicensing is not agreeable to others. Just some thoughts on how other projects tackled this question. It would probably be best if we push any further discussion on this to a small group of your legal counsel as the various levers have different implications and I'm uncomfortable continuing this discussion without your counsel being involved. Thanks, Mike On Wed, Nov 30, 2016 at 9:01 AM, O'Driscoll, Tim wrote: > Here are my notes from Tuesday's call. Please feel free to correct any > errors or to add additional details. > > Attendees: Dave Neary (Red Hat), Ed Warnicke (Cisco), Francois-Frederic > Ozog (Linaro), Hemant Agrawal (NXP), Jan Blunck (Brocade), Jaswinder Singh > (NXP), Jerin Jacob (Cavium), Jim St. Leger (Intel), John McNamara (Intel), > Keith Wiles (Intel), Olga Shern (Mellanox), Thomas Monjalon (6WIND), Tim > O'Driscoll (Intel), Vincent Jardin (6WIND). Note that there may have been > others, but as people joined at different times it was difficult to keep > track. > > Firstly, here are some links to help keep track of things: > Project Charter: https://docs.google.com/document/d/1x43ycfW3arJNX- > e6NQt3OVzAuNXtD7dppIhrY48FoGs > Summary of discussion at Userspace event in Dublin: > http://dpdk.org/ml/archives/dev/2016-October/049259.html > Minutes of October 31st call: http://dpdk.org/ml/archives/ > moving/2016-November/000031.html > Minutes of November 8th call: http://dpdk.org/ml/archives/ > moving/2016-November/000058.html > Minutes of November 15th call: http://dpdk.org/ml/archives/ > moving/2016-November/000061.html > Minutes of November 22nd call: http://dpdk.org/ml/archives/ > moving/2016-November/000085.html > Current technical governance, including composition of the Tech Board: > http://dpdk.org/doc/guides/contributing/index.html & http://dpdk.org/dev. > > > 1. Discussed Contributor License Agreement (CLA) vs Developer Certificate > of Origin (DCO) > - Current process is to use a DCO. > - Francois-Frederic proposed using a CLA. This is based on input from the > Linaro legal team and some Linaro members who have indicated that not > having a CLA prevents them contributing to or using DPDK. > - Discussed what benefit they think they'll get from CLA. The main thing > it adds is patent protection. This could be achieved in other ways, for > example using the Apache 2.0 license. Neither solution would apply to > existing DPDK code though so any benefit would only apply to new code. > - Vincent asked if there are problems with other BSD licensed projects. We > agreed to check with the Linux Foundation (Mike Dolan) to see if they have > any guidance based on other BSD licensed projects. I'll ask Mike. > > 2. Discussed comments on project charter > - Agreed that the Governing Board does not specify requirements for the > Technical Board to implement. The two boards are peers. One can make > suggestions to the other at any time, but these aren't requirements and > don't have to be accepted. > - Discussed how members are added to/removed from the Technical Board. > Agreed that the TB approves adding/removing members. Agreed that the TB > needs to consider technical contributions from the individuals and support > for all architectures when making these decisions. > - Discussed Dave's proposal for a representative of the technical > community on the GB (in addition to the rep from the TB). Agreed not to do > this and just to keep the single rep from the TB on the GB. Also discussed > whether there should be a GB rep on the TB and agreed that this did not > make sense. > - For voting, agreed that the quorum for a meeting for either board is 50% > of the members. Majority required to pass a vote is 50% of the total board > except for: a) changes to the charter require 2/3 of the GB; b) licensing > exceptions require 2/3 of the GB. > - I've updated the charter (section 3 - Project Governance) to reflect > these changes. > > > Next Meeting: > Tuesday December 6th at 3pm GMT, 4pm CET, 10am EST, 7am PST. We'll focus > on the comments on the Membership and Technical Governance sections of the > charter, and also discuss CLA/DCO if we have more input/guidance on this > from the LF. > > > > --001a1141003aa705da0542882e78 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Tim, sorry I couldn't make it with a LF Board meeti= ng conflict yesterday. As for 1), most/all of our projects facing this issu= e decide to go Apache 2. A CLA is less preferably particularly with the BSD= license. Where we do use a CLA on a project it's usually the same as t= he Apache CCLA/ICLA and that combined with the BSD license will I'm fai= rly certain not achieve what Linaro legal is probably concerned about.
=
My guess is the members here are 90% or more of the contribu= tors and a relicensing effort could be done within a reasonable timeframe. = The project could also start under the LF with all new contributions under = the Apache 2 license which is compatible with all prior BSD contributions. = Or you could just required Apache 2 on any future contributions and keep th= e prior BSD if the relicensing is not agreeable to others.

Just some thoughts on how other projects tackled this question. It= would probably be best if we push any further discussion on this to a smal= l group of your legal counsel as the various levers have different implicat= ions and I'm uncomfortable continuing this discussion without your coun= sel being involved.

Thanks,

Mike



On Wed, Nov 30, 2016 at 9:01 AM, O'Drisc= oll, Tim <tim.odriscoll@intel.com> wrote:
Here are my notes from Tuesday's call. Please fee= l free to correct any errors or to add additional details.

Attendees: Dave Neary (Red Hat), Ed Warnicke (Cisco), Francois-Frederic Ozo= g (Linaro), Hemant Agrawal (NXP), Jan Blunck (Brocade), Jaswinder Singh (NX= P), Jerin Jacob (Cavium), Jim St. Leger (Intel), John McNamara (Intel), Kei= th Wiles (Intel), Olga Shern (Mellanox), Thomas Monjalon (6WIND), Tim O'= ;Driscoll (Intel), Vincent Jardin (6WIND). Note that there may have been ot= hers, but as people joined at different times it was difficult to keep trac= k.

Firstly, here are some links to help keep track of things:
Project Charter: http= s://docs.google.com/document/d/1x43ycfW3arJNX-e6NQt3OVzAuNXtD7dpp= IhrY48FoGs
Summary of discussion at Userspace event in Dublin: http://dpdk.org/ml/archives/dev/2016-October/049259.html Minutes of October 31st call: http://dpd= k.org/ml/archives/moving/2016-November/000031.html
Minutes of November 8th call: http://dpd= k.org/ml/archives/moving/2016-November/000058.html
Minutes of November 15th call: http://dp= dk.org/ml/archives/moving/2016-November/000061.html
Minutes of November 22nd call: http://dp= dk.org/ml/archives/moving/2016-November/000085.html
Current technical governance, including composition of the Tech Board: http://dpdk.org/doc/guides/contributing/index.htm= l & http://dpdk.org/dev.


1. Discussed Contributor License Agreement (CLA) vs Developer Certificate o= f Origin (DCO)
- Current process is to use a DCO.
- Francois-Frederic proposed using a CLA. This is based on input from the L= inaro legal team and some Linaro members who have indicated that not having= a CLA prevents them contributing to or using DPDK.
- Discussed what benefit they think they'll get from CLA. The main thin= g it adds is patent protection. This could be achieved in other ways, for e= xample using the Apache 2.0 license. Neither solution would apply to existi= ng DPDK code though so any benefit would only apply to new code.
- Vincent asked if there are problems with other BSD licensed projects. We = agreed to check with the Linux Foundation (Mike Dolan) to see if they have = any guidance based on other BSD licensed projects. I'll ask Mike.

2. Discussed comments on project charter
- Agreed that the Governing Board does not specify requirements for the Tec= hnical Board to implement. The two boards are peers. One can make suggestio= ns to the other at any time, but these aren't requirements and don'= t have to be accepted.
- Discussed how members are added to/removed from the Technical Board. Agre= ed that the TB approves adding/removing members. Agreed that the TB needs t= o consider technical contributions from the individuals and support for all= architectures when making these decisions.
- Discussed Dave's proposal for a representative of the technical commu= nity on the GB (in addition to the rep from the TB). Agreed not to do this = and just to keep the single rep from the TB on the GB. Also discussed wheth= er there should be a GB rep on the TB and agreed that this did not make sen= se.
- For voting, agreed that the quorum for a meeting for either board is 50% = of the members. Majority required to pass a vote is 50% of the total board = except for: a) changes to the charter require 2/3 of the GB; b) licensing e= xceptions require 2/3 of the GB.
- I've updated the charter (section 3 - Project Governance) to reflect = these changes.


Next Meeting:
Tuesday December 6th at 3pm GMT, 4pm CET, 10am EST, 7am PST. We'll focu= s on the comments on the Membership and Technical Governance sections of th= e charter, and also discuss CLA/DCO if we have more input/guidance on this = from the LF.




--001a1141003aa705da0542882e78--