brettw | bc324cb85 | 2016-02-25 21:55:35 | [diff] [blame] | 1 | # Chromium Code of Conduct |
| 2 | |
| 3 | Google and the Chromium team are committed to preserving and fostering a |
| 4 | diverse, welcoming community. Below is our community code of conduct, which |
cbentzel | dcad087 | 2017-05-30 13:06:39 | [diff] [blame] | 5 | applies to our repos and organizations, issue trackers, mailing lists, |
| 6 | blog content, and any other Chromium-supported communication group, as |
| 7 | well as any private communication initiated in the context of these |
Mike Lawther | 4bbcf2e | 2017-12-01 20:15:13 | [diff] [blame] | 8 | spaces. This code of conduct must be followed by everyone contributing to |
| 9 | the Chromium project, regardless of affiliation or position. |
brettw | bc324cb85 | 2016-02-25 21:55:35 | [diff] [blame] | 10 | |
| 11 | Simply put, community discussions should be |
| 12 | |
| 13 | * respectful and kind; |
| 14 | * about Chromium; |
| 15 | * about features and code, not the individuals involved. |
| 16 | |
| 17 | ## Be respectful and constructive. |
| 18 | |
avallee | a4967ca | 2016-03-01 23:45:32 | [diff] [blame] | 19 | Treat everyone with respect. Build on each other's ideas. Each of us has the |
brettw | bc324cb85 | 2016-02-25 21:55:35 | [diff] [blame] | 20 | right to enjoy our experience and participate without fear of harassment, |
| 21 | discrimination, or condescension, whether blatant or subtle. Remember that |
| 22 | Chromium is a geographically distributed team and that you may not be |
| 23 | communicating with someone in their primary language. We all get frustrated |
| 24 | when working on hard problems, but we cannot allow that frustration to turn |
| 25 | into personal attacks. |
| 26 | |
| 27 | ## Speak up if you see or hear something. |
| 28 | |
| 29 | You are empowered to politely engage when you feel that you or others are |
| 30 | disrespected. The person making you feel uncomfortable may not be aware of what |
| 31 | they are doing - politely bringing their behavior to their attention is |
| 32 | encouraged. |
| 33 | |
| 34 | If you are uncomfortable speaking up, or feel that your concerns are not being |
Dirk Pranke | 2f76bca | 2019-02-05 18:52:00 | [diff] [blame] | 35 | duly considered, you can email [email protected], [email protected], or |
groby | 481b8f8 | 2016-08-26 02:01:05 | [diff] [blame] | 36 | [email protected] to request involvement from a community manager. All |
| 37 | concerns shared with community managers will be kept confidential, but you may |
| 38 | also submit an anonymous report [here](https://docs.google.com/a/google.com/forms/d/e/1FAIpQLSe-LDjW9eIJ-TpI2poZxnGtU-SvUWkFZc8x0aiKGY1s7NKPdA/viewform?c=0&w=1). |
| 39 | Please note that without a way to contact you, an anonymous report may be |
| 40 | difficult to act on. You may also create a throwaway account to report. In |
| 41 | cases where a public response is deemed necessary, the identities of victims |
| 42 | and reporters will remain confidential unless those individuals instruct us |
| 43 | otherwise. |
| 44 | |
brettw | bc324cb85 | 2016-02-25 21:55:35 | [diff] [blame] | 45 | While all reports will be taken seriously, the Chromium community managers may |
| 46 | not act on complaints that they feel are not violations of this code of |
| 47 | conduct. |
| 48 | |
| 49 | ## We will not tolerate harassment of any kind, including but not limited to: |
| 50 | |
| 51 | * Harassing comments |
| 52 | * Intimidation |
| 53 | * Encouraging a person to engage in self-harm. |
| 54 | * Sustained disruption or derailing of threads, channels, lists, etc. |
| 55 | * Offensive or violent comments, jokes or otherwise |
| 56 | * Inappropriate sexual content |
| 57 | * Unwelcome sexual or otherwise aggressive attention |
| 58 | * Continued one-on-one communication after requests to cease |
avallee | a4967ca | 2016-03-01 23:45:32 | [diff] [blame] | 59 | * Distribution or threat of distribution of people's personally identifying |
| 60 | information, AKA “doxing” |
brettw | bc324cb85 | 2016-02-25 21:55:35 | [diff] [blame] | 61 | |
| 62 | ## Consequences for failing to comply with this policy |
| 63 | |
| 64 | Consequences for failing to comply with this policy may include, at the sole |
| 65 | discretion of the Chromium community managers: |
| 66 | |
| 67 | * a request for an apology; |
| 68 | * a private or public warning or reprimand; |
| 69 | * a temporary ban from the mailing list, blog, Chromium repository or |
| 70 | organization, or other Chromium-supported communication group, including |
| 71 | loss of committer status; |
| 72 | * a permanent ban from any of the above, or from all current and future |
| 73 | Chromium-supported or Google-supported communities, including loss of |
| 74 | committer status. |
| 75 | |
| 76 | Participants warned to stop any harassing behavior are expected to comply |
| 77 | immediately; failure to do so will result in an escalation of consequences. |
| 78 | |
brettw | bc324cb85 | 2016-02-25 21:55:35 | [diff] [blame] | 79 | ## Acknowledgements |
| 80 | |
| 81 | This Code of Conduct is based on the Geek Feminism Code of Conduct, the Django |
| 82 | Code of Conduct and the Geek Feminism Wiki "Effective codes of conduct" guide. |
| 83 | |
| 84 | ## License |
| 85 | |
| 86 | This Code of Conduct is available for reuse under the Creative Commons Zero |
| 87 | (CC0) license. |