(I found I've said "correct me if I'm wrong" in nearly every paragraph I've written - so please, correct anything below that you don't agree with)
I've been wanting to stay out of this conversation because, as Aymeric put it, it is a very sensitive topic. But I've got a few things to say. It seems like the main issue is that: 1) Portions of the django community would like the code of conduct to guide decision makers when particularly egregious actors outside of django spaces wish to participate within django spaces. 2) Different portions of the django community are worried that (some of) the code of conduct rules attempt to enforce professional behaviour in non-professional environments. (As an aside, I think some people are unaware that certain settings *are* professional environments, like after-work drinks with colleagues). An example brought up previously showed a twitter feed with outright threats and abuse. I think that we can all agree that that particular person would not be welcome at a django event. However, I don't think repeating a joke to a friend at lunch on a weekend, that is overheard, should preclude someone from participating at an event. I would hope that we'd all agree to this too. I act in a professional manner when I'm at work, a workplace function, or any kind of industry event. I act in a respectful manner when I'm around family. I do not hold myself to those standards when I'm with friends in private or semi-private environments - and I would hope that the django community wouldn't either. It's ok to say that "discretion" can be applied by the relevant organiser - but as others feel that a list of exclusions should apply to behaviour, I feel that a list of exclusions could be applied to "outside these spaces" if the rest of #86 was merged. Is there language we could use that would allow organisers at a conference to effectively deny entry to someone that threatens and abuses via twitter, yet doesn't exclude someone that isn't behaving professionally outside of a professional environment? Would that even solve the problem being discussed? Regards, Josh -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/1e7655e6-34bf-4228-b3e5-ac99ab77e75a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
