Re: [Pesci-discuss] Minutes for PESCI team meeting 5th October 2005

"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Tue, 11 October 2005 23:06 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPTCK-00033E-63; Tue, 11 Oct 2005 19:06:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EPTCI-000337-Uu for pesci-discuss@megatron.ietf.org; Tue, 11 Oct 2005 19:06:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08949 for <pesci-discuss@ietf.org>; Tue, 11 Oct 2005 19:06:11 -0400 (EDT)
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EPTMV-0004Wr-5h for pesci-discuss@ietf.org; Tue, 11 Oct 2005 19:16:47 -0400
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=jfc.afrac.org) by montage.altserver.com with esmtpa (Exim 4.44) id 1EPTC5-00082n-Aq; Tue, 11 Oct 2005 16:06:01 -0700
Message-Id: <6.2.3.4.2.20051012004423.04f450a0@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Wed, 12 Oct 2005 00:55:04 +0200
To: Adrian Farrel <adrian@olddog.co.uk>, <pesci-discuss@ietf.org>
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
Subject: Re: [Pesci-discuss] Minutes for PESCI team meeting 5th October 2005
In-Reply-To: <2a6801c5ceaf$12670ff0$f2849ed9@Puppy>
References: <2a6801c5ceaf$12670ff0$f2849ed9@Puppy>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f60d0f7806b0c40781eee6b9cd0b2135
Cc:
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Process Evolution Study Committee of the IETF discussion <pesci-discuss.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/pesci-discuss>
List-Post: <mailto:pesci-discuss@ietf.org>
List-Help: <mailto:pesci-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/pesci-discuss>, <mailto:pesci-discuss-request@ietf.org?subject=subscribe>
Sender: pesci-discuss-bounces@ietf.org
Errors-To: pesci-discuss-bounces@ietf.org

If the following inserts can help?

At 23:59 11/10/2005, Adrian Farrel wrote:
>1. Principles and Goals
>
>* Limited list of sacred cows must be included
>   - open process
>   - rough consensus
>   - running code when we can get it

     - alternative experimentation reports
     - digital convergence with other SSDO (their needs/positions are 
our concerns)
     - user QA

>* All decisions are subject to appeal. A complete complaints, conciliation
>   and appeals process should be documented.

Privacy and Defense rights are to be protected and warrantied.

>* Decision criteria and procedures that support the process should be
>   publicly documented.
>   - This should include criteria for document quality (distinct from
>TechSpec)
>
>* Cycling through leadership positions should be encouraged rather than
>   making them a career.
>   - Debated the underlying goal.
>   - Agreed that discussion of fixed term is not in scope as it is not a
>     goal per se.
>
>* Goal with NomCom is to ensure that there is a sufficiently large pool of
>   volunteers.
>   - Issues of how NomCom work is structured and how much work there is,
>     may impact on this, but discussions of fixing this are solutionism.
>
>* Need a method to develop future leaders within the active community
>   should be added
>   - Problem is that we don't have a large enough pool of candidate leaders
>   - Process must include a way for people to be trained

Local Testing units could be used as local pool of competence, 
representation and IETF cultural training. In coordination with ISOC. 
A way to multiculturalise the IETF.

>* WGs should be primarily responsible for the quality of their output.
>   - An objective is to reduce the number of IESG DISCUSSes
>   - Aim for some consistency of I-Ds as they hit the IESG

There should be a way to block a WG when it becomes politically sided 
or commercially derailed. The problem is that opponents and political 
supporters are outside the IETF, the WG may be on-purpose or lead to 
consensus by exhaustion.

>2. I-D
>* Elwyn has taken over editing the I-D. Aim to have a new version for team
>   review ASAP.
>
>3. Other Points
>* We need to examine each principle that we document to check that it is a
>   real principle and not a solution. Where it is a solution, we need to
>   dig for the real principle.

ditto if introduced solutions do not hide new principles which may 
conflict further on.

jfc


_______________________________________________
Pesci-discuss mailing list
Pesci-discuss@ietf.org
https://www1.ietf.org/mailman/listinfo/pesci-discuss