diff --git a/code-of-conduct/about-code-of-conduct-incident-record.md b/code-of-conduct/about-code-of-conduct-incident-record.md new file mode 100644 index 00000000..d0efcd87 --- /dev/null +++ b/code-of-conduct/about-code-of-conduct-incident-record.md @@ -0,0 +1,93 @@ +# Code of Conduct incident record template guide + +--- +Thank you for downloading the Code of Conduct template from The Good Docs Project! +We welcome any kind of feedback on our templates, both positive and negative. +To suggest improvements, open an issue on our (https://github.com/thegooddocsproject/templates/issues)[Templates repository]. + +This is the guide that explains how to use the Good Docs Project Code of Conduct incident record, which is part of the Code of Conduct template set. + +The Code of Conduct template set includes: + +* A Code of Conduct that you can use to create and explain your community's Code of Conduct. This template is included in the same folder as this template and is named `template-code-of-conduct.md`. See its accompany guide: `about-code-of-conduct.md`. +* A Code of Conduct response plan template that you can use to create and explain the policy your team will follow as you handle Code of Conduct incidents. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-response-plan.md`. See its accompany guide: `about-code-of-conduct-response-plan.md`. +* A Code of Conduct incident record template for a form that is filled out when a community moderator takes an incident report from a community member. This template is included in the same folder as the Code of Conduct template as the Code of Conduct template and is named `template-code-of-conduct-incident-record.md`. See its accompany guide: `about-code-of-conduct-incident-record.md`. +* A Code of Conduct remediation record template for a form that is filled out when a community moderator meets with a community member to explain the consequences of a Code of Conduct violation. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-remediation-record.md`. See its accompany guide: `about-code-of-conduct-remediation-record.md`. + +You might also consider using the `../our-team/template-our-team.md` template to let your community members know who they can contact to report a Code of Conduct violation. This document is useful beyond Code of Conduct violations. It is a core document that helps you clearly communicate who belongs to your open source project or organization. +--- + + +## Why do I need a Code of Conduct incident record? + +See the `guide-code-of-conduct.md` for reasons to incorporate a Code of Conduct and response plan. + +The Code of Conduct incident record is part of the documentation that needs to be kept when investigating and resolving Code of Conduct incidents. +It is important to file this documentation to enable the community moderators to identify and prevent potential repeated patterns of abuse in the community. + + +## Content of the Code of Conduct incident record template + +The following sections provide guidance about how to fill out each section of the Code of Conduct incident record template. + +:information_source: The Code of Conduct incident record template includes boilerplate text that you can customize or adapt, use as-is, or completely replace with your own text. + + +### About the "Introduction" section +The *Introduction* section includes a description of the goals the community moderator should keep in mind while taking an incident report from an individual. +The community moderator should refer to this section regularly to ensure that the incident reporter feels safe and supported throughout the process. + + +### About the "Incident number" section + +Follow your organization's incident number protocol in assigning an incident number. + +The incident number can include the date an investigation was opened. +For example, yyyy-001. + + +### About the "Name of community moderator who took the report" section + +The community moderator who took the report lists their name here. + + +### About the "Reporter's contact information" section + +This section is optional. +If the reporter is comfortable giving their name and contact information, note that information here. + + +### About the "Permission from incident reporter to proceed?" section + +Ask the incident reporter for permission to proceeed. +Indicate their response in thise section. + +If an incident reporter does not give permission to proceed with an investigation, they will be given the option to hold the report “in escrow.” +Escrowed reports will not be acted upon until there is a second report of the same incident or a similar incident involving the same individual. +The goal of an escrow report is to retain a record of incidents in case there is a pattern of misbehavior by the same individual. + +If the reporter wants to keep the report in escrow, the incident record should still be filled out and filed in the appropriate archives for future tracking. + + +### About the "Date, time, and location of incident" section + +This section is optional. Indicate the date, time, or location of the incident if known. + + +### About the "Additional witnesses or contacts" section + +If the incident reporter mentions that other individuals were involved or present as witnesses, list those individuals here. +If possible, note their contact information. + + +### About the "Incident description" section + +After listening to the incident reporter's description of the incident, write the details here. + +As indicated on the template, remember to only document information required to inform the report resolution. +Where possible, avoid documenting your opinion about the incident, or any information about individuals that is not relevant to the report. + + +## Additional resources + +In creating this form, the authors were inspired by the [Otter Tech Code of Conduct Enforcement Training](https://otter.technology/code-of-conduct-training/). diff --git a/code-of-conduct/about-code-of-conduct-remediation-record.md b/code-of-conduct/about-code-of-conduct-remediation-record.md new file mode 100644 index 00000000..552a5a1d --- /dev/null +++ b/code-of-conduct/about-code-of-conduct-remediation-record.md @@ -0,0 +1,99 @@ +# Code of Conduct remediation record template guide + +--- +Thank you for downloading the Code of Conduct template from The Good Docs Project! +We welcome any kind of feedback on our templates, both positive and negative. +To suggest improvements, open an issue on our (https://github.com/thegooddocsproject/templates/issues)[Templates repository]. + +This is the guide that explains how to use the Good Docs Project Code of Conduct remediation record, which is part of the Code of Conduct template set. + +The Code of Conduct template set includes: + +* A Code of Conduct that you can use to create and explain your community's Code of Conduct. This template is included in the same folder as this template and is named `template-code-of-conduct.md`. See its accompany guide: `about-code-of-conduct.md`. +* A Code of Conduct response plan template that you can use to create and explain the policy your team will follow as you handle Code of Conduct incidents. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-response-plan.md`. See its accompany guide: `about-code-of-conduct-response-plan.md`. +* A Code of Conduct incident record template for a form that is filled out when a community moderator takes an incident report from a community member. This template is included in the same folder as the Code of Conduct template as the Code of Conduct template and is named `template-code-of-conduct-incident-record.md`. See its accompany guide: `about-code-of-conduct-incident-record.md`. +* A Code of Conduct remediation record template for a form that is filled out when a community moderator meets with a community member to explain the consequences of a Code of Conduct violation. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-remediation-record.md`. See its accompany guide: `about-code-of-conduct-remediation-record.md`. + +You might also consider using the `../our-team/template-our-team.md` template to let your community members know who they can contact to report a Code of Conduct violation. This document is useful beyond Code of Conduct violations. It is a core document that helps you clearly communicate who belongs to your open source project or organization. +--- + + +## Why do I need a Code of Conduct remediation record? + +See the `guide-code-of-conduct.md` for reasons to incorporate a Code of Conduct and response plan. + +The Code of Conduct remediation record is part of the documentation that needs to be kept when investigating and resolving Code of Conduct incidents. +It is important to file this documentation to enable the community moderators to identify and prevent potential repeated patterns of abuse in the community. + + +## Content of the Code of Conduct remediation record template + +The following sections provide guidance about how to fill out each section of the Code of Conduct remediation record template. + +:information_source: The Code of Conduct remediation record template includes boilerplate text that you can customize or adapt, use as-is, or completely replace with your own text. + + +### About the "Introduction" section + +The *Introduction* section includes a description of the goals the community moderator should keep in mind while taking an incident report from an individual. +The community moderator should refer to this section regularly to ensure that they stay focused on the goal of explaining the outcome of the Code of Conduct violation. +These meetings have the potential to be stressful and full of high emotions. +The introduction section provides some guidelines from keeping these meetings under control. + + +### About the "Incident number" section + +The incident number should match the same incident number assigned on the [Code of Conduct incident record](template-code-of-conduct-incident-record.md) for this incident. + + +### About the "Name of community moderator who remediated the incident" section + +List the name of the community moderator who remediated the incident here. + + +### About the "Name of community member involved in the incident" section + +List the name of the individual who committed the Code of Conduct violation here. + + +### About the "Outcome" section + +Indicate the outcome of the Code of Conduct violation, as discussed with the other community moderators. + + +### About the "Behavior modification plan" section + +Indicate the steps that will be taken as part of the outcome of the Code of Conduct violation. +For example, if the outcome is a temporary ban from the community, indicate what steps will be taken to remove the individual's access to community forums, repositories, etc. + + +### About the "Do you agree to follow the plan?" section + +After explaining the behavior modification plan, the community moderator should ask directly whether the individual will agree to follow the plan and note their response here. + + +### About the "Consequences if they do not agree to the behavior modification plan" section + +In this section, list the consequences for failing to agree to the behavior modification plan. +The suggested consequence is removal from the community. + + +### About the "Who can they appeal this decision to?" section + +Fill out the details for appealing a decision in this form. +If the appeals process doesn't change, simply add that to this form from the start for all incidents. + + +### About the "Reported person's response to the plan" section + +Record the details of how the reported person responded to the plan here. + + +### About the "Additional information gathered" section + +If any additional information needed, it can be noted here. + + +## Additional resources + +In creating this form, the authors were inspired by the [Otter Tech Code of Conduct Enforcement Training](https://otter.technology/code-of-conduct-training/). diff --git a/code-of-conduct/about-code-of-conduct-response-plan.md b/code-of-conduct/about-code-of-conduct-response-plan.md new file mode 100644 index 00000000..65232b67 --- /dev/null +++ b/code-of-conduct/about-code-of-conduct-response-plan.md @@ -0,0 +1,182 @@ +# Code of Conduct response plan template guide + +--- +Thank you for downloading the Code of Conduct response plan template from The Good Docs Project! +We welcome any kind of feedback on our templates, both positive and negative. +To suggest improvements, open an issue on our (https://github.com/thegooddocsproject/templates/issues)[Templates repository]. + +This is the guide that explains how to use the Good Docs Project Code of Conduct response plan, which is part of the Code of Conduct template set. + +The Code of Conduct template set includes: + +* A Code of Conduct that you can use to create and explain your community's Code of Conduct. This template is included in the same folder as this template and is named `template-code-of-conduct.md`. See its accompany guide: `about-code-of-conduct.md`. +* A Code of Conduct response plan template that you can use to create and explain the policy your team will follow as you handle Code of Conduct incidents. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-response-plan.md`. See its accompany guide: `about-code-of-conduct-response-plan.md`. +* A Code of Conduct incident record template for a form that is filled out when a community moderator takes an incident report from a community member. This template is included in the same folder as the Code of Conduct template as the Code of Conduct template and is named `template-code-of-conduct-incident-record.md`. See its accompany guide: `about-code-of-conduct-incident-record.md`. +* A Code of Conduct remediation record template for a form that is filled out when a community moderator meets with a community member to explain the consequences of a Code of Conduct violation. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-remediation-record.md`. See its accompany guide: `about-code-of-conduct-remediation-record.md`. + +You might also consider using the `../our-team/template-our-team.md` template to let your community members know who they can contact to report a Code of Conduct violation. This document is useful beyond Code of Conduct violations. It is a core document that helps you clearly communicate who belongs to your open source project or organization. +--- + + +## Why do I need a Code of Conduct and a response plan? + +See the `guide-code-of-conduct.md` for reasons to incorporate a Code of Conduct and response plan. + + +## Content of the Code of Conduct response plan template + +The following sections provide guidance about how to fill out each section of the Code of Conduct response plan template. + +:information_source: The Code of Conduct response plan template includes boilerplate text that you can customize or adapt, use as-is, or completely replace with your own text. If you use the boilerplate text, make sure you replace the project name placeholders with your own project name. + + +### About the "Introduction" section + +The introduction section explains the purpose of the response plan document. + + +### About the "Community moderators" section + +In the *Community moderators* section, you can list the names of the community moderators or link to a document that lists the community moderators, such as a website that uses the (Our Team)[../our-team/template-our-team.md] template. + +Alternatively, you could list the names of the community moderators and their preferred contact information, such as their Slack handles. +You could also link to a dedicated email address or contact form. + +Remember to respect your community moderator's privacy by only including contact methods that go through official project channels, such as community forums or project-issued email accounts. +Don't include personal email addresses or contact information. +The goal is to strike a balance between making your moderators easy to contact while also respecting their privacy. + + +### About the "Contacting a community moderator" section + +In the *Contacting a community moderator* section, provide clear instructions for the best way to contact the community moderators. +Filling out this section will require some pre-work on your part to clearly think through how community moderators should be contacted. + + +### About the "Community moderator values" section + +In this section, articulate the values that your community moderators should strive to uphold. +You can customize the provided boilerplate text or write your own. + + +### About the "Requirements for community moderators" section + +In this section, explain the eligibility requirements for your community moderators. +Once again, this section will require some pre-work for you to think through what your community moderators will need to do to be prepared to serve in this role: + +- How should individuals be selected or nominated to serve in this role? +- What qualifications should someone in this role have? +- What training will be required to serve in this role? + +Community moderators do need training in handling Code of Conduct incidents in order to be effective in this role. + +Some training options and resources you can consider using: + +- **[The Code of Conduct book](https://frameshiftconsulting.com/resources/code-of-conduct-book/)** - This free book can act as a baseline guide for handling Code of Conduct incidents. Your community moderator team could possibly host a book club and go through the chapters together, discussing them as they go. The authors of this book also offer Code of Conduct training workshops. +- **[Mozilla's Community Participation Guidelines Enforcement](https://mozilla.teachable.com/p/cpg-training-contributors)** - This free course was developed by Mozilla for Mozilla community moderators and only takes a few hours to complete. However, be aware that this course is not as comprehensive as your community may need. The training is also specific to Mozilla's Code of Conduct, although some of its principles are general enough to apply to many projects. +- **[Otter Tech Code of Conduct Enforcement Training](https://otter.technology/code-of-conduct-training/)** - Otter Tech is a diversity and inclusion consulting firm that offers regular workshops. The course provides a general framework for how to respond to Code of Conduct violations and provides many opportunities to role-play and practice acting as a community moderator. The Otter Tech training is excellent, but expensive and is only offered in U.S. friendly time zones. +- If there are other resources that we are not aware of, please (open an issue)[https://github.com/thegooddocsproject/templates/issues] to let us know! + +In addition to these resources, we recommend holding regular practice sessions with your community moderators where you role-play what it would be like to handle an actual incident if one were to occur. +Try creating a hypothetical situation and see if you can take it through the entire process to its conclusion. + + +### About the "Community moderator terms of service" section + +In this section, describe your plan for rotating community moderators or limiting terms of service if needed. + + +### About the "Reviewing the Code of Conduct" section + +In the *Reviewing the Code of Conduct* section, indicate your timetable for reviewing the Code of Conduct and supporting policy documents. + +Consider reviewing your Code of Conduct and your response plan on a yearly basis at least. +An annual review can also be a good time to check that each community moderator is familiar with your Code of Conduct policies and that they have been sufficiently trained in handling Code of Conduct incidents. +Ensure that someone in your community is responsible for ensuring the Code of Conduct is reviewed regularly. +If your community uses a calendar, add an event to your calendar to remind you to do the yearly review. + + +### About the "Key terms used in this document" section + +This section explains the meaning of the terms used throughout the remainder of the document. +You may change these terms if you'd rather use different ones. +If you do change the terms, make sure you find and replace all instances of the old term in the document. + + +### About the "Handling incident reports" section + +The *Handling incident reports* section includes several subsections. +It makes up the main body of this document and explains how you will handle incident reports. + +The remediation process explained in this template was based on the Mozilla process for handling incidents. +Feel free to adapt the process for your community if needed. +Whatever you do, we want you to truly make this process your own. +Take time to really think through the logistics of how to make this process work for your community. + +:information_source: All of the sections in the Code of Conduct response plan template includes boilerplate text that you can customize or adapt, use as-is, or completely replace with your own text. If you use the boilerplate text, make sure you replace the project name placeholders with your own project name. + + +### About the "Overview" section + +The *Overview* section provides a brief overview of the different phases of handling a Code of Conduct incident. + + +### About the "Listen" section + +The *Listen* section explains the policy and procedures for meeting with a Code of Conduct incident reporter to gather information about the Code of Conduct violation. + +At the end of this phase, the investigating moderator should fill out a [Code of Conduct incident record](code-of-conduct-incident-record.md). + + +### About the "Triage" section + +The *Triage* section provides guidelines for assigning an initial severity and impact assessment. + +- **Severity** refers to the overall seriousness of the behavior and the risk that behavior will be repeated. +- **Impact** refers to how public the incident was and the number of community members who were or who could have been impacted by the incident, especially members of marginalized communities. + +You may use your own assessment categories and definitions if preferred. + + +### About the "Recommend" section + +The *Recommend* section provides guidelines for recommending a suggested response to the Code of Conduct incident. + + +### About the "Respond" section + +The *Respond* section explains how to meet with the accused individual to deliver the suggested response and behavior modification plan. + +At the beginning of this phase, the investigating moderator should fill out the [Code of Conduct remediation record](code-of-conduct-remediation-record.md). + + +### About the "Resolve" section + +The *Resolve* section explains how to conclude the Code of Conduct investigation by filing the necessary paperwork for record-keeping purposes. + +It is important to record and store this documentation to enable the community moderators to identify and prevent potential repeated patterns of abuse in the community. + + +### About the "Handling incident appeals" section + +The *Handling incident appeals* provides guidelines for handling incident appeals. + +Filling out this section will require some pre-work on your part to clearly think through which team should best handle appeals. + + +### About the "Preventing conflicts of interest" section + +The *Preventing conflicts of interest* section explains the conditions that can be considered a conflict of interest and the steps that should be taken if a community moderator has a conflict of interest. + + +## Additional resources + +The authors of this template cannot stress enough the important of ensuring your community moderators are trained in the protocol and best practices for handling Code of Conduct incidents. + +The following lists some of the resources for training your moderators that were mentioned earlier in this guide: + +- [The Code of Conduct book](https://frameshiftconsulting.com/resources/code-of-conduct-book/) +- [Mozilla's Community Participation Guidelines Enforcement](https://mozilla.teachable.com/p/cpg-training-contributors) +- [Otter Tech Code of Conduct Enforcement Training](https://otter.technology/code-of-conduct-training/) + +Once again, if there are other resources that we are not aware of, please [open an issue](https://github.com/thegooddocsproject/templates/issues) to let us know! diff --git a/code-of-conduct/about-code-of-conduct.md b/code-of-conduct/about-code-of-conduct.md new file mode 100644 index 00000000..74db2c4e --- /dev/null +++ b/code-of-conduct/about-code-of-conduct.md @@ -0,0 +1,146 @@ +# Code of Conduct template guide + +--- +Thank you for downloading the Code of Conduct template from The Good Docs Project! +We welcome any kind of feedback on our templates, both positive and negative. +To suggest improvements, open an issue on our [Templates repository](https://github.com/thegooddocsproject/templates/issues). + +This is the guide that explains how to use the Good Docs Project Code of Conduct, which is part of the Code of Conduct template set. + +The Code of Conduct template set includes: + +* A Code of Conduct that you can use to create and explain your community's Code of Conduct. This template is included in the same folder as this template and is named `template-code-of-conduct.md`. See its accompany guide: `about-code-of-conduct.md`. +* A Code of Conduct response plan template that you can use to create and explain the policy your team will follow as you handle Code of Conduct incidents. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-response-plan.md`. See its accompany guide: `about-code-of-conduct-response-plan.md`. +* A Code of Conduct incident record template for a form that is filled out when a community moderator takes an incident report from a community member. This template is included in the same folder as the Code of Conduct template as the Code of Conduct template and is named `template-code-of-conduct-incident-record.md`. See its accompany guide: `about-code-of-conduct-incident-record.md`. +* A Code of Conduct remediation record template for a form that is filled out when a community moderator meets with a community member to explain the consequences of a Code of Conduct violation. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-remediation-record.md`. See its accompany guide: `about-code-of-conduct-remediation-record.md`. + +You might also consider using the `../our-team/template-our-team.md` template to let your community members know who they can contact to report a Code of Conduct violation. This document is useful beyond Code of Conduct violations. It is a core document that helps you clearly communicate who belongs to your open source project or organization. +--- + + +## Why do I need a Code of Conduct and a response plan? + +A Code of Conduct is a lot like a good insurance policy: hopefully you'll never have to enforce it. +However, if or when a problem occurs in your community, you'll be glad that your Code of Conduct is there to support you. + +A Code of Conduct has many purposes and benefits. It can: + +- Help you define and clearly communicate your organization's mission, values, and guiding principles. +- Encourage members of your community to behave ethically and inclusively. +- Make your community a better place to collaborate and work. +- Demonstrate to prospective community members that your community is one that is warm, welcoming, and safe to join. + +But it's not enough to merely have a Code of Conduct. +You should also have a clear plan for how your team will respond if a Code of Conduct incident occurs. +Your response plan should include important details, such as: + +- How incidents are reported and documented. +- Who will receive and handle Code of Conduct incidents. +- How incidents are investigated and resolved. +- How you will handle appeals or potential conflicts of interest. + +When you have a well-defined Code of Conduct response plan in addition to a Code of Conduct, it demonstrates that your community takes its ethical responsibilities seriously. +It means that you are willing to do more than simply talk about your community values: you will actively live by them. + +Hopefully, as you create your Code of Conduct and your response plan, your community's leaders will have many important conversations about your community values and you will carefully think through the logistics of promoting and upholding those values in your community. + + +## Maintenance strategy + +A Code of Conduct is considered a foundational document for a healthy open source community. +For that reason, it is important to review your Code of Conduct and your response plan regularly to make sure it hasn't gone stale and still meets your community's needs. + +If you do have a Code of Conduct incident, consider holding a retrospective meeting shortly after resolving a Code of Conduct incident to make sure your Code of Conduct and response plan was effective. + +In addition to retrospectives, consider reviewing your Code of Conduct and your response plan on a yearly basis at least. +An annual review can also be a good time to check that each community moderator is familiar with your Code of Conduct policies and that they have been sufficiently trained in handling Code of Conduct incidents. +Ensure that someone in your community is responsible for ensuring the Code of Conduct is reviewed regularly. +If your community uses a calendar, add an event to your calendar to remind you to do the yearly review. + + +## Content of the Code of Conduct template + +The following sections provide guidance about how to fill out each section of the Code of Conduct template. + +:information_source: The Code of Conduct template includes boilerplate text that you can customize or adapt, use as-is, or completely replace with your own text. If you use the boilerplate text, make sure you replace the project name placeholders with your own project name. + + +### About the "Opening statement of purpose" section + +The first section in the template is where you'll put your opening statement of purpose. +Your opening statement should include information about your core values and the purpose of your Code of Conduct. + + +### About the "Expected behavior" section + +An effective Code of Conduct can help your community feel more warm and welcoming if it starts with a section outlining the positive, prosocial behaviors you'd like to see in your community. +In the *Expected behavior* section, you can list the specific behaviors and attitudes that best support the ethical values you mentioned in your opening statement. + + +### About the "Behavior that will not be tolerated" section + +The *Behavior that will not be tolerated* section is extremely important, so you should definitely include this section in your final draft. +Due to differences in culture and upbringing, some community members might not actually be aware of what behavior is considered unacceptable. +For that reason, you need to clearly explain the specific behaviors that are not allowed in your community. + +As the authors of the [Code of Conduct book](https://frameshiftconsulting.com/resources/code-of-conduct-book/) state: "People often overestimate the level of shared values they have with other people in their community, which is why it is helpful to state your community's values explicitly." + + +### About the "Consequences of unacceptable behavior" section + +The *Consequences of unacceptable behavior* section is also very important because you want to be transparent about what actions your team might take when resolving Code of Conduct incidents. + +This section should include: + +- Instructions or links for reporting a Code of Conduct incident, such as a link to your Code of Conduct response plan. +- A list of the possible consequences that could result from a Code of Conduct violation. +- A statement indicating that compliance is necessary. + + +### About the "Reporting an incident" section + +The *Reporting an incident* section should include clear instructions for reporting Code of Conduct violations. +In this section, try to communicate that your moderators are approachable and that you encourage community members to reach out, even if they're not sure if the incident is a violation or not. +Not all community members necessarily want to file an official report and may instead just want to discuss their concerns in private. + + +### About the "Addressing Code of Conduct reports" section + +In this section, include a general statement about how Code of Conduct reports will be handled and adjudicated. +This section could include: + +- A statement that complaints will be reviewed and investigated promptly and fairly. +- A privacy policy. +- The appeals process +- A notice that an internal record will be kept for all incidents. + +Consider adding a link to your [Code of Conduct response plan](template-code-of-conduct-response-plan.md) to this section for more details. + + +### About the "Where this Code of Conduct applies" section + +This section indicates the spaces in which the Code of Conduct applies. +Include the main spaces where your community officially communicates with one another or where project leaders might represent the project publicly. +Examples can include conferences, meetups, community forums, and social media platforms. + + +### About the "Related resources" section + +Use the *Related resources* section to link out to helpful resources, such as [Code of Conduct response plan](template-code-of-conduct-response-plan.md) and your [Our team page](../our-team/template-our-team). + +You can also include any articles that inspired your values as you wrote your Code of Conduct. + + +## Additional resources +In creating this Code of Conduct, the authors adapted or were inspired by the following resources, listed alphabetically: + +- [Ada Initiative](https://adainitiative.org/continue-our-work/conference-policies/) +- [Apache Foundation Code of Conduct](http://www.apache.org/foundation/policies/conduct#code-of-conduct) +- [Citizen Code of Conduct](https://github.com/stumpsyn/policies/blob/master/citizen_code_of_conduct.md) +- [The Code of Conduct Book](https://frameshiftconsulting.com/resources/code-of-conduct-book/) +- [Contributor Covenant 2.0](https://www.contributor-covenant.org/version/2/0/code_of_conduct/) +- [Django Code of Conduct](https://www.djangoproject.com/conduct/) +- [Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/) +- [No more rock stars: how to stop abuse in tech communities](https://hypatia.ca/2016/06/21/no-more-rock-stars/) +- [Otter Tech Code of Conduct Enforcement Training](https://otter.technology/code-of-conduct-training/) +- [Rust Community Code of Conduct](https://www.rust-lang.org/policies/code-of-conduct) diff --git a/code-of-conduct/template-code-of-conduct-incident-record.md b/code-of-conduct/template-code-of-conduct-incident-record.md new file mode 100644 index 00000000..dca47255 --- /dev/null +++ b/code-of-conduct/template-code-of-conduct-incident-record.md @@ -0,0 +1,68 @@ +# Template Code of Conduct incident record + +--- +The Code of Conduct incident record template includes: + +* Placeholder text that you can replace with your own text. This text is indicated in {curly braces}. +* Writing instructions, also in {curly braces}. +* A supplementary Code of Conduct incident record guide that provides more detailed information about using this template. Read the guide document first! This guide is located in the same folder as the template and is named `about-code-of-conduct-incident-record.md`. +* The Code of Conduct remediation template should be used along with several other templates, including: + * A Code of Conduct that you can use to create and explain your community's Code of Conduct. This template is included in the same folder as this template and is named `template-code-of-conduct.md`. See its accompany guide: `about-code-of-conduct.md`. + * A Code of Conduct response plan template that you can use to create and explain the policy your team will follow as you handle Code of Conduct incidents. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-response-plan.md`. See its accompany guide: `about-code-of-conduct-response-plan.md`. + * A Code of Conduct remediation record template for a form that is filled out when a community moderator meets with a community member to explain the consequences of a Code of Conduct violation. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-remediation-record.md`. See its accompany guide: `about-code-of-conduct-remediation-record.md`. + +You might also consider using the `../our-team/template-our-team.md` template to let your community members know who they can contact to report a Code of Conduct violation. This document is useful beyond Code of Conduct violations. It is a core document that helps you clearly communicate who belongs to your open source project or organization. +--- + +TIPS FOR THE COMMUNITY MODERATOR: +When gathering information from an incident reporter, strive for these goals: + +* **Safety** - Bring in another community moderator if something about the situation is unsafe or dangerous, but avoid inviting too many moderators into the discussion and overwhelming the incident reporter. +* **Privacy** - Where possible, always strive to uphold the incident reporter's privacy. Obtain permission to proceed with the investigation. +* **Empathy** - Be an understanding, active listener who recognizes the real emotions being felt by the incident reporter. For example, say: "It sounds like you felt (this emotion) when (this thing happened)." +* **Support** - Ask if there's anything you can do to make the incident reporter feel safe, emotionally whole, or restored. Explain the possible outcomes that are available, as provided in the [Code of Conduct](CODE_OF_CONDUCT.md) (correction, warning, temporary ban, permanent ban). However, avoid making any direct promises for exactly how the report will be handled until the investigation is concluded. +* **Acknowledgment** - At the end of the meeting, thank the incident reporter for being part of the community and for reaching out about the incident. Let the reporter know that you will be in touch to explain how the incident will be resolved after the investigation is complete. + + +## Incident number + +{Assign a number to this incident for tracking purposes. +It can include the date an investigation was opened. +For example, yyyy-001.} + + +## Name of community moderator who took the report + +{Put your name here.} + + +## Name of incident reporter + +{If the reporter wishes to be anonymous, include a simple description of their role or involvement in the project.} + + +## Reporter's contact information (optional) + +{Ask the reporter if they would like to provide their name and contact information. +If yes, fill in the contact information.} + + +## Permission from incident reporter to proceed? + +{Yes/no.} {If no, ask if they would like to hold the report in escrow.} + + +## Date, time, and location of incident (optional) + +{yyyy-mm-dd} {time} {location}. + + +## Additional witnesses or contacts (optional) + +{List anyone who might be able to provide additional information as part of the investigation.} + + +## Incident description + +{Only document information required to inform the report resolution. +Where possible, avoid documenting your opinion about the incident, or any information about individuals that is not relevant to the report.} diff --git a/code-of-conduct/template-code-of-conduct-remediation-record.md b/code-of-conduct/template-code-of-conduct-remediation-record.md new file mode 100644 index 00000000..4b468557 --- /dev/null +++ b/code-of-conduct/template-code-of-conduct-remediation-record.md @@ -0,0 +1,100 @@ +# Template Code of Conduct remediation record + +--- +The Code of Conduct remediation record template includes: + +* Placeholder text that you can replace with your own text. This text is indicated in {curly braces}. +* Writing instructions, also in {curly braces}. +* A supplementary Code of Conduct remediation record guide that provides more detailed information about using this template. Read the guide document first! This guide is located in the same folder as the template and is named `about-code-of-conduct-remediation-record.md`. +* The Code of Conduct remediation template should be used along with several other templates, including: + * A Code of Conduct that you can use to create and explain your community's Code of Conduct. This template is included in the same folder as this template and is named `template-code-of-conduct.md`. See its accompany guide: `about-code-of-conduct.md`. + * A Code of Conduct response plan template that you can use to create and explain the policy your team will follow as you handle Code of Conduct incidents. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-response-plan.md`. See its accompany guide: `about-code-of-conduct-response-plan.md`. + * A Code of Conduct incident record template for a form that is filled out when a community moderator takes an incident report from a community member. This template is included in the same folder as the Code of Conduct template as the Code of Conduct template and is named `template-code-of-conduct-incident-record.md`. See its accompany guide: `about-code-of-conduct-incident-record.md`. + +You might also consider using the `../our-team/template-our-team.md` template to let your community members know who they can contact to report a Code of Conduct violation. This document is useful beyond Code of Conduct violations. It is a core document that helps you clearly communicate who belongs to your open source project or organization. +--- + +TIPS FOR THE COMMUNITY MODERATOR: +When meeting with a community member to explain the outcome of a Code of Conduct violation, strive for these goals: + +* **Preparation** - Simply tell the community member beforehand that you wish to discuss an issue privately. Invite one other community moderator for support if needed. +* **Calmness** - When explaining what behavior prompted to Code of Conduct investigation, calmly state what the behavior was without judgment or emotion. State the impact on the incident reporter or the community. +* **Clarity** - Set a clear behavior modification plan. If possible, get the community member to agree to this plan. +* **Privacy** - Do not disclose the identity of the incident reporter or allow them to be contacted. If the community member under investigation wants to contact the incident reporter to apologize, explain that you can take the apology on their behalf. With your permission, a public apology may be acceptable under the circumstances. + + +## Incident number + +{Use the same incident number that was assigned to the incident report.} + + +## Name of community moderator who remediated the incident + +{Put your name here.} + + +## Name of community member involved in the incident + +{List the name of the community member who committed the Code of Conduct violation.} + + +## Severity level + +Select one: + +[ ] High +[ ] Medium +[ ] Low + + +## Impact level + +Select one: + +[ ] High +[ ] Low + + +## Outcome + +Select one: + +[ ] Correction +[ ] Warning +[ ] Temporary ban +[ ] Permanent ban +[ ] None + +{List any additional details about the outcome and consequences as needed.} + + +## Behavior modification plan + +{List the details of the behavioral modification plan as discussed with the other community moderators. + + +## Do you agree to follow the plan? + +{Yes/no.} {If no, proceed to the consequences listed in the next section.} + + +## Consequences if they do not agree to the behavior modification plan + +{List the consequences if the community member who committed the Code of Conduction violation does not agree to the plan. +The suggested consequence is removal from the community.} + + +## Who can they appeal this decision to? + +{Explain the options for appealing a decision as explained in the Code of Conduct policy. +Explain that they must still comply with the incident response plan as the appeal process is underway.} + + +## Reported person's response to the plan + +{Provide details about how the community member responded to the proposed plan.} + + +## Additional information gathered + +{List any other observations or notes as needed.} diff --git a/code-of-conduct/template-code-of-conduct-response-plan.md b/code-of-conduct/template-code-of-conduct-response-plan.md new file mode 100644 index 00000000..19d46d4e --- /dev/null +++ b/code-of-conduct/template-code-of-conduct-response-plan.md @@ -0,0 +1,347 @@ +# Code of Conduct response plan template + +--- +The Code of Conduct response plan template includes: + +* Placeholder text that you can replace with your own text. This text is indicated in {curly braces}. +* Writing instructions, also in {curly braces}. +* A supplementary Code of Conduct response plan guide that provides more detailed information about using this template. Read the guide document first! This guide is located in the same folder as the template and is named `about-code-of-conduct-response-plan.md`. +* The Code of Conduct remediation template should be used along with several other templates, including: + * A Code of Conduct that you can use to create and explain your community's Code of Conduct. This template is included in the same folder as this template and is named `template-code-of-conduct.md`. See its accompany guide: `about-code-of-conduct.md`. + * A Code of Conduct incident record template for a form that is filled out when a community moderator takes an incident report from a community member. This template is included in the same folder as the Code of Conduct template as the Code of Conduct template and is named `template-code-of-conduct-incident-record.md`. See its accompany guide: `about-code-of-conduct-incident-record.md`. + * A Code of Conduct remediation record template for a form that is filled out when a community moderator meets with a community member to explain the consequences of a Code of Conduct violation. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-remediation-record.md`. See its accompany guide: `about-code-of-conduct-remediation-record.md`. + +You might also consider using the `../our-team/template-our-team.md` template to let your community members know who they can contact to report a Code of Conduct violation. This document is useful beyond Code of Conduct violations. It is a core document that helps you clearly communicate who belongs to your open source project or organization. +--- + + +This document explains: + +- How to contact the current {Project name} community moderators, such as to report a [Code of Conduct](code-of-conduct.md) incident). +- The policies and procedures that community moderators should follow when responding to a Code of Conduct incident. +- Additional governing policies for the community moderator team (also sometimes referred to as the “Code of Conduct committee”). + + +## Community moderators + +For a list of the current {Project name} community moderators and the best way to reach them, see [Community Moderators](our-team.md). +You may contact any of these individuals to make a Code of Conduct incident report. + +{Instead of linking to a separate page, you could list the names of the community moderators and their preferred contact information.} + + +## Contacting a community moderator + +You can contact a community moderator to make a Code of Conduct incident report or to discuss the process and options related to Code of Conduct incidents. +To make an incident report, send a message to the community moderator that has the best working relationship with you and with whom you feel most comfortable talking. + +To contact a moderator, please {describe your preferred contact method, such as sending a direct private message on Slack or some other method}. +Community moderators will respond as soon as they possibly can. +They might also request a one-on-one meeting with you (such as a phone call or online video conference) to get more information about the incident. + + +## Community moderator values + +Community moderators should strive to: + +- Occupy a position of trust and good rapport within {Project name} community. +- Be active listeners who can show empathy and understanding when meeting with an incident responder. +- Respect the privacy of incident reporters or other potentially sensitive and private information they may have access to in this role. +- Be fair and open-minded when investigating an incident and recommending a response. +- Develop healthy self-care strategies to prevent burnout and reduce personal stress. + + +## Requirements for community moderators + +The {Project name} community moderators play an important role in the community because they help ensure the community is healthy, vibrant, and welcoming to all contributors. +Because of the crucial nature of this role, potential community moderators should be invested in the long-term health of the +{Project name} community and should be willing to develop a set of communication skills that may require some formal training. +For that reason, individuals who are interested in serving as community moderators must: + +- Commit to a day or half-day formal training in incident response skills within {required time period} of joining the moderator team. Formal training involves taking an online training course in incident response skills, mediation, or arbitration. Or it could also involve participating in an informal workshop in incident response skills led by a current {Project name} moderator. Upon joining the moderator team, the new moderator can work with other moderators to develop a training plan and ensure this training requirement is met. +- Be recommended for the team by either another community moderator or a member of the {Project name} core team. Nominated individuals should demonstrate the values and qualities necessary to carry out the responsibilities of community moderators. Note that {Project name} community members may first volunteer for consideration and then seek a recommendation afterwards. +- Be active contributors to the {Project name} who have participated in the community for at least three months. Contributions can include authoring pull requests, submitting issues, attending meetings regularly, and participating in {Project name} community forums. +- Cannot be subject of an ongoing {Project name} Code of Conduct incident. + + +## Community moderator terms of service + +The {Project name} community moderator team should consist of 3-5 community members at a given time. +To prevent burnout, community moderators should serve for a recommended term limit of {time period}, unless there have been little or no incidents in that space of time. +Community members should stagger terms of service to ensure there is some continuity on the team over time. +Community moderators may return to serve second terms after a break from service. +If possible, outgoing community moderators should recommend a replacement from the community. + + +## Reviewing the Code of Conduct + +The Code of Conduct and this document (the community moderators document) should be reviewed by the moderator team at least once a year, typically in {time period}, to ensure these documents are meeting the needs of the community. +The {Project name} community will notify the community of any revisions by publicizing the revisions in the community’s forums of communication on both Slack and the groups.io mailing list. + + +## Key terms used in this document + +This section provides a definition of key terms and roles that appear in the incident response policy that follows this section: + +- **Incident** - Also known as a “Code of Conduct incident” or “conduct violation,” an incident is a behavior by a member of the {Project name} that allegedly violates the community [Code of Conduct](code-of-conduct.md). +- **Incident report** - Also sometimes referred to as the “report,” an incident report begins when a member of the {Project name} reports behavior that violates the community Code of Conduct. The incident report refers to the violating behavior that is then investigated by community moderators. +- **Incident reporter** - Also sometimes referred to as the “reporter,” the incident reporter is the person who reports a Code of Conduct violation to a community moderator. +- **Handling an incident report** - Also known as “investigating a report,” handling an incident report is the process of investigating and resolving an incident report as explained using the processes and guidelines in the subsequent sections. +- **Investigating moderator** - Also known as the “investigator,” the investigating moderator is the community moderator who will handle the incident report and ensure the report moves through all six stages. +- **Accused individual** - The accused individual is the person who is alleged to have violated the Code of Conduct. +- **Escrowed reports** - If an incident reporter does not give permission to proceed with an investigation, they will be given the option to hold the report “in escrow.” Escrowed reports will not be acted upon until there is a second report of the same incident or a similar incident involving the same individual. The goal of an escrow report is to retain a record of incidents in case there is a pattern of misbehavior by the same individual. + + +## Handling incident reports + +An incident report begins when a member of {Project name} contacts a community moderator to report an incident. +The moderator who is contacted should handle the incident report and should try to respond as soon as possible. +This moderator will become the investigating moderator. + +The investigating moderator may involve another community moderator as an additional investigator or as a replacement investigator under these conditions: + +- If the moderator who was contacted by the incident reporter does not feel comfortable investigating and handling the incident alone. +- If the moderator cannot handle the incident in a timely manner and must ask a different moderator to investigate the incident report. +- If the moderator needs to be recused because of a conflict of interest. + +If the moderator who was contacted by an incident reporter intends to involve an additional community moderator for support or as a replacement, they should first inform the incident reporter, explain the circumstances, and offer the opportunity to withdraw their incident report if they are uncomfortable having another moderator involved. + +To promote impartiality, if the incident reporter is a community moderator themselves, then a different community moderator must handle the report. +See [#preventing-conflicts-of-interest](Preventing conflicts of interest) for more information. + +### Overview + +All incident reports have six stages: + +1. Listen +2. Triage +3. Recommend +4. Respond +5. Follow up +6. Resolve + +See the following sections for more information about what occurs in each phase. + + +### Listen + +During the listening phase, the investigating moderator will: + +- Listen to the incident reporter’s explanation of the Code of Conduct violation. +- Explain the available outcomes. +- Obtain permission to proceed to the next steps in the investigation. +- Fill out the {link to your [Code of Conduct incident record](code-of-conduct-incident-record.md)}. NOTE: This record can be filled out after taking the report if needed. + +Throughout the process, the investigating moderator will treat the reporter’s identity as confidential and will only disclose their identity to other moderators on a need-to-know basis. + +The investigating moderator should talk directly to the person who reported the incident either through an online video conference or by phone. + +During this meeting, the investigating moderator should: + +- Note the reporter’s name and contact information. +- If possible, note the incident’s date, time, and/or location. +- Listen carefully to the incident reporter and get a complete understanding of the incident, its context, and the parties involved. The moderator should strive to listen with empathy and understanding. They should default to believing the incident responder. +- Ask what the incident reporter would need in order to feel emotionally whole or restored. Explain the possible outcomes that are available, as provided in the [Code of Conduct](code-of-conduct.md) (correction, warning, temporary ban, permanent ban). However, the moderator should not make any direct promises for exactly how the report will be handled until the investigation is concluded. +- Obtain permission from the incident reporter to proceed with the investigation. If permission is not granted, the investigator can offer to hold the incident report in escrow. Escrowed reports will not be acted upon until there is a second report of the same incident or a similar incident involving the same individual. The goal of escrow reports is to retain incident reports in case there is a pattern of misbehavior by the same individual. + +During or immediately after the meeting, the investigating moderator should: + +- Fill out the {link to your [Code of Conduct incident record](code-of-conduct-incident-record.md)} to ensure that all information from the meeting has been accurately captured. The investigating moderator should avoid over-documenting the incident: only document information required to inform the report resolution. Where possible, avoid documenting your opinion about the incident, or any information about individuals that is not relevant to the report. +- File the incident record in the {describe where these files are kept}. If permission was not obtained, the incident report is kept in the incident record archives. If the incident reporter wanted to keep the report in escrow, the incident report is kept in the escrow incident report archives. +- If permission was obtained, proceed with the rest of the investigation. + +If necessary, the moderator may need to conduct additional interviews with other corroborating witnesses or may have to review any additional recorded evidence of the incident (such as emails, documents, message transcripts, or chat histories). + + +### Triage +After completing the listening phase, the moderator should assign an initial risk and impact level to the incident using their best judgment based on the following guidelines. + + +**Severity levels** +Severity refers to the overall seriousness of the behavior and the risk that behavior will be repeated: + + + + + + + + + + + + + + + + + + + + + + +
Severity levelDefinitionExamples
High +
    +
  • The incident is extremely severe and/or there is a high likelihood the behavior will occur again in the future.
  • +
  • Incidents that are harassing, dangerous, abusive, violent, offensive (especially to marginalized groups), or which threaten the physical and/or psychological safety of one or more community members are designated as high severity.
  • +
  • Repeated medium- or low-level offenses by the same individual are also automatically designated as high severity.
  • +
