[Pesci-discuss] Fw: Last NomCom 2005/06 Call for Volunteers

"Spencer Dawkins" <spencer@mcsr-labs.org> Tue, 04 October 2005 15:29 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMojl-0001t2-1Y; Tue, 04 Oct 2005 11:29:49 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EMojk-0001sw-0o for pesci-discuss@megatron.ietf.org; Tue, 04 Oct 2005 11:29:48 -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 LAA02357 for <pesci-discuss@ietf.org>; Tue, 4 Oct 2005 11:29:45 -0400 (EDT)
Received: from sccrmhc13.comcast.net ([63.240.76.28]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EMosQ-0006Dl-RX for pesci-discuss@ietf.org; Tue, 04 Oct 2005 11:38:48 -0400
Received: from s73602 (unknown[65.104.224.98]) by comcast.net (sccrmhc13) with SMTP id <2005100415293601300als2ue>; Tue, 4 Oct 2005 15:29:37 +0000
Message-ID: <103f01c5c8f8$61dd8800$0500a8c0@china.huawei.com>
From: "Spencer Dawkins" <spencer@mcsr-labs.org>
To: "PESCI Discuss Mailing List" <pesci-discuss@ietf.org>
Date: Tue, 4 Oct 2005 10:29:14 -0500
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Content-Transfer-Encoding: 7bit
Cc:
Subject: [Pesci-discuss] Fw: Last NomCom 2005/06 Call for Volunteers
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

Dear Pesci,

I saw something in Pekka's note on the IETF mailing list that I haven't seen 
discussed previously.

> That aside, I personally didn't volunteer simply because the workload of 
> NomCom appears to be just simply too much given the gains;  weekly [long] 
> conference calls; lots of work going through the persons; an increased 
> number of positions (13, plus more if there will be resignations later on) 
> to fill.
>
> It's not an easy job.  Being able to give input to the IETF leadership 
> certainly is VERY important, and having diverse set of people do it should 
> be a big plus.  However, it may be worth considering whether it's 
> something folks without strong employer backing for getting into that 
> specific post can participate in .. and whether that's a good sign or not.

I forwarded Pekka's note for a few reasons:

- I've been participating in an off-again, on-again discussion about IESG 
overload for a couple of years, but am concerned that even participating in 
NOMCOM may be out of reach for many IETF participants (I know how hard Pekka 
works, and HE doesn't have time for NOMCOM?)

- More to the point for Pesci, we should probably remember this e-mail when 
proposing MORE NOMCOM responsibilities - not that proposing more NOMCOMed 
positions is a bad thing, only that it comes with certain costs. Is it 
possible that PESCI recommendations might involve fewer NOMCOMed positions?

Thanks,

Spencer 


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