Notice: One month feature freeze on Code of Conduct

[tef]

It seems whenever there is a small issue, we leap to changing the code of conduct. I'm generally against a lengthy code, and I think there is some confusion on what a code of conduct should strive to be:

• The code of conduct is not a legal document. It does not serve to catalogue every failure in behaviour.
• The code of conduct should be small, clear and cover the broader picture where possible. The code of conduct should in general not be about specific unwelcome behaviour
• The code of conduct is not an educational resource either.

I am open to longer more informative documents and guidelines, but the code of conduct as it stands is an abstract, an admission of problems within the tech community, not the definite or canonical list of behaviours. We should not be attempting to change behaviours by editing the code of conduct. Community management won't come from language lawyering.

As a result, I am recommending we leave it alone for a few weeks, resist the temptation to yak-shave and refactor it. Thoughts?

Edit: To reiterate: I'm open for more resources, educational material, and finishing off the FAQ on why we have a code of conduct, but I'm against changes to the code in the interim.

[sgsabbage]

+1

[ianthe]

+1

[ntlk]

I fully support this. I think CoC is at the stage where it covers most things in a succinct way. I want to meet people in a relaxed atmosphere where I assume nobody will be a dick to me, I don't want it to be all about the rules. Hopefully as more meetups happen we can see if what we've currently got is enough.

[sjmarshy]

+1

[janepipistrelle]

+1

[seubert]

+1

[igalic]

+1

[williln]

+1

[tef]

I'm considering the Code Frozen for the next four weeks. Unless there is a serious issue, please don't merge or edit it. Thanks :-)

[maestrofjp]

Late to the party here, but the PSF Code of Conduct is positive and is about social atmosphere in nature instead of a bunch of "do not do this...":

http://www.meetup.com/PyMNtos-Twin-Cities-Python-User-Group/pages/PyMNtos_Code_of_Conduct/

As a manager of our local Python User Group, the Code of Conduct was adopted as a by product of obtaining sponsorship from the Python Software Foundation. Code of Conduct is there so it can be relied upon if a situation occurs. Glad, I've never had to invoke the use of it at PyMNtos meetings. I make a causal announcement during the intro at our meetings:

"PyMNtos has a simple Code of Conduct. It is part of our sponsorship agreement with the Python Software Foundation. Our community is made up of members from around the globe with a diverse set of skills, personalities, and experiences. Basically, it boils down to three key points: Open, Considerate and Respectful. I know we are all capable of these key points.

If you want to read the entire Code of Conduct, you can find it in the pages section on our meetup.com site. Thanks!"

We've gotten zero push back from our group about this... it exists for the situations in which a PyMNtos volunteer needs to get involved. Our membership seems to be able to self-police any potential problems themselves. A Code of Conduct is a tool that empowers a member to have the ability to say something without trying to be apologetic in tone or just "take it" or being accused of whiny or "you can't have fun" argument. It also allows other members to be empowered to step in and keep things peaceful before having to get an user group leader / volunteered involved. Personally, it appears things don't escalate as easily because situations are better self-regulated before things go too far that it become a major issue.

Not that I ever want to use it, but if somebody is truly being awful and won't check their own behavior -- its a tool for me as an organizer to ask somebody to leave without looking like I'm making a power move based no previously mentioned document. Since we announcement it at the beginning of every meetings, there is no defense saying you don't know that a Code of Conduct exists.