99 Ways to ruin an open source project

July 22, 2015 opensource , talk 2 min read

Growing and maintaining healthy open source projects is extremely difficult. Sometimes, to be successful, we need to learn all the ways that don’t work.

As users, there are countless ways we use to unintentionally make life more difficult for other users and maintainers. Whether it is by filing bug reports that lack the necessary details about the issue and how to reproduce it, or being so focused on our own needs that we don’t realize how disrespectful we are to the human beings behind the avatars, we contribute to the demoralizing experiences that drive maintainers to burn out.

As maintainers, we overlook all the things we do that make our projects difficult to use and unappealing to contributors. We fail to document important information about using or contributing to the project, or we are unresponsive to issues and contributions.

This absurd, humorous, and completely serious talk will teach you everything you need to know to ensure that a healthy open source project meets its demise. Whether you are a user testing the open source waters, an experienced maintainer, or open source ate your hard drive, discover techniques to ruin your corner of the world.


This content is open source. Suggest Improvements.


avatar of Brandon Keepers I am Brandon Keepers, and I work at GitHub on making Open Source more approachable, effective, and ubiquitous. I tend to think like an engineer, work like an artist, dream like an astronaut, love like a human, and sleep like a baby.