[coc-tf] [ripe-list] Updated Draft Code of Conduct Published for Review

Hi Mirjam,

On Jul 12, 2021, at 2:25 AM, Mirjam Kuehne <mir at zu-hause.nl> wrote:
> 
> Hi Leo,
> 
> Many thanks for publishing the new version of the Code of Conduct,
> including a redline version and a RIPE Labs article. That's very helpful.
> 
> I just have a couple of small comments and suggestions:
> 
> - Some people might find the acronym CoC confusing. It may be better to
> use "Code of Conduct" where possible. And otherwise maybe use "the Code"?

We can definitely make a change like this to improve readability.

> - The documents refers a couple of times to "the Trusted Contacts or
> future Code of Conduct Team". I understand that the responsibilities of
> a Code of Conduct Team might be different than those of the Trusted
> Contacts. But if we can agree that the Trusted Contacts are serving as
> the Code of Conduct Team (with limited responsibilities) until a new
> process is in place, you could say that in the intro or in a footnote
> and then simply refer to the Code of Conduct Team. That would make those
> sections easier readable and we don't have to change the document later.

We could add that. I think I’d put it in section 3 (Call to Action).

> - Under section 7. did you consider adding that until these other two
> documents are in place, violations can be reported to the Trusted
> Contacts (or the current Code of Conduct Team if we agree on the
> suggestion above)?

We didn’t discuss putting wording like that at the end of the document. Instead, we added section 3.

> Please feel free to share this with the rest of the Task Force.
> 
> Did you receive any other feedback (apart from Randy's)?

I have not seen any other feedback yet. I think we should send a reminder a week before the webinar. That should give people two weeks to read, listen, think and write feedback before your decision.

Regards,

Leo

> 
> Best regards,
> Mirjam
> 
>> On 07/07/2021 14:29, Leo Vegoda wrote:
>> Dear RIPE community,
>> 
>> As promised at RIPE 82, we have published an updated draft RIPE Code
>> of Conduct. A clean text version of the document and a redline
>> version, showing all the changes from the version published in March,
>> can be found at:
>> 
>> https://www.ripe.net/publications/docs/ripe-documents/other-documents/copy_of_ripe-code-of-conduct/
>> 
>> Please send comments in support of this draft, or asking for specific
>> changes, to the RIPE Discussion List by 17 September 2021. The RIPE
>> Chair will evaluate the community’s consensus based on comments made.
>> 
>> Some of the key changes in this draft:
>> 
>> - We have numbered the major sections and simplified some of the language
>> - We have expanded the introduction to provide background on the
>> discussion that led to the development of this document
>> - We have added a new “Call to Action” section
>> - We have clarified the language in the “Scope” section and removed
>> the bulleted lists there
>> - We simplified the subsection on law
>> - We added a new subsection on aggressive behaviour in the “Behaviour” section
>> - We added a section noting that reports that are not made in good
>> faith, such as in retaliation for another report, can be rejected
>> 
>> We have also published a RIPE Labs article about why we made the
>> changes you’ll see in the new draft.
>> 
>> https://labs.ripe.net/author/leo_vegoda/updated-draft-ripe-code-of-conduct/
>> 
>> We will hold a session with the community to discuss the changes,
>> which has been scheduled for 1 September 2021. We recognise that it
>> will not be possible for everyone to attend this webinar so it will be
>> recorded and published, and we will release more information about the
>> session nearer the time.
>> 
>> Kind regards,
>> 
>> Leo Vegoda
>> for the Code of Conduct TF
>> 
> 
> 
>