1# Code of Conduct 2 3## When Something Happens 4 5If you see a Code of Conduct violation, follow these steps: 6 71. Let the person know that what they did is not appropriate and ask them to stop and/or edit their message(s) or commits. 82. That person should immediately stop the behavior and correct the issue. 93. If this doesn’t happen, or if you're uncomfortable speaking up, [contact the maintainers](#contacting-maintainers). 104. As soon as available, a maintainer will look into the issue, and take [further action (see below)](#further-enforcement), starting with a warning, then temporary block, then long-term repo or organization ban. 11 12When reporting, please include any relevant details, links, screenshots, context, or other information that may be used to better understand and resolve the situation. 13 14**The maintainer team will prioritize the well-being and comfort of the recipients of the violation over the comfort of the violator.** See [some examples below](#enforcement-examples). 15 16## Our Pledge 17 18In the interest of fostering an open and welcoming environment, we as contributors and maintainers of this project pledge to making participation in our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, technical preferences, nationality, personal appearance, race, religion, or sexual identity and orientation. 19 20## Our Standards 21 22Examples of behavior that contributes to creating a positive environment include: 23 24 * Using welcoming and inclusive language. 25 * Being respectful of differing viewpoints and experiences. 26 * Gracefully accepting constructive feedback. 27 * Focusing on what is best for the community. 28 * Showing empathy and kindness towards other community members. 29 * Encouraging and raising up your peers in the project so you can all bask in hacks and glory. 30 31Examples of unacceptable behavior by participants include: 32 33 * The use of sexualized language or imagery and unwelcome sexual attention or advances, including when simulated online. The only exception to sexual topics is channels/spaces specifically for topics of sexual identity. 34 * Casual mention of slavery or indentured servitude and/or false comparisons of one's occupation or situation to slavery. Please consider using or asking about alternate terminology when referring to such metaphors in technology. 35 * Making light of/making mocking comments about trigger warnings and content warnings. 36 * Trolling, insulting/derogatory comments, and personal or political attacks. 37 * Public or private harassment, deliberate intimidation, or threats. 38 * Publishing others' private information, such as a physical or electronic address, without explicit permission. This includes any sort of "outing" of any aspect of someone's identity without their consent. 39 * Publishing private screenshots or quotes of interactions in the context of this project without all quoted users' *explicit* consent. 40 * Publishing of private communication that doesn't have to do with reporting harassment. 41 * Any of the above even when [presented as "ironic" or "joking"](https://en.wikipedia.org/wiki/Hipster_racism). 42 * Any attempt to present "reverse-ism" versions of the above as violations. Examples of reverse-isms are "reverse racism", "reverse sexism", "heterophobia", and "cisphobia". 43 * Unsolicited explanations under the assumption that someone doesn't already know it. Ask before you teach! Don't assume what people's knowledge gaps are. 44 * [Feigning or exaggerating surprise](https://www.recurse.com/manual#no-feigned-surprise) when someone admits to not knowing something. 45 * "[Well-actuallies](https://www.recurse.com/manual#no-well-actuallys)" 46 * Other conduct which could reasonably be considered inappropriate in a professional or community setting. 47 48## Scope 49 50This Code of Conduct applies both within spaces involving this project and in other spaces involving community members. This includes the repository, its Pull Requests and Issue tracker, its Twitter community, private email communications in the context of the project, and any events where members of the project are participating, as well as adjacent communities and venues affecting the project's members. 51 52Depending on the violation, the maintainers may decide that violations of this code of conduct that have happened outside of the scope of the community may deem an individual unwelcome, and take appropriate action to maintain the comfort and safety of its members. 53 54### Other Community Standards 55 56As a project on GitHub, this project is additionally covered by the [GitHub Community Guidelines](https://help.github.com/articles/github-community-guidelines/). 57 58Enforcement of those guidelines after violations overlapping with the above are the responsibility of the entities, and enforcement may happen in any or all of the services/communities. 59 60## Maintainer Enforcement Process 61 62Once the maintainers get involved, they will follow a documented series of steps and do their best to preserve the well-being of project members. This section covers actual concrete steps. 63 64### Contacting Maintainers 65 66You may get in touch with the maintainer team through any of the following methods: 67 68 * Through email: 69 * [[email protected]](mailto:[email protected]) (Kat Marchán) 70 71 * Through Twitter: 72 * [@zkat__](https://twitter.com/zkat__) (Kat Marchán) 73 74### Further Enforcement 75 76If you've already followed the [initial enforcement steps](#enforcement), these are the steps maintainers will take for further enforcement, as needed: 77 78 1. Repeat the request to stop. 79 2. If the person doubles down, they will have offending messages removed or edited by a maintainers given an official warning. The PR or Issue may be locked. 80 3. If the behavior continues or is repeated later, the person will be blocked from participating for 24 hours. 81 4. If the behavior continues or is repeated after the temporary block, a long-term (6-12mo) ban will be used. 82 83On top of this, maintainers may remove any offending messages, images, contributions, etc, as they deem necessary. 84 85Maintainers reserve full rights to skip any of these steps, at their discretion, if the violation is considered to be a serious and/or immediate threat to the health and well-being of members of the community. These include any threats, serious physical or verbal attacks, and other such behavior that would be completely unacceptable in any social setting that puts our members at risk. 86 87Members expelled from events or venues with any sort of paid attendance will not be refunded. 88 89### Who Watches the Watchers? 90 91Maintainers and other leaders who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership. These may include anything from removal from the maintainer team to a permanent ban from the community. 92 93Additionally, as a project hosted on GitHub, [its own Codes of Conducts may be applied against maintainers of this project](#other-community-standards), externally of this project's procedures. 94 95### Enforcement Examples 96 97#### The Best Case 98 99The vast majority of situations work out like this. This interaction is common, and generally positive. 100 101> Alex: "Yeah I used X and it was really crazy!" 102 103> Patt (not a maintainer): "Hey, could you not use that word? What about 'ridiculous' instead?" 104 105> Alex: "oh sorry, sure." -> edits old comment to say "it was really confusing!" 106 107#### The Maintainer Case 108 109Sometimes, though, you need to get maintainers involved. Maintainers will do their best to resolve conflicts, but people who were harmed by something **will take priority**. 110 111> Patt: "Honestly, sometimes I just really hate using $library and anyone who uses it probably sucks at their job." 112 113> Alex: "Whoa there, could you dial it back a bit? There's a CoC thing about attacking folks' tech use like that." 114 115> Patt: "I'm not attacking anyone, what's your problem?" 116 117> Alex: "@maintainers hey uh. Can someone look at this issue? Patt is getting a bit aggro. I tried to nudge them about it, but nope." 118 119> KeeperOfCommitBits: (on issue) "Hey Patt, maintainer here. Could you tone it down? This sort of attack is really not okay in this space." 120 121> Patt: "Leave me alone I haven't said anything bad wtf is wrong with you." 122 123> KeeperOfCommitBits: (deletes user's comment), "@patt I mean it. Please refer to the CoC over at (URL to this CoC) if you have questions, but you can consider this an actual warning. I'd appreciate it if you reworded your messages in this thread, since they made folks there uncomfortable. Let's try and be kind, yeah?" 124 125> Patt: "@keeperofbits Okay sorry. I'm just frustrated and I'm kinda burnt out and I guess I got carried away. I'll DM Alex a note apologizing and edit my messages. Sorry for the trouble." 126 127> KeeperOfCommitBits: "@patt Thanks for that. I hear you on the stress. Burnout sucks :/. Have a good one!" 128 129#### The Nope Case 130 131> PepeTheFrog��: "Hi, I am a literal actual nazi and I think white supremacists are quite fashionable." 132 133> Patt: "NOOOOPE. OH NOPE NOPE." 134 135> Alex: "JFC NO. NOPE. @keeperofbits NOPE NOPE LOOK HERE" 136 137> KeeperOfCommitBits: "�� Nope. NOPE NOPE NOPE. ��" 138 139> PepeTheFrog�� has been banned from all organization or user repositories belonging to KeeperOfCommitBits. 140 141## Attribution 142 143This Code of Conduct was generated using [WeAllJS Code of Conduct Generator](https://npm.im/weallbehave), which is based on the [WeAllJS Code of 144Conduct](https://wealljs.org/code-of-conduct), which is itself based on 145[Contributor Covenant](http://contributor-covenant.org), version 1.4, available 146at 147[http://contributor-covenant.org/version/1/4](http://contributor-covenant.org/version/1/4), 148and the LGBTQ in Technology Slack [Code of 149Conduct](http://lgbtq.technology/coc.html). 150 151