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-list@ripe.net/
[ripe-list] Call for consensus RIPE Chair & Vice Chair selection by Nominating Committee
- Previous message (by thread): [ripe-list] Call for consensus RIPE Chair & Vice Chair selection by Nominating Committee
- Next message (by thread): [ripe-list] Call for consensus RIPE Chair & Vice Chair selection by Nominating Committee
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Koch
pk at DENIC.DE
Thu Jul 25 15:41:21 CEST 2019
On Thu, Jul 04, 2019 at 12:17:40PM +0200, Hans Petter Holen wrote: > The Chair Selection Process > https://www.ripe.net/ripe/mail/archives/ripe-chair-discuss/2019-May/000262.html > > The RIPE Nominating Committee > https://www.ripe.net/ripe/mail/archives/ripe-chair-discuss/2019-May/000263.html I support the architecture of the process and the gist and spirit of the documents. The community should be able to fill the two initial positions well by implementing the described procedures. The approach to stick very closely to the text of RFC 7437 leads to some ambiguities that the initial NomCom might want to seek to resolve. Any such attempt will benefit significantly from experience with the IETF's NomCom procedure - and practice. -Peter
- Previous message (by thread): [ripe-list] Call for consensus RIPE Chair & Vice Chair selection by Nominating Committee
- Next message (by thread): [ripe-list] Call for consensus RIPE Chair & Vice Chair selection by Nominating Committee
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]