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-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] New RIPE Document: RIPE Accountability Task Force Final Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joao Luis Silva Damas
joao at bondis.org
Wed Jul 31 13:11:12 CEST 2019
Dear all, I also support the current proposed documents and am happy that they are modelled on existing working processes from communities with which RIPE has a good affinity. > On 29 Jul 2019, at 15:19, Daniel Karrenberg <dfk at ripe.net> wrote: > > > > On 25 Jul 2019, at 15:41, Peter Koch wrote: > >> 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. > > Anything we should fix now? I don’t see any. There have been questions around details of the IETF process, such as the recent questions of whether the NomCom Chair’s (or even its prior chair) primary affiliation count against the limit on the number of members sharing primary affiliation in the noncom, but I have no idea how likely that is to happen in practice and would suggest that we observe how the deliberations at the IETF progress while we at RIPE get our own instance of process established and executed. Joao
- Previous message (by thread): [ripe-list] Call for consensus RIPE Chair & Vice Chair selection by Nominating Committee
- Next message (by thread): [ripe-list] New RIPE Document: RIPE Accountability Task Force Final Report
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]