DPDK patches and discussions
 help / color / mirror / Atom feed
From: Dave Neary <dneary@redhat.com>
To: "O'Driscoll, Tim" <tim.o'driscoll@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Technical Steering Committee (TSC)
Date: Wed, 20 May 2015 12:04:01 -0700	[thread overview]
Message-ID: <555CDAA1.7030703@redhat.com> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BA54D43080@IRSMSX102.ger.corp.intel.com>

Hi,

On 05/14/2015 01:55 PM, O'Driscoll, Tim wrote:
> At Tuesday's Beyond DPDK 2.0 call, one topic we discussed was decision making and whether we need a Technical Steering Committee (TSC). As a follow-up to that discussion, I'd like to propose that we create a TSC for DPDK to guide the long-term strategic direction of the project.

As others have said, I think a TSC can have value, more as the "guardian
of the roadmap", a place to engage to set high level goals and
priorities for the project. And as Neil and Thomas said, I also agree
that it does not make sense for the TSC to get involved in the
day-to-day of the project (patch review, for example).

There is a danger with TSCs that you end up with "design by committee" -
but I think that is a risk that can be mitigated by limiting the scope.

In terms of membership: I do think it's important to have the voice of
users in the technical community, but I agree with Stephen that the TSC
would not be the appropriate forum for that.

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

      parent reply	other threads:[~2015-05-20 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-14 20:55 O'Driscoll, Tim
2015-05-19 14:43 ` Stephen Hemminger
2015-05-19 15:34   ` Neil Horman
2015-05-19 15:45     ` Thomas Monjalon
2015-05-19 17:34       ` Neil Horman
2015-05-19 20:21         ` O'Driscoll, Tim
2015-05-20 19:04 ` Dave Neary [this message]

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=555CDAA1.7030703@redhat.com \
    --to=dneary@redhat.com \
    --cc=dev@dpdk.org \
    --cc=tim.o'driscoll@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).