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 Job description
- Previous message (by thread): [ripe-chair-discuss] RIPE Chair Job description
- Next message (by thread): [ripe-chair-discuss] RIPE Chair Job description
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Jim Reid
jim at rfc1035.com
Tue Oct 11 11:55:26 CEST 2016
> On 11 Oct 2016, at 10:32, Filiz Yilmaz <koalafil at gmail.com> wrote: > > I tend to agree with Shane's point of somewhat defining the scope of > RIPE Chair responsibilities, so what is expected of this position in > its broad terms, as well as any selection process for the position. > > Having said that, I would not use "Job description" in any document > eventually describing these, because that sounds requiring a level of > detail which I believe we do not need to prescribe to this position. > There will always be things this position can find itself to be > involved as our Community and industry evolves. So I would leave it to > RIPE Chair Responsibilities or Scope of RIPE Chair, or something along > those lines. +1 I would be wary of “defining the scope” though. That could be unduly restrictive and inflexible. A scoping exercise will also encourage far too much rat-holing and shed-painting, something which we’re overly fond of doing. [That’s probably going to happen regardless. Sigh.] An outline of the general responsibilities of the role seems to be the thing to do here.
- Previous message (by thread): [ripe-chair-discuss] RIPE Chair Job description
- Next message (by thread): [ripe-chair-discuss] RIPE Chair Job description
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]