From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <pmatilai@redhat.com>
Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28])
 by dpdk.org (Postfix) with ESMTP id C63A7C4EC
 for <web@dpdk.org>; Fri, 19 Feb 2016 08:18:40 +0100 (CET)
Received: from int-mx11.intmail.prod.int.phx2.redhat.com
 (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24])
 by mx1.redhat.com (Postfix) with ESMTPS id E13E9486A3;
 Fri, 19 Feb 2016 07:18:39 +0000 (UTC)
Received: from sopuli.koti.laiskiainen.org (vpn1-4-167.ams2.redhat.com
 [10.36.4.167])
 by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id
 u1J7Ibkq020223; Fri, 19 Feb 2016 02:18:38 -0500
To: Stephen Hemminger <stephen@networkplumber.org>,
 Thomas Monjalon <thomas.monjalon@6wind.com>
References: <1455568495-26734-1-git-send-email-thomas.monjalon@6wind.com>
 <20160218103948.420d6ca5@xeon-e3>
From: Panu Matilainen <pmatilai@redhat.com>
Message-ID: <56C6C1CD.5020906@redhat.com>
Date: Fri, 19 Feb 2016 09:18:37 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
 Thunderbird/38.5.0
MIME-Version: 1.0
In-Reply-To: <20160218103948.420d6ca5@xeon-e3>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24
Cc: jerin.jacob@caviumnetworks.com, web@dpdk.org, konstantin.ananyev@intel.com
Subject: Re: [dpdk-web] [PATCH] decision making via technical board
X-BeenThere: web@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: website maintenance <web.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/web>,
 <mailto:web-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/web/>
List-Post: <mailto:web@dpdk.org>
List-Help: <mailto:web-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/web>,
 <mailto:web-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Feb 2016 07:18:41 -0000

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 -