Some useful open source guides I refer to:
For Open Source Program offices (OSPOs):
The TODO group has a great set of guides to learn from and contribute to.
General best practices for organizations using or contributing open source software:
- Organizational compliance guidelines
- Participating in open source projects and contributing code
- Why create an open source project?
- Impactful open source contribution
- Project culture and building project leadership
- Succession planning and when to call it quits on an open source project
For Individual Contributors:
A lot has been said about what works and what doesn’t for setting up your open source project. In my experience, open source projects started by individual developers have been driven mostly by the need to solve a technical problem and then sharing lessons learned and code with other fellow developers. Guides available are good reference points to start from but usually need to be adapted for your own personal project.
Some useful resources I’ve referred to:
- Apache.org: Apache Developers and Contributors Overview
- Opensource.com: What is Open Source?
- GitHub.com: Open Source Guides
- OpenHatch.org: Resources for a Free and Open Source software contributor
- NodeJS.org: Contributing to NodeJS
- Python.org: Python Developer’s Guide
- RubyonRails.org: Contributing to Ruby on Rails
- Opensource.google.com: Contributing to Open Source
- Google Code-In: Getting started with open source
- Choosing an open source license
By Developers for Developers:
- How I learn an open source codebase by Kent.C.Dodds
- Your first open source contribution: a step-by-step technical guide by Jen Weber, EmberJS
- Contributing to open source for the first time by Laeta Keane on Hackernoon
- How do I starting contributing to an open source project? by Sayan Chowdhury on Quora
- How to start an open source project? by Nicholas Zakas