[diversity] Updated Draft RIPE Code of Conduct Published for Community Review

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-code-of-conduct/

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-of-conduct-3-0-draft
[2] Python Community Code of Conduct https://www.python.org/psf/conduct/