|
1 | | ---- |
2 | | ---- |
| 1 | +## Community Participation Guidelines |
3 | 2 |
|
4 | | -# Developer Tools Code of Conduct |
| 3 | +This repository is governed by Mozilla's code of conduct and etiquette guidelines. |
| 4 | +For more details, please read |
| 5 | +[Mozilla Community Participation Guidelines](https://www.mozilla.org/about/governance/policies/participation/). |
5 | 6 |
|
6 | | -This file describes the Developer Tools (aka "DevTools") code of conduct. |
| 7 | +## How to Report |
7 | 8 |
|
8 | | -# Conduct |
| 9 | +For more information on how to report violations of the Community Participation Guidelines, please read our '[How to Report](https://www.mozilla.org/en-US/about/governance/policies/participation/reporting/)' page. |
9 | 10 |
|
10 | | -We are committed to providing a friendly, safe and welcoming |
11 | | -environment for all, regardless of level of experience, gender, gender |
12 | | -identity and expression, sexual orientation, disability, personal |
13 | | -appearance, body size, race, ethnicity, age, religion, nationality, or |
14 | | -other similar characteristic. |
15 | | - |
16 | | -On IRC, please avoid using overtly sexual nicknames or other nicknames |
17 | | -that might detract from a friendly, safe and welcoming environment for |
18 | | -all. |
19 | | - |
20 | | -Please be kind and courteous. There’s no need to be mean or rude. |
21 | | - |
22 | | -Respect that people have differences of opinion and that every design |
23 | | -or implementation choice carries a trade-off and numerous costs. There |
24 | | -is seldom a right answer. |
25 | | - |
26 | | -We will exclude you from interaction if you insult, demean or harass |
27 | | -anyone. That is not welcome behaviour. We interpret the term |
28 | | -“harassment” as including the definition in the |
29 | | -[Citizen Code of Conduct](http://citizencodeofconduct.org/); if you |
30 | | -have any lack of clarity about what might be included in that concept, |
31 | | -please read their definition. In particular, we don’t tolerate |
32 | | -behavior that excludes people in socially marginalized groups. |
33 | | - |
34 | | -Private harassment is also unacceptable. No matter who you are, if you |
35 | | -feel you have been or are being harassed or made uncomfortable by a |
36 | | -community member, please contact one of the moderators (see below) |
37 | | -immediately. Whether you’re a regular contributor or a newcomer, we |
38 | | -care about making this community a safe place for you and we’ve got |
39 | | -your back. |
40 | | - |
41 | | -Likewise any spamming, trolling, flaming, baiting or other |
42 | | -attention-stealing behaviour is not welcome. |
43 | | - |
44 | | -# Moderation |
45 | | - |
46 | | -These are the policies for upholding our community’s standards of |
47 | | -conduct. If you feel that a thread needs moderation, please use the |
48 | | -point of contact for the medium in which you're communicating: |
49 | | - |
50 | | -* For one of the IRC channels, contact a channel operator (they |
51 | | - have an "@" in front of their names); |
52 | | -* Bugzilla and the dev-developer-tools mailing list, contact |
53 | | - |
54 | | -* The debugger.html repository on GitHub has [its own code of conduct](https://github.com/devtools-html/debugger.html/blob/master/CODE_OF_CONDUCT.md), but you can also |
55 | | - |
56 | | - |
57 | | -Remarks that violate these standards of conduct, including hateful, |
58 | | -hurtful, oppressive, or exclusionary remarks, are not |
59 | | -allowed. (Cursing is allowed, but never targeting another user, and |
60 | | -never in a hateful manner.) |
61 | | - |
62 | | -Remarks that moderators find inappropriate, whether listed in the code |
63 | | -of conduct or not, are also not allowed. |
64 | | - |
65 | | -Moderators will first respond to such remarks with a warning. |
66 | | - |
67 | | -If the warning is unheeded, then on IRC the user will be “kicked,” |
68 | | -i.e., kicked out of the communication channel to cool off. |
69 | | - |
70 | | -If the user comes back and continues to make trouble, they will be |
71 | | -banned, i.e., indefinitely excluded. On other communications media, |
72 | | -such as bugzilla or mailing lists, it will be up to the moderator's |
73 | | -discretion whether a user will be banned after the first warning. |
74 | | - |
75 | | -Moderators may choose at their discretion to un-ban the user if it was |
76 | | -a first offense and they offer the offended party a genuine apology. |
77 | | - |
78 | | -If a moderator bans someone and you think it was unjustified, please |
79 | | -take it up with that moderator, or with a different moderator, in |
80 | | -private. Complaints about bans in-channel (or on the mailing list or |
81 | | -in the bug tracker) are not allowed. |
82 | | - |
83 | | -Moderators are held to a higher standard than other community |
84 | | -members. If a moderator creates an inappropriate situation, they |
85 | | -should expect less leeway than others. |
86 | | - |
87 | | -In this community we strive to go the extra step to look out for |
88 | | -each other. Don’t just aim to be technically unimpeachable, try to be |
89 | | -your best self. In particular, avoid flirting with offensive or |
90 | | -sensitive issues, particularly if they’re off-topic; this all too |
91 | | -often leads to unnecessary fights, hurt feelings, and damaged trust; |
92 | | -worse, it can drive people away from the community entirely. |
93 | | - |
94 | | -And if someone takes issue with something you said or did, resist the |
95 | | -urge to be defensive. Just stop doing what it was they complained |
96 | | -about and apologize. Even if you feel you were misinterpreted or |
97 | | -unfairly accused, chances are good there was something you could’ve |
98 | | -communicated better — remember that it’s your responsibility to make |
99 | | -your fellow devtoolers comfortable. Everyone wants to get along and we |
100 | | -are all here first and foremost because we want to talk about cool |
101 | | -technology. You will find that people will be eager to assume good |
102 | | -intent and forgive as long as you earn their trust. |
103 | | - |
104 | | -The enforcement policies listed above apply to all official DevTools |
105 | | -venues; including official IRC channels (those starting with |
106 | | -"#devtools"); GitHub repositories associated with DevTools; and |
107 | | -DevTools bugs in bugzilla. |
108 | | - |
109 | | -# Also Applicable |
110 | | - |
111 | | -The |
112 | | -[Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/) |
113 | | -also apply. Please read these as well. |
114 | | - |
115 | | -# History |
116 | | - |
117 | | -This was derived from the |
118 | | -[Rust Code of Conduct](https://www.rust-lang.org/en-US/conduct.html). |
119 | | - |
120 | | -See [bug 1315344](https://bugzilla.mozilla.org/show_bug.cgi?id=1315344) if |
121 | | -you are curious about the genesis of this document. |
| 11 | +## Project Specific Guidelines |
122 | 12 |
|
| 13 | +- Be nice to each other |
| 14 | +- Remember that we are all humans, and we are all on the same team |
| 15 | +- Self-care is of utmost importance (take breaks, eat food, plenty of sleep) |
| 16 | +- "Please" and "Thank you" are always nice ways to facilitate communication |
| 17 | +- Have fun |
0 commit comments