We value the participation of every member of our community and want to ensure that every contributor has an enjoyable and fulfilling experience. Accordingly, everyone who participates in The Research Software Reactor is expected to show respect and courtesy to other community members at all times.
All project members, are dedicated to a harassment-free experience for everyone, regardless of gender, gender identity and expression, sexual orientation, disability, physical appearance, body size, race, age or religion. We do not tolerate harassment by and/or of members of our community in any form.
We are particularly motivated to support new and/or anxious collaborators, people who are looking to learn and develop their skills, and anyone who has experienced discrimination in the past.
To make clear what is expected, we ask all members of the community to conform to the following Code of Conduct.
The Research Software Reactor is a community-oriented and -led project. We value the involvement of everyone in the community. We are committed to creating a friendly and respectful place for learning, teaching and contributing. All participants in our in-person events and online communications are expected to show respect and courtesy to others at all times.
To make clear what is expected, everyone participating in activities associated with The Research Software reactor is required to conform to this Code of Conduct. This Code of Conduct applies to all spaces managed by The Research Software reactor including, but not limited to, in-person events and networking opportunities, and communications online via GitHub, email and Slack.
The lead co-organiser Dr. Tania Allard is responsible for enforcing the Code of Conduct. She can be contacted by emailing email@example.com.
Reports may be reviewed by other members of the core development team, unless there is a conflict of interest, and will be kept confidential.
The Research Software Reactor team are dedicated to providing a welcoming and supportive environment for all people, regardless of background or identity. As such, we do not tolerate behaviour that is disrespectful to our community members or that excludes, intimidates, or causes discomfort to others. We do not tolerate discrimination or harassment based on characteristics that include, but are not limited to: gender identity and expression, sexual orientation, disability, physical appearance, body size, citizenship, nationality, ethnic or social origin, pregnancy, familial status, veteran status, genetic information, religion or belief (or lack thereof), membership of a national minority, property, age, education, socio-economic status, technical choices, and experience level.
Everyone who participates in The Research Software reactor activities is required to conform to this Code of Conduct. This Code of Conduct applies to all spaces managed by The Research Software reactor including, but not limited to, in-person events and networking opportunities, and communications online via GitHub, email and Slack. By participating, contributors indicate their acceptance of the procedures by which The Research Software reactor core development team resolves any Code of Conduct incidents, which may include storage and processing of their personal information.
We are confident that our community members will together build a supportive and collaborative atmosphere at our events and during online communications. The following bullet points set out explicitly what we hope you will consider to be appropriate community guidelines:
All interactions should be professional regardless of platform: either online or in-person. See this explanation of the four social rules - no feigning surprise, no well-actually’s, no back-seat driving, no subtle -isms - for further recommendations for inclusive behaviours.
Examples of unacceptable behaviour by Turing Way community members at any project event or platform include:
Participants who are asked to stop any inappropriate behaviour are expected to comply immediately. This applies to all Turing Way community events and platforms, either online or in-person. If a participant engages in behaviour that violates this Code of Conduct, any member of the core development team may warn the offender, ask them to leave the event or platform (without refund), or impose any other appropriate sanctions (see the enforcement manual for details).
This Code of Conduct is not intended as a static set of rules by which everyone must abide. Rather, you are invited to make suggestions for updates or clarifications by contacting Dr Tania Allard firstname.lastname@example.org or by making a pull request to this document on GitHub.
If you feel able to, please contact Dr Tania Allard at email@example.com.
If you would like to contact someone outside of the core development team, please contact Adam Jackson adam.jackson[at]microsoft.com.
If you believe someone is in physical danger, please contact the appropriate emergency responders.
A detailed enforcement policy is available in the Enforcement Manual below.
This is the enforcement manual followed by The Research Software reactor research team. It’s used when we respond to an issue to make sure we’re consistent and fair. Enforcement of the Code of Conduct should be respectful and not include any harassing behaviours.
The Code of Conduct committee is:
As the community grows, we will seek to build a larger committee including members outside of the core development team.
If the incident involves physical danger, or involves a threat to anyone’s safety (e.g. 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 Research Software Reactor team.
If the act is ongoing, any community member 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 Kirstie Whitaker as soon as possible, and report their actions for review within 24 hours.
Upon receiving a report of an incident, the CoC committee will review the incident and determine, to the best of their ability:
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 “Community Member 1”, “Community Member 2”, or “Research 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.
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, Dr Allard will break the tie.
If Dr Allard is unable to take part in the discussion due to a conflict of interest, Dr Ben Murton, as an external member of the CoC committee, will make the decision.
Possible responses may include:
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.
In the event of any conflict of interest such that Dr Allard is not able to evaluate or enforce the reported violation, Adam Jackson will take Tania’s place.
This code is adapted from the Carpentries Code of Conduct with sections from the Alan Turing Institute Data Study Group Code of Conductand The Turing Way Code of Conduct. All of which are used under the creative commons attribution license.
The Carpentries Code of Conduct was adapted from guidelines written by the Django Project, which was itself based on the Ada Initiative template and the PyCon 2013 Procedure for Handling Harassment Incidents. Contributors to the Carpentries Code of Conduct were: Adam Obeng, Aleksandra Pawlik, Bill Mills, Carol Willing, Erin Becker, Hilmar Lapp, Kara Woo, Karin Lagesen, Pauline Barmby, Sheila Miguez, Simon Waldman, Tracy Teal.
The Turing Institute Data Study Group Code of Conduct was heavily adapted from the Citizen Lab Summer Institute 2017 Code of Conduct and used under a CC BY 2.5 CA license. Citizen Lab based their Code of Conduct on the xvzf Code of Conduct, the Contributor Covenant, the Django Code of Conduct and Reporting Guide and we are also grateful for this guidance from Ada Initiative.
We really appreciate the work that all of the communities linked above have put into creating such a well considered process.
This Code of Conduct is licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0 CA) license which means you are free to share and adapt the work so long as the attribution to Tania Allard and The Research Software Reactor community is retained, along with the attribution to the Carpentries, the Alan Turing Institute Data Study Group organising team, Citizen Lab and the other resources.