> For the complete documentation index, see [llms.txt](https://guidebook.theopensourceway.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guidebook.theopensourceway.org/getting-started/new-project-checklist.md).

# New Project Checklist

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:

## Goals of project

* [ ] Technical problem addressed by the project
* [ ] Intended users and value proposition
* [ ] Establish beginning roadmap with milestones

## Market positioning

* [ ] List of related/similar projects
* [ ] Why a net-new project?
* [ ] Key differentiators

## Project name

* [ ] Compile and vet candidate list
* [ ] Logo design
* [ ] Legal review (if required)
* [ ] Reserve name (domain name, GitHub, social media handles, etc.)

## Licensing & legal

* [ ] Document license criteria
* [ ] License selection
* [ ] Need ™ or other mark registration?

## Governance

* [ ] Define officers & their responsibilities
* [ ] Org structure, voting requirements and process
* [ ] Rules for amending governance
* [ ] Rules for contribution, committer status
* [ ] Provisions for sub-projects and lifecycle management
* [ ] Privacy policy
* [ ] Code of conduct
* [ ] Foundation membership options, if planned

## Project infrastructure

* [ ] 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, development and test environments
* [ ] Lab requirements, how they will be acquired
* [ ] Code contribution tools and process
* [ ] Project documentation platform

## Ownership and financing

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

## Launch planning

* [ ] D\&I plan
* [ ] Community health and metrics vision/plan


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://guidebook.theopensourceway.org/getting-started/new-project-checklist.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
