Code of Conduct¶
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 Mentored Sprints community 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, ethnic background and heritage, 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 Code of Conduct document has been written in 4 parts:
- Overview (this document)
- Code of Conduct detailed view
- Reporting guidelines
- Code of Conduct enforcement.
Finally, we have a section that acknowledges all the sources that this Code of Conduct has been built upon (see Acknowledgement).
1 Code of Conduct: Overview¶
The Mentored Sprints project 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 and online events as well as on our 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 Mentored Sprints project is required to conform to this Code of Conduct. This Code of Conduct applies to all spaces managed by Mentored Sprints project including, but not limited to, in-person and online events, and communications online via our mailing list, GitHub, Twitter and Discord.
Reports may be reviewed by other members of the core development team, unless there is a conflict of interest. All reports will be kept confidential.