From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: web@dpdk.org, techboard@dpdk.org
Subject: Re: [dpdk-web] [dpdk-techboard] [PATCH] update techboard description
Date: Wed, 8 Mar 2017 15:29:03 -0800 [thread overview]
Message-ID: <20170308152903.60009058@xeon-e3> (raw)
In-Reply-To: <1487589865-15596-1-git-send-email-thomas.monjalon@6wind.com>
On Mon, 20 Feb 2017 12:24:25 +0100
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> The Technical Board has new members and a new operation mode.
> Some of the changes have been discussed in the Linux Foundation meetings.
> Everything has been agreed in the Technical Board meetings.
>
> Cc: techboard@dpdk.org
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> ---
> about.html | 4 ++
> about/techboard.html | 106 +++++++++++++++++++++++++++++++++++++++++++++++++
> dev.html | 30 ++------------
> scripts/serve_local.py | 2 +-
> 4 files changed, 114 insertions(+), 28 deletions(-)
> create mode 100644 about/techboard.html
>
> diff --git a/about.html b/about.html
> index 1bf3859..c567d23 100644
> --- a/about.html
> +++ b/about.html
> @@ -43,6 +43,10 @@
> <p>For an update of this web site, please join <a href="/ml/listinfo/web">web@dpdk.org</a>
> and check the <a href="/browse/tools/dpdk-web/">git repository</a>.
> <p>For any other question, please contact <a href="mailto:admin@dpdk.org">admin@dpdk.org</a>.
> + <h2>Maintainers</h2>
> + <p>Each project on <a href="/browse/">dpdk.org</a> has its own maintenance process.
> + <p>The main DPDK project has a <a href="/browse/dpdk/tree/MAINTAINERS">list of maintainers</a>
> + and a <a href="/about/techboard">Technical Board</a>.
> <h2>Services</h2>
> <p id="services">Companies able to provide services and support for DPDK environments:</p>
> <ul>
> diff --git a/about/techboard.html b/about/techboard.html
> new file mode 100644
> index 0000000..0390f14
> --- /dev/null
> +++ b/about/techboard.html
> @@ -0,0 +1,106 @@
> +<!DOCTYPE html>
> +<html lang="en">
> +<head>
> + <meta charset="utf-8" />
> + <meta name=viewport content="width=device-width, initial-scale=1" />
> + <title>DPDK Technical Board</title>
> + <link rel="stylesheet" href="/reset.css" />
> + <link rel="stylesheet" href="/layout.css" />
> + <link rel="stylesheet" href="/content.css" />
> + <script type="text/javascript">
> + var _gaq = _gaq || [];
> + _gaq.push(['_setAccount', 'UA-39229303-1']);
> + _gaq.push(['_setDomainName', 'dpdk.org']);
> + _gaq.push(['_setAllowLinker', true]);
> + _gaq.push(['_trackPageview']);
> + (function() {
> + var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
> + ga.src = 'http://www.google-analytics.com/ga.js';
> + var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
> + })();
> + </script>
> +</head>
> +<body>
> +<header>
> + <h1><a href="http://dpdk.org/"><img src="/dpdk.png" alt="DPDK: Data Plane Development Kit"></a></h1>
> + <nav>
> + <ul>
> + <li><a href="/">Home</a>
> + <li><a href="/download">Download</a>
> + <li><a href="/doc">Documentation</a>
> + <li><a href="/dev">Development</a>
> + <li><a href="/ml">Mailing Lists</a>
> + <li><a href="/events">Events</a>
> + <li><a href="/news">News</a>
> + <li><a href="/about" id="current">About</a>
> + </ul>
> + </nav>
> +</header>
> +<section>
> +<h2>Technical Board</h2>
> +
> +<p>More high level details are defined in the
> +<a href="https://docs.google.com/document/d/1x43ycfW3arJNX-e6NQt3OVzAuNXtD7dppIhrY48FoGs">charter</a>.</p>
> +
> +<h3 id="scope">Scope</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 the questions directly related
> +to the development in the following repositories:
> +<ul>
> + <li>dpdk.git
> + <li>dpdk-stable.git
> + <li>dpdk-next-*.git
> + <li>dpdk-ci.git
> + <li>dpdk-web.git
> +</ul>
> +
> +<h3 id="members">Members</h3>
> +<p>The 9 current members of
> +<a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a> are:
> +<ul>
> + <li>Bruce Richardson
> + <li>Hemant Agrawal
> + <li>Jan Blunck
> + <li>Jerin Jacob
> + <li>Konstantin Ananyev
> + <li>Olivier Matz
> + <li>Stephen Hemminger
> + <li>Thomas Monjalon
> + <li>Yuanhan Liu
> +</ul>
> +
> +<h3 id="renewal">Renewal</h3>
> +<p>Technical Board positions are held by individuals, not companies.
> +However, employees of a single company should not occupy more than 40% of board seats.
> +<p>It can be decided to remove a member if there is an approval of 2/3 of the whole Technical Board.
> +It can be decided either to replace the member, or to redefine the size of the board.
> +<p>There will be some renewal when it will be felt as needed.
> +
> +<h3 id="meetings">Meetings</h3>
> +<p>A short meeting happens on IRC (freenode #dpdk-board) every two weeks.
> +<p>The quorum required for a meeting to proceed is a 70% majority of the Technical Board.
> +<p>The Chair is a rotating role among members.
> +<p>Any contributor can ask to add a topic in the agenda by sending an email
> +to <a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a>.
> +The board members will add any topic of interest in the agenda.
> +<p>Minutes are sent to <a href="/ml/archives/dev/">dev@dpdk.org</a> so anyone can comment.
> +However, the technical discussions should happen in the original thread.
> +
> +<h3 id="roles">Roles</h3>
> +<ul>
> + <li>The new project repositories must be approved by the Technical Board,
> + while applying the non-technical criteria defined by the <a href="/404">Governing Board</a>.
> + <li>If a technical discussion lacks of explanation, details or evidence,
> + it will be asked on the mailing list.
> + <li>If a patch does not receive any or enough comment, the board will help
> + to make it progressing on the mailing list.
> + <li>If there is no consensus in a discussion, a decision can be taken
> + by the Technical Board and explained on the mailing list.
> +</ul>
> +<p>For a vote to be passed, a majority (> 50%) of the total Technical Board is required
> +(not just a majority of those in attendance at the meeting).
> +In the event of a deadlock the Technical Board Chair shall have the casting vote.
> +
> +</section>
> diff --git a/dev.html b/dev.html
> index a4b7386..478f712 100644
> --- a/dev.html
> +++ b/dev.html
> @@ -133,32 +133,8 @@
> <p>Most of the patchwork actions can be done
> with a <a href="/dev/patchwork/help/pwclient/">pwclient</a> command line.
>
> - <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 the questions directly related to
> - the development in the following repositories:
> - <ul>
> - <li>dpdk.git
> - <li>dpdk-next*.git
> - <li>dpdk-web.git
> - </ul>
> - <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 current members of
> - <a href="mailto:techboard@dpdk.org">techboard@dpdk.org</a> are:
> - <ul>
> - <li>Bruce Richardson
> - <li>Jerin Jacob
> - <li>Konstantin Ananyev
> - <li>Olivier Matz
> - <li>Panu Matilainen
> - <li>Stephen Hemminger
> - <li>Thomas Monjalon
> - </ul>
> + <h3 id="board">Technical Board</h3>
> + <p>The Technical Board may intermediate in the development process,
> + as described in the <a href="/about/techboard">Technical Board operation</a>.
>
> </section>
> diff --git a/scripts/serve_local.py b/scripts/serve_local.py
> index 63a0e59..bdfc92e 100644
> --- a/scripts/serve_local.py
> +++ b/scripts/serve_local.py
> @@ -2,7 +2,7 @@ import BaseHTTPServer
> from os import curdir, sep, listdir
>
> port = 8000
> -folders = [".", "./doc", "./dev"]
> +folders = [".", "./about", "./doc", "./dev"]
>
> html_files = []
>
Fine as far as it goes. There are some later issues that need to be addressed
in revisions. We need a Code Of Conduct and a process for handling infractions
documented before first offense. This will help CYA and attract a more diverse
set of contributors. If a CoC is not created by techboard one will be placed
upon us by LF.
One issue that has come up on the kernel developers list is how to handle people
who spam the community with useless and broken patches. There is already an unofficial
short list of known abusers who are ignored. As DPDK gets bigger we are bound
to attract these clueless developers. What is the plan for that? Is it a tech
board topic.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2017-03-08 23:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 11:24 [dpdk-web] " Thomas Monjalon
2017-03-08 23:29 ` Stephen Hemminger [this message]
2017-03-09 10:24 ` [dpdk-web] [dpdk-techboard] " Thomas Monjalon
2017-03-09 10:49 ` Mcnamara, John
2017-03-09 17:25 ` Stephen Hemminger
2017-03-09 10:28 ` [dpdk-web] " Thomas Monjalon
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=20170308152903.60009058@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=techboard@dpdk.org \
--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).