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

[Initiative]: Vendor neutrality guidance for CNCF projects

Open
  • Is something wrong?
#2,231 1 comment 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
38/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
docker
Domain
devops, documentation, infrastructure

Research direction

Start with the CNCF vendor-neutrality guidelines and the cited due diligence reports to identify recurring requirements. Define maturity-level guidance covering governance, container image metadata, infrastructure ownership, and website content, then update the DD application templates. Done means the guidance document, metadata template, reviewer checklist, and template update are complete.

Written by the indexing model from the issue text.

Description

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

Vendor neutrality guidance for CNCF projects

Short description

Standardize vendor-neutrality expectations for CNCF projects across governance rules, container image metadata, and infrastructure ownership.

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 24 of 42 DD reports (57%) scanned over the last 5 years, including cncf/toc#2198 (HAMi), cncf/toc#1919 (Crossplane), cncf/toc#1468 (wasmCloud), cncf/toc#1862 (KServe), cncf/toc#1923 (OpenFGA), cncf/toc#1820 (Knative), and others. The most recent DD to surface this was HAMi incubation DD (merged 2026-07-02).

DDs routinely flag vendor-neutrality concerns across three areas: (1) governance docs lacking written vendor-neutrality rules, (2) container images using employer-specific LABEL maintainer values or email addresses instead of project-neutral contacts, and (3) project infrastructure (websites, release pipelines, security contacts) tied to a single vendor. The CNCF vendor-neutrality guidelines exist but are not operationalized into specific, checkable requirements for DD reviewers.

Scope: Translate the CNCF vendor-neutrality guidelines into actionable requirements for projects at each maturity level. Cover governance documentation (written vendor-neutrality rules), container image metadata (OCI annotations, project-neutral contacts), infrastructure ownership (domains, CI/CD, release signing), and website content (commercial product links, sponsor visibility).

Timeline: TBD

Deliverable(s) or exit criteria
  • Guidance document: vendor-neutrality requirements by maturity level
  • Container image metadata template (OCI annotations, Dockerfile LABEL patterns)
  • Vendor-neutrality checklist for DD reviewers
  • 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 DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.