From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: jerin.jacob@caviumnetworks.com, web@dpdk.org,
konstantin.ananyev@intel.com
Subject: Re: [dpdk-web] [PATCH] decision making via technical board
Date: Thu, 18 Feb 2016 10:39:48 -0800 [thread overview]
Message-ID: <20160218103948.420d6ca5@xeon-e3> (raw)
In-Reply-To: <1455568495-26734-1-git-send-email-thomas.monjalon@6wind.com>
> + <h3 id="board">Technical board</h3>
> + <p>The decision making process is primarily based on consensus.
> + However in rare cases, the technical board can make a decision
> + when consensus is not reached on the mailing list.
> + <p>The scope of this body is limited to questions directly related to the
> + following repositories:
> + <ul>
> + <li>dpdk.git
> + <li>dpdk-next*.git
> + <li>dpdk-web.git
> + </ul>
If you limit to just git it seems too narrowly focused. What if we had to kick someone
off mailing list? Or negotiate with other organizations. I really don't understand
what this sentence is trying to say (in a legal sense).
> + <p>After having tried to solve every concerns, a maintainer
> + (listed in the <a href="/browse/dpdk/tree/MAINTAINERS">MAINTAINERS file</a>)
> + or a board member (listed below) can request a board meeting as a last resort.
> + Then the technical board will meet on IRC to issue a decision within 2 weeks.
> + A quorum of 6 members is required.
> + <p>The 7 members are:
Maybe add current
> + <ul>
> + <li>Bruce Richardson
> + <li>Jerin Jacob
> + <li>Konstantin Ananyev
> + <li>Olivier Matz
> + <li>Panu Matilainen
> + <li>Stephen Hemminger
> + <li>Thomas Monjalon
> + </ul>
> +
> </section>
next prev parent reply other threads:[~2016-02-18 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 20:34 Thomas Monjalon
2016-02-15 21:06 ` Richardson, Bruce
2016-02-16 7:57 ` Panu Matilainen
2016-02-16 14:06 ` Olivier MATZ
2016-02-16 14:15 ` Ananyev, Konstantin
2016-02-18 18:23 ` Thomas Monjalon
2016-02-18 18:39 ` Stephen Hemminger [this message]
2016-02-19 7:18 ` Panu Matilainen
2016-03-02 18:01 ` [dpdk-web] [PATCH v2] " Thomas Monjalon
2016-03-03 0:13 ` Stephen Hemminger
2016-03-03 11:26 ` Jerin Jacob
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=20160218103948.420d6ca5@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jerin.jacob@caviumnetworks.com \
--cc=konstantin.ananyev@intel.com \
--cc=thomas.monjalon@6wind.com \
--cc=web@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).