April 2022 - coc-tf - mailman.ripe.net

CoC Process and Next Steps
by Leo Vegoda 06 Apr '22

06 Apr '22

Hi, Antony, Kjerstin, and I met earlier today. These are some lightweight notes. Kjerstin will provide proper minutes later. We reviewed the updated draft process. The key change in this is that only significant breaches of the Code of Conduct will be reported to the RIPE Chair Team and the RIPE NCC before actions are taken. We made some changes to the section dealing with data during the meeting. We were advised that we cannot just make a statement that the record system will comply with the law. We need to state how long the RIPE NCC will keep records for. The update we made recognises minor and major breaches of the Code of Conduct. The records system will always keep data that does not identify individuals to allow trend analysis. It will keep information identifying an individual for a minor breach for 12 months. It will keep information identifying an individual for a major breach for 24 months. If a person is permanently barred from attending RIPE events or posting to RIPE lists, it will need to keep information on them indefinitely. Otherwise, that action could not be implemented. We intend to publish the updated draft as soon as possible. We would like the RIPE NCC's legal team to review it before publishing but if that is not possible, we plan to publish next week. We have a blog post drafted. It presents a fairly concise summary, asks two questions, and asks the community to provide any feedback they have. We'd like to have a three week comment period on the draft. We agreed that it made sense to propose a Code of Conduct BoF for RIPE 84. The focus in the proposal to the RIPE Programme Committee will be: 1. Present the proposed Code of Conduct Team recruitment process, based on the one used for the Arbiters 2. Present the Code of Conduct Team training plans and estimated time commitment 3. Discussion - which could include discussion on the process document if significant issues are raised on the RIPE Discussion List I will draft a proposal for the BoF and circulate it. Kind regards, Leo

4 8

Draft agenda for this week's meeting
by Leo Vegoda 05 Apr '22

05 Apr '22

Hi, Here is a draft agenda for Thursday's meeting. The goal is to make final changes to the document and blog post asking questions. Regards, Leo Title Who What Time Outcome Minutes TF Review the draft minutes of the last meeting. Identify any changes. Finalise. 5 mins Minutes Agenda TF Review agenda and adjust as needed. 5 mins Agenda Actions All Review status of actions from the previous meeting: - (Ongoing) TF to think about how the CoC Team and the WGc Chairs would work together to manage discussions on mailing lists. Including tools, e.g. Mattermost channel - (Ongoing) TF to think about the appropriate level of process to allow further improvements to the CoC. - Athina to review the language on appeals and propose an amendment if needed. - RIPE NCC to update the working draft so it makes consistent use of simple language. - Leo to draft a blog post 5 mins Status Record retention All Decide on periods for minor/major breaches 10 mins Decision Blog post All Adjust blog post to include question about record retention 10 mins Document BoF All Adjust BoF proposal 10 mins Decision AOB All Any other business 5 mins - Actions NCC Review actions agreed during the meeting 5 mins Action list

1 0

Updated Process Document (v5)
by Antony Gollan 03 Apr '22

03 Apr '22

Dear TF members, I've got an updated v5 of the Process Document here: https://docs.google.com/document/d/1MSW2d-dEmZT8KyczTGnEo2Q8Uw3j-dex3I6BbTS… There is one hiccup. Before we publish, we will need to be a little more specific under "6. Evaluation is Recorded" in terms of how long we will store personal data for. After talking with Athina, we thought it might be best for the TF to propose some time frames and reasons on the call. Legal can then check if this is works and we should be able to develop a paragraph of legalese to cover any GDPR-related aspects in pretty short order. Cheers Ant

2 1

Draft proposal for Code of Conduct BoF at RIPE 84
by Leo Vegoda 01 Apr '22

01 Apr '22

Hi, I have drafted a proposal for a Code of Conduct BoF at RIPE 84 in Berlin. I'd like to focus it on recruiting volunteers for the Code of Conduct Team. That means explaining the recruitment process, the training, anticipated time commitment etc... We could change direction if the feedback to draft process document makes that necessary. What needs to change in this draft? Thanks, Leo 8<----- START DRAFT ----->8 This BoF will follow the discussion on the draft Code of Conduct Process. The precise design of the BoF will depend on the community's feedback on the draft. We plan to present three things: 1. A summary of the discussion and decisions made based on it. 2. The proposed recruitment process for the Code of Conduct Team, based on the RIPE NCC Arbiters process. 3. The planned training for the team. We'll explain: - The options evaluated - The organisation we'd like to use, and - The time commitment. The session will conclude with a discussion that will guide the TF's next steps. 8<----- END DRAFT ----->8

2 2