+
+
    +
  • Sexual assault or unwanted sexual attention
  • +
  • Violent threats or language
  • +
  • Personal attacks
  • +
  • Derogatory language (especially aimed at marginalized groups)
  • +
  • Repeated inappropriate comments after a warning
  • +
+
Medium +
    +
  • The incident is moderately severe and is potentially disruptive to the community.
  • +
  • The incident could possibly cause one or more community members to feel unwelcome or uncomfortable in the community.
  • +
+
+
    +
  • Mildly inappropriate comments or jokes
  • +
  • Bullying
  • +
  • Tone-policing
  • +
  • Repeatedly dominating a conversation (such as repeatedly talking over another person or not inviting discussion from others where appropriate)
  • +
  • Excessive profanity
  • +
  • Sustained disruptions of community events
  • +
LowThe incident is minor in nature and doesn’t pose serious harm or risk of harm. +
    +
  • Heated discussions or disagreements between community members.
  • +
+
+ + +**Impact levels** +Impact refers to how public the incident was and the number of community members who were or who could have been impacted by the incident, especially members of marginalized communities: + + + + + + + + + + + + + + + + + +
Impact levelDefinitionExamples
High +
    +
  • The incident occurred in a public event, in a {Project name} meeting or community event, or on a community forum (such as on a mailing list or in Slack).
  • +
  • The accused individual is a {Project name} leader or a high-profile community member.
  • +
  • Incidents involving someone who was representing {Project name} in an official capacity while the incident occurred.
  • +
