ietf
[Top] [All Lists]

Updating BCP 10 -- NomCom ELEGIBILITY

2015-01-09 13:04:02

I would like to change the nomcom eligibility criteria.
SM has proposed some things awhile ago in:
        draft-moonesamy-nomcom-eligibility-01

kept the current rules of 3/5, but added options where
the "3rd" meeting could really be in the form either having
been to a lot of meetings, or having used day-passes..

I don't think SM's proposal does the right thing.
My concern is primarily about people who enter our culture,
and then for some reason are unable to travel. (Could be health,
could be inability to get VISAs, could be funding, could be children) 

So I would keep the 3/5 in-person meetings to *become* nomcom 
eligible.  

Once eligible, the rules for remaining eligible would be different.
I would propose something like having *contributed* to at least two
meetings in the past four.  We could come up with complex or simple
rules on what it means to contribute, we could automated it, and
we can discuss all the ways that various rules could be gamed.
My ideas for contribution would include:
  0) attend the meeting in person.
  1) be a document shepherd or working group chair on a document
     that entered AUTH48.
  2) be the document uploader (pressed submit) on a document that
     was scheduled into a WG session. (A document authors that has
     never been to a meeting would never have become eligible. If
     document authors want to rotate who submits, that actually
     seems like a good idea if it keeps their hand in, as I've had to almost
     stalk some co-authors during AUTH48 who seem to have fallen off the
     planet) 
  3) opened a ticket on a document that was scheduled into a WG session.
  4) scribed for the I* telechats.

Note that I have avoided counting "remote attendance" activities
specifically, because that would require us to figure out who attended
and register them, etc. and I don't think we are ready for that yet.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr(_at_)sandelman(_dot_)ca  http://www.sandelman.ca/        |   ruby on 
rails    [ 
        

Attachment: signature.asc
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>