[dpdk-web] [PATCH] decision making via technical board

[Thomas Monjalon <thomas.monjalon@6wind.com>]

Explains the decision making process for consensus exception.
It has been discussed and decided by the technical board during
its first meeting.

Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
---
 dev.html | 33 +++++++++++++++++++++++++++++++++
 1 file changed, 33 insertions(+)

diff --git a/dev.html b/dev.html
index a091efc..2851eb2 100644
--- a/dev.html
+++ b/dev.html
@@ -44,8 +44,10 @@
 	Coming patches are listed in <a href="/dev/patchwork">patchwork</a>.
 	<p>Planned features are listed in the <a href="/dev/roadmap">roadmap</a>
 	and integrated during a <a href="/dev/roadmap#cycle">cycle started by a merge window</a>.
+
 	<h3 id="licenses">Licenses</h3>
 	<p>Main code is BSD licensed and Linux kernel related parts are naturally licensed under the GPL.
+
 	<h3 id="clone">Get source code</h3>
 	<p>Read-only access:
 	<pre>git clone git://dpdk.org/dpdk</pre>
@@ -53,6 +55,7 @@
 	<pre>git clone http://dpdk.org/git/dpdk</pre>
 	<p>The source code can be <a href="/browse/dpdk/tree/">browsed online</a>.
 	<p>Focus is on next version in git <em>HEAD</em>. There is no maintenance of previous versions.
+
 	<h3 id="send">Contribute by sending patches</h3>
 	<p>Patches should be sent and reviewed via the <a href="/ml/archives/dev">mailing list</a>.
 	Be sure <a href="/ml/listinfo/dev">to be registered</a>.
@@ -104,12 +107,14 @@
 	fixline = log -1 --abbrev=12 --format='Fixes: %h (\"%s\")'</pre>
 	<p>The built-in documentation have more details about the
 	<a href="/doc/guides/contributing/patches.html">contribution guidelines</a>.
+
 	<h3 id="review">Contribute by testing or reviewing patches</h3>
 	<p>Patches are applied in the git repository when it becomes clear that
 	they are well written and do the right things.<br>
 	Test reports and reviews help a lot in the process.
 	Such contributions are marked with flags
 	<em>Tested-by</em>, <em>Reviewed-by</em> or <em>Acked-by</em>.
+
 	<h3 id="patchwork">Status of patches</h3>
 	<p>Once sent to the mailing list, patches are automatically registered
 	in <a href="/dev/patchwork">patchwork</a> with status <em>"New"</em>.
@@ -124,4 +129,32 @@
 	<p>Patchwork can also help to download patches individually or bundled.
 	<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 questions directly related to 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 members are:
+	<ul>
+		<li>Bruce Richardson
+		<li>Jerin Jacob
+		<li>Konstantin Ananyev
+		<li>Olivier Matz
+		<li>Panu Matilainen
+		<li>Stephen Hemminger
+		<li>Thomas Monjalon
+	</ul>
+
 </section>
-- 
2.7.0