- coc-tf - mailman.ripe.net

Draft agenda for upcoming meeting
by Leo Vegoda 25 Apr '21

25 Apr '21

Hi, We have a meeting coming up this Friday, 30 April. Here's a draft agenda for the meeting. Please suggest changes if you need any. Thanks, Leo Title Who What Time Outcome Minutes TF Review the draft minutes of the last meeting. Identify any changes. Finalize. 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) RIPE NCC to review reporting requirements to inform a process of improvements to the CoC (likely tooling and legal analysis). - (Ongoing) TF to think about how the CoC Team and the WG Chairs would work together to manage discussions on mailing lists. - (Ongoing) TF to think about the appropriate level of process to allow further improvements to the CoC. - Leo to draft slides for BoF (see agenda item below) - TF to review Mailing List Guidelines for RIPE Working Group Chairs <https://www.ripe.net/participate/ripe/wg/wg-chairs/mailing-list-guidelines-…> - TF to think about practical ways to help WG Chairs and CoC Team members collaborate to effectively support positive discussion on mailing lists, e.g. a shared Mattermost channel 10 mins Status Guidelines collaboration tools All Share thoughts on the current text and what is needed from tools. - Are the current guidelines good? - What features are needed? 15 mins Discuss BoF All Discuss draft BoF structure and adjust as needed 15 mins Refine design AOB All Any other business 5 mins - Actions NCC Review actions agreed during the meeting 5 mins Action list

1 0

Potential Considerations & Language
by Brian Nisbet 23 Apr '21

23 Apr '21

Folks, As discussed, some thoughts and language in regard to people reacting to potential CoC breaches that could in themselves, be interpreted, in bad faith, as CoC breaches. An example of this would be Person A being told to "feic off" or "get in the sea" or similar by Person B in response to something racist, sexist, demeaning etc. that Person A said to Person B. The Geek Feminist CoC - https://geekfeminismdotorg.wordpress.com/about/code-of-conduct/- uses: The Geek Feminism community prioritizes marginalized people’s safety over privileged people’s comfort. The Geek Feminism Anti-Abuse Team will not act on complaints regarding: - ‘Reverse’ -isms, including ‘reverse racism,’ ‘reverse sexism,’ and ‘cisphobia’ (because these things don’t exist) - Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you.” - Refusal to explain or debate social justice concepts - Communicating in a ‘tone’ you don’t find congenial - Criticizing racist, sexist, cissexist, or otherwise oppressive behaviour or assumptions Food for thought. Thanks, Brian Brian Nisbet (he/him) Service Operations Manager HEAnet CLG, Ireland's National Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

1 0

Please get rid of the RIPE Diversity TF and rewrite the CoC, (stop being political)
by Rolf Stenholm 22 Apr '21

22 Apr '21

I have noticed that RIPE NCC for some reason has become political recently I would like to express my opinion that I want RIP NCC to be unpolitical and not create political task force such as "RIPE Diversity TF" or adopt political renaming of words because of politics. The object of "RIPE Diversity TF" follows socialist political programs (such as diversity), ideas that caused the genocide of the people of the baltic states which are neighbours to our nation. It cannot be right that RIPE NCC adopts ideas that killed a third of the population of the baltic states. I email you to strongly protest your adoption of socialist politics in the CoC and ask you to get rid of these idea from the organisation and adopt an apolitical stance. Regards Rolf Stenholm

1 0

Draft agenda for upcoming meeting
by Leo Vegoda 20 Apr '21

20 Apr '21

Dear TF, I have drafted an agenda for our meeting this Friday. My apologies for not sharing this earlier. I have tried to devote a lot of time to discussing the feedback we got from the community both in the initial comment period and since. Rather than list every single item of feedback I have pulled out two significant issues to discuss. If we have time we can talk about more but I want to make sure that we give ourselves time to think carefully about these issues before moving on to new issues. Thanks, Leo Title Who What Time Outcome Minutes TF Review the draft minutes of previous meetings. Identify any changes. Finalize. 5 mins Minutes Agenda TF Review agenda and adjust as needed. 5 mins Agenda Actions All Review status of actions from the previous meeting: - RIPE NCC to review reporting requirements to inform a process of improvements to the CoC (likely tooling and legal analysis). - TF to think about how the CoC Team and the WG Chairs would work together to manage discussions on mailing lists. - TF to think about the appropriate level of process to allow further improvements to the CoC. - TF to think about their schedules between April/June and consider changing call times. This can be coordinated via the ML to allow a new schedule before April. 10 mins Status Feedback All Discuss feedback from the community. Look at issues including: - Tension between calls for additional details in lists and calls for less detail with greater focus on general guiding principles. - CoC TF and ENOG, MENOG, and SEE. 30 mins Discussion & decision if needed AOB All Any other business 5 mins - Actions NCC Review actions agreed during the meeting 5 mins Action list

1 1

Status update: blog post and socialising the draft CoC with ENOG, MENOG and SEE
by Leo Vegoda 16 Apr '21

16 Apr '21

Hi, A quick update to let you know that after a discussion with Mirjam, we have published the blog post earlier than previously planned and it is now at the top of https://labs.ripe.net. Mirjam will make sure that ENOG, MENOG, and SEE are alerted to the blog post so that they can decide whether they want to adopt the CoC when it is finalised. Kind regards, Leo

3 4

Meeting schedule
by Leo Vegoda 15 Apr '21

15 Apr '21

