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 ]
Nick Hilliard
nick at foobar.org
Sun Oct 7 17:32:43 CEST 2018
Mirjam Kuehne wrote on 02/10/2018 10:27: > Based on community input, including a plenary session at RIPE 76 and a > discussion on this mailing list, we put together a final version of the > RIPE Chair selection process: > > https://labs.ripe.net/Members/mirjam/ripe-chair-selection-process > > This will be presented during the plenary at RIPE 77 with the aim to > reach consensus on the process. This looks mostly fine, with the exception of the involvement of the WG Chairs Collective in the NomCom appointment process. There is long running disquiet in the RIPE community about the WG Chairs Collective as an institution. There are other similar organisation structures on the internet who have nomcom mechanisms which work well, which the RIPE community could use. As a separate consideration, there is no particular reason to use the WG Chairs Collective for this purpose. In the interests of bottom-up process and transparency, it would be better to invest the nomcom mechanism in something else. I'm not able to support the current proposal, due to this point. Nick
- 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 ]