COC

Show me your Code of Conduct or I don’t go

A quick declaration:

I’ve been thinking about which events I should and should not be attending this year. There are so many, it’s hard to choose. One of the issues that I’ve been becoming increasingly aware of is the importance of a code of conduct to so many people in our industry. Many folks feel uncomfortable attending events if there is not a code of conduct.

It’s such an easy thing to do. I like the PipelineConf code of conduct which is why I pinched it for SpeakingMentors. Now SpeakingMentors is a fast growing community I’m going to be reviewing it with the others to ensure it meets our needs. It really doesn’t have to be any more complicated than that.

It’s sad that these are necessary nowadays, but they are. If you don’t believe me then they don’t exist for your benefit. And if you can’t agree to live by a set of rules which basically amount to being a decent human being you probably aren’t welcome at the event anyway.

So, until further notice:

While I/we will honour all existing commitments, neither I nor DLM Consultants will be taking part in any more events that do not have a code of conduct. 

That goes for taking part as an attendee, speaker, sponsor, helper or organiser. (SQL Relay will have a code of conduct for 2018.)

I encourage you to make this commitment too. If enough of us commit to this we will force all events to publish a code of conduct.

  2 comments for “Show me your Code of Conduct or I don’t go

  1. February 25, 2018 at 3:10 pm

    hi Alex, I agree with you about code of conduct – a simple and right thing to include.

    I wondered why you left age out of the list of attributes not to use as a reason to harass?

    Personally I think it ought to be included.

    • Alex Yates
      February 25, 2018 at 5:16 pm

      That’s a very good point.

      The honest answer is I pretty much cut and pasted it. I’ll raise it with the team.

Leave a Reply to Graham Coleman Cancel reply

Your email address will not be published. Required fields are marked *