This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-list@ripe.net/
[ripe-list] Updated NRO NC Election Process - Please review
- Previous message (by thread): [ripe-list] New on RIPE Labs: Pushing the Needle Forward - A Community Engagement Quarterly Report
- Next message (by thread): [ripe-list] Rob Blokzijl Foundation: Call for Award Committee 2023
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nurani Nimpuno
nurani at nimblebits.net
Tue May 2 11:53:09 CEST 2023
Hi, Thanks for this. I have two comments. One on the actual description of the role, and one of the selection process. Role Description As someone who has served on the NRO NC, I think it would be helpful to have a clear description of what the role actually entails and the workload associated with the role. This is vital for transparency, in particular for volunteer positions. Clear role descriptions make it easier for those who may not be in the inner circle in a community to feel encouraged to step forward and volunteer. Personally, I only stepped forward after having done some pretty significant research and quizzing those already in the role, to ensure that I was the right fit and that I could commit the time. If we want more people to step forward and volunteer, it is key to be clear about what we are asking from them. Imo it needs to clear that whoever serves on the NRO NC is expected to (among other things): - Actively participate in all NRO NC teleconferences (monthly) and in-person meetings (usually only per year, at one of the ICANN meetings) - Actively participate in all IANA RC teleconferences - Attend at least one ICANN meeting per year - Attend (in-person or remotely) all RIPE meetings - Stay abreast with policy developments in the RIPE region - Keep the RIPE community informed of any relevant NRO NC/ ASO / ICANN developments There is also some non-trivial workload associated with the Seat 9 and 10 selection process for the ICANN board, in which the NRO NC members are expected to actively drive. It could be helpful to provide a little more information about what this process actually entails. (There is an initial selection process, there is an interview process etc. A subsection of the NRO NC is driving the process, but as a member of the NRO NC you are expected to participate and gather enough information about each candidate to contribute with your evaluation.) As the ICANN board seats are rather prominent appointments and it involves some rather sensitive information, I also think it would be comme-il-faut to have some sort of Conflict of Interest and Confidentiality policy for NRO NC members to sign and adhere to, (particularly in regards to the ICANN board selection). Voting Eligibility I find the current eligibility rather weak (register for the meeting), especially given some of the developments we have seen in other RIR communities with attempts to stack elections. This process may have worked in the earlier days when there was not much focus on these roles, but it is very easy to manipulate this process if someone has bad intentions. I don’t have a great suggestion and there is no perfect process, but I think the APNIC one is at least an attempt to make a better process (https://www.apnic.net/community/participate/elections/nro-elections/nro-voting/). In essence to be either: 1. APNIC member or 2. Registered for the current meeting, plus at least one of the last 8 meetings My 2cts. Thanks and kind regards, Nurani Nimpuno > On 29 Apr 2023, at 12:11, Dmitry Kohmanyuk via ripe-list <ripe-list at ripe.net> wrote: > > On 2023-04-29, at 12:12, Leo Vegoda <leo at vegoda.org <mailto:leo at vegoda.org>> wrote: >> >> Hi, >> >> It all looks pretty reasonable, so a +1 from me. >> >> It might be helpful to place the explanation of what the NRO NC does >> at the top of the document as that is the "why do we care" bit. At the >> moment, that follows the scope and some history. >> > > As a former member of NRO NC, I appreciate clarity that comes with new document. Perhaps we should remind of new nomination procedure before next NC election, too? > >>> On Fri, 28 Apr 2023 at 03:01, Mirjam Kuehne <mir at zu-hause.nl> wrote: >>> >>> Hi, >>> >>>> On 28/04/2023 09:14, Mirjam Kuehne wrote: >>>> Dear colleagues, >>>> >>>> As promised, we reviewed and updated the processes related to the >>>> election of representatives from the RIPE community to the Number >>>> Resource Organization (NRO) Numbering Council (NC). The draft document >>>> is now available online for your review: >>>> >>>> https://www.ripe.net/publications/docs/ripe-documents/other-documents/nro-nc-election-process/ >>>> >>>> >>>> If you have any comments, questions, suggestions, please send them to >>>> this list or to me directly before 19 May 2023. >>>> >>> >>> I realised I could have provided some more context here: The current >>> process was developed over 20 years ago and is fairly high-level and >>> leaves a lot of room for interpretation: >>> https://www.ripe.net/participate/ripe/address-council-election-procedure >>> >>> This was recognised and discussed by the community, and the RIPE Chair >>> Team together with the RIPE NCC took on the task to review this >>> procedure. In this new draft document we describe a more detailed >>> process, including candidate and voter eligibility, term limits and the >>> election process itself. >>> >>> Kind regards, >>> Mirjam Kühne >>> >>> >>> -- >>> >>> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ >> >> -- >> >> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ > > > -- > > To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/ <https://mailman.ripe.net/> -------------- next part -------------- An HTML attachment was scrubbed... URL: </ripe/mail/archives/ripe-list/attachments/20230502/4cbbbf75/attachment.html>
- Previous message (by thread): [ripe-list] New on RIPE Labs: Pushing the Needle Forward - A Community Engagement Quarterly Report
- Next message (by thread): [ripe-list] Rob Blokzijl Foundation: Call for Award Committee 2023
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]