Open source contributor guidelines should be easy to read, thorough, and friendly.
Open-Source Contribution: The Ultimate Guide | Built In
How to get into open-source contribution according to these experts.
Our Handbook is open source: here's why
In this post we’re explaining the reasons why having an open source Handbook works for us and how it can help you.
Creating and growing healthy community open source projects [PLoP 2020]
Abstract: This article presents a succinct and minimal handbook of best practices of how to create and grow community open source projects. We start with the assumption that the handbook’s user has…
Building great open source documentation
Twelve tips for growing communities around your open source project | Ben Balter
Publishing code isn't enough. Twelve practical tips to attract users, welcome contributors, and grow a healthy open source community.
How to manage casual contributors to open source projects
Try these strategies to better utilize contributions from your project's episodic volunteers.
Why your Open Source Project might lack (my?) contribution (1)
"In this article I describe some things to consider when maintaining
Ten Rules for Open Source Success - Hintjens.com
Biography | Portfolio | GitHub Books | Videos | Slides | Stories | Wiki Contact
Roles in open source projects
home > resources > briefing notes > Roles in open source projects
GitHub Community Guidelines - GitHub Docs
Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.
Ten simple rules for helping newcomers become contributors to open projects
Citation: Sholler D, Steinmacher I, Ford D, Averick M, Hoye M, Wilson G (2019) Ten simple rules for helping newcomers become contributors to open projects. PLoS Comput Biol 15(9): e1007296. https://doi.org/10.1371/journal.pcbi.1007296
What Is Open Source Strategy? — Open Tech Strategies | Blog
There is a lot of documentation out there on how to do open source well at the project level. Historically, many projects have been started by developers, often on their own initiative, and the first non-technical questions they faced tended to be about project coordination (like "What collaboration tools shall we use?" or "What will our code review practices be?") and about community management (like "How do we decide who has commit access?" and "How do we integrate newcomers smoothly?"). Because developers hate to solve the same problems over and over, there is a wealth of detailed and varied material addressing those sorts of questions (we've even written some ourselves, but it's just a drop in the bucket of what's available). Taken together, this literature thoroughly answers the question "How do we execute the best tactics for developing open source software?"
Open Source Saturation
In Supporting Open Source Software I discussed the critical need for better support for contributors to open source projects. Now, Quo Vadi...
LibGuides: Open Access Publishing : OA Journals, Books and Repositories
This guide provides guidance in open access scholarly publishing for researchers in all disciplines.