Does your README have an install section? A Usage secton? How about a mention of API methods? Contributing Guides? A good description? We have a checklist we’ll go over to make it look great. We’ll even review your README now for free.
Our tools and processes will help us maintain your GitHub project. We don’t merge your major PRs, but we’ll help improve the quality of issues and PRs you do get, by making your documentation tighter and easier to use.
We’ll help you sort and manage open issues and pull requests, providing you with copy and templates for recurring questions. If you have dozens of issues you feel you need to resolve, we’ll help you feel like some can wait until later.
Merged the wrong patch, and now someone is throwing a fit? We’re skilled at using non-violent communication with coders; we’ll work with you to defuse the situation, taking the stress out of open source demands.
Going away for a long hike in the mountains? No problem. We’ll watch your issues and make sure that your contributors know that you’re not forgetting them.
Richard’s efforts dramatically improved our community, and saved significant amounts of time. He overhauled the GitHub org structure for IPFS and several other open source projects. He created standards and tooling to ensure good open source hygiene, to improve the experience of all contributors, and to save us time.
Richard makes open source contribution accessible to developers of all levels in a very direct and personal way, helping people from our community find a project they can start contributing to right away. He’s helping bring diversity and inclusion to open source communities, while simultaneously lowering the barrier of entry to people from a wide variety of backgrounds.
Richard has helped us identify numerous contribution-smells: where our project structure, onboarding, and contribution guidelines are inhibiting new users and participants from joining.
Wondering if Open Source really helps? Measure it! Track your community over time. Use our data-based feedback about how your community is growing to get more open source contributions, more eyes on your site, and ultimately more great developers who want to work with you.
We’ve built tools and processes to help your developers maintain your GitHub organization as a whole. We specialize in user flow over large organizations. This saves your developers time and money, and makes it easy for newcomers to contribute to your code, and stay on as community members.
To have a great community, you need to have great contributing documentation. Tell newcomers how to get involved, what steps they need to take to contribute, and that they are welcome.
Not sure what license to go with? Worried about intellectual property? Call a lawyer. But we can give you advice about how to standardize licensing and best practices to make sure contributions conform to your licensing protocol.
Want to make your project open source, but don’t know how? We’ll help you modularize the code, and outline a strategy for getting people excited about your code.
Gabi codes from whatever train, bus, or hostel she happens to be in while traveling. She comes from the .NET world, bringing an important closed-source perspective to the team.
Amna is a freelancer writer, with work in HuffPo, Entrepreneur, and Business Insider. As a writer, she brings a creative eye to the documentation process.
Lianna is a conversion copywriter and comedian who blends marketing psychology and customer research into clear, effective copy. She’s behind the email templates and microcopy that make your users feel taken care of.
Kayli Barth is a freelance nomad and full-time dreamer. She helps small businesses and marketing agencies with their social media campaigns, and fulfills every Canadian stereotype you can think of. Will run for beer.
Richard is happiest coding from a ski lodge on top of a mountain. He’s dedicated to building fantastic READMEs and growing communities.