All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Neary <dneary@redhat.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
	"O'Driscoll, Tim" <tim.odriscoll@intel.com>
Cc: dev@dpdk.org
Subject: Re: Architecture Board Proposal
Date: Fri, 30 Oct 2015 11:17:17 -0400	[thread overview]
Message-ID: <563389FD.30407@redhat.com> (raw)
In-Reply-To: <5157985.jDBArynuku@xps13>



On 10/30/2015 09:25 AM, Thomas Monjalon wrote:
> 2015-10-30 13:23, O'Driscoll, Tim:
>> From: Dave Neary
>>> 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.
>>
>> 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?
> 
> Do we need a board to define the scope of this board? ;)

:-)

> The only reason I see to reject a project, would be to consider that the
> project is not related to DPDK enough. I think it will be an obvious decision.
> So it shouldn't be a high responsibility nor a high workload to add to this
> board.
> But clearly, the hosted projects (except DPDK itself) should not be impacted
> by the DPDK board.

You have a good point - and in the spirit of "the board exists only to
make decisions that aren't converging in the community", maybe we don't
need more.

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

  reply	other threads:[~2015-10-30 15:17 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
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 [this message]
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=563389FD.30407@redhat.com \
    --to=dneary@redhat.com \
    --cc=dev@dpdk.org \
    --cc=thomas.monjalon@6wind.com \
    --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.