This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-chair-discuss@ripe.net/
[ripe-chair-discuss] RIPE Chair Selection Process
- Previous message (by thread): [ripe-chair-discuss] RIPE Chair Selection Process
- Next message (by thread): [ripe-chair-discuss] RIPE Chair Selection Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Randy Bush
randy at psg.com
Thu Oct 11 16:40:57 CEST 2018
>>>> Would it work if we let PC appoint NomCom? There are probably problems >>>> with this that I don't see. >>> No. The same perceived problems arise with whatever group appoints the >>> Nomcom. >> >> so don't *appoint* the nomcom at all. random selection. but i already >> said that. > > I think the problem with a random selection is just that, it’s random, > would you really want someone who has never been involved with the > RIPE community picking the potential next RIPE chair? the ietf has the same problem. which is why it is random selection from a QUALIFIED pool of volunteers. in the ietf's case, the sole qualification is attended N out of the last M meetings. where N and M are in one of the RFC citations i gave. it is somewhat odd that meeting attendance is the criterion in a community which claims that the mailing lists are the place where work is done. and, of course, this is re-discussed. it is all spelled out in horrid detail in the rfc cites i gave back in this thread. hard as it is to believe, the ietf is even more obsessed about documenting corner cases than the ripe wannabe technical lawyers. randy
- Previous message (by thread): [ripe-chair-discuss] RIPE Chair Selection Process
- Next message (by thread): [ripe-chair-discuss] RIPE Chair Selection Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]