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 ]
Jim Reid
jim at rfc1035.com
Sun Oct 14 14:35:45 CEST 2018
> On 14 Oct 2018, at 13:18, Nigel Titley <nigel at titley.com> wrote: > > I like this, it isn't too formal and it's descriptive rather than > prescriptive, which always seems to me to be the best way of proceeding > in cases such as this. +1 > Where i differ is in thinking that the process of selecting the RIPE > Chair can pretty well be decoupled from the job description. However I'd > not lose sleep if we decide to sort out the job description first. Well it looks like we'll have consensus on the job description before we have that on the selection process. Creating a dependency between the two will add unwelcome complexity IMO. > Is it appropriate to formalise the job of the vice chair at this time > (if we decide to have a vice chair)? How about this: The vice chair deputises for the chair as needed and deals with all the stuff that the RIPE chair doesn't want to do?
- 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 ]