Keir Mierle | 72cae43 | 2021-04-10 02:03:40 -0700 | [diff] [blame] | 1 | .. _docs-code-of-conduct: |
| 2 | |
| 3 | =============== |
| 4 | Code of Conduct |
| 5 | =============== |
| 6 | |
| 7 | Our Pledge |
| 8 | ---------- |
| 9 | |
| 10 | In the interest of fostering an open and welcoming environment, we as |
| 11 | contributors and maintainers pledge to making participation in our project and |
| 12 | our community a harassment-free experience for everyone, regardless of age, body |
| 13 | size, disability, ethnicity, gender identity and expression, level of |
| 14 | experience, education, socio-economic status, nationality, personal appearance, |
| 15 | race, religion, or sexual identity and orientation. |
| 16 | |
| 17 | Our Standards |
| 18 | ------------- |
| 19 | Examples of behavior that contributes to creating a positive environment |
| 20 | include: |
| 21 | |
| 22 | * Using welcoming and inclusive language |
| 23 | * Being respectful of differing viewpoints and experiences |
| 24 | * Gracefully accepting constructive criticism |
| 25 | * Focusing on what is best for the community |
| 26 | * Showing empathy towards other community members |
| 27 | |
| 28 | Examples of unacceptable behavior by participants include: |
| 29 | |
| 30 | * The use of sexualized language or imagery and unwelcome sexual attention or |
| 31 | advances |
| 32 | * Trolling, insulting/derogatory comments, and personal or political attacks |
| 33 | * Public or private harassment |
| 34 | * Publishing others' private information, such as a physical or electronic |
| 35 | address, without explicit permission |
| 36 | * Other conduct which could reasonably be considered inappropriate in a |
| 37 | professional setting |
| 38 | |
| 39 | Our Responsibilities |
| 40 | -------------------- |
| 41 | Project maintainers are responsible for clarifying the standards of acceptable |
| 42 | behavior and are expected to take appropriate and fair corrective action in |
| 43 | response to any instances of unacceptable behavior. |
| 44 | |
| 45 | Project maintainers have the right and responsibility to remove, edit, or reject |
| 46 | comments, commits, code, wiki edits, issues, and other contributions that are |
| 47 | not aligned to this Code of Conduct, or to ban temporarily or permanently any |
| 48 | contributor for other behaviors that they deem inappropriate, threatening, |
| 49 | offensive, or harmful. |
| 50 | |
| 51 | Scope |
| 52 | ----- |
| 53 | This Code of Conduct applies both within project spaces and in public spaces |
| 54 | when an individual is representing the project or its community. Examples of |
| 55 | representing a project or community include using an official project e-mail |
| 56 | address, posting via an official social media account, or acting as an |
| 57 | appointed representative at an online or offline event. Representation of a |
| 58 | project may be further defined and clarified by project maintainers. |
| 59 | |
| 60 | This Code of Conduct also applies outside the project spaces when the Project |
| 61 | Steward has a reasonable belief that an individual's behavior may have a |
| 62 | negative impact on the project or its community. |
| 63 | |
| 64 | Conflict Resolution |
| 65 | ------------------- |
| 66 | We do not believe that all conflict is bad; healthy debate and disagreement |
| 67 | often yield positive results. However, it is never okay to be disrespectful or |
| 68 | to engage in behavior that violates the project’s code of conduct. |
| 69 | |
| 70 | If you see someone violating the code of conduct, you are encouraged to address |
| 71 | the behavior directly with those involved. Many issues can be resolved quickly |
| 72 | and easily, and this gives people more control over the outcome of their |
| 73 | dispute. If you are unable to resolve the matter for any reason, or if the |
| 74 | behavior is threatening or harassing, report it. We are dedicated to providing |
| 75 | an environment where participants feel welcome and safe. |
| 76 | |
| 77 | Reports should be directed to Pigweed Community Managers at |
| 78 | pigweed-community-managers@google.com, the Project Steward(s) for Pigweed. It |
| 79 | is the Project Steward’s duty to receive and address reported violations of the |
| 80 | code of conduct. They will then work with a committee consisting of |
| 81 | representatives from the Open Source Programs Office and the Google Open Source |
| 82 | Strategy team. If for any reason you are uncomfortable reaching out the Project |
| 83 | Steward, please email opensource@google.com. |
| 84 | |
| 85 | **We will investigate every complaint**, but you may not receive a direct |
| 86 | response. We will use our discretion in determining when and how to follow up |
| 87 | on reported incidents, which may range from not taking action to permanent |
| 88 | expulsion from the project and project-sponsored spaces. We will notify the |
| 89 | accused of the report and provide them an opportunity to discuss it before any |
| 90 | action is taken. The identity of the reporter will be omitted from the details |
| 91 | of the report supplied to the accused. In potentially harmful situations, such |
| 92 | as ongoing harassment or threats to anyone's safety, we may take action without |
| 93 | notice. |
| 94 | |
| 95 | Attribution |
| 96 | ----------- |
| 97 | This Code of Conduct is adapted from `Contributor Covenant version 1.4 |
| 98 | <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>`_ |