Re: [ietf-nomcom] announcing list of willing candidates

Thomas Narten <narten@us.ibm.com> Sun, 17 May 2009 19:53 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: ietf-nomcom@core3.amsl.com
Delivered-To: ietf-nomcom@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3293528C24C for <ietf-nomcom@core3.amsl.com>; Sun, 17 May 2009 12:53:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.294
X-Spam-Level:
X-Spam-Status: No, score=-6.294 tagged_above=-999 required=5 tests=[AWL=0.305, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N8L7gearWSiv for <ietf-nomcom@core3.amsl.com>; Sun, 17 May 2009 12:53:02 -0700 (PDT)
Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) by core3.amsl.com (Postfix) with ESMTP id AD8FD28C1B7 for <ietf-nomcom@ietf.org>; Sun, 17 May 2009 12:53:02 -0700 (PDT)
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e2.ny.us.ibm.com (8.13.1/8.13.1) with ESMTP id n4HJoaj0022646 for <ietf-nomcom@ietf.org>; Sun, 17 May 2009 15:50:36 -0400
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n4HJsZXq232740 for <ietf-nomcom@ietf.org>; Sun, 17 May 2009 15:54:37 -0400
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n4HJsZ91022375 for <ietf-nomcom@ietf.org>; Sun, 17 May 2009 15:54:35 -0400
Received: from cichlid.raleigh.ibm.com (sig-9-76-131-135.mts.ibm.com [9.76.131.135]) by d01av04.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id n4HJsXR4022355 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 17 May 2009 15:54:34 -0400
Received: from cichlid.raleigh.ibm.com (cichlid [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.2/8.12.5) with ESMTP id n4HJsW2W013397; Sun, 17 May 2009 15:54:32 -0400
Message-Id: <200905171954.n4HJsW2W013397@cichlid.raleigh.ibm.com>
To: SM <sm@resistor.net>
In-reply-to: <6.2.5.6.2.20090512111353.03369dd0@resistor.net>
References: <8EFB68EAE061884A8517F2A755E8B60A1CD8A4B0C3@NA-EXMSG-W601.wingroup.windeploy.ntdev.microsoft.com> <72E1E2EDDBD5CBDD92BF837F@eList-eXpress-LLC.local> <499F3A1A.7020205@thinkingcat.com> <51C740C6-2F58-4B5D-BB51-C6C937D5EF35@tcb.net> <D02C39BBF12140D78A7A1D2959BFDFCA@china.huawei.com> <C6B562F0-5D5D-42BD-BAB2-686CD664D840@tcb.net> <874B0EA5B7474E40BC4771582E20F135@china.huawei.com> <4A01FF14.1000802@joelhalpern.com> <68203580453A41F9BE4A8E17676A40DD@china.huawei.com> <52670AA1-1957-4C8C-9A51-4336DFB1ECFC@cisco.com> <FCB5120A1CD64E909F4211EF37A783AA@china.huawei.com> <675982CA-8EED-470C-888D-DB876816D256@cisco.com> <5CEDB6DE69CE4EB18AD366AFFEC06F54@china.huawei.com> <EEBB63F1-9BBF-4D2C-8AC0-EB7437F287A3@nokia.com> <C01E0DD4CB124AD6A4C06790EBD5F5C7@china.huawei.com> <4A02DD01.3040009@joelhalpern.com> <E1B7E9E104194E449E12752075358FC2@china.huawei.com> <93AEDB8B-47E1-4FEA-A342-1D549F157453@cisco.com> <11211.1241802463@epsilon.noi.kre.to> <6.2.5.6.2.20090508212200.031d3! d80@resistor.net> <5809C3060E3948E8BFF2846F44C614CD@china.huawei.com> <6.2.5.6.2.20090512111353.03369dd0@resistor.net>
Comments: In-reply-to SM <sm@resistor.net> message dated "Tue, 12 May 2009 12:56:45 -0700."
Date: Sun, 17 May 2009 15:54:32 -0400
From: Thomas Narten <narten@us.ibm.com>
Cc: NomComDiscussion <ietf-nomcom@ietf.org>
Subject: Re: [ietf-nomcom] announcing list of willing candidates
X-BeenThere: ietf-nomcom@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussions of possible revisions to the NomCom process <ietf-nomcom.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sun, 17 May 2009 19:53:08 -0000

SM <sm@resistor.net> writes:

> At 07:16 12-05-2009, Thomas Narten wrote:
> >I'd still really like to see more context about what the intention
> >here is, rather than just listing rules. How about something like:
> >
> >      The list of nominees willing to serve in positions under review
> >      in the current NomCom cycle is not confidential.  The NomCom should
> >      publish a list of names of willing nominees to the community, in
> >      order to obtain feedback from the community on these nominees.

> I suggest something along the lines of:

>    All deliberations and supporting information that relates to specific
>    nominees, candidates, and confirmed candidates are confidential.
>    The nominating committee retains the discretion to disclose the names
>    of the nominees and the positions in which they are willing to serve to
>    obtain feedback from the community on these nominees.

I think this text is better in some ways, but saying "retains the
discretion to disclose names" does not capture the WG intent, which is
clearly a "SHOULD publish the names".

If every other nomcom decides (based on the inclinations of each
year's particular nomcom) decide not to publish a list at all, I
suspect the community would not be happy.

> I used "names" instead of "list" so that NomCom can publish a partial 
> list of nominees.  Although I did not suggest a time frame for 
> publication, I gather that NomCom will need to have guidelines for 
> that and it will also depend on the circumstances.  But it's up to 
> NomCom to draw that up instead of having text in the draft.  I didn't 
> mention "padding".  The discussion within the IETF Community might 
> influence NomCom to stop that practice.

Generally, I do prefer that the operational details of what to post be
left to the nomcom.

> >For paragraph 4, I've added some text at the end (in CAPS for clarity):
> >
> >      Feedback on willing nominees should always be provided privately
> >      to NomCom.  Willing nominees should not solicit support, and
> >      other IETF community members should not post statements of
> >      support/non-support for nominees IN ANY PUBLIC FORA (E.G.,
> >      MAILING LIST)

> Do we really need to say that the feedback should be provided 
> privately?

Yes. If there is no text saying discussions on the IETF list are not
appropriate, somebody will end up doing it, claiming it is perfectly
OK to do so.

> I have not seen any nominees publicly soliciting support 
> or participants posting statements of support.

In the past we viewed the list of nominees to be confidential and
solicting support would have been frowned upon. By loosening up the
rules, we would presumably also be loosening up the expectations in
other areas to.

> I gather that it's due to the "culture" of the IETF where it is
> understood that such behavior will be viewed as unacceptable.  Once
> we start saying the community "should not do", we'll have everything
> else as acceptable.  I don't think that's a good idea.

You seem to be saying that if we say in a document "you should not do
X", that somehow implies anything "not X" implicitely becomes
allowed. I don't see how that follows. Moreover, the implications of
such reasoning would surely complicate all our documents, that weren't
written with such an assumption

> >Then add:
> >
> >      Discussion: Prior to this document, the names of willing nominees
> >      was considered confidential and not disclosed publically. The
> >      community has long had differing views on this rule. Many have
> >      argued that the lack of a published list made it difficult for
> >      the community to provide adequate feedback to the nomcom. Others
> >      have argued that publishing such a list could lead to campaigning
> >      and other undesireable behaviors.
> >
> >      The intention of relaxing this rule is to have the nomcom publish
> >      a list of willing candidates so that the community has the
> >      ability to provide feedback on those being considered for
> >      service. However, the nomcom is also chartered to find the best
> >      candidate for any particular position. Even after an initial list
> >      of willing nominees has been compiled, the nomcom is expected to
> >      continue to actively recruit additional nominees, especially in
> >      cases where the nominee pool is deemed insufficient. While the
> >      nomcom is encouraged to publish all names when it can, it is not
> >      required to do so in cases that could interfere with its ability
> >      to find the best candidate, e.g., where a nominee is not willing
> >      to have their name published, or where a nominee is found
> >      relatively late in the process, etc.

> Having that as a discussion is fine.  It gives an idea of the intent 
> for the change.  BTW, why is there emphasis on "willing"?

"Willing" comes from earlier text, and indicates the person is
"willing to serve", and by implication, is not a ringer.

> Nomcom requires feedback on all nominees, whether they are willing
> to serve or not.  If you use "willing" in the above, NomCom has less
> leeway for recruitment.

Seems like the nomcom (and the community) should not spend much time
on nominees that are not willing to serve...

> At 07:45 12-05-2009, Thomas Narten wrote:
> >But there is a slippery slope here. And I think we do not want
> >discussion of individual candidates to ever take place on public
> >mailing lists. So some sort of guidance is needed. (We should't try to
> >regulate what goes on in private, however, as enforcement is tricky)

> And how would it be enforced if it's done publicly?  I don't expect a 
> answer to the question as it may be better to leave some things
> unsaid. :-)

Public shaming. If it does, I'd expect the community to say "stop
doing this" and point to the document for justification.

> At 10:48 12-05-2009, Spencer Dawkins wrote:
> >I am wondering if this material needs to be part of a small revision 
> >to Section 3, bullet 6, or if it should go into (for example) an 
> >Informational statement of NomCom principles (such as the excellent 
> >"don't pick a nominee just because you can't find anyone else who's 
> >willing to serve"), that could be discussed and advanced separately.

> I prefer to have any guidance in a separate Informational document.
> Then it cannot be read as telling NomCom how it should do its work.

As said in another post, the guidance we give should be
normative. Otherwise, why bother giving it?

Thomas