![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
bouteillebleuPython Software Foundation moves to require that Python conferences have a Code of Conduct if they want grant money from the PSF for running the conference.
(In this case a code of conduct is a written statement, usually on the conference website, saying what behaviour is and is not okay at the conference. The PyCon US one is pretty good and has been borrowed or adapted for a lot of other Python conferences. It contains a useful but not restrictive definition of things that constitute harrassment, a list of people to talk to about harrassment or security concerns, and statements of what the conference will do about it.)
A PyCon IE attendee feels a little down about this, as it seems to be too "formal".
The first couple of paragraphs saddened me (I was worried it would be a whole post of "I've never encountered this problem, so I don't think it exists"), but I'm kind of glad for the last few:
And Jacob Kaplan-Moss's comment on the post is excellent (he's written more about Codes of Conduct on his blog):
As for me, I'm happy about this change - it means that maybe local-to-me Python conferences might not see Codes of Conduct as an afterthought or something nice but low priority. I'm not even sure whether PyCon UK got its Code of Conduct written before the "conference song" someone wrote.
(In this case a code of conduct is a written statement, usually on the conference website, saying what behaviour is and is not okay at the conference. The PyCon US one is pretty good and has been borrowed or adapted for a lot of other Python conferences. It contains a useful but not restrictive definition of things that constitute harrassment, a list of people to talk to about harrassment or security concerns, and statements of what the conference will do about it.)
A PyCon IE attendee feels a little down about this, as it seems to be too "formal".
The first couple of paragraphs saddened me (I was worried it would be a whole post of "I've never encountered this problem, so I don't think it exists"), but I'm kind of glad for the last few:
I don’t know, makes me think about what is the general perception and behaviour of the development community. I know there is discussion out there about whether the geek population is welcoming to diversity or just a bunch of jerks that just can’t behave (and all the spectrum in between). I guess it just makes me sad to think that we may need "an adult" telling us not to say things that we already know that we shouldn’t. It’s 2012, we have no excuse.
As I say, I just feel a little... disappointed. Like thinking that there is something wrong in all that, that we are grow up and that things are not on the same level of friendly informality. That we need rules to ensure everyone feels safe. I guess that a small number of spoiler brats are just ruining the party to everyone else.
And Jacob Kaplan-Moss's comment on the post is excellent (he's written more about Codes of Conduct on his blog):
I think the discomfort you’re feeling is totally legit and valid – codes of conduct are kinda patronizing to the vast majority of people who know better. The fact that you don’t need a CoC to tell you how to behave is a good sign: it means you’re a Normal Person who understands how to make other people feel comfortable in your presence. But you have to understand that the CoC isn’t about you. It’s about making other people comfortable in settings that have traditionally been quite hostile to them.
As for me, I'm happy about this change - it means that maybe local-to-me Python conferences might not see Codes of Conduct as an afterthought or something nice but low priority. I'm not even sure whether PyCon UK got its Code of Conduct written before the "conference song" someone wrote.
