<html><head><meta http-equiv="content-type" content="text/html; charset=us-ascii"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>Dear colleagues,</div><div><br></div><div>I would like to thank the community for reaching consensus on what is an important document for the RIPE community and particularly for RIPE NCC staff, who are now formally recognised as being able to participate in RIPE on an equal footing. This is an important principle for us, and I hope it will further encourage our staff to engage freely and frequently when appropriate with the rest of the community.</div><div><br></div><div>The second principle, noting that staff should take care to disclose their positions when discussing matters relating to community guidance to the RIPE NCC, is also one that we are fully committed to.</div><div><br></div><div>Niall rightly notes that we are planning to review our internal guidelines on staff interaction with the community. I will invite all staff to join me in discussing how we can best interact with the community for its benefit and the benefit of our staff. The Works Council will also play an important role in this process. In the meantime, we published our internal code of conduct[1], section 9 of which contains guidelines on staff engagement externally, and we will adhere to this until we have completed our internal review. I will come back to the community with the outcome of that review.</div><div><br></div><div>Finally, I wish to thank the RIPE Chair Team for their work on this RIPE Document, and especially Niall who steered it through the community process.</div><div><br></div><div>I sincerely look forward to our continued engagement together as a community.</div><div><br></div><div>Kind regards,</div><div>Hans Petter Holen</div><div>RIPE NCC Managing Director, CEO</div><div><br></div><div>[1] https://www.ripe.net/about-us/staff/ripe-ncc-code-of-conduct.pdf</div><div><br></div><div> <div dir="auto" style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br></div></div> </div> <div><br><blockquote type="cite"><div>On 4 Oct 2023, at 15:39, Niall O'Reilly <niall.oreilly@ucd.ie> wrote:</div><br class="Apple-interchange-newline"><div> <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8"> <div><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;"><p dir="auto">Dear Colleagues,</p><p dir="auto">I am glad to declare RIPE community consensus on draft v2 [<a href="https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-ncc-staff-participation-in-the-ripe-community-draft-v2" style="color: #3983C4;">1</a>] of the<br> document on RIPE NCC staff participation in RIPE.</p><p dir="auto">I expect that the text of this draft will be published as a RIPE<br> document in the near future, after final editing to add<br> acknowledgements, check spelling and terminology, and make whatever<br> other minor changes may be needed to prepare it for release.</p><p dir="auto">I should like to add a few remarks.</p><p dir="auto">Last call on this draft was re-opened on 21 July 2023 [<a href="https://www.ripe.net/ripe/mail/archives/ripe-list/2023-July/002967.html" style="color: #3983C4;">2</a>], and closed<br> on 4 September 2023.</p><p dir="auto">During this second last-call period, there were a number of expressions<br> of support, and none of objection, to the two principles enunciated in<br> this draft.</p><p dir="auto">In addition, on 2 August 2023, Andy Davidson maintained [<a href="https://www.ripe.net/ripe/mail/archives/ripe-list/2023-August/002984.html" style="color: #3983C4;">3</a>],</p> <blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><p dir="auto">As a responsible community, it is incumbent upon us to safeguard NCC<br> staff from potential conflicts of interest by defining clear<br> protocols for how such situations are considered and managed when<br> NCC staff participate in RIPE activities with activity plans,<br> budgets, or hiring decisions.</p> </blockquote><p dir="auto">He also asked,</p> <blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"><p dir="auto">Can this be captured in the lovely<br> succinct way that you have approached the first two drafts?</p> </blockquote><p dir="auto">At the time, I replied that I hoped so.</p><p dir="auto">On reflection, I believe that the initiative for addressing Andy's<br> concerns is best left to RIPE NCC management and staff.</p><p dir="auto">Pragmatically, they have well-established internal mechanisms which<br> would likely not run more smoothly if the community were to try to<br> orchestrate them. Diplomatically, the community should avoid<br> telling NCC management and staff what is good for them.</p><p dir="auto">Moreover, I have been made aware that the RIPE NCC is planning to<br> review its internal guidelines on staff interaction with the<br> community, and needs to know the consensus of the community in order<br> to inform that review.</p><p dir="auto">For all these reasons, I believe it is appropriate to declare<br> consensus on this document now, rather than to attempt improving it<br> further.</p><p dir="auto">Finally, I wish to thank everyone who has participated in discussing<br> this draft and its predecessor.</p><p dir="auto">Best regards,</p><p dir="auto">Niall O'Reilly<br> RIPE Vice-Chair</p> <hr style="border: 0; height: 1px; background: #333; background-image: linear-gradient(to right, #ccc, #333, #ccc);"> </div> </div> </div></div></blockquote></div><br></body></html>