<!DOCTYPE html> <html> <head> <meta http-equiv="Content-Type" content="text/xhtml; charset=utf-8"> </head> <body><div style="font-family: sans-serif;"><div class="markdown" style="white-space: normal;"> Dear Colleagues, 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 document on RIPE NCC staff participation in RIPE. I expect that the text of this draft will be published as a RIPE document in the near future, after final editing to add acknowledgements, check spelling and terminology, and make whatever other minor changes may be needed to prepare it for release. I should like to add a few remarks. 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 on 4 September 2023. During this second last-call period, there were a number of expressions of support, and none of objection, to the two principles enunciated in this draft. 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>], <blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"> As a responsible community, it is incumbent upon us to safeguard NCC staff from potential conflicts of interest by defining clear protocols for how such situations are considered and managed when NCC staff participate in RIPE activities with activity plans, budgets, or hiring decisions. </blockquote> He also asked, <blockquote style="margin: 0 0 5px; padding-left: 5px; border-left: 2px solid #777777; color: #777777;"> Can this be captured in the lovely succinct way that you have approached the first two drafts? </blockquote> At the time, I replied that I hoped so. On reflection, I believe that the initiative for addressing Andy's concerns is best left to RIPE NCC management and staff. Pragmatically, they have well-established internal mechanisms which would likely not run more smoothly if the community were to try to orchestrate them. Diplomatically, the community should avoid telling NCC management and staff what is good for them. Moreover, I have been made aware that the RIPE NCC is planning to review its internal guidelines on staff interaction with the community, and needs to know the consensus of the community in order to inform that review. For all these reasons, I believe it is appropriate to declare consensus on this document now, rather than to attempt improving it further. Finally, I wish to thank everyone who has participated in discussing this draft and its predecessor. Best regards, Niall O'Reilly RIPE Vice-Chair <hr style="border: 0; height: 1px; background: #333; background-image: linear-gradient(to right, #ccc, #333, #ccc);"> </div> </div> </body> </html>