How containerd/project works
Project type and purpose
• This is not a running application or service but a “documentation & governance” repository for the containerd organization.
• Its sole purpose is to act as the single source of truth for:
– Project governance (GOVERNANCE.md)
– Maintainer list (MAINTAINERS)
– Contributing guidelines (CONTRIBUTING.md)
– Security policies (SECURITY.md + SECURITY_ADVISORS)
– Related boilerplate (LICENSE, EMERITUS.md, SIG-NODE.md)
• It also holds the CI configuration template under .github/workflows/ci.yml and a go.mod to tag this repo as a Go module.
File structure
• Top-level files:
– Markdown docs: README.md, GOVERNANCE.md, CONTRIBUTING.md, etc.
– CI config: .github/workflows/ci.yml
– Go module descriptor: go.mod
– Image assets folder: img/
• No src/ or lib/: there is no service code, only docs and config.
• CI workflow is a wrapper that pulls in “project-checks” actions from the external project-checks repo.
• README points to external sub-repos for release-tool and CI checks.
README for additional insights
• Explicitly states this repo contains core governance docs and points to:
– release-tool repository (github.com/containerd/release-tool)
– project-checks repository (github.com/containerd/project-checks)
• Describes how other containerd subprojects should reference these docs.