[diversity] Code of Conduct

Hi Hans Petter,

On 19/10/2019 23:50, Hans Petter Holen wrote:
> Thanks for the hard work with the next version of the code of conduct. 
> Special thanks to Brian and Sahsa for presenting the work.
>
> Now the final challenge is to establish consensus. This means 
> identifying remaining issues and address them. (This does not mean 
> that all can be solved, but we should aim to document why they are not 
> solved at this point.)
>
> I have done a quick analisys of the differences between the existing 
> code of conduct and the new code of conduct.
> https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-of-conduct
> and
> https://www.ripe.net/participate/meetings/ripe-meetings/ripe-meeting-code-of-conduct-3-0-draft
>
> The main text: « For over a quarter of a century, the RIPE community's 
> strength comes from its breadth of experience, diversity of views, and 
> an open, respectful exchange of ideas – values that we want all of our 
> RIPE Meeting attendees to uphold.»
>
> Is the same in the two documents.
>
> In the old code of conduct it continues: « Please treat each other 
> with tolerance and respect. Free speech and an open exchange of ideas 
> are encouraged and celebrated. Demeaning, intimidating or harming 
> anyone at the meeting is wrong. We are especially sensitive to 
> behaviour that offends based on gender, sexual orientation, religion, 
> race or ethnic origin, or other perceived social, cultural, or 
> personal differences.»
>
> This has been removed from the new Coc, at least from the Intro. Is 
> this deliberate?
No, it wasn't deliberate - the text is just so explicit later in the 
document on this but we can add it back it in, no problem.
>
> In the old code of conduct, there are currently 3 trusted contacts, 
> selected by the RIPE chair without any documented process. In the new 
> version the trusted contacts has been renamed to a CoC team of 4 to 6 
> and with a process on how the RIPE Chair selects the
>
>
> As for consequences the existing CoC only states « Please be aware 
> that attendees violating the RIPE Meeting CodeofConduct may be asked 
> to leave the meeting without a refund and other actions may be taken 
> as deemed necessary.»
>
> In the new version there is a much more detailed list.
> It goes one step further on two areas:
> * Ban from future meetings is explicitly stated (which I would argue 
> could happen under the existing CoC too)
> * Removing content from presentations on the meeting web. Here the PC 
> has taken a very principal possition that the submitted presentation 
> will be published as presented.
>
> Appeals is not at all covered in the existing CoC but is specified in 
> the new version.
>
> While this is a very quick and high level analisys, I am thinking of 
> publishing my thoughts on this, but would like your input before I do so.
Just to clarify - the intention with the CoC Team wasn't to replace the 
Trusted Contacts necessarily. But yeah, I think that if we have a CoC 
Team, then it's probably not necessary and if the existing TC members 
were to receive the additional training that the CoC Team would get, 
they could easily nominate themselves to be on the team. Having two 
bodies around this may be confusing and we definitely do not want that.

As per the concerns raised earlier by Daniel and the discussion I had 
with you, we added the appeals process (two parts - for appealing a 
potential member of the CoC Team and for appealing a decision from the 
CoC Team on an investigation). Before sending it to the list, I spoke 
about this in detail with legal and incorporated their feedback into the 
3.0 version.
>
> -hph
Amanda
>
> -- 
> -- Hans Petter Holen Mobile +47 45 06 60 54 | hph at oslo.net 
> <mailto:hph at oslo.net> | http://hph.oslo.net
>
>
> _______________________________________________
> diversity mailing list
> diversity at ripe.net
> https://mailman.ripe.net/


-------------- next part --------------
An HTML attachment was scrubbed...
URL: </ripe/mail/archives/diversity/attachments/20191020/3a4ef941/attachment.html>