A Tier 0 project is an experimental or historical repository that is private and generally used by a single developer or a small group. It typically includes working projects, example scripts, or early prototypes that serve as a foundation for future work or experimentation. This type of project is not shared publicly and often remains private due to its preliminary or incomplete nature.
The main purpose of a Tier 0 project is to provide a space for initial development, exploration, and testing. These repositories generally lack formal documentation or governance structures that are typical of more mature projects.
- Private and often limited to individual or small team access.
- Primarily experimental or developmental in nature.
Although these projects are private, there are specific files that are required and recommended to include in the repository as part of the CMS Open Source Program Office's repository hygiene guidelines and standards.
| File | Requirement | Description |
|---|---|---|
LICENSE |
Mandatory | Defines the licensing terms under which the project is distributed. |
SECURITY.md |
Recommended | Outlines the agency's security policies, including how to report security issues or vulnerabilities in the code. |
README.md |
Mandatory | Provides an overview of the project, including its purpose, setup instructions, or any relevant notes for the developer(s). |
CONTRIBUTING.md |
Recommended | Guidelines for contributing, useful if the project is later opened to collaborators or transitioned to a public repository. |
For more information about sections and content within the files above, please visit maturity-model-tiers.md.