Friction
Sure, there are all sorts of metrics that you can collect about an open source project, but there’s only one that really matters: friction.
Friction can be measured as the amount of time that elapses between “I want to contribute”, and “I have contributed”. It’s the energy level necessary to transform a potential contributor to an actual contributor. It’s TTFC — time to first commit — and minimizing it is absolutely essential to building a strong open source community.
Think through the contributor UX
Think through every aspect of the experience of a potential contributor. They’ve found a bug. They’ve got a great idea for a new feature. Now what? What’s the first action they take, and how do they know to take it? For many projects, this will most likely involve cloning down the source code, establishing a development environment, making the change, testing things to verify it now does what I want it to do, and figuring out how to get this proposed change back to the project maintainers.
That’s a lot. And if the time it takes to do that is more than a few minutes, you’re unlikely to find a contribution from that person, especially if it’s their first time contributing to the project. Potential contributors may have a high tolerance for the bug itself to be tricky or time consuming (hey, that’s half the fun), but if the workflow and tooling surrounding that bugfix takes longer than the fix itself, they’re likely to move on to another project, and rightfully so. You’ve forever lost that contributor to friction.
So how do you reduce it? Wherever possible, absorb complexity on your contributors’ behalf.
Documentation
It starts with documentation. What anticipate questions. All of them. Don’t let the potential contributor think. What are the projects goals? What’s the founder’s vision? What’s the development roadmap look like? What’s the release schedule? Where are we on the project timeline? What’s the project current status, is it even being developed? What language is the project in? What are the system requirements to run this thing locally? How do I get it set up? How do I contribute? Does the project have a style guide? Where can I find the FAQ?
Tooling
If the same task is going to be performed by all contributors, just script it. There’s no need to decentralize a headache. Setup my development environment for me. Install the gems I need. Get that random database engine you chose configured. At GitHub, we call this script/bootstrap.
Okay, I’ve got my development environment, great, now what? How do I run this darn thing. Give me a single command. Absorb all that complexity you just created on my machine. Spin up the fifteen different processes you need running, each with their own unique arguments, and when I’m done, shut it all down so my CPU doesn’t melt. At GitHub, this is always script/server.
How do I know my change didn’t break something else four modules away? Have automated testing baked in, and give me an easy way to run it. Better yet, run it for me when I submit the proposed change. Give my contribution instant feedback. Give yourself the confidence to merge it. At GitHub, that’s script/cibuild.
Culture
Something went wrong and I have a question. If I post it to your forum will I find a timely and helpful response? Will community members go out of their way to make me feel welcome and to make sure my desired contribution becomes a reality? When I do submit my potential change, no matter how stupid or poorly coded it is, is someone there to thank me? This process is scary. If my code sucks, will you give me feedback and help me to get it to where it needs to be? Okay, so I’ve contributed, do I get my name in lights? On the about page? In the changelog? How do you acknowledge that I am now a contributor?
Friction in the wild
So what’s the TTFC of your open source project? Once I’ve got the desire and have found the appropriate information (not an easy task), contributing to Drupal, for example, on macOS requires you to manually download, install, configure, and start it’s MySQL database server; edit your Apache server configuration in four different places; download their Drush command-line tool; use Drush to download Drupal’s source code, move it to the appropriate folder, create a configuration file, and modify Drupal’s file permissions; create a database for Drupal, and as one guide I found put it best at this point in the tutorial, “now we are finally ready to install Drupal.”
If your potential contributor is like most people, they have a certain tolerance for friction, and once they’ve hit it, they’re just going to move on. Absorb your project’s complexity, so they don’t have to, and all of a sudden, by lowering the barrier to entry, you’ve just empowered an even greater slice of the open source community to contribute. Friction can easily kill an otherwise great project, or at the very least, it may attract a highly-technical subset of developers that will likely be out of touch with your users’ needs. Minimizing friction is absolutely essential to building a strong open source project. Potential contributors should be pampered and encouraged, not hazed and subjected to needless work.
If you enjoyed this post, you might also enjoy:
- Twelve tips for growing communities around your open source project
- Five best practices in open source: external engagement
- 15 rules for communicating at GitHub
- 19 reasons why technologists don't want to work at your government agency
- Why open source
- How to make a product great
- Four characteristics of modern collaboration tools
- Why you probably shouldn't add a CLA to your open source project
- Everything an open source maintainer might need to know about open source licensing
- Eight things I wish I knew my first week at GitHub
- Five best practices in open source: internal collaboration
Ben Balter is the Director of Hubber Enablement within the Office of the COO at GitHub, the world’s largest software development platform, ensuring all Hubbers can do their best (remote) work. Previously, he served as the Director of Technical Business Operations, and as Chief of Staff for Security, he managed the office of the Chief Security Officer, improving overall business effectiveness of the Security organization through portfolio management, strategy, planning, culture, and values. As a Staff Technical Program manager for Enterprise and Compliance, Ben managed GitHub’s on-premises and SaaS enterprise offerings, and as the Senior Product Manager overseeing the platform’s Trust and Safety efforts, Ben shipped more than 500 features in support of community management, privacy, compliance, content moderation, product security, platform health, and open source workflows to ensure the GitHub community and platform remained safe, secure, and welcoming for all software developers. Before joining GitHub’s Product team, Ben served as GitHub’s Government Evangelist, leading the efforts to encourage more than 2,000 government organizations across 75 countries to adopt open source philosophies for code, data, and policy development. More about the author →
This page is open source. Please help improve it.
Edit