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 ]
Jim Reid
jim at rfc1035.com
Mon Oct 8 17:49:40 CEST 2018
> On 8 Oct 2018, at 16:36, Randy Bush <randy at psg.com> wrote: > >> But if any alternatives have been suggested, I've missed them, and >> we're now effectively in last call. > > sorry i was insufficiently explicit. random selection from qualified > vulunteer pool, à la ietf. IIUC that’s what is envisaged here. The WGCC definitely won't be the Nomcom. However it’ll have some role in determining how stuckees get selected for the Nomcom. Something similar to how the IETF nomcom is formed seems the most likely method. Though I suppose the WGCC could have a brain fart and come up with something completely different. YMMV.
- 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 ]