Conflict Resolution for Open Source Teams
summary
Creates a clear taxonomy of conflicts — interpersonal, value-based, issue/data, organizational, and compound — and maps five resolution strategies to each: accommodation, compromise, avoidance, competition, collaboration. Uses concrete historical examples (GNU Emacs fork in 1993, x86 license change ~2007 that lost users, GNOME menu naming disputes) and a hands-on practicum with anonymized real conflicts. Argues collaboration is win‑win but slow, competition fits urgent decisions, avoidance buys cooling‑off time, and compromise often only buys temporary peace.
AI-written summary · about
chapters (14)
- 0:00Conflict resolution intro
- 1:47Conflict types taxonomy
- 12:13Interpersonal conflicts
- 15:07Value conflicts in projects
- 24:01Task issue conflicts
- 26:56Organizational conflicts
- 33:12Compound conflicts strategies
- 36:00Five resolution strategies
- 44:34Accommodation and compromise
- 59:52Transparency frameworks
- 1:00:19When to avoid conflicts
- 1:04:57Power-based resolution
- 1:09:58Collaboration win-win
- 1:11:45Q&A
related talks
27mCommunities, Organisations, Relationships, Conflict and Hope
27m5 Approaches to Increasing Your Open Source (Team) Happiness
33mBuilding Compassionate Communities in Tech
41mTransformative Mediation for your Code of Conduct & Community Management Toolkit
01h 06mManaging Community Conflict in Drupal and Beyond
37mThe Acceptance - Tolerance - Model
45mThe Conflict and Burnout Survival Guide: Handling When Things Go Wrong
40mWhy You Should Adopt an Open Source Code of Conduct