<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"> P {margin-top:0;margin-bottom:0;} </style>
</head>
<body dir="ltr">
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Nick,</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
You believe the process needs to be paused. I do not agree.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
As I and others have said yes, there are things that need to be addressed and unquestionably improved, but that was always going to happen. And I acknowledge that it will be five years before there is another run of the process, so it's not like there won't
be a long period where the decisions made are in effect, but it is still the first time.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
And honestly, you say there isn't a problem with the process or document or people, then go on to say there is a problem with at least one, if not more, of them.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I think it's clear that, in future the involvement of NCC staff in the NomCom (other than agreed secretariat roles) should be severely limited (ie I think Daniel should occupy the non-voting ex-Chair position for the next run, and then that's it) and there
should be consideration given to limits or grace periods or the like where someone has been working for the NCC or on the Exec Board. </div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
In regards to payment, perhaps the simplest option there is to make it clear that at least for this 5 year period there will be no remuneration and that, if it is absolutely decided to go down this route, it's taken as a priority to figure out those details
long before a new call for nominations goes out? I mean, I'm not a huge fan of the idea, in no small part for some of the governance & separation issues that have been discussed, but now is not the time for that debate.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Are there improvements that can be made? Yes, I haven't seen anyone disagree with that, but I stand by the statement I made elsewhere in this thread. I don't think the issues raised are big enough to pause this or to need to change things. I'm not being glib
here, I've thought a lot about the points you and others have raised, but this specific part of the RIPE Community is happy that the process is suitable independent of the NCC.</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
I am very much trying to avoid falling into the sunk cost fallacy, albeit with any mental exercise it is always hardest to audit oneself. However we worked on the process, everyone is agreeing the candidates are a good bunch, and I have a genuine fear that
if we do attempt to repair the plane mid-flight, then we'll set a precedent of being able to reach this point again and find something else to say "No" to, which should be fixed in the normal iteration cycle.</div>
<div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, Helvetica, sans-serif; background-color: rgb(255, 255, 255); display: inline !important">There is an element of risk in continuing, just as there was in the first chair appointment, in the succession, in all of this. But both
the safeguards (the recall etc) that are in the process and a greatly heightened awareness in the Community of the role of the Chair persuade me that while things could be better that they are not bad enough to need to take the pauses or steps you outline.</span><br>
</div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, Helvetica, sans-serif; background-color: rgb(255, 255, 255); display: inline !important"><br>
</span></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, Helvetica, sans-serif; background-color: rgb(255, 255, 255); display: inline !important">I continue to support the NomCom and the continuation of this process to a speedy conclusion.</span></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, Helvetica, sans-serif; background-color: rgb(255, 255, 255); display: inline !important"><br>
</span></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<span style="font-family: Calibri, Helvetica, sans-serif; background-color: rgb(255, 255, 255); display: inline !important">Brian</span></div>
<div style="font-family: Calibri, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div id="Signature">
<meta content="text/html; charset=UTF-8">
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p style="margin-top: 0px; margin-bottom: 0px;">Brian Nisbet </p>
<p style="margin-top: 0px; margin-bottom: 0px;">Service Operations Manager</p>
<p style="margin-top: 0px; margin-bottom: 0px;">HEAnet CLG, Ireland's National Education and Research Network</p>
<p style="margin-top: 0px; margin-bottom: 0px;">1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland</p>
<p style="margin-top: 0px; margin-bottom: 0px;">+35316609040 brian.nisbet@heanet.ie www.heanet.ie</p>
<p style="margin-top: 0px; margin-bottom: 0px;">Registered in Ireland, No. 275301. CRA No. 20036270 </p>
</div>
</div>
</div>
<div id="appendonsend"></div>
<div style="font-family:Calibri,Helvetica,sans-serif; font-size:12pt; color:rgb(0,0,0)">
<br>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> ripe-list <ripe-list-bounces@ripe.net> on behalf of Nick Hilliard <nick@foobar.org><br>
<b>Sent:</b> Wednesday 27 May 2020 12:55<br>
<b>To:</b> Gert Doering <gert@space.net><br>
<b>Cc:</b> Jim Reid <jim@rfc1035.com>; Andy Davidson <andy@nosignal.org>; RIPE list <ripe-list@ripe.net><br>
<b>Subject:</b> Re: [ripe-list] The NomCom Requests your Support</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">CAUTION[External]: This email originated from outside of the organisation. Do not click on links or open the attachments unless you recognise the sender and know the content is safe.<br>
<br>
<br>
Gert Doering wrote on 26/05/2020 07:20:<br>
> We have a document that tells us what to do. We do that.<br>
><br>
> In the middle of the road, concerns are voiced that the document is not<br>
> good enough - which might be a valid statement or not, but how should it<br>
> affect the current process, given the simultaneously expressed support for<br>
> all the persons involved?<br>
<br>
The problem is not with the process, or the document, and it is<br>
particularly not with the people involved.<br>
<br>
The problem is with the roles that some of the people involved in this<br>
process hold within the RIPE NCC, and the relationship between those<br>
roles. Specifically, the chair of the nomcom and one of the RIPE chair<br>
candidates are NCC employees who report to the RIPE NCC MD, who is also<br>
ad-interim RIPE Chair.<br>
<br>
We have a bottom-line expectation that the RIPE Chair is independent of<br>
the RIPE NCC, and this position has been expressed unequivocally by the<br>
nomcom.<br>
<br>
It is not tenable to hold this expectation and at the same time for the<br>
NomCom to be chaired by a RIPE NCC staff member, while one of the<br>
candidates is also a RIPE NCC staff member, and where the current RIPE<br>
Chair is the RIPE NCC MD.<br>
<br>
This situation was further complicated mid-process by the announcement<br>
that the RIPE Chair position would be funded by the RIPE NCC, thereby<br>
raising further questions about the ability of the RIPE Chair to<br>
maintain independence from the RIPE NCC.<br>
<br>
The timing of this announcement was also difficult, as it happened after<br>
the call for candidates was ended: this has likely cut out other people<br>
who may have been interested in the position but who could not afford to<br>
apply. The reality is that most people are simply not in a position to<br>
work on a free-gratis basis for several years at a time.<br>
<br>
If the NomCom follows through on the current trajectory, it will be<br>
difficult to defend against claims that the selection process and the<br>
resulting candidate were free from undue influence from the RIPE NCC.<br>
This will compromise the process, and the RIPE chair, and will raise<br>
questions about the RIPE Community's ability to govern itself. This<br>
would be unfortunate and unnecessary.<br>
<br>
As Erik Bais noted in a separate email, no-one is suggesting blowing up<br>
or restarting the nomcom or the process. I think generally people<br>
recognise and are sympathetic to the fact that this is a difficult,<br>
awkward and delicate situation for all, and particularly for the<br>
candidates. And also that it's a situation where external factors<br>
played a substantial part in forming.<br>
<br>
For the moment, the process needs to be paused.<br>
<br>
To move it forward:<br>
<br>
1. if the positions of RIPE Chair and vice-Chair are to be paid, then<br>
the details of this need to be clarified, and if possible finalised, as<br>
soon as possible. Given that this is a fundamental shift in the<br>
position spec, there will either need to be a new call for applicants or<br>
a pretty clear justification about why this is not possible. As Gordon<br>
Lennox noted, sunk costs are not an adequate explanation.<br>
<br>
2. The nomcom needs to consider whether people who are currently or have<br>
recently been working at the RIPE NCC at any level should be subject to<br>
timeout / grace periods to protect both the candidates and the position<br>
from suggestions of revolving doors. There's plenty of precedent and<br>
experience in this area of governance.<br>
<br>
3. the RIPE community needs to understand whether the NomCom can<br>
continue to assert that the process is independent of the RIPE NCC given<br>
not just the individual impact of the issues raised, but also the<br>
cumulative impact of these issues.<br>
<br>
These are not easy questions to answer, or to remedy when they've been<br>
answered.<br>
<br>
Nick<br>
<br>
</div>
</span></font></div>
</body>
</html>