- ripe-list - mailman.ripe.net

Re: [ripe-list] Updated Draft RIPE Code of Conduct Published for Community Review
by Hans Petter Holen 21 Apr '21

21 Apr '21

On Mon, 19 Apr 2021 at 19:12, Randy Bush <randy(a)psg.com> wrote: >> The RIPE NCC regularly organizes events for communities which are >> distinct from RIPE. When preparing for such an event, the RIPE NCC >> will ascertain whether the respective community has adopted the >> RIPE Code of Conduct and, if not, also ascertain which Code must >> be applied. my naïve view is that, if the ncc is an organiser, then the coc MUST apply. We strongly believe that all RIPE NCC-organised events should follow the same CoC, and we think this is something the community should be able to agree on. The updated draft provides for this. We understand that it will apply to all RIPE NCC-organised events - including RIPE, MENOG, ENOG, and SEE meetings, as well as things like the Roundtable Meetings, Member Lunches and RIPE NCC Regional Meetings that we organise. Perhaps the CoC TF can look at whether this needs to be made clearer in its draft. Once the community agrees on an updated CoC, the TF will then work to define procedures and how a future CoC Team will handle reports and be constituted. This is where unexpected details or regional differences could become relevant. For example, will members of the CoC Team need to attend every Member Lunch and Regional Meeting, or will an email contact be enough in some cases? Should there be one CoC Team, or would it be better for MENOG, ENOG and SEE to have their own teams with more understanding of local contexts? My understanding is that it was an awareness of these factors that led the TF to include this provision, as well as respecting the autonomy of these communities, as Niall points out. It is my hope and expectation that the outcome of this process should be a single code of conduct that is applied in a more or less uniform way across all of the events that we organise. Regards Hans Petter Holen Managing Director RIPE NCC

2 2

Updated Draft RIPE Code of Conduct Published for Community Review
by Leo Vegoda 21 Apr '21

21 Apr '21

Dear RIPE community, An updated draft RIPE Code of Conduct (CoC) is now published for your review. As this is intended to cover all participation within RIPE, it applies to interactions over the Internet, mailing lists, as well as in-person at RIPE Meetings. You can find the document here: https://www.ripe.net/publications/docs/ripe-documents/other-documents/ripe-… This draft keeps most of the text in v3.0[1], which was developed by the RIPE Diversity TF. It also draws from CoCs that are in use in other communities, including the Python CoC[2]. The biggest change is that the updated draft covers scope and behaviour only. It doesn’t touch on process or the CoC Team – these aspects will be addressed in two separate documents that are still to come. Please review the draft and share any comments on the RIPE Discussion List by Friday, 2 April 2021. We welcome suggested changes, but if you don’t see problems with the draft then statements of support are also helpful. The RIPE Chair Team will evaluate your comments and determine whether there is consensus on this draft or additional work is needed. While we would prefer comments to be shared on the RIPE Discussion List, we recognise that some people might have feedback that they would like to share in private. If you want to provide feedback in private you can contact members of the CoC TF or the RIPE Chair Team directly. Some key changes in this version: - The goal of “a neutral, transparent and open framework for report handling” has been removed and will be covered in the upcoming document that describes process. - The scope is defined as “all participation in RIPE.” - Groups and events with separate governance from RIPE may adopt this CoC but will need to manage their own implementation. - A new section covers how the CoC relates to national law. - A new section lists desired behaviours along with an updated list of unacceptable behaviours. - Both lists are arranged alphabetically, to avoid suggesting a hierarchy. We look forward to reading your thoughts on the current draft. Kind regards, Leo Vegoda On behalf of the RIPE Code of Conduct TF [1] RIPE Meeting Code of Conduct 3.0 - Draft https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-o… [2] Python Community Code of Conduct https://www.python.org/psf/conduct/

23 52

Updating the RIPE Policy Development Process (PDP)
by Mirjam Kuehne 20 Apr '21

20 Apr '21

