Code of Conduct: initial draft

[willfurnass]

Addresses #354

• Draft text
• Finalise list of contacts
• Create form
• Decide on visibility within site

[willfurnass]

@annakrystalli, @drj11 and @bobturneruk Any of you want to be explicitly listed as contacts on this?

[bobturneruk]

Please no. Perhaps rse@sheffield.ac.uk?

[willfurnass]

@bobturneruk That address is already listed. Think it's common in CoCs to have individuals listed too should folks not want to discuss incidents with an anonymous group. Happy for the named contacts to be just me and @mondus.

[bobturneruk]

Should maybe be whoever's running the training?

[willfurnass]

@bobturneruk Good suggestion but points us towards having a template CoC that we instantiate per event?

[annakrystalli]

From previous experience, there needs to be additional contacts, independent of instructors in case participants need to report bad behaviour by an instructor

[annakrystalli]

Turing Way enforcement guidelines are pretty robust and could serve as a good starting point: https://github.com/alan-turing-institute/the-turing-way/blob/master/book/website/community-handbook/coc/coc-enforcement.md

[drj11]

yeah, so per @bobturneruk and @annakrystalli comments, the "generic" CoC should also say that any particular event should (or may?) also list an event-specific contact for CoC issues.

[willfurnass]

I think this PR is now ready for review. My suggestion would be that we try to get something simple and generic in place soon then refine after reviewing other CoCs - would others be happy with that? The CoC in this PR is quite strong on what behaviours aren't permitted and flexible on what actions can result from violations of the CoC, so could make for a good starting point.

[annakrystalli]

An overarching first comment from me is whether or not to use language that implies that the coc only applies to events. I would prefer it to include mention to any form of interaction with us, eg contributing or interacting with any of our materials online.

[willfurnass]

@annakrystalli Good suggestion; made some small tweaks in the latest commit (and associated Google Form) that hopefully address that.

[willfurnass]

This PR is temporarily parked whilst we check whether there are existing CoC/enforcement resources at TUOS that we can use for external facing events.

[willfurnass]

Started incorporating some enforcement guidance adapted from the Turing Way's policy but it isn't logistically compatible with the CoC, so a little effort is required to unify them. One difference is that one mechanism allows for anonymous reporting and the other doesn't. The team suggested that anonymous reporting may not be essential.

[ns-rse]

If this is something that we want to incorporate it will need updating with a new committee.