You are here: Home > Participate > Join a Discussion > RIPE Forum
RIPE Forum v1.4.1

RIPE Diversity

Threaded
Collapse

[diversity] Some examples from other communities about the procedures of the CoC-Teams

User Image

Vesna Manojlovic

2021-05-18 18:12:43 CET

RIPE NCC staff member

Here are some examples:

Cultural Catalyst Lab (attached)

TechInc hackerspace
https://wiki.techinc.nl/Dispute_Procedure

IETF
(please find a link yourself)

CCC
(please find a link yourself)

Another kind of example: Debian
https://people.debian.org/~enrico/dcg/ch04s07.html#meta-links-cr

And let's look at all the examples provided on this list, mostly by
Sasha Romijn.

Vesna




User Image

Brian Nisbet

2021-05-18 18:25:50 CET

Thanks Vesna, I've forwarded this on to the coc-tf mailing list now.

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 _at_ heanet _dot_ ie www.heanet.ie

Registered in Ireland, No. 275301. CRA No. 20036270

________________________________
From: diversity <diversity-bounces _at_ ripe _dot_ net> on behalf of Vesna Manojlovic <BECHA _at_ ripe _dot_ net>
Sent: Tuesday 18 May 2021 17:12
To: diversity _at_ ripe _dot_ net <diversity _at_ ripe _dot_ net>
Subject: [diversity] Some examples from other communities about the procedures of the CoC-Teams

CAUTION[External]: This email originated from outside of the organisation. Do not click on links or open the attachments unless you recognise the sender and know the content is safe.


Here are some examples:

Cultural Catalyst Lab (attached)

TechInc hackerspace
https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.techinc.nl%2FDispute_Procedure&data=04%7C01%7C%7Ce932be22ba72421b783508d91a17ce9e%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637569512708046549%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=XJMCcgg1wdrs19PIj9hzf67BsRSqTe51k4x3XppEcuk%3D&reserved=0

IETF
(please find a link yourself)

CCC
(please find a link yourself)

Another kind of example: Debian
https://eur02.safelinks.protection.outlook.com/?url=https:%2F%2Fpeople.debian.org%2F~enrico%2Fdcg%2Fch04s07.html%23meta-links-cr&data=04%7C01%7C%7Ce932be22ba72421b783508d91a17ce9e%7Ccd9e8269dfb648e082538b7baf8d3391%7C0%7C0%7C637569512708046549%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=Tat77i%2BHimjecSJ9P4QJVHLECVDKtZumls3PeKIPuLY%3D&reserved=0

And let's look at all the examples provided on this list, mostly by
Sasha Romijn.

Vesna




User Image

Vesna Manojlovic

2021-06-01 11:34:33 CET

RIPE NCC staff member

Some more examples on how adjacent communities are dealing with their
Equity, Inclusion & Diversity efforts: this time from RightsCom:

https://www.rightscon.org/our-approach-to-convening-safe-productive-inclusive-spaces/

Regards,
Vesna

========

Strengthening our approach

Last year, we had to quickly transition our policies and processes for
an online environment. In an effort to be clear and transparent about
adapting our practices, we outlined our process in detail. We were
impressed and heartened by the community’s ability to adapt and engage
in this new space. While we have all learned a lot about effectively and
sustainably convening since our last summit, the reality is many are
still experiencing the different and inequitable effects of COVID-19. We
know it is important that our approaches continue to adapt and reflect
the current moment.

This year, the RightsCon security working group – an internal committee
operated by Access Now – has had more time to reflect and prepare. In
this time, we undertook a comprehensive review of our safety and
security documentation and processes, both internally, and with an
external partner who is a trusted and experienced expert in community
safety – online and off.

We’re confident that in undertaking this review we have strengthened our
plans and ways of working, as well as deepened our understanding of the
capacities required from our teams to uphold our Code of Conduct and
Privacy and Participation policies. As a result of the review, we have:

Clarified our workflows, roles, and processes;
Updated and improved our governing and process documents;
Improved and further tailored our Code of Conduct training for staff and
partners;
Closed registration ahead of the summit;
Mapped out all platform and technical spaces (see our FAQ section for
more details);
Completed detailed, updated scenario planning and evaluations.
Informing your participation
RightsCon is online, it’s open to the public, and free registration is
available. It is, and always has been, a multi-stakeholder space and
environment and an opportunity to bring diverse voices and opinions into
one space.

While we take great care to ensure every participant enjoys a safe,
enriching experience, we also rely on each participant taking stock of
their own safety and security, and implementing measures appropriate to
their own circumstances. As you prepare for next week, we encourage you
to take some time to assess your digital hygiene and digital security
best practices when working and interacting in online spaces.

When participating in RightsCon, we encourage you to:

Be mindful of the public nature of certain spaces and manage the
information you share accordingly;
Be thoughtful regarding the information you share or receive (including
URLs and attachments) relative to your ability to verify a fellow
participant’s identity;
Where you have the need to discuss highly sensitive topics, consider the
most appropriate platform or channel for such exchanges.
Reporting and responding
During RightsCon, participants will be able to reach out to our response
team with any questions or to report an incident. To create a safe and
supportive environment that remains productive there might be some
instances where our team needs to respond with a quick decision (“First
Response”) to ensure the safety of the community, prevent further harm,
and stabilize the situation. Our response team will then work to assess
the situation carefully and decide on the final response and remedy,
with the best interests of our community, and those most at risk, in mind.

In building an adaptive reporting and response process, we were guided
by the following objectives:

Maintaining a safe environment where participants can engage freely
without fear of intimidation, harassment or violence, or threat or reprisal;
Fostering a space that supports strong dialogue and productive conversation;
Developing strong response mechanisms designed to take quick action to
reduce the amount of harm;
Operating with confidentiality, recusal, and documentation security as
top priority;
Clearly and transparently communicating our policies and processes;
Continuously listening and learning about how we can best support and
serve the community.