Dear colleagues, The following two documents have now been published as RIPE documents: Review of the RIPE Appeals Procedure (ripe-760) https://www.ripe.net/publications/docs/ripe-760 Evolution of the RIPE Policy Development Process (ripe-761) https://www.ripe.net/publications/docs/ripe-761 The documents contain a number of recommendations, some of them related to the Policy Development Process (https://www.ripe.net/publications/docs/ripe-710). Please find those recommendations below together with a suggested way forward. For more context and background, please refer to the two documents above. We would like to hear your feedback so that we can then update the PDP document accordingly. In a second mail, we will discuss recommendations that are specifically related to the appeals procedure as currently described in the PDP. Kind regards, Mirjam Kühne & Niall O'Reilly RIPE Chair Team ---- 1. To clarify how the policy development process should be amended. The PDP is a community governance document that describes how policy is made within RIPE. Changes to the PDP are presented on the ripe list and discussed during a RIPE Community Plenary. A consensus call is then issued on the ripe-list by the RIPE Chair. Question to the community: Do you agree to add this to the PDP document? 2. To clarify or omit the identification of the RIPE Chair as "author and owner" of the policy development process. The community owns the PDP. The RIPE Chair is listed as the author of the document and oversees the community consensus process. Question to the community: Do you agree with this statement? 3. To discuss an idea for a policy proposal on the relevant mailing list before it is submitted as a formal policy proposal. Since the discussion phase is now part of the PDP, we recommend to add another step before a formal policy is submitted: It is recommended that an idea for a new policy or a change of an existing policy is sent to the relevant mailing list before it enters the formal PDP. Also, the relevant WG chairs are encouraged to work with the proposer in preparing a policy proposal. Question to the community: Do you agree with this approach?

1 0

NRO NC Nominations Deadline
by Hans Petter Holen 20 Apr '21

20 Apr '21

Dear colleagues, The call for nominations from the RIPE NCC service region to fill one seat on the Number Resource Organization (NRO) Number Council (NC) will close on 23 April 2021. Any individual residing within the RIPE NCC service region is eligible for nomination, except Regional Internet Registry (RIR) staff members. Self-nominations are permitted. The nomination process is available at: https://www.ripe.net/nro-nc-nominations-process-may-2021 Please send your nominations to <nominations(a)ripe.net> by 23:59 UTC on 23 April 2021. All confirmed nominations will be listed on the RIPE NCC website by 26 April 2021. The election for this NRO NC seat will take place during the RIPE 82 meeting that will be held virtually from 17-21 May 2021. All members of the Internet community who are attending the RIPE Meeting except Regional Internet Registry (RIR) staff members may vote in the election. All nominees may submit a written statement in support of their nomination for publication on the RIPE NCC website. Other people can express support for nominated individuals by sending an email to <nominations(a)ripe.net>. Expressions of support will also be published on the RIPE NCC website. To find out more about the NRO NC and the election process, please see: https://www.ripe.net/nro-nc-may-2021 Regards, Hans Petter Holen Managing Director RIPE NCC ------------------- Important Dates ------------------- 23 April 2021: Deadline for NRO NC nominations 26 April 2021: Deadline for all confirmed nominations to be published on the RIPE NCC website 17-21 May 2021: Election to fill NRO NC seat during RIPE 82 21 May 2021: Announce successful candidate in closing plenary of RIPE 82

1 0

New on RIPE Labs: Code of Conduct Task Force - Spring 2021 Update
by Alun Davies 16 Apr '21

16 Apr '21

Dear colleagues, The Code of Conduct Task Force published their draft of an updated RIPE Code of Conduct in March this year. In this article on RIPE Labs, Leo Vegoda looks back at why and how the task force came together, shares key feedback on the draft from the community, and discusses plans for a BoF at RIPE 82 and next stages of the TF’s work: https://labs.ripe.net/author/leo_vegoda/code-of-conduct-task-force-spring-2… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

RIPE Database Requirements Task Force BoF, 5 May 2021
by Bijal Sanghani 15 Apr '21

15 Apr '21

Dear all, The RIPE Database Requirements Task Force (DBTF) will organise its third BoF on Wednesday, 5 May 2021 from 16:00-17:30 (UTC+2) via Zoom. During this BoF, the DBTF will present its latest recommendations and discuss open issues. More information and joining details are available at: https://www.ripe.net/participate/ripe/tf/rdb-requirements-tf/bof-5-may-2021 Kind regards, Bijal on behalf of the DBTF

1 0

RIPE DBTF Feedback
by Bijal Sanghani 14 Apr '21

14 Apr '21

