Re: [Pesci-discuss] Finding and nurturing the bright sparks of genius

Dave Crocker <dhc@dcrocker.net> Sat, 29 October 2005 18:21 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVvKP-00049j-Dg; Sat, 29 Oct 2005 14:21:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EVvKN-00049e-Rx for pesci-discuss@megatron.ietf.org; Sat, 29 Oct 2005 14:21:16 -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 OAA15903 for <pesci-discuss@ietf.org>; Sat, 29 Oct 2005 14:20:57 -0400 (EDT)
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EVvY8-0002d3-P5 for pesci-discuss@ietf.org; Sat, 29 Oct 2005 14:35:33 -0400
Received: from [192.168.0.2] (adsl-67-127-166-199.dsl.irvnca.pacbell.net [67.127.166.199]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id j9TILUAq018426 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <pesci-discuss@ietf.org>; Sat, 29 Oct 2005 11:21:31 -0700
Message-ID: <4363BD7D.7030800@dcrocker.net>
Date: Sat, 29 Oct 2005 11:20:45 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Thunderbird 1.4 (Windows/20050908)
MIME-Version: 1.0
To: pesci-discuss@ietf.org
Subject: Re: [Pesci-discuss] Finding and nurturing the bright sparks of genius
References: <435F63E7.1050705@dial.pipex.com> <F2C57C27B6C69254E554E419@B50854F0A9192E8EC6CDA126>
In-Reply-To: <F2C57C27B6C69254E554E419@B50854F0A9192E8EC6CDA126>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Found to be clean
X-Songbird-From: dhc@dcrocker.net
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
X-BeenThere: pesci-discuss@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: dcrocker@bbiw.net
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


> Some of these have been adopted, most have not. And of the set not 
> adopted, one common thread for many is that we do not know *how to make 
> that change*.

Dave is also fond of pointing out that the *real* common thread is a 
demonstrated community desire to spend more time criticizing and dismissing 
proposals than in making them work.

 From that perspective, the "we do not know how to make that change" 
argument is merely a convenient process hack that successfully distracts us 
from doing the hard work of making real changes.

An alternative to constantly turning every change suggestion into a process 
issue is encourage going about the direct work of making the change.  This 
involves rallying basic support and then focusing on improvement and 
adoption of the change. In such a context, the process oversight merely 
isone of ensuring that an effort doesn't do silly and/or destructive things.

Hence, "process" divides simply into sanity-checking and recruitment of 
community support.

(By the way, that's the way successful IETF process changes have been done 
in the past.)

d/

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