We've built a suite of tools to overhaul your GitHub project or organization docs, making it easier for new users to become great contributors. Don't scramble to find great devs: build them by having a welcoming community.
We'll help you sort and manage your issues and pull requests, providing you with empathetic copy and templates for recurring questions. And we'll pen human responses when you don't want to, letting you sleep easier.
Use our dashboard to track your community over time, to provide data-based feedback about how you can grow, get more open source contributions, and spend less time maintaining and more time creating.
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 helped us keep our GitHub issues under control at Read the Docs. He was quick to respond and triage incoming issues, and gave our community the sense that they were being looked after. Previously issues would sit for weeks, frustrating users, and filling us with guilt. With maintainer.io we had happier users, and felt much better about the support we were giving our community.
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.