Re: [ietf-nomcom] The Nominating Committee Process: Eligibility - Recalls

S Moonesamy <sm+ietf@elandsys.com> Thu, 27 June 2013 09:47 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: ietf-nomcom@ietfa.amsl.com
Delivered-To: ietf-nomcom@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84D8121F9C9A for <ietf-nomcom@ietfa.amsl.com>; Thu, 27 Jun 2013 02:47:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pIzOTr+rSYYI for <ietf-nomcom@ietfa.amsl.com>; Thu, 27 Jun 2013 02:47:29 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id A196321F9C6D for <ietf-nomcom@ietf.org>; Thu, 27 Jun 2013 02:47:29 -0700 (PDT)
Received: from SUBMAN.elandsys.com ([197.224.150.5]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id r5R9lDGQ007028 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 27 Jun 2013 02:47:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1372326446; bh=IZw2/HIdQlUy2E/lp5+2CSMs7aCuozEL90j48DpfRUU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=O8e2zQ9tCqbD+r0U7RpybM/UiIPJhbArK4QyBktG5wxWlMIg2yRi56ut4jZc2XA+6 tKoXwLuTqHKLvFZO4R+Ll9Ki9IsWyjnm/jrIhqc7PRqG8J30uqKaYppuL9BgW+zfh3 n/2Y4m3cV/n8wFLUiPYFjyqC+rtYmWdOYUqAloiE=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=elandsys.com; s=mail; t=1372326446; i=@elandsys.com; bh=IZw2/HIdQlUy2E/lp5+2CSMs7aCuozEL90j48DpfRUU=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=ZFrUBcy98PFWn95ErR9G6bAiHeqP7hdwmOBHOX6cl+Q1widajvpBuUCe2Vq6gWuSG 3TDx7GW+IW3lzCn6dmJ9kfaN7xxI7i7ed3BaQM/6YrbVrVAxNMs5+lZc4ZVSLJVRS+ CxNWN2tSdgoWEgqgnVp9Ftakom9MS8onzlYz3YfU=
Message-Id: <6.2.5.6.2.20130627020427.0e9a0b60@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Thu, 27 Jun 2013 02:37:06 -0700
To: Joel <joel@stevecrocker.com>, John C Klensin <john-ietf@jck.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <51CB9E4E.1060004@stevecrocker.com>
References: <6.2.5.6.2.20130625152043.0d65aad0@elandnews.com> <51CA1A54.7080004@stevecrocker.com> <6.2.5.6.2.20130625153339.0d642d00@resistor.net> <51CA1EA5.8040903@stevecrocker.com> <8C48B86A895913448548E6D15DA7553B92660C@xmb-rcd-x09.cisco.com> <6.2.5.6.2.20130625162728.0d645228@elandnews.com> <8C48B86A895913448548E6D15DA7553B9267AD@xmb-rcd-x09.cisco.com> <6.2.5.6.2.20130625184003.0c545fb0@elandnews.com> <51CA68A2.8080304@joelhalpern.com> <6.2.5.6.2.20130625210953.0deb8c48@resistor.net> <51CAEDED.3070607@stevecrocker.com> <6.2.5.6.2.20130626085011.0c47d550@elandnews.com> <51CB267F.20900@dcrocker.net> <6.2.5.6.2.20130626114318.0b83e3e8@elandnews.com> <51CB3D7E.3080908@dcrocker.net> <51CB9E4E.1060004@stevecrocker.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Cc: ietf-nomcom@ietf.org
Subject: Re: [ietf-nomcom] The Nominating Committee Process: Eligibility - Recalls
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-nomcom>
List-Post: <mailto:ietf-nomcom@ietf.org>
List-Help: <mailto:ietf-nomcom-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-nomcom>, <mailto:ietf-nomcom-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jun 2013 09:47:30 -0000

At 19:07 26-06-2013, Joel wrote:
>PS: Addressing the efficacy of remote participation is a fine 
>thing.  It is not something I have a clue how to do, and not a topic 
>for the nomcom list.

Spencer mentioned the following last month:

   "participants have to learn how to collaborate with folks"

   "it's still not easy for me to have conversations with total strangers.
    That's not a cultural challenge, and it's not a language challenge,
    but it is a challenge"

I don't have the clue to make remote participation better.  If "we" 
collaborate we might be able to find solutions.

At 01:00 27-06-2013, John C Klensin wrote:
>At the same time, I think that, if we want broader and more
>diverse participation, including active participation from those
>who don't regularly attend meetings it would be highly desirable
>for Nomcoms to consider sensitivity to those issues as one of
>many factors in selecting members of leadership groups,
>especially the IESG and IAOC.  As has been regularly pointed out
>in "diversity" discussions, having someone who is not a member
>of a particular group speak for and represent that group is
>rarely optimal.

One of the problems with "diversity" discussions is that we get into 
representativity.  The question came up in one of my non-IETF 
roles.  My stance was that I do not represent a group or claim to 
speak on their behalf; I am accountable to them and everybody else.

>Since I've encouraged others to think creatively, let me mention
>a quick thought:   If we conclude that effective Nomcom
>membership requires physical attendance at a majority of recent
>meetings and physical attendance at all meetings during that
>Nomcom's term (I'm not convinced, but that is another matter),
>would the effectiveness of the Nomcom be improved by adding a
>special member who was selected using the usual mechanism but
>drawn from a pool consisting of volunteers from the portion of
>the community who had made multiple observable contributions but
>who didn't meet the meeting attendance criteria?  Those special
>members might not be allowed to vote (consistent with "effective
>Nomcom membership") but, unlike liaisons, would be able to
>participate in all discussions and evaluations of possible
>candidates.

My concern is that once we have a different pool or treat different 
parts of the community differently it can be argued that there should 
be more pools.  Groups that feel slighted will ask for special members.

>Perhaps someone needs to decide to move all or part of this
>discussion to the IETF list.  Until and unless that is done, I
>don't think this list can dodge the apparent inconsistency I
>mentioned in my note of a few minutes ago.

I'll start a thread on that list.

Regards,
S. Moonesamy