RFC: YAPC Code of conduct up on github?

Matt S Trout mst at shadowcat.co.uk
Sun Mar 24 14:00:23 PDT 2013

On Fri, Mar 22, 2013 at 11:14:23PM -0700, Michael G. Schwern wrote:
> With the work we're doing on the CoC I hope this year I can say another
> thing to attendees.
>   If you have a problem at YAPC, you don't have to deal with it alone.

I'd like to raise a hand here and say "you could already have said that"
- certainly every ::NA I've attended had people working hard to make that
true, some in the organisation team, some from attendees applying JFDI to
looking after their community.

I think it's good to get this stuff formalised - but please try not to do
it in such a way as to minimise the efforts of all the community members
who've been standing up and making sure people don't face problems alone in
previous years, just by listening out for problems on the floor and doing our
best to either deal with them (where possible) or take them to the organisers
(where preferable).

Having a specific CoC as a way to get these values written down and to give
the organisers something to refer to is nice.

But it's very much a way to formalise and improve a desire for inclusivity
that is already strong in our community, and we need to say very clearly
that what we're doing here isn't creating something new, it's caulking the
leaks in something that's already there and then shouting that fact from
the rooftops.

Matt S Trout - Shadowcat Systems - Perl consulting with a commit bit and a clue

http://shadowcat.co.uk/blog/matt-s-trout/   http://twitter.com/shadowcat_mst/

Email me now on mst (at) shadowcat.co.uk and let's chat about how our Catalyst
commercial support, training and consultancy packages could help your team.

More information about the yapc mailing list