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

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

[Thomas Monjalon]

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

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

[Richardson, Bruce]

> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Monday, February 15, 2016 8:35 PM
> To: web@dpdk.org
> Cc: stephen@networkplumber.org; pmatilai@redhat.com; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; Richardson, Bruce
> <bruce.richardson@intel.com>; olivier.matz@6wind.com;
> jerin.jacob@caviumnetworks.com
> Subject: [PATCH] decision making via technical board
> 
> 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
Acked-by: Bruce Richardson <bruce.richardson@intel.com>

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

[Panu Matilainen]

On 02/15/2016 10:34 PM, Thomas Monjalon wrote:
> 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>
>

Acked-by: Panu Matilainen <pmatilai@redhat.com>

	- Panu -

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

[Olivier MATZ]

On 02/15/2016 09:34 PM, Thomas Monjalon wrote:
> 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>

Acked-by: Olivier Matz <olivier.matz@6wind.com>

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

[Ananyev, Konstantin]

> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Monday, February 15, 2016 8:35 PM
> To: web@dpdk.org
> Cc: stephen@networkplumber.org; pmatilai@redhat.com; Ananyev, Konstantin; Richardson, Bruce; olivier.matz@6wind.com;
> jerin.jacob@caviumnetworks.com
> Subject: [PATCH] decision making via technical board
> 
> 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>
> ---

Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>

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

[Thomas Monjalon]

Stephen, Jerin,

Ack or comment?

2016-02-15 21:34, Thomas Monjalon:
> 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>

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

[Stephen Hemminger]

> +	<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>

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

[Panu Matilainen]

On 02/18/2016 08:39 PM, Stephen Hemminger wrote:
>
>> +	<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).

I think the point was, the technical board is for technical issues only 
and kicking somebody off a mailing list is something else. We did 
discuss code of conduct for the project but not how it would be 
enforced, or by whom.

	- Panu -

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

[Thomas Monjalon]

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>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Acked-by: Panu Matilainen <pmatilai@redhat.com>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
---
v2:
- add current
- add mailing list address
- add some words in scope
The previous acks were kept. Please comment.

--- 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,33 @@
 	<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 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>
+
 </section>
-- 
2.7.0

Re: [dpdk-web] [PATCH v2] decision making via technical board

[Stephen Hemminger]

On Wed,  2 Mar 2016 19:01:18 +0100
Thomas Monjalon <thomas.monjalon@6wind.com> wrote:

> 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>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> Acked-by: Panu Matilainen <pmatilai@redhat.com>
> Acked-by: Olivier Matz <olivier.matz@6wind.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>

Acked-by: Stephen Hemminger <stephen@networkplumber.org>

Re: [dpdk-web] [PATCH v2] decision making via technical board

[Jerin Jacob]

On Wed, Mar 02, 2016 at 07:01:18PM +0100, Thomas Monjalon wrote:
> 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>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> Acked-by: Panu Matilainen <pmatilai@redhat.com>
> Acked-by: Olivier Matz <olivier.matz@6wind.com>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>

Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>