Contacting the TOC
This page helps CNCF projects and maintainers find the right way to reach the Technical Oversight Committee (TOC), raise an issue, or locate the guidance you need. Pick the channel that matches your situation below.
Quick reference
| If you need to... | Use |
|---|---|
| Ask a general question | #toc on CNCF Slack, the public mailing list, or email info@cncf.io |
| Apply to move levels or ask about an application | Open an issue in the TOC repository and see Project Lifecycle and Process |
| Report a governance concern (public) | File a Governance issue in the TOC repository |
| Report a governance concern anonymously or confidentially | Email the private mailing list |
| Raise a sensitive or leadership issue | Email the private mailing list |
| Give feedback or observe the TOC's work | Attend a TOC meeting or comment on GitHub issues |
General questions
For everyday questions about the TOC, the project lifecycle, or where to find something:
- Slack: join the CNCF Slack and post in
#toc. - Public mailing list: cncf-toc@lists.cncf.io (browse the archive).
- CNCF staff: email info@cncf.io if you are unsure who to ask.
Project applications and moving levels
If your project is applying to join the CNCF or move from one maturity level to the next, start with the process documentation and then open an issue so the TOC can track and assign your application:
- Project Lifecycle and Process
- How Projects Move Levels
- How to Submit a Project
- Open an issue in the TOC repository to begin
The TOC's Due Diligence Guide explains how the committee evaluates projects, so you can see what to expect during a review.
Governance concerns
Governance issues, including behavioral concerns involving project leaders, are handled through the TOC's governance remediation process. There are three ways to report, depending on the sensitivity involved:
- Public reports: in most cases, file a Governance-type issue in the TOC repository. If a concern is first raised in another venue, a tracking issue should still be created in the TOC repo for assignment.
- Anonymous reports: if you would prefer your name not be known, email cncf-private-toc@lists.cncf.io. The TOC will create a tracking issue, and your identity will be known only to the TOC team.
- Confidential reports: if there are risks around the details being public, email cncf-private-toc@lists.cncf.io. The TOC and the assessment team will track the request through privately shared documents.
Leadership and behavioral concerns can be raised as violations of the Technical Leadership Principles.
Sensitive issues
When public discussion is not appropriate, reach the TOC privately through the private mailing list. Use this for matters that need confidentiality rather than for general questions.
Meetings and feedback
TOC meetings are open to the public and are a good way to observe the committee's work or share your perspective. See Meeting Information for the schedule, calendar, agendas, and recordings. You can also share feedback by commenting on GitHub issues or posting to the mailing list.
Where to find guidance
- Technical Oversight Committee (TOC) - overview, members, communication channels, and structure
- TOC Operations - the committee's documented processes
- Due Diligence Guide - how projects are evaluated when moving levels
- Project Health Review - how the TOC assesses ongoing project health
- Project Lifecycle and Process - stages, criteria, and how to move levels
- Project Best Practices - governance, security, community, and accessibility guidance
- CNCF Principles - the technical and leadership principles projects are expected to uphold