rubyaustralia/ruby.org.au — pull request #21 by tjmcewan (2013-10-16 10:23:58+00:00)
Title: Code of conduct

**TLDR; Ruby Australia supported events are required to follow a code of conduct. Organisers, sponsors and attendees of RA supported events must adhere to this code of conduct.**

* As an organiser, you, the ruby alumni / support people will be expected to take action and do whatever it necessary to provide the expected environment for all people present.
* As an attendee, if you do not follow these requirements, action will be taken.
* As a sponsor, your sponsorship may be revoked. We may provide contracts describing these conditions, and moneys may not be returned. (That, is a whole other ballgame, but we need to cover it.)

#### Background

Ruby Australia now offers support to Railscamp, Rubyconf & Railsgirls events — that support still needs to be defined (I'll cross-reference a new github issue), but in a nutshell it means: limited financial support, insurance, banking and general administration.

As such, in order for Ruby Australia to facilitate professional and safe events, with support to all volunteers for aforementioned events, we need a document that describes what we expect of all participants.

------

I'd like to supply this quote, [from this article](http://superopinionated.com/2012/09/17/let-this-be-a-lesson/).

> I do not think you are responsible for everyone’s behavior or anything puppet-master-ish, but I think you are responsible for defining the intellectual “space” everyone’s behavior is conducted in. You create and enforce the boundaries. You define what is okay and what is not. And if you refuse to own that power, then you are an unsafe event runner, and I don’t trust you.

#### Deliverables

These items will change as we add detail to this issue over time.

- [ ] Add a code of conduct to ruby.org.au, available in either the footer or main navigation
- [ ] Main navigation to be reduced, we'll need a bit of a re-jiggle of content here
- [ ] Code of conduct to be sent to, discussed and reviewed with current railscamp, rubyconf and railsgirls organisers

This thread / issue is the place to pitch suggestions, or reference pull requests, all opinions are welcome. Keep it friendly and professional.

References:

* [Python code of conduct](http://www.python.org/psf/codeofconduct/) (Thanks @garann!)
* [JSConf code of conduct](http://jsconf.com/codeofconduct.html)
* [Pycon code of conduct](https://github.com/python/pycon-code-of-conduct) (Thanks @stefsullrew)

**Matz is nice, so we are nice too**