Managing Community Conflict in Drupal and Beyond
summary
Community Working Group runs a volunteer conflict process using a public incident report form on drupal.org, weekly Google Hangouts and a private Slack for urgent escalation, and publishes redacted minutes to a shared Google Drive. Surveys show ~60% reported experiencing or observing conflict during Drupal 8 and an external study finds 18% experienced harassment while 50% witnessed it; 21% stop contributing because of it. Responses include mediation, written action plans, warnings or coordinated bans across Drupal spaces, plus calls for better mentorship, docs, and cross‑project harassment tools.
AI-written summary · about
chapters (14)
- 0:00Introduction and background
- 1:06Defining conflict and its types
- 8:02Negative conflict in open source
- 14:27Code of conduct importance
- 18:59Community Working Group structure
- 21:27CWG role and responsibilities
- 25:01Community governance challenges
- 29:16Misconceptions about CWG
- 31:23Accountability and compassion
- 33:14CWG conflict resolution process
- 42:10Key lessons from CWG work
- 45:03Addressing unmet needs
- 52:37Online harassment challenges
- 57:57Q&A and closing remarks
related talks
27mThorny Problems in Open Source Community Management
46mDrupal Diversity & Inclusion: Volunteer-led strategies for the community
30mHow We Updated Drupal's Code of Conduct
33mCommunity Working Group Update and Q&A
44m"Drupal Diversity & Inclusion: Building a Stronger Community"
50mCreating a Healthy Community Culture
45mOpen Source Contribution Panel
27mCommunities, Organisations, Relationships, Conflict and Hope