Re: Updating BCP 10 -- NomCom ELEGIBILITY

Joel Halpern <jmh@joelhalpern.com> Thu, 12 February 2015 20:57 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 99CA51A82E2 for <ietf@ietfa.amsl.com>; Thu, 12 Feb 2015 12:57:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_DBL_ABUSE_REDIR=0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6AqiSkul8mT9 for <ietf@ietfa.amsl.com>; Thu, 12 Feb 2015 12:57:20 -0800 (PST)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F81D1A6F10 for <ietf@ietf.org>; Thu, 12 Feb 2015 12:57:20 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 10C031C0497; Thu, 12 Feb 2015 12:57:20 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (pool-70-106-135-240.clppva.east.verizon.net [70.106.135.240]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 343081C0180; Thu, 12 Feb 2015 12:57:16 -0800 (PST)
Message-ID: <54DD139B.2010602@joelhalpern.com>
Date: Thu, 12 Feb 2015 15:56:59 -0500
From: Joel Halpern <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: Michael Richardson <mcr+ietf@sandelman.ca>, ietf <ietf@ietf.org>
Subject: Re: Updating BCP 10 -- NomCom ELEGIBILITY
References: <CAL0qLwZk=k-CWLte_ChK9f1kzLwMOTRyi7AwFa8fLjBsextBcA@mail.gmail.com> <9772.1420830216@sandelman.ca> <CAL0qLwZatYW2e4Wk6GXB2U26fsCn8BV2qt-07kHBugiq34zrcQ@mail.gmail.com> <6025.1423672358@sandelman.ca> <CAL0qLwYtE618sA99hgXP-5wk+BYdcXLbiZqd_36OreYQ1LB7hQ@mail.gmail.com> <54DBD71C.20101@joelhalpern.com> <26803.1423772214@sandelman.ca>
In-Reply-To: <26803.1423772214@sandelman.ca>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/EmyO68Kt-OsgcvBLqy5CrBsw3RA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Feb 2015 20:57:22 -0000

Taking this out of order, I think I had one person fail qualification, 
and one person withdraw because they should not have been allowed, 
although the rules at the time would have allowed him.  So your having 
to reject 1/3 of your volunteers is interesting.  I wonder if this is a 
consequence of our pushing so hard for folks to volunteer?

With regard to nomcom qualification and diversity, I wonder if this is 
in part a consequence of our conflating two things.  On one side we have 
actual eligibility to serve on the nominating committee.

On the other hand we have a (small, but significant) number of processes 
which treat nomcom eligibility as essentially membership for having 
standing of various kinds.  This update is probably not the place to 
disentangle the two.  But I think trying to relax nomcom criteria in 
order to solve that problem is putting things the wrong way around.  We 
may well have taken too much of a shortcut in other cases.

I really don't think that relaxing nomcom membership rules is an 
effective way to address our (very real) leadership diversity issue. 
That being said diversity is clearly of value for the nomcom itself, in 
addition to the value for our leadership bodies.  I have no idea whether 
the proposed rules would actually qualify a more diverse set of people. 
  Larger, yes.  More diverse?  Maybe.  But given that all of these rules 
are very rough approximations for what we need, I am concerned that 
relaxing them without sufficient relationship to our needs has a too 
high a probability of making things worse in important ways.

All of which is why I want to see a specific proposal.  And why I have 
said that in the abstract I would like to see improvement.

Yours,
Joel

On 2/12/15 3:16 PM, Michael Richardson wrote:
>
> Joel Halpern <jmh@joelhalpern.com> wrote:
>      > I am starting to sympathize with Mike.  What is our goal here.
>
> I wrote a long email last night, but I did not press send, because I wanted
> to try to be clear, and I know that I tend to be long winded and
> rambly. {"Oops, I did it again" http://goo.gl/sLebz}
>
> The goal is, I think, to have an I* which is make up competent people, who
> spend a reasonable amount of time, but not 100%, making the Internet a better
> place for everyone on the planet.  That means not just having a diverse group
> of people in charge, but making sure that it's clear to everyone on the
> planet that we welcome them: that we desire their participation.
>
> A major feedback from the confirming bodies into the nomcom is about
> diversity of all sorts: gender, age, culture, geography.   The ISOC board
> really cares about this (and that discussion is one reason the IAB
> announcement took longer, btw).  How can we have more diversity without
> sacrificing any of the other things that are also important: like being able
> to work well together.
>
> People have been upset during the past two nomcoms (both of which I was on),
> about the resulting diversity coming out of the selection process.  The
> reality is that the nomcom can't produce diversity; it only filter the input
> for the best people.  That means we if we want diversity, we have to feed the
> pipeline at the bottom.  That presents a bit of an innovator's dilemma
> because the current group of people have been doing things this way for a
> long time, and it has supposedly been "working"...
>
> Yet, notice how hard it is to get younger people in?
> How has the average age of IETF participants grown?
>
> The nomcom eligibility is about as close as we have to a membership process.
> The nomcom eligibility really says to most people: this the minimal amount of
> resources we expect a person to have (and expend) in order to participate.
>
> Right now that criteria significantly excludes people for whom:
>     - travel is expensive for them and/or their company
>
>     - obtaining a US visa is hard. *this is really a huge diversity killer*
>
>     - being away from home and/or office for ~10 days is a challenge
>       (remember that operators have other events, and if we want people
>       who write the code to be enfranchised, we have to remember that they
>       have other *code* related events)
>
>     - travel is just physically difficult for all sorts of reasons
>       (we have a regular and recurring thread on this)
>
> Furthermore, the current criteria, essentially leads to a kind of oligarchy.
> People who are present are the people who decide who shall make the
> decisions, and can essentially only select among those who are present.
>
> The remote participation process is poor in part because nobody of
> significance uses it regularly (and it doesn't enfranchise you).  Since the
> people who make the decisions are never remote, and the people who make the
> decisions about who makes the decisions are also not remote participants.
>
> We claim that we are an open, no-membership required, inclusive organization.
>
> But, the "cabal" that runs the IETF is the group of ~600 people who attend
> essentially every meeting, and I think that about 100 of those people are
> possibly "Elmers".  Of the other 600, I suspect 300 attend regularly, but
> below the 3/5 level, are sometimes above/sometimes below thus too busy
> to volunteer, and 300 were proximal to the meeting, so they came (even if it
> wasn't their first meeting).
>
> But, I note that the nomcom doesn't get 600 volunteers, and of the 233 names
> that I did get, about 80 were rejected: half were very new and surprised at
> the criteria, and the other half were surprised to realize that they were not
> eligible.  Perhaps Joel, you still have your list from when you were chair;
> it would be interesting to compile those statistics into a graph.
>
> I also want to repeat what Ted said this morning about "carbonfest".
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
>   -= IPv6 IoT consulting =-
>
>
>