Re: [Pesci-discuss] Draft BOF agenda
Sam Hartman <hartmans-ietf@mit.edu> Wed, 19 October 2005 09:53 UTC
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32)
id 1ESAdX-000833-BN; Wed, 19 Oct 2005 05:53:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
by megatron.ietf.org with esmtp (Exim 4.32) id 1ESAdS-00081P-Fu
for pesci-discuss@megatron.ietf.org; Wed, 19 Oct 2005 05:53:30 -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 FAA03271
for <pesci-discuss@ietf.org>; Wed, 19 Oct 2005 05:53:17 -0400 (EDT)
Received: from carter-zimmerman.suchdamage.org ([69.25.196.178]
helo=carter-zimmerman.mit.edu)
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ESAp9-0005a9-BR
for pesci-discuss@ietf.org; Wed, 19 Oct 2005 06:05:32 -0400
Received: by carter-zimmerman.mit.edu (Postfix, from userid 8042)
id 9AB6CE0038; Wed, 19 Oct 2005 05:53:24 -0400 (EDT)
To: Brian E Carpenter <brc@zurich.ibm.com>
Subject: Re: [Pesci-discuss] Draft BOF agenda
References: <4355FE38.4070101@zurich.ibm.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Wed, 19 Oct 2005 05:53:24 -0400
In-Reply-To: <4355FE38.4070101@zurich.ibm.com> (Brian E. Carpenter's message
of "Wed, 19 Oct 2005 10:05:12 +0200")
Message-ID: <tsloe5lrfxn.fsf@cz.mit.edu>
User-Agent: Gnus/5.1006 (Gnus v5.10.6) Emacs/21.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0
Cc: pesci-discuss@ietf.org
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
Hi. I asked Brian to send this here so I could respond on the open list rather than continuing a private discussion with the team. After talking to Brian I've realized there are two things going on with pesci. First, we're defining a set of principles for how we handle process change and proposing next steps to accomplish process change. Second, at the same time, we're trying to create principles to seed and direct the process change effort (section 4.2.3 through 4.2.7). The hope is that we can focus and limit discussions by having a common vision of where we are going. Brian points to section 2.2 of BCP 101 as an example of how this worked for us in the past. We had a long discussion on the IETF list on those principles, but once we agreed, it made the rest of the document easier. Realizing that we had both of these efforts underway was helpful for me at least. I kept trying to figure out why the second part--deciding on general principles to seed process change--mattered. It seems like we have a lot of process change proposals around and I couldn't figure out where these principles would come into play. It seemed like either a proposal would work its way through the process change process and lead to consensus or to failure. At some level that's true. However I can see that the principles will, should they achieve strong community consensus, be a valuable tool for the community in focusing its discussion and forming consensus around specific proposals. I am still concerned that having a focused BOF that attemptes to get agreement on both principles for how to conduct process change plus the next steps for process change and on principles to seedand direct that process change effort. I also wonder whether a BOF is the right forum to really discuss the guiding principles to seed and direct our process change. Here are some of the potential failure conditions I see. We might spend too much time discussing one part of what we're trying to accomplish and fail to get consensus or adequately discuss the other part. We might find that the BOF is not a good enough community cross-section for the general principles discussion and that we end up thinking we've reached agreement only to find in the plenary we've wasted our time and created bad will. My inclination is to focus the BOF discussion on principles for process change and on next steps and to hold the general principles discussion on the list, in the plenary and probably later on the ietf list. However I'm open to other proposals for maintaining bof focus and for addressing my concerns of the previous paragraph. Regardless, I would recommend separating the principles discussion on the agenda. Please consider discussing the process change principles (4.1, 4.2.1 and 4.2.2) separatly from the more general principles (4.2.3 through 4.2.7). You may consider 4.1.1 to be part of the more general principles. Finally, this message has been composed without input from Bert. I know that we were in fairly close alignment last week, but my thinking has changed significantly based on reading the draft and on discussions via jabber with Brian. I don't know if Bert will agree with this proposal. I was not able to get ahold of him before sending this message. _______________________________________________ Pesci-discuss mailing list Pesci-discuss@ietf.org https://www1.ietf.org/mailman/listinfo/pesci-discuss
- [Pesci-discuss] Draft BOF agenda Brian E Carpenter
- Re: [Pesci-discuss] Draft BOF agenda Sam Hartman
- Re: [Pesci-discuss] Draft BOF agenda Scott W Brim
- Re: [Pesci-discuss] Draft BOF agenda Brian E Carpenter