Hi, We have a meeting scheduled for Friday, 16 April but Denesh and I are unable to attend on that day. Would people prefer to reschedule that meeting to Friday, 23 April (St George's Day in England) and resume the normal cadence the following Friday? Alternatively, we could skip a meeting or we could keep the cadence starting on Friday, 23 April? In other news, I have drafted the blog post and am working with Alun to get it posted. I have included a paragraph about the BoF at RIPE 82 but that is contingent on the PC's decision, so publication will not happen until after the PC has decided on BoFs. Kind regards, Leo

2 3

Heads up: CoC TF blog post on RIPE Labs
by Leo Vegoda 07 Apr '21

07 Apr '21

Hi, Mirjam and I have discussed publishing a blog post on RIPE Labs about the CoC TF. The goal is to do at least two things. Firstly, we should tell the story, going back to RIPE 80, of how the CoC TF was discussed and chartered. Using the medium of a blog we can visualise a timeline, to help tell the story to people who dislike long screeds of text. Secondly, we can discuss the draft we recently shared for review, the feedback we got, and the changes we plan to make as a result. We can use the same elements in a different style at the BoF, should we get onto the agenda for RIPE 82. I will get started with drafting some text. But no-one should be their own editor. I'd be grateful for help reviewing the text and making the graphics. Kind regards, Leo

2 1

Fwd: [Community-Discuss] Call for comments is Open on the AFRINIC Community Code of Conduct
by Leo Vegoda 31 Mar '21

31 Mar '21

FYI ---------- Forwarded message --------- From: AFRINIC Communication <comms(a)afrinic.net> Date: Wed, Mar 31, 2021 at 5:56 AM Subject: [Community-Discuss] Call for comments is Open on the AFRINIC Community Code of Conduct To: General Discussions of AFRINIC <community-discuss(a)afrinic.net> [Sent on behalf of the AFRINIC Governance Committee] [Version en français au bas] Dear community, On 31 August 2020, the Chief Executive Officer of AFRINIC pursuant to Article 3.1.7 of the Governance Committee’s Terms of Reference requested the committee’s assistance as follows: 1. Examine the text of the code of conduct to determine if updates are needed; 2. Consider if there are situations that may arise which are not adequately covered in the current text; 3. Advise on the process through which updates to the text can be made, discussed with the members and community, and finally approved; 4. Make such other recommendations as the Governance Committee may deem appropriate. https://afrinic.net/govcom/request <https://afrinic.net/govcom/request> In furtherance of the above, the Governance Committee has at its meeting held on 30 March 2021 decided to engage in a consultation process with its stakeholders which shall be opened from 01 April 2021 to 30 April 2021. You are hereby invited to share your valuable views and comments in respect of the above at govcom(a)afrinic.net <mailto:govcom@afrinic.net>. You may also consult the provisions of AFRINIC’s existing Code of Conduct at https://afrinic.net/code <https://afrinic.net/code>. The Governance Committee wishes to thank its stakeholders in advance for their valuable contribution and looks forward to continuous beneficial engagement. Mr Daniel Nanghaka Chair, Governance Committee ……………………………………………………………………. Cher communauté, Le 31 août 2020, le Directeur général d'AFRINIC, conformément à l'article 3.1.7 des termes de référence du Comité de gouvernance, a demandé l'assistance du comité comme suit : 1. Examiner le texte du code de conduite pour déterminer si des mises à jour sont nécessaires 2. Examiner s'il existe des situations susceptibles de se produire qui ne sont pas couvertes de manière adéquate par le texte actuel ; 3. Donner des conseils sur le processus par lequel les mises à jour du texte peuvent être faites, discutées avec les membres et la communauté, et finalement approuvées. 4. Faire toute autre recommandation que le comité de gouvernance peut juger comme étant appropriée. https://afrinic.net/govcom/request <https://afrinic.net/govcom/request> Dans le cadre de ce qui précède, le Comité de gouvernance a décidé, lors de sa réunion du 30 mars 2021, d'engager un processus de consultation avec ses parties prenantes qui sera ouvert du 1er avril 2021 au 30 avril 2021. Vous êtes par la présente invités à partager vos points de vue et commentaires sur ce qui précède à l'adresse govcom(a)afrinic.net. <mailto:govcom@afrinic.net>. Vous pouvez également consulter les dispositions du code de conduite existant d'AFRINIC à l'adresse https://afrinic.net/code <https://afrinic.net/code>. Le Comité de gouvernance souhaite remercier à l'avance ses parties prenantes pour leur précieuse contribution et se réjouit d'un engagement bénéfique continu. M. Daniel Nanghaka Président du Comité de gouvernance _______________________________________________ Community-Discuss mailing list Community-Discuss(a)afrinic.net https://lists.afrinic.net/mailman/listinfo/community-discuss

1 0

This Friday's Meeting
by Brian Nisbet 30 Mar '21

30 Mar '21

Leo, all, I won't be available this Friday, apologies. As I flagged it's a holiday for HEAnet (it's complicated from an Irish point of view, but we're closed) and some things have come up that mean I won't be able to join at that time. Brian Brian Nisbet (he/him) Service Operations Manager HEAnet CLG, Ireland's National Education and Research Network 1st Floor, 5 George's Dock, IFSC, Dublin D01 X8N7, Ireland +35316609040 brian.nisbet(a)heanet.ie www.heanet.ie Registered in Ireland, No. 275301. CRA No. 20036270

2 1

Sharing Summary of Comments with RIPE Discussion List
by Leo Vegoda 30 Mar '21

30 Mar '21

Hi, Several people have provided comments on the draft CoC but not indicated whether they think the current version is good enough, or if a specific change is required. I plan to post the table of comments on Monday and request people who have question marks next to their names to either specify that what we have is good enough or identify the change(s) they want in the document. That gives people about five business days to respond with specific answers. Kind regards, Leo

2 1