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/[email protected]/
[ripe-list] Last Call for Draft: NRO NC Election Process (v3)
- Previous message (by thread): [ripe-list] Last Call for Draft: NRO NC Election Process (v3)
- Next message (by thread): [ripe-list] Last Call for Draft: NRO NC Election Process (v3)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mirjam Kuehne
mir at zu-hause.nl
Mon Oct 9 09:57:14 CEST 2023
Hi Nurani, Thanks for reviewing the document and for your constructive suggestions throughout the process. Please see some comments below. On 06/10/2023 14:05, Nurani Nimpuno wrote: > HI, > > Thanks for this Mirjam. > > I can’t seem to find the link to the role description, would you mind sharing this? I think this needs to be linked from the election process as candidates need to understand what role they are undertaking as it at times does have a rather high workload (in relation to the election of the ICANN board seats 9 and 10.). As suggested earlier, we created this page that contains general information about the NRO NC including a list of responsibilities: https://www.ripe.net/participate/internet-governance/internet-technical-community/nro/nro-nc The link to the page is listed under References in Appendix A of the document. I'll see how we can make this more visible. > Also, I think that if we agree that voting eligibility should be having attended at least one RIPE meeting in the past, shouldn’t we add this as a very bare minimum criterion for the candidate eligibility as well? (I would in fact say “having attended at least three previous RIPE meetings, but I don’t have strong opinions on the exact number”.) So far I believe the community felt that candidates who don't have the necessary skills and background will mostly likely not receive many votes. But let's see what others say. Kind regards, Mirjam > > Kind regards, > > Nurani > > >> On 6 Oct 2023, at 09:41, Mirjam Kuehne <mir at zu-hause.nl> wrote: >> >> Dear colleagues, >> >> Since version 2 of the Number Resource Organization Number Council (NRO >> NC) Election Document was published [1], we received one suggestion for >> clarification. No other concerns or comments were submitted. >> >> Following this suggestion, we changed “last ” to “previous” in the >> following sentence: >> >> "Have attended (registered and checked-in for) at least one out of the >> previous eight RIPE Meetings." >> >> This is therefore a LAST CALL for comments for the final version of this >> document [2], to expire on Monday, 23 October at 06:00 UTC. >> >> At the same time, I would like to draw your attention to the call for >> nominations to fill two seats on the NRO NC that is still open until 30 >> October 2023. >> >> Kind regards, >> Mirjam >> ===== >> >> [1] Announcing Updated NRO NC Election Process (v2) >> https://www.ripe.net/ripe/mail/archives/ripe-list/2023-September/002998.html >> >> >> [2] Updated NRO NC Election Process (v3) >> https://www.ripe.net/publications/docs/ripe-documents/other-documents/draft-nro-nc-election-process-v3 >> >> >> [3] NRO NC Nominations 2023: Call to Fill Two Seats >> https://www.ripe.net/ripe/mail/archives/ripe-list/2023-September/003001.html >> >> >> >> -- >> >> To unsubscribe from this mailing list, get a password reminder, or change your subscription options, please visit: https://mailman.ripe.net/
- Previous message (by thread): [ripe-list] Last Call for Draft: NRO NC Election Process (v3)
- Next message (by thread): [ripe-list] Last Call for Draft: NRO NC Election Process (v3)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]