From: Matthew Hall <mhall@mhcomputing.net>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Architecture Board Proposal
Date: Fri, 30 Oct 2015 11:05:23 -0700 [thread overview]
Message-ID: <20151030180523.GB21104@mhcomputing.net> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA67449C7B@IRSMSX108.ger.corp.intel.com>
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.
next prev parent reply other threads:[~2015-10-30 18:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:21 O'Driscoll, Tim
2015-10-29 15:43 ` Thomas Monjalon
2015-10-29 16:23 ` O'Driscoll, Tim
2015-10-29 19:48 ` Dave Neary
2015-10-30 11:01 ` O'Driscoll, Tim
2015-10-30 13:11 ` Dave Neary
2015-10-30 13:23 ` O'Driscoll, Tim
2015-10-30 13:25 ` Thomas Monjalon
2015-10-30 15:17 ` Dave Neary
2015-10-30 18:05 ` Matthew Hall [this message]
2015-11-02 17:50 ` Stephen Hemminger
2015-11-18 17:54 ` O'Driscoll, Tim
2015-12-11 9:47 ` O'Driscoll, Tim
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151030180523.GB21104@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=tim.odriscoll@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).