Re: SUMMARY: publish list of nominees?

[Mark Allman <mallman@grc.nasa.gov>]

Folks-

I have been wading through the email on this list for some days
now and now have collected my two pennies to throw into the mix:

  * First, I am not sure I buy the argument that we should be making
    it easier for the confirming bodies to reject a selection made
    by the nomcom.  I agree that making this choice a rubber stamp
    based on the timeline is a lousy and should be fixed.  But, that
    seems like a "bug" to me -- i.e., let's just move things out a
    little more so the confirming bodies have more time to review
    things (as has been suggested by others).

    And, there should be process oversight of the nomcom by the
    confirming bodies.  I agree with another suggestion that says
    the liasons should be responsible for vouching for the process
    to their organizations.  The nomcom should not be able to pick
    people arbitrarily behind some veil of secrecy (not that I am
    alleging that has happened to date).

    An easy thing to add to the mix would be for the confirming
    bodies to regularly ask for input on the process while a nomcom
    is active (to ietf-announce).  This gives folks an outlet to
    complain about process issues -- for instance, if I throw my hat
    in the ring and the nomcom never sends a questionnaire and won't
    give me even a chance to say why I think I'd do a good job I
    might like to let someone know (and, I would think the
    confirming bodies would *want* to know this and that it would be
    a good reason to throw a nomcom's selections into doubt).

    So, let's assume the process is clean and everyone (voting
    members, ex-officios, liasons) agrees that the process was sound
    and the appropriate folk were considered and questioned about
    various candidates.  Why should the confirming bodies reject a
    selection made by the nomcom?  It seems to me that should be a
    *very difficult* button to press.  In other words, I think we
    pick a nomcom for a reason and picking an AD (for instance)
    should not be a negotiaion between the nomcom and the IAB.  If
    the nomcom does due diligence and sifts through all the
    candidates and twists arms and talks to people in the community,
    shouldn't their reasoned decision trump the confirming body's?
    The confirming body has not sifted through the information from
    the community as the nomcom has -- so, why should they be in a
    position to say that someone is wrong for a particular slot?

    The above might be a little harsh, or a little out of whack --
    but my high order bit is that pushing the "reject" button should
    be difficult for a confirming body to do.  And, that we should
    not swing from the current state of "very difficult to press" to
    another state of "very easy to press".

  * And then there is the issue of tranparency.  I am unconvinced
    that sending out lists of names is an overall useful idea.  But,
    I think there are several things the nomcom can do to make the
    process a little more transparent to the community:

      + Send the candidate questionnaire to the IETF list for
        *comment*.  The community does not have to come to consensus
        on the questionnaire, however by letting the community look
        at what information the nomcom is gathering (at least as a
        first cut) the community can tell the nomcom that what it
        thinks is important and what should be asked but is not and
        etc.  Of course, I am sure lots of useful information is
        gathered during interviews and informal chats at the
        December IETF meeting.  This would not be captured by
        publishing the questionnaire.  But, it's a start and a way
        to kick the community into giving some thoughts to the
        nomcom. 

      + Rather than a blanket solicitation for input and
        nominations, put together a list of specific questions for
        the community: "Who would be the best person for TSV AD?
        What are this person's key qualifications for the job?  Give
        an example of an instance when this person worked well with
        others to better a specification and obtain community
        consens.  Is there someone you think *should not* be TSV AD?
        Why?"  Etc.  Of course, free-form input would also be
        accepted, but this may end up honing the input from the
        community and help the nomcom.  That is at least a tip to
        folks that saying "Joe Smith for TSV AD" is not enough for
        the nomcom to go on.

      + A bit heavier weight mechanism would be a more verbose
	written report to the community from the nomcom.  Or, at
	least a real report in the plenary about the process.  What
	process does the nomcom actually take?  How many nominees
	are considered?  What sort of guidelines/criteria were
	developed for picking folks, etc.  In other words, give a
	bit of insight into how the nomcom arrived at their
	decisions without talking about people or listing
	candidates.

	(Some conferences have such a report (on the paper review
        process) in the first few pages of the proceedings (usually
        an attempt to calm fears about biases on PCs that lead to
        rejecting worthy papers).  They don't list out the rejected
        papers, or all submitted papers.)

FWIW.

allman


--
Mark Allman -- BBN/NASA GRC -- http://roland.grc.nasa.gov/~mallman/