From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 7C5028E84 for ; Thu, 29 Oct 2015 17:23:12 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP; 29 Oct 2015 09:23:11 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,215,1444719600"; d="scan'208";a="590429532" Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25]) by FMSMGA003.fm.intel.com with ESMTP; 29 Oct 2015 09:23:10 -0700 Received: from irsmsx156.ger.corp.intel.com (10.108.20.68) by irsmsx110.ger.corp.intel.com (163.33.3.25) with Microsoft SMTP Server (TLS) id 14.3.248.2; Thu, 29 Oct 2015 16:23:08 +0000 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.138]) by IRSMSX156.ger.corp.intel.com ([169.254.3.245]) with mapi id 14.03.0248.002; Thu, 29 Oct 2015 16:23:09 +0000 From: "O'Driscoll, Tim" To: Thomas Monjalon Thread-Topic: [dpdk-dev] Architecture Board Proposal Thread-Index: AdESXXFZp4hchkInQi2ciOcDI//rHAAAw+YAAAFRSgA= Date: Thu, 29 Oct 2015 16:23:08 +0000 Message-ID: <26FA93C7ED1EAA44AB77D62FBE1D27BA67448AEF@IRSMSX108.ger.corp.intel.com> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674488A2@IRSMSX108.ger.corp.intel.com> <1502184.oKzFkHpXjH@xps13> In-Reply-To: <1502184.oKzFkHpXjH@xps13> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Architecture Board Proposal X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2015 16:23:12 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon > Sent: Thursday, October 29, 2015 3:43 PM > To: O'Driscoll, Tim > Cc: dev@dpdk.org > Subject: Re: [dpdk-dev] Architecture Board Proposal >=20 > Hi Tim, >=20 > 2015-10-29 15:21, O'Driscoll, Tim: > > Scope > > ----- > > Issues that are within the scope of the Architecture Board include: > > - Project scope/charter. What is and isn't within the scope of the > project? What happens if somebody wants to upstream a new > library/capability and it's not clear whether it fits within DPDK or > not? As a random example, if somebody wanted to upstream a DPDK-enabled > TCP/IP stack to dpdk.org, should that be accepted or rejected? >=20 > Do you mean the scope of this board would be about the whole projects > hosted > on dpdk.org (http://dpdk.org/browse/) or only the DPDK > (http://dpdk.org/browse/dpdk)? >=20 > Using your TCP stack example, I think it should be hosted on dpdk.org > but it may be out of the scope of the DPDK tree. Good question. I think the scope should be just the DPDK project.