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