Improve Code of Conduct

[lengarvey]

The problem

We should be looking to improve our code of conduct. For me the most problematic aspect of it is attribution to Jeff Casimir, a person who has publicly stated that:

I don’t believe the existence of a Code of Conduct has any real influence, so don’t care about #CoCPledge. They’re just words on a page. (source)

I find it highly ironic that a man who has stated such skepticism towards a Code of Conduct is listed an influence on ours.

Furthermore, people I've contacted privately find it problematic on a safety level making it less likely they'll want to attend our events.

So, I believe we should rewrite that second paragraph, and remove reference to Jeff from our CoC because it's sadly ironic and, more importantly, it's actively discourages diversity. We can also just cut the paragraph completely with absolutely no loss in clarity or function allowing us to directly remove the attribution to Jeff.

Other things we can improve on

• Consider revising the CoC to bring it more in line with: http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy. Ours isn't bad but the one there is considered the "gold standard".
• We should publish contact information, or at minimum have a policy that before events such as RailsCamp and RubyConf contact information for people handling incidents will be publically published.
• We should have a harrassment incident plan like: https://us.pycon.org/2013/about/code-of-conduct/harassment-incidents-staff/ and http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports

I'm happy to submit a PR if that would make things easier.

Thanks

[jcasimir]

I'm extremely hesitant to comment here.

The above quote is accurate, I don't deny it. In the course of that conversation I learned that many people see a Code of Conduct as (A) a response tool to bad behavior and (B) a clarification to concerned persons that their rights will be respected. I now understand that better.

My original understanding of a Code of Conduct is outlining your expected behavior with the intent of being instructive. I don't feel that potential bad-actors are going to read a Code of Conduct, which is why I referred to it as "words on a page." If organizers feel pressured into posting a CoC, especially one they didn't write, I'd worry that some of the original value is diminished.

I don't run a conference. I put some ideas together in a gist and shared them. I didn't know/remember that RubyConfAU took inspiration from that text. That's neat and really the only positive thing that's come out of it. I appreciate the footer shoutout, but would much rather have it removed then have any of the anger coming my way be directed at a great conference.

[ghost]

I don't feel that potential bad-actors are going to read a Code of Conduct, which is why I referred to it as "words on a page."

Does this mean that laws shouldn't exist, because people are just going to break them anyway?

You're right, there will be people out there that are terrible no matter what you tell them not to do, and when they eventually do terrible things, having "words on a page" that explain exactly why somebody is doing something wrong comes in handy.

[jcasimir]

@grenuttag I agree with you, but laws I consider a "Penal Code" which is a little different. But, as I was saying above, if people feel that having the repercussions for bad actions in a CoC and the research says that's the right thing to do, then it should be done!

[notahat]

For anyone who hasn't seen it, Ashe Dryden has written an amazing Codes of Conduct 101.

In particular, see "What are some good examples of Codes of Conduct?".

[pat]

I think each of the bullet points @lengarvey has listed should definitely be addressed, and ideally in separate issues to keep things focused. @lengarvey when you have a spare moment, could you create each of those issues please?

Probably worth copying @notahat's links for the first of those, too.

[pat]

And further to all of this: my personal goal is to have each of the items @lengarvey's raised addressed and lock in the next version of Ruby Australia Code of Conduct at the upcoming general meeting in May at Rails Camp 15.

Though maybe a deadline of the end of March is even better, to avoid leaving everything to the last minute ;)