logo

cncf/toc

⚖️ The CNCF Technical Oversight Committee (TOC) is the technical governing body of the CNCF Foundation.

Hosted by Cloud Native Computing Foundation · part of Linux Foundation

View on GitHub ↗Jump to charts ↓Open shareable report →

cncf/toc has 1.5k+ stars and 700+ forks on GitHub, is written in HTML, and was last pushed on Oct 13, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 29 minutes ago
Type:Documentation / SpecificationCategory(s):General Awesome Lists & DirectoriesLearning & Resources
Added to GitGenius on October 12th, 2026
Created on December 7th, 2015
Open Issues & Pull Requests: 147 (+0)
GitHub issues: Enabled
Number of forks: 729
Total Stargazers: 1,885 (+0)
Total Subscribers: 216 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.7 days
Mean response time: 41.4 days
90th percentile: 146.3 days
Tracked items: 431

Most active contributors

Sign in to see contributor activity.
Sign in

Related repositories by overlapping contributors

Maintainer activity

62 people did triage or write work on this repository in the last 12 months.

At least 10% of toc's 62 maintainers work at Red Hat. 50 say where they work, and 6 of those are Red Hat.

Cloud Native Computing Foundation owns this repository. 4 of its people did this work here, and are not included above.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

About 8% of issues opened in the past year have never received a reply. 95% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "gitvote" is answered fastest, typically in about an hour, while "kind/meeting" waits about 8 weeks. 21% of tracked open issues have had no activity in three months. Only 52% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 118
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 311 days
Stale 30+ days: 58
Stale 90+ days: 39

Recent activity

Opened in 7 days: 2
Closed in 7 days: 1
Comments in 7 days: 6
Events in 7 days: 16

Top labels

  • needs-triage (150)
  • toc (108)
  • kind/meeting (89)
  • kind/initiative (75)
  • triage/valid (70)
  • sub/project-reviews (67)
  • needs-kind (63)
  • gitvote/closed (58)

Most active issues this week

Sign in to see which issues are moving.
Sign in
Explore full issue details

Detailed Description

The CNCF Technical Oversight Committee is the technical governing body of the Cloud Native Computing Foundation that admits, oversees, and provides strategic direction for all projects within the CNCF ecosystem.

The TOC addresses the challenge of maintaining coherent technical vision and governance across a large, distributed ecosystem of cloud-native projects. It operates by establishing principles and technical direction, reviewing and approving new projects, creating conceptual architecture for the ecosystem, aligning project interfaces, and defining common practices. The committee takes a problem-centric approach, encouraging projects to solve real adopter challenges while remaining responsive to changes in the broader technical landscape.

This repository is not a tool for adoption by individual developers or organizations. Rather, it serves as the public record and operational hub for the CNCF's technical governance structure. It is relevant to maintainers of projects seeking CNCF membership, end users participating in technical advisory boards, and anyone needing to understand the governance framework and technical principles guiding the cloud-native ecosystem. The repository documents the TOC's mandate, principles, member composition, and decision-making processes.

The project maintains active governance with regular member terms and a defined election schedule. The repository contains operational documentation including principles, election procedures, and liaison structures with technical advisory groups. Development activity centers on governance updates and administrative records rather than software development in the traditional sense.