Diversity team in your community, and then what
summary
Maps out four development phases from “all dudes” to phase four: civil war, claiming diversity teams often trigger governance conflict once they broaden scope. Uses two case studies: Wikimedia’s LGBT groups escalating to event safety and protests, and OpenStreetMap adopting a 2012 peer‑reviewed paper, forming Geochicas, then adding a safety policy that leads to canceled or relocated conferences. Recommends prewritten processes, early community feedback, predetermined hard decisions, and plans for bad‑faith actors.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:25Diversity theory in open source
- 3:10Wikimedia’s diversity struggles
- 6:22OpenStreetMap’s diversity approach
- 8:50Protests and community responses
- 9:12Practical diversity advice
- 11:39Global diversity issues
- 12:00Q&A
related talks
31mHow to amplify diversity inside a Python community?
22mCreative Approaches To Diversity
01mDiversity Workshop
30mTokenism in Open Source: Diversity or Decoration?
47mActions Speak Louder Than Words: Building Better Communities
49mDiversity & Inclusion in Community in 2021
26mBetter Together Diversity Networking Lunch
46mDrupal Diversity & Inclusion: Volunteer-led strategies for the community