CoC definitions, enforcement, suggestions

[emmacunningham]

Thanks @zkourouma for getting us off to a great start w/ the Code of Conduct!

A few things:

• To what extent do we want to be explicit about what defines harassment? Specifically, I'm thinking about things like using gendered language ("hey guys"), racist and racially coded language, ableist language, transphobic language (misgendering, biological essentialism, etc), and just a lot of stuff that "well meaning people" often have a hard time with. There is also the stuff specific to unfortunately common experiences for women in tech spaces (being stalked, groped, threatened, etc) that of course we hope would never happen at one of our events but is prevalent enough that I wonder if we need to call that out. Double Union has a list of examples of harassment that we might take some inspiration.
• Should organizers be the go-to for enforcement of the CoC? If something happens and an attendee reports it to an organizer, what is the organizer's responsibility? Should they inform the other organizers about what happened? And how is the situation handled with respect to both the person who is the target of harassment and the person who caused it?
• A suggestion for an addition to the doc as I've seen this happen a lot: Don't take the keyboard away (instead of dialoguing with the person on how to do something)
• Another suggestion from the WriteSpeakCode CoC - When someone let's you know that something you've said or done is problematic, consider impact over intention. That means addressing the issue brought to you first before you start off with "Well that's not what I meant..." etc.

Not sure we want to break these out into separate issues or just discuss them here.

[zkourouma]

1. i think including specific examples is good, especially if we can also emphasize that harassment is not limited to the examples we outline. but to your point, giving people language to articulate what happened could help encourage reporting when incidents occur.
2. regarding enforcement, we should be consistent across events (regardless of who organized, location, etc), but beyond that i'd defer to others with more experience.
3. i really like this "dont take the keyboard away" idea! pr here
4. i like the "impact over intention" guidance because it gives tools to those involved to resolve the issue without escalating it.

[anup-the-magic]

Stumbled on this -- I think we cover most of it, but I really like the "Low effort criticism", "easy/trivial", and backseat driving sections (backseat driving probably fits nicely in the "don't take the keyboard away")