Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Move cncf/project-template ownership to TOC Project Reviews Subproject

Open
#2,226 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@riaankleinhans is already working on this.

Since Jul 6, 2026.

Assessment

This issue has not been assessed yet.

Description

needs-group needs-kind needs-triage

Proposal

Transfer ownership of cncf/project-template from TAG Contributor Strategy to the TOC Project Reviews Subproject, and move the template content into the cncf/toc repository.

Why

The project-template repo contains governance, maintainer, contributor ladder, and security templates that are directly referenced by:

  • TOC DD triage and evaluation processes
  • Incubation and graduation application templates
  • The governance best practices document (PR #2224)

These templates are consumed by the TOC during due diligence, not by TAG Contributor Strategy during project onboarding. The Project Reviews Subproject already reviews governance and technical artifacts — owning the templates they reference is a natural fit.

TAG Contributor Strategy's charter has evolved with the TAG restructuring. The project-template repo should align with the group that actively maintains and references these templates in the DD process.

Consolidating the templates into cncf/toc eliminates the indirection of referencing a separate repo and ensures template updates go through the same review process as the DD checklist and application templates they support.

Requested Changes

  1. Move template content into cncf/toc — add GOVERNANCE.md, GOVERNANCE-subprojects.md, GOVERNANCE-elections.md, GOVERNANCE-maintainer.md, CONTRIBUTOR_LADDER.md, CONTRIBUTING.md, MAINTAINERS.md, REVIEWING.md, DESIGN-PROPOSALS.md, and README-template.md under a templates/project-template/ directory (or similar) in cncf/toc

  2. Update CODEOWNERS to include:

    • TOC members
    • CNCF projects staff
    • Project Reviews Subproject members
  3. Update references in DD application templates, dd-toc-guide, and governance review template to point to the new location in cncf/toc

  4. Archive cncf/project-template with a README redirect pointing to the new location in cncf/toc

  5. Update any references in TAG Contributor Strategy docs that point to project-template as their responsibility

Related

Dominant language
HTML
Stars
1.9k
Forks
728
Avg merge
3d 23h
Merged PRs (30d)
10

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cncf/toc

All issues in cncf/toc

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.