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

[Initiative]: Public roadmap documentation standards

Open
  • Is something wrong?
#2,230 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Quiet
Domain
documentation

Research direction

Start by reviewing the cited due diligence findings, including cncf/toc#2198, and compare how projects currently document roadmaps. Define the recommended format, minimum content, change process, and freshness expectations, then produce the guidance document, roadmap template, and DD checklist template updates listed in the exit criteria.

Written by the indexing model from the issue text.

Description

init/not-started kind/initiative needs-triage sub/project-reviews
Name

Public roadmap documentation standards

Short description

Standardize how CNCF projects maintain a persistent, discoverable public roadmap with a documented change process.

Responsible group

TOC

Does the initiative belong to a subproject?

Yes

Subproject name

Project Reviews

Primary contact

TBD

Additional contacts

@angellk (TOC Chair, DD finding source)

Origin

DD finding (automated)

Initiative description

This initiative is a request from the TOC. During due diligence reviews, the TOC evaluates projects against incubation and graduation criteria. When the same finding appears across multiple projects, it signals an ecosystem-wide gap that would be better addressed through standardized guidance than repeated per-project recommendations.

This finding has appeared in 34 of 42 DD reports (81%) scanned over the last 5 years, including cncf/toc#2198 (HAMi), cncf/toc#2057 (Kyverno), cncf/toc#2038 (Microcks), cncf/toc#1754 (Fluid), cncf/toc#1468 (wasmCloud), cncf/toc#1416 (cert-manager), and others. The most recent DD to surface this was HAMi incubation DD (merged 2026-07-02).

Projects routinely have closed roadmap issues, outdated milestones, or no public roadmap at all. Governance docs frequently lack a documented roadmap change process. The TOC recommends a persistent public roadmap but has no standardized guidance for format, location, or freshness expectations.

Scope: Define recommended roadmap format (project board vs in-repo document vs milestone-based), minimum content expectations, change process documentation requirements, and freshness expectations.

Timeline: TBD

Deliverable(s) or exit criteria
  • Guidance document: public roadmap standards (format, location, change process, freshness)
  • Template: roadmap document or project board configuration
  • DD checklist item update — PR to incubation and graduation application templates
Tracking document for meeting and progress

TBD

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

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.