From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 2C5A33DC for ; Wed, 8 Mar 2017 17:37:50 +0100 (CET) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Mar 2017 08:37:50 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,264,1486454400"; d="scan'208";a="74300538" Received: from irsmsx105.ger.corp.intel.com ([163.33.3.28]) by fmsmga006.fm.intel.com with ESMTP; 08 Mar 2017 08:37:49 -0800 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.173]) by irsmsx105.ger.corp.intel.com ([169.254.7.38]) with mapi id 14.03.0248.002; Wed, 8 Mar 2017 16:37:48 +0000 From: "O'Driscoll, Tim" To: Thomas Monjalon , "moving@dpdk.org" Thread-Topic: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, March 7th Thread-Index: AQHSmBqcl1JsvLiZMEmI1Yuo12IBhKGLIcVw Date: Wed, 8 Mar 2017 16:37:47 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA72319C86@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA72319828@IRSMSX108.ger.corp.intel.com> <2433082.cJ3p5dltz2@xps13> In-Reply-To: <2433082.cJ3p5dltz2@xps13> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMWVhM2FlMGQtZWJiYi00NjhjLTgyYTUtNzQ4OGIyYmY4NTdkIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjIuMTEuMCIsIlRydXN0ZWRMYWJlbEhhc2giOiJ3UHp1ckRiWnl4QUh2bldWOVJEc0s4Z3hSd2pHUWZhMWdhdmwrclhHVUpJPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-moving] Minutes from "Moving DPDK to Linux Foundation" call, March 7th 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, 08 Mar 2017 16:37:51 -0000 > From: moving [mailto:moving-bounces@dpdk.org] On Behalf Of Thomas Monjalo= n >=20 > 2017-03-08 13:44, O'Driscoll, Tim: > > Adding the charter to the website: > > - Thomas proposed on the mailing list that we post the charter on the > website and manage changes in git > (http://dpdk.org/ml/archives/moving/2017-March/000191.html). Agreed that > this is a good idea. > > - We need to agree which mailing list should be used for future > discussion on the charter once it's baselined. Agreed that the best > approach is to rename moving@dpdk.org to charter@dpdk.org when the > project is launched, and use it for any future discussion. The archives > will still contain the history of discussions on moving to LF. >=20 > I think any changes in the charter or in the structure could be > discussed on moving@dpdk.org. > Why renaming? We could do either. The only reason to change is that the moving@dpdk.org l= ist was for discussions on moving to LF. That name won't be meaningful any = more after the move is completed. Changing the name to charter@dpdk.org wou= ld make the future purpose clearer. It's a minor point though, and I don't = really think the name matters too much. > > - After it's baselined, proposed changes to the charter should be made > on the charter@dpdk.org list. They can then be discussed in public on > the list, and will also be discussed and voted on at a governing board > meeting. A member of the board will indicate on the list if the board > approves the proposed change. >=20 > The changes must also be posted to web@dpdk.org. Yes, that can be done too. I think the key point is that people interested = in the charter have subscribed to the moving list but not to the web list. = So, I think we should use moving (or charter if we rename it) as the list f= or discussion on future charter changes. Requested changes can be sent to t= he web list as well. > > - We can also set up a private mailing list for the governing board > once its members are known, similar to techboard@dpdk.org. > > > > Membership: > > - Mike is working on the membership agreement and expects to have a > draft in the next day or two. He'll distribute this as soon as it's > available. >=20 > Is this agreement going to change anything in the charter? > If not, I'm going to send a patch for charter integration in the web > site. I think we should wait until we have the membership agreement from Mike, an= d people have had a chance to review this internally to get the required ap= proval. That might throw up some proposed changes to the charter, and I thi= nk we should handle those via the current process and then baseline the cha= rter when the project is launched at ONS.