This is a relatively simple checklist for you to consider when starting a new open source project, especially where the project may be starting small but wants room to grow. By simple we mean: this list doesn’t propose a process or project management for accomplishing these items; in its most simple form it does not have definitions for items; it suggests what is to come without prescribing or demanding obedience to the list.
These are separated out into several different lists, depending on the area covered:
-
❏ Technical problem addressed by the project
-
❏ Intended users and value proposition
-
❏ Establish beginning roadmap w/milestones
-
❏ List of related/similar projects
-
❏ Why a net-new project?
-
❏ Key differentiators
-
❏ Compile & vet candidate list
-
❏ Logo design
-
❏ Legal review (if required)
-
❏ Reserve name (domain name, GitHub, social media handles, etc.)
-
❏ Document license criteria
-
❏ License selection
-
❏ Need ™ or other mark registration?
-
❏ Define officers & their responsibilities
-
❏ Org structure, voting reqs & process
-
❏ Rules for amending governance
-
❏ Rules for contribution, committer status
-
❏ Provisions for sub-projects & lifecycle mgmt
-
❏ Privacy policy
-
❏ Code of conduct
-
❏ Foundation membership options, if planned
-
❏ Mail tool (and moderators)
-
❏ Forum/Chat (and moderators)
-
❏ Doc repository (slides, planning docs, etc)
-
❏ Web conferencing platform
-
❏ Community calendar (tool + who will maintain)
-
❏ Public website and website maintenance
-
❏ CI/CD, dev & test environments
-
❏ Lab requirements, how they will be acquired
-
❏ Code contribution tools and process
-
❏ Project documentation platform
These items may be ignored if donating project assets to a foundation
-
❏ Website URL
-
❏ Logo
-
❏ Social media handles
-
❏ Web conferencing platform (if paid)
-
❏ Process for funding project needs