From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id 9D8628DA1 for ; Fri, 30 Oct 2015 19:07:12 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 9322C80C00E; Fri, 30 Oct 2015 11:05:23 -0700 (PDT) Date: Fri, 30 Oct 2015 11:05:23 -0700 From: Matthew Hall To: "O'Driscoll, Tim" Message-ID: <20151030180523.GB21104@mhcomputing.net> References: <26FA93C7ED1EAA44AB77D62FBE1D27BA674488A2@IRSMSX108.ger.corp.intel.com> <56327827.1030306@redhat.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA674499B6@IRSMSX108.ger.corp.intel.com> <56336C69.5000405@redhat.com> <26FA93C7ED1EAA44AB77D62FBE1D27BA67449C7B@IRSMSX108.ger.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA67449C7B@IRSMSX108.ger.corp.intel.com> User-Agent: Mutt/1.5.23 (2014-03-12) 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: Fri, 30 Oct 2015 18:07:12 -0000 On Fri, Oct 30, 2015 at 01:23:52PM +0000, O'Driscoll, Tim wrote: > That makes sense. So maybe what we're converging on is the following: > - The scope of the Architecture Board covers all projects hosted on dpdk.org. > - The Architecture Board will approve new projects to be hosted on dpdk.org. > - If it's not clear whether a new piece of functionality resides within one of the existing projects on dpdk.org or needs a new project of its own, the Architecture Board will decide. > > Is that in line with your thoughts on this? > Tim I think a small adjustment to this part could be valuable. DPDK itself is kind of an embedded C programmer thing. So this is likely who will appear in the Arch Board. So is the TCP / IP stack if one comes out. But librte_ipsec and some other stuff would be security related. Something like Apache's ability to have a loosely affiliated / Incubator / Partner project controlled by its original maintainers, and somehow labeled as a friend of DPDK but managed by its original maintainers could be useful. To set expectations it would be labeled on the page for that sort of project that it is included because the DPDK Team felt it is useful, but it does not necessarily follow the standard guarantees of the more official entrants. Matthew.