From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: dev@dpdk.org
Subject: Re: Architecture Board Proposal
Date: Thu, 29 Oct 2015 16:43:06 +0100 [thread overview]
Message-ID: <1502184.oKzFkHpXjH@xps13> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA674488A2@IRSMSX108.ger.corp.intel.com>
Hi Tim,
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?
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)?
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.
next prev parent reply other threads:[~2015-10-29 15:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 15:21 Architecture Board Proposal O'Driscoll, Tim
2015-10-29 15:43 ` Thomas Monjalon [this message]
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
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=1502184.oKzFkHpXjH@xps13 \
--to=thomas.monjalon@6wind.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.