Re: [Eligibility-discuss] Suggestions for nomcom chair selection?

[Michael Richardson <[e-mail]>]

Michael StJohns <[e-mail]> wrote:
    >> On Wed, Sep 09, 2020 at 04:28:49PM -0400, Michael StJohns wrote:
    >>>
    >>> Let's let the Nomcom select the next Nomcom chair, with the approval
    >>> of the IAB and IESG.
    >>
    >> One complaint I have heard repeatedly is that the nomcom is already
    >> overloaded.  Beating the bushes for a good candidate and deciding on
    >> one this way strikes me as another pretty big burden. I am certainly
    >> willing to try it, however, if people want: I would agree to appoint
    >> whomever was selected that way, so that we didn't actually need to
    >> make a process change to try it out.  Of course, we'd have to get a
    >> nomcom to agree to add this to their plate!
    >>
    >> Best regards,
    >>
    >> A

    > One of the things here is that the selection period for the chair is
    > distinct from the normal work period for the Nomcom.  Say they start in
    > March and finish in July for the selection of the next chair?  Or even
    > a much shorter period than that  - May to June - given that there's
    > only one slot being filled.

Let me suggest that the Nomcom N (for years N/N+1), does not select
for Nomcom N+1, but for Nomcom N+2.

Nomcom N could work on this from January to March in year N+1.
They have to stick around waiting for the IAB to confirm IESG members, and
answer queries, and other stuff anyway.

Having selecting the chair for Nomcom N+2, that person could be appointed in
October of year N+1, and if Nomcom N+1 is happy, they could join as
Chair-Elect, learning the ropes by watching much easier.
This is what Allison had proposed, and I tried push convince people it was a
good idea, but did not get far.

This has a initialization challenge where in the first year we need to find
a chair for year 0 (in March), and for year 1 (by October), but aside from
that, it's not any more arduous, I think.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     [e-mail]  http://www.sandelman.ca/        |   ruby on rails    [


--
Michael Richardson <[e-mail]>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide