Shared Values and the Drupal Community

Events happening in the community are now at Drupal community events on www.drupal.org.
gdemet's picture

Dries recently wrote a blog post about the challenges of fostering diversity and inclusivity in the Drupal community. This is the latest installment of a conversation that’s been going on for years.

In 2012, a group of Drupal community members worked together to draft a Code of Conduct that could be used to supplement the Drupal community’s Code of Conduct at DrupalCon and other in-person events.

This effort prompted a large (and sometimes heated) conversation that involved people from all corners of the Drupal community. This conversation was a difficult one, and many of us disagreed about many different things, but ultimately, we all agreed on several general principles:

  • We are a group of diverse people from a wide variety of ethnic, cultural, and religious backgrounds, and we embrace that.
  • Making all attendees feel welcome and included at DrupalCon is everyone’s job.
  • We treat each other with dignity and respect.
  • We take responsibility for our words and actions and the impact that they may have on others.

These principles informed the DrupalCon Code of Conduct, which was ratified by the Drupal Association in the summer of 2012 and has been used at every DrupalCon since.

At the last few DrupalCons, there have been a number of reported incidents, including groping, sexual harassment, physical assault, inappropriate comments made about female speakers, and more. While we are grateful that these incidents are being reported, even a single incident is too many.

In early 2013, the Community Working Group was chartered by Dries to uphold the Drupal Code of Conduct and to maintain a friendly and welcoming community for the Drupal project.

As a community, it’s important that we always keep our shared principles and values in mind when interacting with others, whether that be in person at DrupalCon, in the issue queues on Drupal.org, on IRC, or via social media. As the DrupalCon Code of Conduct states, the purpose is not to restrict the diversity of ideas and expression, but instead to ensure that there is a place for everyone in the Drupal community who agrees to abide by these basic principles.

Even when everyone has the best intentions, however, it’s inevitable that conflicts will occur. To ensure that these are addressed in a manner consistent with our shared values, the Community Working Group has worked with the community to develop a conflict resolution policy that lays out the process for addressing disagreements. This policy was developed by participants in the Community Summits at DrupalCons Prague and Austin, with additional review on Drupal.org.

This policy seeks to first and foremost empower individuals to resolve issues between themselves when possible, asking for help when needed, and only after that fails to escalate further. This approach gives people more control over their dispute and is the most likely to result in a positive outcome for everyone involved.

For matters that cannot or should not be resolved in any other way, the Community Working Group is available as a point of escalation. Incidents can be confidentially reported to the Community Working Group using the Incident Report Form. If the issue falls within the purview of the Community Working Group’s jurisdiction, we will then work with the involved individuals to find a remedy.

In her DrupalCon Austin keynote Erynn Petersen talked about how diversity is a key component of a healthy and productive community. While the Drupal community is one of the most diverse and welcoming communities in open source, we still have room for improvement. If you’re interested in joining us in that effort, let us know by responding to our call for volunteers or by participating in a Community Summit at an upcoming DrupalCon.

Actively supporting and maintaining a welcoming environment is something that every one of us in the Drupal community needs to be a part of, and it’s essential to the long-term health and growth of the project and community that we all love so much.

Comments

Incidents can be

gaele's picture

Incidents can be confidentially reported to the Community Working Group using the Incident Report Form

If it's supposed to be confidential I'd rather not use Google Forms.

http://www.google.com/intl/en/policies/terms/
http://www.google.com/intl/en/policies/privacy/

An alternative is the

webchick's picture

An alternative is the drupal-cwg [at] drupal.org email address, as documented on https://www.drupal.org/governance/community-working-group.

We chose to use Google Forms because a wide variety of people about whom conflicts may occur have very high-level access to Drupal.org. A neutral third-party service doesn't have this problem, although I totally get why some have ToS concerns with it.

Could we please have that

damienmckenna's picture

