rfc: enforcement steps in coc (#40)

* rfc: enforcement steps in coc

* enforcement: remove concrete enforcement steps

* coc: Add enforcement steps directly to CoC

* site: remove references to enforcement doc from homepage

* postsignup: remove reference to enforcement doc

Author: zkat

_layouts/default.html

@@ -21,7 +21,6 @@
       <ul>
         <li><a href="/">Home</a></li>
         <li><a href="/code-of-conduct.html">Code of Conduct</a></li>
-        <li><a href="/enforcement.html">CoC Enforcement</a></li>
         <li><a href="/culture-and-process.html">Culture and Processes</a></li>
       </ul>
     </div>

_pages/code-of-conduct.md

@@ -6,6 +6,19 @@ permalink: /code-of-conduct
 
 # WeAllJS Code of Conduct
 
+## When Something Happens
+
+If you see a Code of Conduct violation, follow these steps:
+
+1. Let the person know that what they did is not appropriate and ask them to stop and/or edit their message(s).
+2. That person should immediately stop the behavior and correct the issue.
+3. If this doesn’t happen, or if you're uncomfortable speaking up, [contact admins](#contacting-admins).
+4. As soon as available, an admin will join, identify themselves, and take [further action (see below)](#further-enforcement), starting with a warning, then temporary deactivation, then long-term deactivation.
+
+When reporting, please include any relevant details, links, screenshots, context, or other information that may be used to better understand and resolve the situation.
+
+**The Admin 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).
+
 ## Our Pledge
 
 In the interest of fostering an open and welcoming environment, we as members of the WeAllJS community 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.
@@ -36,36 +49,92 @@ Examples of unacceptable behavior by participants include:
   * "[Well-actuallies](https://www.recurse.com/manual#no-well-actuallys)"
   * Other conduct which could reasonably be considered inappropriate in a professional or community setting.
 
-## Our Responsibilities
-
-Community admins are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Admins have the right and responsibility to remove any messages, channels, images, or other contributions that are not aligned with this Code of Conduct, or to ban temporarily or permanently any member or participant for other behaviors that they deem inappropriate, threatening, offensive, or harmful. Members expelled from events or venues with any sort of paid attendance will not be refunded.
-
 ## Scope
 
 This Code of Conduct applies both within community spaces and in other spaces involving the community. This includes the WeAllJS Slack, its Twitter community, private email communications in the context of the community, and any events where members of the community are participating, as well as adjacent communities and venues affecting the community's members.
 
 Depending on the violation, the admins 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.
 
-## Enforcement
+## Admin Enforcement Process
 
-**The Admin team will prioritize the well-being and comfort of the recipients of the violation over the comfort of the violator.**
+Once the admins get involved, they will follow a documented series of steps and do their best to preserve the well-being of WeAllJS members. This section covers actual concrete steps. For further information/details on values and practices that admins will generally apply when enforcing the Code of Conduct, refer to [the full enforcement document](http://wealljs.org/enforcement).
 
-The detailed enforcement procedure for any violation of the WeAllJS community standards can be found at the [Enforcement Procedures](/enforcement) page.
+### Contacting Admins
 
-[tl;dr](https://en.wikipedia.org/wiki/TL%3BDR): Mention the issue to the person involved, if possible, and if needed, use one of the following methods to contact the admin staff when you believe a violation has occurred:
+You may get in touch with the WeAllJS admin team through any of the following methods:
 
   * Use the `/admin` command in the WeAllJS Slack to send a message directly to the admin channel.
-  * Direct Message [@WeAllJS](https://twitter.com/wealljs) on Twitter with the details and any relevant links.
-  * Email the admins directly at [coc@wealljs.org](mailto:coc@wealljs.org)
   * Directly message any admin in private (through either Twitter, Slack, or email, as available) if it is a preferred or more comfortable avenue.
+  * Use the `/join-private #wealladmin` command for a private conversation with all admins.
+  * Email the admins directly at [coc@wealljs.org](mailto:coc@wealljs.org)
+  * Direct Message [@WeAllJS](https://twitter.com/wealljs) on Twitter with the details and any relevant links.
+
+In Slack, `?admins` will list the names of all current admins.
+
+### Further Enforcement
+
+If you've already followed the [initial enforcement steps](#enforcement), these are the steps admins will take for further enforcement, as needed:
+
+  1. Repeat the request to stop.
+  2. If the person doubles down, they will be removed from the channel and given an official warning.
+  3. If the behavior continues or is repeated later, the person will be deactivated for 24 hours.
+  4. If the behavior continues or is repeated after the temporary deactivation, a long-term (6-12mo) deactivation will be used.
+
+On top of this, admins may remove any offending messages, images, contributions, etc, as they deem necessary.
+
+Admins 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.
+
+Members expelled from events or venues with any sort of paid attendance will not be refunded.
+
+### Who Watches the Watchers?
+
+Admins 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 community's leadership. These may include anything from removal from the admin team to a permanent ban from the community.
+
+### Enforcement Examples
+
+#### The Best Case
+
+The vast majority of situations work out like this, in our experience. This interaction is common, and generally positive.
+
+> Alex: "Yeah I used X and it was really crazy!"
+
+> Patt: "Hey, could you not use that word? What about 'ridiculous' instead?"
+
+> Alex: "oh sorry, sure." -> edits old message to say "it was really confusing!"
+
+#### The Admin Case
+
+Sometimes, though, you need to get admins involved. Admins will do their best to resolve conflicts, but people who were harmed by something **will take priority**.
+
+> Patt: "Honestly, sometimes I just really hate using $library and anyone who uses it probably sucks at their job."
+
+> Alex: "Whoa there, could you dial it back a bit? There's a CoC thing about attacking folks' tech use like that."
+
+> Patt: "I'm not attacking anyone, are you deaf?"
+
+> Alex: "/admin hey uh. Can someone look at #javascript? Patt is getting a bit aggro. I tried to nudge them about it, but nope."
+
+> MxAdmin1: <joins #javascript> "Hey Patt, admin here. Could you tone it down? This sort of attack is really not okay in this space."
+
+> Patt: "Leave me alone I haven't said anything bad wtf is wrong with you."
+
+> MxAdmin1: "/remove @patt", "/msg @patt I mean it. Please refer to the CoC over at wealljs.org/code-of-conduct if you have questions, but you can consider this an actual warning. I'd appreciate it if you reworded your messages in #javascript, since they made folks there uncomfortable. Let's try and be kind, yeah?"
+
+> Patt: "/msg @mxadmin1 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."
+
+> MxAdmin1: "/msg @patt Thanks for that. I hear you on the stress. Burnout sucks :/.  Have a good one!"
+
+#### The Nope Case
+
+> PepeTheFrog🐸: "Hi, I am a literal actual nazi and I think white supremacists are quite fashionable."
+
+> Patt: "NOOOOPE. OH NOPE NOPE."
 
-Please include any relevant details, links, screenshots, context, or other information that may be used to better understand and resolve the situation.
+> Alex: "JFC NO. NOPE. `/admin nope nope nope @ #javascript`"
 
-The admin team will do its best to address the issue in a timely manner and follow the [enforcement procedure](/enforcement). They will, within reason, keep you up to date on progress and do their best to respect reasonable boundaries.
+> MxAdmin1: "👀 Nope. NOPE NOPE NOPE. 🔥"
 
-Admins 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 community's leadership.
+> PepeTheFrog🐸 has been deactivated.
 
 ## Attribution
 

_pages/enforcement.md

@@ -4,18 +4,20 @@ title: "Enforcement"
 permalink: /enforcement
 ---
 
-# Code of Conduct Enforcement
-
-## tl;dr
-
-  1. Tell someone "hey, that's not ok".
-  2. That person should apologize immediately and correct the behavior.
-  3. If this doesn't happen, isn't safe to do, or is not satisfactory, message admins.
-  4. Admins will take appropriate action in a timely manner, prioritizing those who were hurt.
+# Code of Conduct Enforcement Philosophy
 
 ## Introduction
 
-No matter how kind or nice people think they are, at some point, someone's gonna say Some Shit:tm: and things are going to go awry. This document is meant as a writeup and guideline holding core values about what this community considers the best approach to resolving these conflicts in a kind and positive way, as much as possible. It is paired with the community's [Code of Conduct](/code-of-conduct). It is a living document, informed by new problems, new conflicts, and always strives to help make the WeAllJS community successful while including the voices of those who are too often not heard.
+No matter how kind or nice people think they are, at some point, someone's gonna
+say Some Shit:tm: and things are going to go awry. This document is meant as a
+writeup and guideline holding core values about what this community considers
+the best approach to resolving these conflicts in a kind and positive way, as
+much as possible. It is paired with the community's [Code of
+Conduct](/code-of-conduct), which includes the concrete enforcement steps.
+
+It is a living document, informed by new problems, new conflicts, and always
+strives to help make the WeAllJS community successful while including the voices
+of those who are too often not heard.
 
 ## Guiding Principles
 
@@ -30,14 +32,3 @@ This guide is opinionated, and it considers the following to be core values that
   7. **Trust the Ouch**: It's more likely that if someone says they're hurt, they really are hurt, and you should listen and trust them on it, even (and especially if) you don't understand why or how.
   8. **Education is Emotional Labor**: and the one who was hurt does not owe you an explanation or a 101. It's ok to expect people to do their own thinking and research when told there was a wrong, and correct the behavior, instead of placing undue burden on someone who's already been hurt or who is already frustrated with the situation.
   9. **Support is something we can promise -- not Safety**: We don't believe safety, as a general thing is something we can reasonable promise members of a community. Harm comes suddenly, often unexpectedly. Instead, we believe it's a more worthwhile endeavor to try and prevent harm from happening through education, documentation, and policy, and build trust with the community that **when** something happens, they won't have to fight tooth and nail for even basic fairness.
-
-## When an Admin Gets involved
-
-  1. Admin will identify themself as an admin of this community, and assert their role in maintaining the well-being of this space.
-  2. The Admin will remind the user of the CoC and point out their behavior
-  3. Admin should stick to/reference what was said in the conversation
-  4. Admin should suggest an alternative behavior (rephrasing using specific language, moving the conversation to another channel if it's offtopic)
-  5. If behavior persists, the violators will be removed from the specific channel (`/remove`).
-  6. Admin will give them a warning via DM and have them read the CoC again.
-  7. If a problem still persists with user after a warning, their account should be disabled for 12-24 hours, with an explanation to return after that time.
-  8. If the problem still continues with a user, or the violation is so flagrant, endangering, or otherwise harmful, the user's account will be permanently disabled. Determining whether a violation is serious enough to warrant permanent banning is ultimately up to the admin, who should consult with those who felt harmed by the particular actions.

_pages/postsignup.md

@@ -11,7 +11,7 @@ policy](http://wealljs.org/rfc-signup) for more info.
 
 In the meantime, here's some stuff to keep handy:
 
-* [Code of Conduct](/code-of-conduct.html) and [Enforcement](/enforcement.html) policies
+* [Code of Conduct](/code-of-conduct.html)
 * [Culture and Process](/culture-and-process.html) notes about how the WeAllJS handles regular community stuff, how it’s organized, and all that.
 * The list of [private ("identity") channels](https://slack-files.com/T1WSA6TGQ-F27V6KM1C-5335c58dd0). You can request an invite to any of these using the `/join-private #channelname` command once you're logged in.
 * The list of [public ("resource") channels](https://slack-files.com/T1WSA6TGQ-F27V51W22-821023e17a).