Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Abstract over examples of abuse #43

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Abstract over examples of abuse #43

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions _pages/code-of-conduct.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,27 +96,27 @@ Admins and other leaders who do not follow or enforce the Code of Conduct in goo

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!"
> Alex: "Yeah I used X and it was [negative association with mental health]"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice. Good point that including the language itself can server to unnecessarily re-traumatize.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many many people wouldn't know that kind of words that would involve, so could we link to this document: https://wealljs.org/rfc-slackbot-language-shorthands?

I know that you don't want us to use these words in our documentation (i agree), but people need to know what we dont tolerate and mental health slurs are so ingrained in our culture.


> Patt: "Hey, could you not use that word? What about 'ridiculous' instead?"
> Patt: "Hey, could you not say that? 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."
> Patt: [disparaging comment about users of $library]

> 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?"
> Patt: [defends words by attacking Alex's comprehension]

> 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."
> Patt: "Leave me alone I haven't said anything bad [aggressive jab]."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that [aggressive jab] here isn't even required; rejecting MxAdmin1's comments would be bad enough without attacking the admin.


> 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?"

Expand Down