Dear colleagues, I am writing to inform you that the RIPE Database Requirements Task Force (DBTF), is soliciting feedback on our recommendations for; Person Objects Historical Data Legal Address If you are interested or have any feedback on these topics, then please join the conversation on the RIPE Database WG mailing list so that we can keep all feedback and discussions in one place. Kind regards, Bijal on behalf of the DBTF

1 0

RIPE Working Group Chairs Collective Meeting Summary (March 2021)
by Mirjam Kuehne 13 Apr '21

13 Apr '21

Dear colleagues, The RIPE Working Group Chairs met in March to discuss recommendations for possible changes to the RIPE Policy Development Process. We also discussed how the proposed new RIPE Code of Conduct would work in practice and what the role of a WG chair would be in the process. You can find a summary from the meeting here: https://www.ripe.net/participate/ripe/wg/wg-chairs/working-group-chair-coll… Kind Regards, Mirjam Kühne RIPE Chair

7 9

New on RIPE Labs: A Brand New Look at the Best of RIPE Labs
by Alun Davies 12 Apr '21

12 Apr '21

Dear colleagues, We're proud to announce the launch of the new RIPE Labs! We're very happy with the redesign and we hope you'll all agree that the new layout is a big improvement on the old. To get a feel for what's changed, our latest article looks back at some of the great contributions authors have made over the past couple of years so you can enjoy their articles all over again in their fresh new setting. We also cover how to contribute to RIPE Labs and invite readers to give us their feedback. Read more now on the new and improved RIPE Labs: https://labs.ripe.net/author/alun_davies/a-brand-new-look-at-the-best-of-ri… Kind regards, Alun Davies RIPE Labs Editor RIPE NCC

1 0

Register Now for RIPE 82
by RIPE NCC Event Team 12 Apr '21

12 Apr '21

Dear colleagues, RIPE 82 will be held as a virtual meeting and will take place from 17-21 May 2021. You can now register for free at: https://ripe82.ripe.net/attend/register/ ------------- RIPE 82 Conference Platforms ------------- We are pleased to inform you that the RIPE 82 Meeting will use Meetecho as its conference platform and SpatialChat as its virtual networking space. In addition to Meetecho, you will be able to watch the presentations live on the RIPE 82 website and on YouTube. Please note that in both cases, there will be no separate IRC channel or chat functionality. If you would like to participate in the discussions and ask questions, you will have to register for the meeting and join Meetecho. More information on how to participate to the meeting is available on the RIPE 82 website: https://ripe82.ripe.net/attend/how-to-participate/ ------------- Programme ------------- The RIPE 82 Meeting plan uses the CEST time zone (UTC+2): https://ripe82.ripe.net/programme/meeting-plan/ -- Pre-meeting events on Friday, 14 May Keep some time free on the Friday before RIPE 82 begins to participate in these pre-meeting events: - Platform-testing for Meetecho and SpatialChat - Newcomers' Introduction - Newcomers' Social and Mentoring Programme Meet up -- Plenary Sessions The draft plenary programme is online: https://ripe82.ripe.net/programme/meeting-plan/plenary/ BoFs and lightning talk proposals can still be submitted at: https://ripe82.ripe.net/submit-topic/cfp/ -- WG Sessions Each working group has a dedicated session in the RIPE Meeting agenda for presentations on topics relevant to the working group’s agenda. If you want to present in one of the WGs, get in touch with the relevant WG chairs via email: https://ripe82.ripe.net/programme/ripe-wg-chairs/ ------------- RIPE Meeting Mentoring ------------- Experienced RIPE Meeting attendees can help newcomers make the most of their meeting by volunteering to be a mentor. We match mentors with mentees based on interests and areas of expertise. You can sign yourself up to be a mentor or mentee when you register for the meeting. The deadline is *3 May*. Learn more at: https://ripe82.ripe.net/attend/mentoring-programme/ ------------- Call for Sponsors ------------- Supporting a RIPE Meeting through sponsorship gives your organisation fantastic exposure in the global Internet community. Get in touch with the RIPE Meeting team if you are interested in sponsoring RIPE 82: https://ripe82.ripe.net/sponsors/become-a-sponsor/ ---- More information on RIPE 82 can be found at: https://ripe82.ripe.net/ For the latest updates, you can follow us on Twitter at @ripemeeting and by using the hashtag #RIPE82. Best regards, RIPE Meetings Team

1 0