[ripe-chair-discuss] In-person discussion of RIPE Chair Selection (was: RIPE Chair Job description)

Filiz & all,

tl;dr I think we need an in-person discussion of the procedure. We need
      to have the discussion at RIPE 73, or defer using the procedure
      until we have had the discussion.

More words:

Your question about a discussion next week is important. Thanks
for bringing it up.

Looking at the post that kicked off this discussion:

https://labs.ripe.net/Members/hans_petter_holen/draft-ripe-chair-election-procedure

We see the proposal:

* Use the process for electing RIPE Chair at RIPE 74 in May 2017 

It seems like an in-person discussion of the RIPE chair selection
process is worthwhile, and RIPE 73 is the last time to have such a
discussion before RIPE 74.

I'd be happy if we deferred selecting a RIPE Chair until RIPE 75; I
don't think there is any hurry. Alternately, we need to get some time
on the agenda next week to discuss it. It's as late as can possibly be,
but if it is important to use this procedure for RIPE 74 then I think
we must have a face-to-face discussion about it.

Sorry if I missed time for this already on the agenda. I don't remember
seeing anything, but my memory is definitely not perfect.

Cheers,

--
Shane

At 2016-10-21 10:04:46 +0200
Filiz Yilmaz <koalafil at gmail.com> wrote:

> Thanks Mirjam. This helps. Glad to hear there was indeed a draft
> document on this.
> 
> This draft addresses my comments about the responsibilities and the
> scope of this position.
> It also relates to the current "process" discussion with its content as:
> 
> "Term duration:
> 
> The duration of this role is five years after which the exiting Chair
> may choose to place him/herself up for reelection in the pool of
> qualifying candidates.
> "
> 
> I have no objections to the 5 years term.
> But we may need to consider the purpose of the "may" in this sentence,
> "the exiting Chair may choose to place him/herself up for
> reelection...", as we are discussing a process.
> 
> So with this discussion we may have the opportunity to both come up
> with a process for an election and move this document from a Draft
> state to a proper RIPE Document status.
> 
> Where will this discussion take place during the upcoming meeting next week?
> 
> 
> Thank you
> Filiz
> 
> 
> 
> 
> On Tue, Oct 11, 2016 at 5:18 PM, Mirjam Kuehne <mir at ripe.net> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA512
> >
> > Hi all,
> >
> > Some time ago we drafted a function description for a RIPE Chair. Hans
> > Petter now asked me to pass it on to the list for further discussion.
> > Please see the pdf attached. It is also posted here:
> >
> > https://www.ripe.net/participate/ripe/draft-ripe-chair-function-descript
> > ion
> >
> > Kind regards,
> > Mirjam Kuehne
> > RIPE NCC
> >
> >
> > On 11/10/16 11:10, Shane Kerr wrote:  
> >> All,
> >>
> >> Is there a document which actually documents what the RIPE Chair
> >> actually is? Sorry if I missed it, I don't think this exists.
> >> Perhaps such a document would be a good starting point for the
> >> discussion?
> >>
> >> We have a nice web page talking about *who* the chair is:
> >>
> >> https://www.ripe.net/participate/ripe/ripe-chair
> >>
> >> We also have a RIPE Document which describes what the job of a
> >> RIPE working group chairs, RIPE 542:
> >>
> >> https://www.ripe.net/publications/docs/ripe-542
> >>
> >> Somewhat related, we also have a document describing the RIPE
> >> Programme Committee, RIPE 600:
> >>
> >> https://www.ripe.net/publications/docs/ripe-600
> >>
> >> Note that writing down what the RIPE Chair is does not need to be
> >> super detailed, or restrictive. Hopefully it can be done in a page
> >> or two of text.
> >>
> >> Cheers,
> >>
> >> -- Shane
> >>  
> >
> > -----BEGIN PGP SIGNATURE-----
> > Comment: GPGTools - https://gpgtools.org
> >
> > iQEcBAEBCgAGBQJX/QK6AAoJEPXqNN7m+XRf75EH/2ylnfKpoGc3tk0scRSV2ZgG
> > OYBX5dAiD0eYvWV9Clzj5RSLbL91ptgDOgUBIyGfY1bBjc95qRTyPmK3nD2RStuw
> > Mqc7t1I7n3IOldHxJM90NfaUu/YQSuqZshtiBkd9v0qa7ym4YzDKx2NlbreiF8A3
> > Sdc8Zbfo+H5qS2Ryh29SUcbjnrTwlmWe6tx7xXGbZauEL3XOxH8JQUHHU4HarTe9
> > k8RzeTrq6wt4BWvgIyXhMzlPY1vAJBvWQ7TXCS3rLRwFT6wYoKCGhJHD2JYjq47b
> > FBbRUSuN+uGVLbu6dWNmLl2moPj+dLzRhXy89E1cbZalqeaw769vP32nkN8ZGWE=
> > =laGc
> > -----END PGP SIGNATURE-----  
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 163 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ripe.net/ripe/mail/archives/ripe-chair-discuss/attachments/20161021/fbd60750/attachment.sig>