Jerks Are Killing Your Projects

### Overview In this talk, an industry analyst and former open-source contributor reflects on how toxic behavior, bullying, and incivility severely harm technical communities and software projects. Drawing on personal experiences with Gentoo Linux and supported by organizational psychology research, the speaker explains that technical brilliance never excuses destructive behavior. Negative interactions create high barriers to entry, drive away contributors, lower diversity, and damage productivity across entire ecosystems.

### Key Topics - **Barriers to Entry and Catalysis**: Applying concepts from biochemistry to open-source communities, where lowering the barrier to entry attracts contributors and arbitrary pain or incivility repels them. - **The Asymmetry of Behavior**: Citing research showing that negative interactions are roughly five times more impactful than positive ones (requiring five positive interactions to counterbalance one negative one). - **The True Cost of Jerks**: Calculating the organizational and community toll, including target/witness turnover (50% of targets and 12% of witnesses consider quitting; 25% of targets actually quit), reduced performance, lost recruitment, management distraction, and damaged project reputation. - **Technical vs. Social Skills**: Emphasizing that social behavior and technical ability are orthogonal axes. No developer is productive enough to outweigh the network-wide damage caused by toxic conduct. - **Healthy Debate vs. Abuse**: Distinguishing constructive conflict (vigorous technical debate over implementations) from abusive conduct (personal attacks targeting individuals).

### Technical Details & Case Studies - **Gentoo Linux**: Following an initial drop around Ubuntu's launch, the project experienced severe complaints regarding three core developers. Removing those toxic developers led to a plateau and stabilization in contributor numbers, though full cultural recovery took five to seven years. - **glibc**: Contributor numbers showed sharp increases around two major shifts: adopting git for decentralized version control, and the departure of a notorious lead maintainer. - **NetBSD**: Contributor growth was flat until a contentious core developer (who later founded OpenBSD) was asked to resign in 1994, after which contributor metrics sharply rose. - **Measurement Tools**: Communities can monitor health quantitatively using tools like OpenHub, Bitergia, CHAOSS metrics (discussed at CHAOSScon), cohort analysis (such as 30-day retention), and modern sentiment analysis using LLMs.

### Takeaways & Prevention Strategies - **Enforce Codes of Conduct Publicly and Quickly**: Address toxic interactions immediately and publicly in open forums so bystander effects don't normalize the behavior. Maintain a clear reporting path with expected response SLAs. - **Cultivate In-Person Trust**: Gatherings (such as Google Summer of Code meetups, SCALE, LinuxWorld Expo, or FOSDEM) build empathy and rapport that make remote collaboration healthier. - **Intervene Early**: Confront problematic contributors with clear, objective evidence of their impact. Provide them an opportunity to correct their behavior, but remove them swiftly if they fail to reform. - **Align Cultural Expectations**: Explicitly set communication and behavioral standards for the project culture (e.g., leveraging insights from resources like *The Culture Map* by Erin Meyer) to bridge different regional or background communication norms.