Add CoC enforcement process and update CoC contact info (still WIP)

pages/community/coc-enforcement.md

@@ -0,0 +1,95 @@
+---
+title: "RSE Sheffield's Community Code of Conduct: enforcement process"
+permalink: /community/coc-enforcement/
+slug: coc-enforcement
+type: text
+---
+
+This is the Code of Conduct (CoC) enforcement process followed by the RSE Sheffield team in relation to
+RSE Sheffield-curated events and online communities.
+It is used when we respond to an issue to make sure we're consistent and fair.
+Enforcement of the CoC should be respectful and not include any harassing behaviours.
+
+# CoC Committee
+
+The CoC Committee is:
+
+  * Will Furnass: `[email protected]`
+  * Paul Richmond: `[email protected]`
+  * David Wilby: `[email protected]`
+
+Over time this list may be expanded.
+
+# Urgent Situations: Acting Unilaterally
+
+If the incident involves physical danger,
+or involves a threat to anyone's safety (such as threats of violence),
+any member of the community may -- and should -- act unilaterally to protect the safety of any community member.
+This can include contacting law enforcement (or other local personnel) and
+speaking on behalf of the RSE Sheffield team.
+
+If the act is ongoing,
+any member of the team may act immediately, before reaching consensus, to diffuse the situation.
+In ongoing situations,
+any member may at their discretion employ any of the tools available in this enforcement manual,
+including bans and blocks online, or removal from a physical space.
+
+In situations where an individual community member acts unilaterally,
+they must inform Will Furnass as soon as possible,
+and report their actions for review within 24 hours.
+
+# Less-Urgent Situations
+
+Upon receiving a report of an incident,
+the CoC Committee will review the incident and determine, to the best of their ability:
+
+  * whether this is an ongoing situation
+  * whether there is a threat to anyone's physical safety
+  * what happened
+  * whether this event constitutes a CoC violation
+  * who, if anyone, was the bad actor
+
+This information will be collected either in person or in writing.
+The CoC Committee will provide a written summary of the information surrounding the incident.
+All participants will be anonymised in the summary report, referred to as e.g. "Community Member 1", "Community Member 2", or "RSE Team Member 1".
+The "de-anonymising key" will be kept in a separate file and only accessed to link repeated reports against the same person over time.
+
+The CoC Committee will aim to have a resolution agreed upon within one week.
+In the event that a resolution can't be determined in that time, a member of the CoC Committee will respond to the reporter(s) with an update and projected timeline for resolution.
+
+# Resolutions
+
+The CoC Committee will seek to agree on a resolution by consensus of all members investigating the report in question.
+If the Committee cannot reach consensus and deadlocks for over a week, Will Furnass will break the tie.
+If Will Furnass is unable to take part in the discussion due to a conflict of interest Paul Richmond will make the decision.
+
+Possible responses may include:
+
+* A mediated conversation or agreement between the impacted community members.
+* A request for a verbal or written apology, public or private, from a community member.
+* A public announcement clarifying community responsibilities under the CoC.
+* Nothing, if the issue reported is not a violation or outside of the scope of this CoC.
+* A private in-person conversation between a member of the RSE team and the individual(s) involved.
+  In this case, the person who has the conversation will provide a written summary for record keeping.
+* A private written reprimand from a member of the RSE team to the individual(s) involved.
+  In this case, the RSE team member will deliver that reprimand to the individual(s) over email, cc'ing Will Furnass for record keeping.
+* A public announcement of an incident, ideally in the same venue that the violation occurred (such as on GitHub for a GitHub violation).
+  The Committee may choose to publish this message elsewhere for posterity.
+* An imposed "time out" from online spaces.
+  Will Furnass will communicate this "time out" to the individual(s) involved.
+* A permanent or temporary ban from some or all RSE Sheffield spaces (like on GitHub, online calls or in-person events).
+  The CoC Committee will maintain records of all such bans so that they may be reviewed in the future, extended to a CoC safety team as it is built, or otherwise maintained.
+  If a member of the community is removed from an event they will not be reimbursed for any part of the event that they miss.
+
+Once a resolution is agreed upon, but before it is enacted, a member of the CoC Committee will contact the original reporter and any other affected parties and explain the proposed resolution.
+The CoC Committee member will ask if this resolution is acceptable, and must note feedback for the record.
+However, the CoC Committee is not required to act on this feedback.
+
+# Conflicts of Interest
+
+In the event of any conflict of interest such that Will Furnass is not able to evaluate or enforce the reported violation, Paul Richmond will take Will's place.
+
+# Acknowledgement
+
+Adapted from [The Turing Way's process](https://github.com/alan-turing-institute/the-turing-way) (Copyright © The Turing Way; licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/)).
+

pages/community/coc.md

@@ -1,25 +1,26 @@
 ---
 title: RSE Sheffield's Community Code of Conduct
 permalink: /community/coc/
-slug: seminars
+slug: coc
 type: text
 ---
 
 # Summary
 
-We are dedicated to providing a welcoming and supportive environment for all people, regardless of background or identity.
-By participating in activities organised by the University of Sheffield's Research Software Engineering team,
+We are dedicated to providing a welcoming and supportive environment for all people,
+regardless of background or identity.
+By participating in activities organised by RSE Sheffield,
 participants accept to abide by RSE Sheffield's Community Code of Conduct and
 accept the procedures by which any Code of Conduct incidents are resolved.
 Any form or behaviour to exclude, intimidate, or cause discomfort is a violation of the Code of Conduct.
 In order to foster a positive and professional learning environment
 we encourage the following kinds of behaviours in all activities and events:
 
-  - Use welcoming and inclusive language
-  - Be respectful of different viewpoints and experiences
-  - Gracefully accept constructive criticism
-  - Focus on what is best for the community
-  - Show courtesy and respect towards other community members
+  * Use welcoming and inclusive language
+  * Be respectful of different viewpoints and experiences
+  * Gracefully accept constructive criticism
+  * Focus on what is best for the community
+  * Show courtesy and respect towards other community members
 
 If you believe someone is violating the Code of Conduct, we ask that you
 report it to the RSE Sheffield Community Code of Conduct Committee by [completing
@@ -36,12 +37,15 @@ We are committed to creating a friendly and respectful place for learning, teach
 All participants in our activities, events and communications are expected to show respect and courtesy to others.
 
 To make clear what is expected, everyone participating in RSE Sheffield-led activities is required to conform to the Code of Conduct.
-This Code of Conduct applies to all spaces managed by RSE Sheffield including, but not limited to, workshops, email lists, and online forums such as GitHub and course chat pages.
+This Code of Conduct applies to all spaces managed by RSE Sheffield including, but not limited to,
+workshops,
+email lists,
+and online forums such as GitHub and course chat pages.
 Workshop hosts are expected to assist with the enforcement of the Code of Conduct.
 
-The RSE Sheffield management team is responsible for enforcing the Code of Conduct.
-They can be contacted by emailing `[email protected]`.
-All reports will be reviewed by RSE Sheffield's managers and will be kept confidential.
+The RSE Sheffield Code of Conduct team is responsible for enforcing the Code of Conduct.
+They can be contacted by emailing `rse-coc-group@sheffield.ac.uk`.
+All reports will be reviewed by the RSE Sheffield's Code of Conduct team and will be kept confidential.
 
 ## Part 2. RSE Sheffield's Community Code of Conduct
 
@@ -86,39 +90,39 @@ All interactions should be professional regardless of platform: either online or
 In order to foster a positive and professional learning environment
 we encourage the following kinds of behaviours in all RSE Sheffield activities and platforms:
 
-  - Use welcoming and inclusive language
-  - Be respectful of different viewpoints and experiences
-  - Gracefully accept constructive criticism
-  - Focus on what is best for the community
-  - Show courtesy and respect towards other community members
+  * Use welcoming and inclusive language
+  * Be respectful of different viewpoints and experiences
+  * Gracefully accept constructive criticism
+  * Focus on what is best for the community
+  * Show courtesy and respect towards other community members
 
 ## Part 2.2 Unacceptable behaviour
 
 Examples of unacceptable behaviour by participants in any RSE Sheffield
 activities/events include:
 
--   written or verbal comments which have the effect of excluding people
+  * written or verbal comments which have the effect of excluding people
     on the basis of membership of any specific group
--   causing someone to fear for their safety, such as through stalking,
+  * causing someone to fear for their safety, such as through stalking,
     following, or intimidation
--   violent threats or language directed against another person
--   the display of sexual or violent images
--   unwelcome sexual attention
--   nonconsensual or unwelcome physical contact
--   sustained disruption of talks, events or communications
--   insults or put downs
--   sexist, racist, homophobic, transphobic, ableist, or exclusionary
+  * violent threats or language directed against another person
+  * the display of sexual or violent images
+  * unwelcome sexual attention
+  * nonconsensual or unwelcome physical contact
+  * sustained disruption of talks, events or communications
+  * insults or put downs
+  * sexist, racist, homophobic, transphobic, ableist, or exclusionary
     jokes
--   excessive swearing
--   incitement to violence, suicide, or self-harm
--   continuing to initiate interaction (including photography or
+  * excessive swearing
+  * incitement to violence, suicide, or self-harm
+  * continuing to initiate interaction (including photography or
     recording) with someone after being asked to stop
--   publication of private communication without consent
+  * publication of private communication without consent
 
 ## Part 2.3 Consequences of Unacceptable behaviour
 
 Participants who are asked to stop any inappropriate behaviour are
-expected to comply immediately. This applies to any RSE Sheffield activities/events, 
+expected to comply immediately. This applies to any RSE Sheffield activities/events,
 either online or in-person. If a participant engages in
 behaviour that violates this code of conduct, the organizers may warn
 the offender, ask them to leave the event or platform (without refund),
@@ -142,20 +146,22 @@ action will be taken.
 # Alternative Contact Points
 
 If you would prefer other ways to contact us,
-an email to `[email protected]` will be seen by the RSE Sheffield management team.
+an email to `rse-coc-group@sheffield.ac.uk` will be seen by the RSE Sheffield Code of Conduct team.
 If you are uncomfortable reporting to the team,
 incidents can also be reported by email to any of the team:
 
-  * Director of RSE Sheffield: [Paul Richmond](mailto:[email protected])
-  * Senior Research Software Engineer : [Will Furnass](mailto:[email protected])
+  * Will Furnass: `[email protected]`
+  * Paul Richmond: `[email protected]`
+  * David Wilby: `[email protected]`
 
 Any particular event may also list one or more additional event-specific contacts for Code of Conduct issues.
 
 # Update Logs
 
-  - 2021-01-05 Initial version
+  * 2021-04-06 Revise contact list
+  * 2021-01-05 Initial version
 
-# About this document
+# Acknowledgements
 
 This document is adapted from [The ARCHER Training Code of Conduct](http://www.archer.ac.uk/training/code-of-conduct/index.php),
 which in turn was adapted from [The Carpentries Code of Conduct](https://docs.carpentries.org/topic_folders/policies/code-of-conduct.html),