From: Dave Neary <dneary@redhat.com>
To: "O'Driscoll, Tim" <tim.odriscoll@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Architecture Board Proposal
Date: Fri, 30 Oct 2015 09:11:05 -0400 [thread overview]
Message-ID: <56336C69.5000405@redhat.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA674499B6@IRSMSX108.ger.corp.intel.com>
Hi,
On 10/30/2015 07:01 AM, O'Driscoll, Tim wrote:
>>> 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?
>>
>> I agree with Thomas here that this seems like it would be a separate
>> project under dpdk.org, rather than part of DPDK - I think it's OK for
>> the Architecture Board to own the scope of "projects on dpdk.org" rather
>> than just DPDK.
>
> I think there are two questions here. The first is one that Thomas raised and you've also touched on: Is the scope of the Architecture Board just DPDK (i.e. everything in http://dpdk.org/browse/dpdk/), or is it everything hosted on dpdk.org (list at: http://dpdk.org/browse/). My original intent was just DPDK, but I'm fine with either option.
>
> The second question is who decides whether something is within the scope of DPDK or not? A TCP/IP stack was just an example. If I were to submit patches for a DPDK-accelerated IPsec library (librte_ipsec), who would decide whether that's OK or if it needs to reside somewhere else outside of the DPDK? I think that managing the scope of the project should be one of the roles of the Architecture Board.
The issue I see is that if we agree that the architecture board's scope
is limited to DPDK only, and the architecture board owns the scope of
DPDK, that we still have the open question of which projects are
appropriate to be housed under dpdk.org
There was a general agreement in Dublin that DPDK related projects and
applications could live in dpdk.org, but we didn't really touch on the
process or requirements for adding new projects. I think it's
appropriate for the architecture board to own those too.
Thanks,
Dave.
--
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
next prev parent reply other threads:[~2015-10-30 13:11 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 [this message]
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=56336C69.5000405@redhat.com \
--to=dneary@redhat.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 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).