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/[email protected]/
[ripe-chair-discuss] RIPE Chair Selection Process
- Previous message (by thread): [ripe-chair-discuss] WG Chair selection
- Next message (by thread): [ripe-chair-discuss] RIPE Chair Selection Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joao Damas
joao at bondis.org
Tue Oct 9 16:37:35 CEST 2018
> On 9 Oct 2018, at 12:00, Filiz Yilmaz <koalafil at gmail.com> wrote: > > > - We could also consider NOMCOM's decision to be the ultimate decision, so their role will be to select the RIPE Chair, full stop. Not just to hand-over a shot-list to the WG Chairs Collective. This is how it is done in some other Communities too. Not the case in IETF and not the case at ICANN, where a background process runs after the nomcom sends the slate of candidates. Of course, they can only refuse a candidate on grounds of problems found during the background check. Personally I would prefer the whole community to agree with the nomcom choices (with the wg chairs just doing the equivalent of the background sanity check before forwarding the list). SO the way I see the WG chair involvement in any stage of this is as a purely caretaker of the admin process, not a selection agent. Joao
- Previous message (by thread): [ripe-chair-discuss] WG Chair selection
- Next message (by thread): [ripe-chair-discuss] RIPE Chair Selection Process
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]