The Drupal Code of Conduct needs to state we won't tolerate harassment... here is the text.
We will not tolerate bullying or harassment of any member of the Drupal community.
If you feel threatened or violated as a result of intimidating, bullying, harassing, abusive, discriminatory, derogatory or demeaning conduct, please speak up and ask it to stop. If you
are fearful of speakingdo not feel that you can speak up, contact the Community Working Group immediately with evidence of the incident. Incidents of bullying and harrassment can be reported privately and will be treated seriously and discretely.Please speak up if you notice someone else being subjected to such behaviour. Refer people to our code of conduct and point out such behaviour is unwelcome.
See threads:
Why?
Every harassment policy I've read reinforces the necessity of stating this kind of behaviour is unwelcome.
Every time this issue comes up, there are usually a large number of people who say this does not need to be said.
However incidents still happen, and for there to be effective strategies for responding to it, we need to be able to point back and say - hey - this kind of behaviour is not welcome, and won't be tolerated up front.
Comments
Comment #1
tvn commentedThis is done. KatteKrab edited the page herself.
Comment #2
kattekrab commentedNope - it's not done yet. The CWG is meeting on Thursday to confirm and finalise it. We'll do it then. :)
But huge thanks to @tvn and @dww for empowering me to get this done once the process has gone full circle!
- donna
Comment #3
webchickOk, the Code of Conduct has been updated. :) https://drupal.org/node/895254/revisions/view/1133698/2813875
Here's the changelog from the original text in the issue summary:
Comment #4
leehunter commentedI think this needs more thought.
Here are the problems that I see with it:
The intro to the code needs updating as well. We should drop the two paragraphs about the Ubuntu code of conduct or just say that it was inspired by their code. Right now, it says that our code is 'essentially identical' to theirs which is not true at all.
Comment #5
Crell commentedEr, shouldn't a change to the CoC also have slightly more review than a lonely issue most people aren't watching? There was no notification of it that I saw other than KatteKrab posting a courtesy notice, after-the-fact, to the original COC issue on g.d.o: https://groups.drupal.org/dcoc#comment-952888 CoC changes should get more attention than just 2-3 people stating a fait accomplis.
Even just as a practical matter, Lee's comments in #4 illustrate why. That's aside from the problem of the "social contract" of Drupal.org being edited without notice.
(To be clear, I am fully in favor of a "no bullying" clause in the CoC. I just don't like not knowing about it until after the fact.)
Comment #6
webchickJust for clarification, the original discussion at #1815958: Define enforceable consequences for online + in person harassment that led to this issue (which was just tweaking the text based on the consensus there) has 50 replies and 30 followers. One could argue that might not exactly constitute critical mass, but it certainly wasn't done in the dark.
Comment #7
Crell commentedThat is certainly closer to critical mass, thanks. And a rather old issue. Still, I'd think CoC changes need some sort of "flag raised" for people who aren't routinely following the content queue, like we do with g.d.o/core for major core dev issues.
(No, not all d.o content needs that flag raised. The CoC is a special case.)
Comment #8
webchickCan you make an issue in the https://drupal.org/project/drupal-cwg project about this? Since that's the body now responsible for maintaining the CoC, makes sense to discuss process about edits to it there.
Comment #9
Crell commentedI have done so: #2079935: Certain issues need raising outside this group before implementation
Comment #10
kattekrab commentedAnd following on from what @webchick said in 8 #8
It was also raised here: https://groups.drupal.org/dcoc#comment-842833 Which according to the CoC was the place to discuss such things...
"Discussion about this policy belongs in the Drupal.org Policies group [groups.drupal.org/dcoc]" and @LeeHunter is in that group too...
Anyway - on to moving forward and not defending total lack of consultation...
I agree the intro needs an update.
I agree that under "be respectful" is possibly a better place for this for now. But I think it really needs to be part of the still as yet unresolved "complaints and conflict resolution process" bit... #1493430: [meta] Develop a conflict resolution process for community issues
This amendment arose because nowhere do we explicitly say we won't tolerate harassment and bullying. After the incident that prompted #1815958: Define enforceable consequences for online + in person harassment I went digging for how we might handle this better in the future... Our DrupalCon CoC makes it clear for in person meetings, but our standard CoC does not. Just about every guideline I looked at suggested the first step was to make sure these kinds of behaviours are outlined somewhere as unwelcome and won't be tolerated.
I would also argue that encouraging people to speak up for themselves is indeed the kind of behaviour we should expect, as is encouraging bystanders to speak up too...
Strikes me the best place for these statements is the code of conduct, and NOT in some other random, (as yet non-existent) policy.
So... what next. New words? Anyone?
Comment #11
tvn commentedMoving to the proper queue for further discussion. This issue appeared in the Content queue purely because kattekrab was not able to edit dcoc page at that time. That is fixed and she has access now.
Comment #12
kattekrab commentedOk - sooooooo...
Would like to see some progress again here. What do we need to do here?
Comment #12.0
kattekrab commentedadded strike through of "fearful of speaking" that should have been there all along.
Comment #13
kattekrab commentedI'd like to close this ticket, its aim has been achieved.
But @LeeHunter's comments in #4 are valid and I think it would be worth revisiting the code and updating it. It is no longer the same as the Ubuntu code, they have also since changed theirs, and we are working on the conflict resolution policy and processes for responding to conflict. #2227717: Proposed Conflict Resolution Policy
Any objections to closing this issue, and posting a follow up to revise the code of conduct more wholistically?
Comment #14
Crell commented+1. I think we're done here.
Comment #15
kattekrab commentedOk then.
Comment #17
kattekrab commented