Could we please have that email address added to the top of the Incident Report form, just to make it obvious for people? Thanks!

Sure; filed an issue here:

webchick's picture

Sure; filed an issue here: https://www.drupal.org/node/2299737

Needs Review :)

kattekrab's picture

I've edited the form and updated the issue.

https://www.drupal.org/node/2299737#comment-8950891

Would be good to get some sanity check eyeballs on it though!

Thanks all!
@gaele - for raising the question
@DamienMcKenna - for the suggestions.
@webchick - for adding to the queue.

Donna Benjamin
Former Board Member Drupal Association (2012-2018)
@kattekrab

Sanity check eyeballs

jhodgdon's picture

You asked for "sanity check eyballs" on https://www.drupal.org/governance/community-working-group/incident-report

I have a few comments:

a) There is a very large wall of text at the top. Maybe it could be organized into bullets or sections or something? [see below]

b) You might also want to take a look at the descriptions for the Who/What etc. questions. They are a bit repetitive.

c) The "Who" question also has a mix of questions (ending in ?) and ... sort-of questions (ending in .) which turned me off.

d) "Please include links or quoted text if relevant." is under "where". Um... I think that would be under "what"? At least the "quoted text" sounds like a "what" not a "where"? It's kind of confusing what the distinction is.

So... Here's my suggestion for the top. Items in [] are my notes on the edits.


The community working group (CWG) upholds the Drupal Code of Conduct (DCOC). See:
- https://drupal.org/governance/community-working-group
- https://drupal.org/dcoc

[made this a bullet list]

Reporting incidents to the CWG

[header added]

This form can be used to report incidents that may breach the code of conduct, or to report non-code, non-technical issues that can't be resolved between members of the community.

Alternatively, you may email the CWG directly: drupal-cwg@drupal.org
Please make sure to include as much information as you can by answering the questions in the form in your email. [note: small edit in this sentence]

Incidents to report elsewhere

[added header, and this information came from elsewhere on the page]
IMPORTANT: If you are in any kind of immediate physical danger, please contact your local authorities.

Technical disputes should be raised with the Technical Working Group. Personal disputes that have arisen out of technical issues can be brought to the CWG.

https://drupal.org/governance/technical-working-group

Notes about incident reports

[added header, and the information here elsewhere on the page]
We hope you've tried to resolve issues between yourselves. If that failed, we hope that you reached out to fellow friends and colleagues in the community to help mediate your dispute. This form should only be used when those steps did not lead to resolution.

These incident reports are shared with the immediate members of the Drupal Community Working Group and are kept confidential. In some cases we may decide it necessary to make a public statement. In that case, the identities of all involved will remain confidential unless there are strong reasons, or mutual agreement they should be revealed.


Great Review!

kattekrab's picture

Thanks Jennifer - really useful review and patch.

Going to paste this into the issue https://www.drupal.org/node/2299737

Let's see if we can tighten up the wording around those questions too.

Donna Benjamin
Former Board Member Drupal Association (2012-2018)
@kattekrab

Form updated.

kattekrab's picture

It's taken a while, but finally, we've brought those changes in to the form!

https://www.drupal.org/governance/community-working-group/incident-report

We've also made an email template so you don't have to use Google.
https://www.drupal.org/governance/community-working-group/incident-repor...

we can be emailed at drupal-cwg@drupal.org

Thanks Jennifer, Gaele and Damien for your input on this!

cheers
Donna

Donna Benjamin
Former Board Member Drupal Association (2012-2018)
@kattekrab

Values on Drupal Sprints Community

Patrícia Jyotsna's picture

Hi, I heard about Drupal is now a growing community and knowing that the mentored sprints was attended by many to listen to tools presentation is such a very successful one. In relevance to this, I am with you to say that we must be aware in keeping our shared principles and values in mind when interacting with others to be able to attain an inspiring event like the Drupal sprints at Amsterdam.

Drupal Governance

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: