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-10.md & ripe-nomcom-10.md
- Previous message (by thread): [ripe-chair-discuss] ripe-chair-selection-10.md & ripe-nomcom-10.md
- Next message (by thread): [ripe-chair-discuss] ripe-chair-selection-10.md & ripe-nomcom-10.md
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Sun May 12 14:53:09 CEST 2019
Minor nit: "the RIPE WG Chairs Collective promptly selects a person to act as RIPE Chair Ad Interim and initiates this selection procedure" is ambiguous/unclear. I think this should be "... RIPE Chair Ad Interim who initiates..." Adopting a suitably tweaked IETF's Nomcom process seems a bit excessive but I can live with it because that process is mature and has been well debugged/scrutinised => there's no need to reinvent the wheel. And compared to the alternatives of trying to build something comparable from scratch that could get consensus... I support these draft documents and thank Anna, Daniel, Hans Petter and Mirjam for preparing them.
- Previous message (by thread): [ripe-chair-discuss] ripe-chair-selection-10.md & ripe-nomcom-10.md
- Next message (by thread): [ripe-chair-discuss] ripe-chair-selection-10.md & ripe-nomcom-10.md
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]