Create report handling manual in CoC #3
Conversation
Following discussion in the-turing-way/the-turing-way#3229 -- creating this PR to add an Enforment Manuel. The text is reused from another CoC where the process was reviewed by some of The Turing Way members: https://github.com/alan-turing-institute/open-research-community-management/blob/main/CODE_OF_CONDUCT.md
malvikasharan
requested review from
gedankenstuecke,
KirstieJane and
JimMadge
CODE_OF_CONDUCT.md
Outdated
| described in this Report Handling Manual. | ||
| The committee will determine the cause and consequences that violated this Code of Conduct and take further actions. | ||
|
|
||
| ### 4.1 If the breach is considered within the scope of this Code of Conduct |
There was a problem hiding this comment.
This might be nitpicky, but "breach" here somewhat pre-supposes that the reported incident was a breach? But I guess a report can be within scope but ultimately "not a breach"?
There was a problem hiding this comment.
And I'm not sure if I missed it somewhere, but I could not find a description of what would be considered within/outside the scope of the CoC?
There was a problem hiding this comment.
Let me rephrase to make it clear that this section applies only if a breach has been identified and is also considered severe enough to escalate.
There is no scope section, and i agree that there should be. That's one of my original ask for this PR. Your response is definitely nudging to having an explicit scope section.
There was a problem hiding this comment.
I have added a scope section.
| Mediating interaction or communication between reporter and reportee | ||
| is not in the scope of this Code of Conduct. | ||
|
|
||
| ### 4.2 If the breach is considered outside the scope of this Code of Conduct |
There was a problem hiding this comment.
I was about to post the same comment on using "breach" here, but now, after reading this section it makes me wonder if the goal of the "report handling manual" is to cover these cases where "we find there was no breach of the CoC"?
There was a problem hiding this comment.
True. That can make it a bit more open to the fact that not all reports will be about breach of CoC.
There was a problem hiding this comment.
Added the scope section and updated the header to "If the report is outside the scope of the Code of Conduct"
| Mediating interaction or communication between reporter and reportee | ||
| is not in the scope of this Code of Conduct. | ||
|
|
||
| ### 4.2 If the breach is considered outside the scope of this Code of Conduct |
There was a problem hiding this comment.
| ### 4.2 If the breach is considered outside the scope of this Code of Conduct | |
| ### 4.2 If the report is outside the scope of the Code of Conduct |
|
|
||
| * Reporter: Person reporting an incident. | ||
| * Reportee: Person being reported. | ||
|
|
There was a problem hiding this comment.
| ## 3.7 Scope of this Code of Conduct | |
| This Code of Conduct applies to all online and in-person events, and meetings conducted in *The Turing Way* community spaces (online/in-person), as well as all text-based synchronous and asynchronous interactions as described below. | |
| - _The Turing Way_ organised meetings, such as Collaboration Cafés, Book Dashes, Fireside Chats, community calls, project meetings (both openly hosted meetings for the community and closed meetings for the team only), and similar events. | |
| - The Turing Way team and community leaders such as a sub-project or Working Group member, who attend an event or community spaces while representing The Turing Way. | |
| - Community members who take formal roles in _The Turing Way_, internships or in formal mentorship roles such as through Outreachy, Google Summer of Code, Google Season of Doc and similar time-bound activities. | |
| - Communication and community engagement platforms, such as project repositories on GitHub (issues, PRs or other contributions), Slack Workspace and workshops or training events, and social media platforms such as X/Twitter, Mastodon and LinkedIn. | |
| For events where *The Turing Way* is not the main organiser and if a separate Code of Conduct applies, it will be stated clearly. |
| For all incident reports that are considered beyond the scope of this Code of Conduct, **the Turing Institute's employment policies will apply**. | ||
|
|
||
| The committee will **escalate the issue to Kirstie Whitaker** (if not already involved), | ||
| who is ** project lead and Director of the Tools, Practices and Systems Research Programme at the Turing. |
There was a problem hiding this comment.
| who is ** project lead and Director of the Tools, Practices and Systems Research Programme at the Turing. | |
| who is the project lead and Director of the Tools, Practices and Systems Research Programme at the Turing. |
Summary
Following discussion in the-turing-way/the-turing-way#3229 -- creating this PR to add a Report Handling Manuel.
The text is reused from another CoC where the process was reviewed by some of The Turing Way members: https://github.com/alan-turing-institute/open-research-community-management/blob/main/CODE_OF_CONDUCT.md
Reviewers should focus on