[ripe-chair-discuss] Status of RIPE Chair discussion?
Daniel Karrenberg daniel.karrenberg at ripe.net
Fri May 19 11:06:29 CEST 2017
On 17.05.17 10:33 , Shane Kerr wrote: > All, > > Another RIPE meeting has come and gone, but I don't remember any > discussion about the missing RIPE Chair stuff - either the job > description or appointment procedure. > > Honestly I'm not sure what to do. > > While there does not seem to be a lot of enthusiasm for this work, it > seems like the kind of thing that should move forward before it is > needed. > > Perhaps we just need to wait for the accountability task force to > remind us that we don't have these things? Or do we need to declare the > RIPE Chair list a task force so that Daniel will insist that we have a > deadline? ;) Shane, there is no rush with this. [My insistence on an end-date in the other discussion is not intended to expedite that work either, but rather to avoid creating a working group in the disguise of a task force.] I know that Hans-Peter is working on it and we should let him take his time. Of course we can discuss here and inform his work, and we should! Personally I feel that the discussion so far has been going straight into detailed and overly prescriptive 'job descriptions' and 'procedures'. We should start from our tradition of simple pragmatism and only add more procedure when we are very sure that it is necessary. Besides being the RIPE style it would also be in honor of Rob's legacy to us. In this vain I have participated in a number of community discussions in Budapest and during the last few days. On that, admittedly non representative, basis let me offer this personal proposal as a basis for our discussion on this list: ------ ripe-xxx: The RIPE Chair Scope: This document describes the position of RIPE Chair Introduction Traditionally the main responsibility of the RIPE Chair is to ensure the proper functioning of RIPE. Traditionally the RIPE Chair has little formal power and relies on personal authority, credibility and a firm anchoring in the community. 1. Job Description Doing the sort of things the RIPE Chair usually does while maintaining an open and public channel of communication with the RIPE community. Other RIPE documents may describe specific tasks of the RIPE chair. 2. Continuity The RIPE chair may appoint and dismiss a vice chair. The RIPE chair may delegate some of their tasks to the vice chair. In the event that the RIPE chair is unable to perform their tasks for an extended period of time the vice chair may assume all duties of the RIPE chair after consulting the community. 3. Selection Usually the RIPE chair and the vice chair swap positions not earlier than during the fifth year and not later than during the seventh year of service of the RIPE chair. Usually the previous RIPE chair resigns from the vice chair position about one year later. -------- Rationale: 1. Being overly specific here is bad because it provides a huge target surface for disruptive discussions. Also it may be slightly inconsistent with other RIPE docments such as the "Working Group Chair Job Description and Procedures". Lets define these tasks only in one place. 2. I still hear quite some support for trusting the chair with appointing their successor. The vice-chair way will allow the community to form an opinion about the person as they perform some duties and before the trigger is pulled. 3. This addresses concerns about the chair clinging to his seat while keeping suitable flexibility. It also re-inforces continuity. Can we continue discussion with specific proposals to amend this language or are there still those who dismiss it out-of-hand? Specifically: if you have different ideas about the selection, propose language that includes a clear definition of who does what, specifically the electorate should you propose elections. Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 801 bytes Desc: OpenPGP digital signature URL: <https://lists.ripe.net/ripe/mail/archives/ripe-chair-discuss/attachments/20170519/1ee5379d/attachment.sig>