+
+
    +
  • Comments in the {Project name} Slack or mailing list.
  • +
  • Comments or actions in a {Project name} meeting.
  • +
  • Speaking or participating at a conference or fund-raising event as a representative of {Project name}.
  • +
+
Low +
    +
  • The incident occurred in a private conversation, message, or email. Also includes posts or comments made in a forum or context outside of official {Project name} channels, such as on a personal social media account.
  • +
+
+
    +
  • Comments in a private email.
  • +
  • Comments in a direct message on Slack.
  • +
  • Comments or actions made in a one-on-one meeting in person or virtually.
  • +
+
+ + +### Recommend + +Once an initial severity or impact level has been assigned, the investigating moderator should send a private message to the rest of the community moderators through email. +Moderators who have recused themselves over conflicts of interest should not be included in this email. +It would also be appropriate to send a separate direct message on Slack to notify the other moderators to check for the email to ensure everyone is aware of the email. + +In the email, indicate your assessment of the incident’s severity and impact level and your recommended response. +See the [Code of Conduct](code-of-conduct.md) for the four possible responses to a conduct violation (correction, warning, temporary ban, permanent ban). + +Community moderators have an ethical responsibility to respond as soon as possible and work toward consensus. +Delaying action in response to the Code of Conduct violation can possibly make the situation worse. + +In their response, moderators should indicate whether they agree with the incident severity and impact levels and the recommended response. +If community moderators disagree with the original assessment, the moderators should indicate the nature of their disagreement. Where disagreements occur, the committee should work quickly to reach a consensus (ideally within 1-2 days) and may require a video conference discussion. +If a consensus cannot be reached and has ended in a stalemate, the response should be put to a vote. +In incidents where a tied vote occurs, the chair of the community moderators acts as the deciding vote. + +After a response has been recommended, the incident reporter should be notified of the outcome of the investigation and the recommended response before proceeding. + + +### Respond + +Once the incident response has been determined by the community moderators, the investigating moderator should meet with the accused individual in person (either through an online video conference or by phone). +The moderator may invite an additional moderator to attend the meeting if support is desired. + +Before this meeting, the investigating moderator should fill out the [Code of Conduct remediation record](code-of-conduct-remediation-record.md) and use this document to guide the meeting. + +In this meeting, the moderator should explain the nature of the reported incident and the specifics of the incident response (correction, warning, temporary ban, permanent ban). +The accused individual will be given a chance to respond (within reason) and will be informed about the process for appealing the incident response. + +If a new Code of Conduct violation occurs in this meeting (such as a derogatory or threatening comment made to a community moderator or about another member of the community), it should be treated as a separate incident and should be reported as a new incident to the community moderators. + +If the individual wishes to appeal the incident response, the community moderator can send them a link to this document for information. +Ensure that the individual is aware that they must still comply with the incident response plan as the appeal process is underway. + +To protect the identity of the incident reporter, the accused individual must not be given the identity of the incident reporter nor will they be allowed to contact the incident reporter, even to apologize. +If an apology is required as part of the response, the following options are permissible: + +- The apology can be delivered to the investigating community moderator who will then deliver it to the incident reporter. +- The apology may be delivered in a public forum with permission from the investigating community moderator. + +During or immediately after the meeting, the investigating moderator should fill out the any additional notes on the the [Code of Conduct remediation record](code-of-conduct-remediation-record) to ensure that all information from the meeting has been accurately captured. + + +### Resolve + +The investigating moderator should implement the consequence(s) of the incident response, depending on what the response was. +The moderator should also follow up with the incident reporter to let them know what the outcome of the report was. + +If a temporary ban was implemented, a community moderator who handled the incident should meet with the accused individual to ensure compliance before readmittance into the community. + +All documentation should be filed in the {describe where your documents are kept}: + +- The [Code of Conduct incident record](code-of-conduct-incident-record.md) form. +- The [Code of Conduct remediation record](code-of-conduct-remediation-record.md) form. + +It is important to file this documentation to enable the community moderators to identify and prevent potential repeated patterns of abuse. + + +## Handling incident appeals + +If an accused individual wants to dispute the decision of the community moderators, that individual is entitled to one appeal. +An appeal can be requested directly from the community moderators using the same process of reporting an incident. +That means that the accused individual can send a direct message to one of the community moderators to request an appeal. +While the appeal process is underway, the accused individual must still comply with the incident response plan. + +When an appeal is requested, 2-3 members of {Project name} {team name} will review the incident documentation and the reason for the appeal. +They will consult with the community moderators about the investigation and decision-making process to determine if the Code of Conduct was fairly and properly applied. +They will then recommend to uphold, modify, or reverse the original incident response. +Decisions made by the {Project name} {team name} are final. + + +## Preventing conflicts of interest + +A moderator is considered to have a conflict of interest when any of the following conditions are met: + +- The moderator is the individual accused of a Code of Conduct violation. +- The moderator has a close working or personal relationship with the individual accused of a Code of Conduct violation that could impede their ability to be impartial. +- The moderator was personally involved in the Code of Conduct violation in some way (such as being the direct target of a Code of Conduct violation). Merely witnessing or being present during the incident does not necessarily qualify as a conflict of interest. Merely being part of a protected group that was targeted in a derogatory statement or action does not necessarily qualify as a conflict of interest. + +Moderators that meet any of these conditions should recuse themselves from all discussions and decisions about the incident where they have a conflict of interest. +Another member of the community moderation team should act as the investigating moderator. +The moderator with a conflict of interest should ensure that another moderator is designated to handle the incident. + +If the accused individual is a leader or prominent member of the {Project name} community, avoidance of a conflict of interest may not be possible as all moderators could possibly have a personal working relationship with the accused individual. +In this situation, recusal is not necessary and moderators should instead make their best effort to remain impartial. diff --git a/code-of-conduct/template-code-of-conduct.md b/code-of-conduct/template-code-of-conduct.md new file mode 100644 index 00000000..d9c60aab --- /dev/null +++ b/code-of-conduct/template-code-of-conduct.md @@ -0,0 +1,149 @@ +# Code of Conduct template + +--- +The Code of Conduct template includes: + +* Placeholder text that you can replace with your own text. This text is indicated in {curly braces}. +* Writing instructions, also in {curly braces}. +* A supplementary Code of Conduct guide that provides more detailed information about using this template. Read the guide document first! This guide is located in the same folder as the template and is named `about-code-of-conduct.md`. +* The Code of Conduct template should be used along with several other templates, including: + * A Code of Conduct response plan template that you can use to create and explain the policy your team will follow as you handle Code of Conduct incidents. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-response-plan.md`. See its accompany guide: `about-code-of-conduct-response-plan.md`. + * A Code of Conduct incident record template for a form that is filled out when a community moderator takes an incident report from a community member. This template is included in the same folder as the Code of Conduct template as the Code of Conduct template and is named `template-code-of-conduct-incident-record.md`. See its accompany guide: `about-code-of-conduct-incident-record.md`. + * A Code of Conduct remediation record template for a form that is filled out when a community moderator meets with a community member to explain the consequences of a Code of Conduct violation. This template is included in the same folder as the Code of Conduct template and is named `template-code-of-conduct-remediation-record.md`. See its accompany guide: `about-code-of-conduct-remediation-record.md`. + +You might also consider using the `../our-team/template-our-team.md` template to let your community members know who they can contact to report a Code of Conduct violation. This document is useful beyond Code of Conduct violations. It is a core document that helps you clearly communicate who belongs to your open source project or organization. +--- + +{Include your project's opening statement of purpose in this section. +Replace your own project's name in the indicated placeholder text. +You are welcome to customize or reword this boilerplate text as needed. +Alternatively, you can write your own project's statement of purpose from scratch.} + +{Project name} and its members, contributors, sponsors, and leaders pledge to make participation in our community a positive, inclusive, and safe experience for all. +{Project name} encourages contributions from everyone who shares our goals and wants to participate in a healthy, constructive, and professional manner. + +This Code of Conduct aims to support a community where all people should feel safe to participate, to introduce new ideas, and to inspire others. +This includes everyone, regardless of: ability, age, background, body size or type, caste, disability (either visible or invisible), education, ethnicity, family status, gender, gender identity and expression, geographic location, level of +experience, marital status, nationality or national origin, native language, personal appearance, race, religion, sexual identity and orientation, socio-economic status, or any other dimension of diversity. + +Openness and respectful collaboration are core values at {Project name}. +We are committed to being a community that everyone feels good about joining, and we will always work to treat everyone well. +No matter how you identify yourself or how others perceive you, you are welcome. +We gain strength from diversity and actively seek participation from those who enhance it. + +These guidelines exist to enable all {Project name} community members to collaborate effectively. +As such, this document outlines both expected behavior and behavior that will not be tolerated. +The Code of Conduct isn’t an exhaustive list of things that you must do or can’t do. +Rather, take it in the spirit in which it’s intended. +It’s a set of guidelines to make it easier to enrich our community. + + +## Expected behavior + +We expect our members, contributors, and leaders to: + +- Participate in the community actively and authentically. Your meaningful contributions add to the health and longevity of this community. +- When you make commitments, do your best to keep those commitments. Other community members will trust you and build confidence in you if you fulfill your promises. If something may prevent you from keeping a commitment or if you discover you won't be able to complete a task on time, try to notify others as soon as possible. +- Attempt collaboration before conflict. Seek out and be respectful of differing opinions, styles, viewpoints, and experiences. +- Give and accept constructive feedback, gracefully. When expressing disagreement, be professional and respectful. Be open to learning from and educating others where needed. +- Demonstrate empathy and kindness toward other people. Be considerate and respectful in your word choice, speech, and actions. Show respect with the terms you use to address others. +- Look out for those around you in the community, especially if you are in a position of influence. Alert the {Project name} {link to your community moderators document [community moderators](../our-team/template-our_team.md)} if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential. +- Gracefully accept responsibility and apologize to those affected by any mistakes, whether made intentionally or unintentionally. If someone says they have been harmed through your words or actions, listen carefully, make amends, learn from the experience, and correct the behavior going forward. +- Focus on what is best for the overall community, not just for each of us individually. Ensure that leadership roles and opportunities are well-distributed across the community membership and not just centered in one person or the same few people. To help our community develop and build up leaders at every level of the {Project name}, ensure that you share knowledge with others as much as possible and be mindful of fostering healthy dialogue where no one voice dominates a conversation. + + +## Behavior that will not be tolerated + +The following behaviors are unacceptable within our community, whether they occur online, offline, privately, or publicly: + +- Violent language or threats directed against another person. +- Sexist, racist, or otherwise discriminatory jokes and language. +- Deliberate intimidation, following, or stalking (online or in person). +- Personal insults, especially those related to gender, sexual orientation, race, religion, or disability. This includes misgendering, name calling, and mockery. +- Trolling (posting controversial comments in order to provoke others), insulting, or making derogatory comments. +- The use of sexualized language, jokes, or imagery, and sexual attention, inappropriate physical contact, or sexual advances of any kind. +- Bullying, tone-policing (attacking a person’s tone rather than the content of their message), or repeatedly dominating a topic of conversation (such as regularly talking over another person or not inviting discussion from others where appropriate). +- Publishing or threatening to publish others’ private information without their explicit permission. Private information includes physical addresses, email addresses, and emails or other communications sent privately or non-publicly. +- Deliberate “outing” of any private aspect of a person’s identity without their consent except as necessary to protect vulnerable people from intentional abuse. This includes sharing personally identifying information (“doxing”). +- Excessive or unnecessary profanity. +- Deliberate misgendering. +- Knowingly making harmful false claims about a person. +- Pushing a person to drink alcohol when they don’t want to drink, or deceiving someone into drinking alcohol. +- Marketing to our community members either individually or collectively without their express approval. Solicitations on behalf of your business should be restricted to designated channels or areas. For more information about appropriate ways to market your business to the community, ask one of the {Project name} {link to your community moderators document [community moderators](../our-team/template-our_team.md)}. +- Repeatedly communicating with a community member who has asked you to leave them alone. +- Sustained disruption of community events, including meetings and presentations. +- Recording or photography at community meetings and events without explicit permission. +- Advocating for, or encouraging, any of the above behavior. +- Other conduct which could reasonably be considered inappropriate in a professional setting. + + +## Consequences of unacceptable behavior + +Unacceptable behavior from any {Project name} community member, contributor, sponsors, or leaders will not be tolerated. +We expect everyone to comply with requests to stop unacceptable behavior immediately. + +If any community member engages in unacceptable behavior, any community member or moderator should report the incident to the {Project name} {link to your community moderators document [community moderators](../our-team/template-our_team.md)}. +The moderators will investigate the incident to determine the incident’s severity and overall impact to the community. +See our {link to your [Code of Conduct response plan](template-code-of-conduct-response-plan.md)} for more details. + +Depending on the risk and impact level, the moderators may respond by requiring: + +- **Correction:** A private, written warning from community moderators, providing clarity around the nature of the violation, an explanation of why the behavior was inappropriate, and what behavior is expected going forward. A public apology may be requested. +- **Warning:** A warning with consequences for continued behavior. No interaction with the people involved is allowed for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media and it includes unsolicited interaction with community moderators. Violating these terms may lead to a temporary or permanent ban. +- **Temporary ban:** A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with community moderators, is allowed during this period. Violating these terms may lead to a permanent ban. Readmittance to the community usually requires an additional meeting with a community moderator to ensure future compliance. +- **Permanent ban:** A permanent ban from any sort of public interaction within the community. + +The action taken is at the discretion of the {Project name} {link to your community moderators document [community moderators](../our-team/template-our_team.md)}. +Participants are expected to comply immediately, and further action may be taken in case a participant does not comply. + +Every community member is entitled to one appeal using the [same process for reporting a Code of Conduct incident](#reporting-an-incident). +Community members are expected to comply with the requested action while appeals are being considered. +After an appeal has been resolved, the decision is considered final. + + +## Reporting an incident + +Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to one of the {Project name} +{link to your community moderators document [community moderators](../our-team/template-our_team.md)}. +If you would like to discuss your concerns or if you have personally experienced unacceptable behavior, please reach out to a community moderator as soon as possible. + +We encourage reaching out to a community moderator, even if you are unsure whether something counts as a Code of Conduct incident or even if the situation is merely something you observed and did not happen to you directly. + +Please reach out as soon as possible if: + +* You would like to discuss any concerns. +* You have personally experienced unacceptable or potentially unacceptable behavior. +* You want to report a situation happening to someone else. + + +## Addressing Code of Conduct reports + +All complaints will be reviewed and investigated promptly and fairly. +If possible, community moderators will recuse themselves in cases where there is a conflict of interest. +See our {link to your [Code of Conduct response plan](template-code-of-conduct-response-plan.md)} for more details. + +An internal record will be kept of all incidents. +However, all community leaders are obligated to respect the privacy and security of the reporter of any incident. +In some cases, community moderators may determine that a public statement will need to be made. +If that's the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise. + +If you feel you have been unfairly accused of violating these guidelines, please follow the [same process for reporting a Code of Conduct incident](#reporting-an-incident). + + +## Where this Code of Conduct applies + +These guidelines apply to all members of the {Project name} and to all {Project name} activities, including but not limited to: + +- Representing the {Project name} at public events and in social media. +- Participating in the {Project name} meetings and events, whether virtual or in person. +- Participating in the {Project name}’s related messaging forums, including our Slack workspace and mailing list and other {Project name}-related correspondence. +- Interpersonal communications between {Project name} community members, whether virtual or in person. + +While this Code of Conduct applies specifically to the {Project name}’s work and community, it is possible for actions taken outside of the{Project name}’s online or in-person spaces to have a deep impact on community health if it concerns the {Project name} or its members in some way. +The Code of Conduct moderators reserve the right to consider communications or actions that occur outside of official {Project name} spaces if they have a demonstrated impact on one or more community members. + + +## Related resources + +{Include a list of links to related resources, such as your Code of Conduct Response Plan and the Our Team page where you list who can be contacted to report Code of Conduct incidents. +You can also include additional information, such as links to articles that explain the rationale behind your Code of Conduct.}