From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] Technical Steering Committee (TSC)
Date: Tue, 19 May 2015 17:45:05 +0200 [thread overview]
Message-ID: <6422303.qpQUJvDa9r@xps13> (raw)
In-Reply-To: <20150519153434.GA29078@hmsreliant.think-freely.org>
2015-05-19 11:34, Neil Horman:
> On Tue, May 19, 2015 at 07:43:14AM -0700, Stephen Hemminger wrote:
> > > Composition of the TSC should reflect contributions to the project, but be
> > > balanced so that no single party has an undue influence. It should also be
> > > kept to a manageable size(maybe 7?).
> > >
> > > The TSC should elect its own chair, who would have the deciding vote in
> > > the event that the TSC was deadlocked. Once in place, the TSC should
> > > approve any new members.
> > >
> > > Specific details on membership can be discussed and agreed later, if we
> > > agree on the creation of a TSC.
> >
> > TSC should be limited to those individuals and companies that have
> > contributed in a non-trivial way to the DPDK distributed code base.
> > It should not be a users group, or place for network vendors who take but
> > never give back.
> >
> +1
>
> It should also endavour to only act as a fallback body for any issues commonly
> handled by the development communtiy (patch acceptance/review, etc)
I agree that it should be a fallback.
And I'm wondering how useful it would be: have we ever known such discussion or
conflict without finding a solution or a consensus?
By the way, is there a TSC in Linux netdev?
next prev parent reply other threads:[~2015-05-19 15:45 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 [this message]
2015-05-19 17:34 ` Neil Horman
2015-05-19 20:21 ` O'Driscoll, Tim
2015-05-20 19:04 ` Dave Neary
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=6422303.qpQUJvDa9r@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
/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).