HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
cncf
toc
HTML2017–2026
cncf / toc

toc

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

28Distinct people
31Mentions
0Explicit recommenders
1.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

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

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 4:01:40 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year31 dated mentions

Observed mentions: 2017-09-24 22:57:50 UTC to 2026-05-12 11:34:25 UTC.

02462017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments20172018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 5 mentions; 2 submissions, 3 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 4 submissions, 2 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 7 mentions; 2 submissions, 5 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC523
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC211
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC642
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC110
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC725
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC303
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC303
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

From the project README

An excerpt from the repository, fetched Nov 13, 2026.

Read the project’s introduction
CNCF Technical Oversight Committee (TOC) The CNCF TOC is the technical governing body of the CNCF. It admits and oversees all projects in the CNCF and has a mandate to facilitate driving neutral consensus for: defining and maintaining the technical vision and principles for the Cloud Native Computing Foundation, approving new projects within the scope of the CNCF set by the Governing Board (GB), creating a conceptual architecture for the projects, aligning projects, removing or archiving projects, accepting feedback from end user technical advisory board and map to projects, aligning interfaces to components under management (code reference implementations before standardizing), and defining common practices to be implemented across CNCF projects, if any. TOC Technical Vision The technical direction of the ecosystem is problem-centric. We encourage and support our projects to solve problems faced by adopters, to build the right ecosystem for innovation and embrace changes in the broader technical landscape. To exercise and increase the expertise within the technical community to compose solutions that stand the test of time. TOC Members Ahmed Bebars (term: 2 years - start date: 5/12/2026 - 5/12/2028) [EndUser-appointed] Alex Chircop (term: 2 years - start date: 3/4/2025 - 3/4/2027) [TOC-appointed] Brandt Keller (term: 2 years - start date: 5/12/2026 - 5/12/2028) [TOC-appointed] Chad Beaudin (term: 2 years - start date: 3/4/2025 - 3/4/2027) [EndUser-appointed] Faseela K (term: 2 years - start date: 3/4/2025 - 3/4/2027) [GB-appointed] Jeremy Rickard (term: 2 years - start date: 3/4/2025 - 3/4/2027) [GB-appointed] Joseph Sandoval (term: 2 years - start date: 5/12/2026 - 5/12/2028) [GB-appointed] Karena Angell (term: 2 years - start date: 3/4/2025 - 3/4/2027) [GB-appointed][TOC Chair] Kevin Wang (term: 2 years - start date: 5/12/2026 - 5/12/2028) [GB-appointed] Mario Fahlandt (term: 2 years - start date: 5/12/2026 - 5/12/2028) [GB-appointed] Mauricio Salatino (term: 2 years - start date: 5/12/2026 - 5/12/2028) [Maintainer-appointed] TOC Alternates Katie Gamanji (term: 1 year - start date: 5/12/2026 - 5/12/2027) [GB-appointed][alternate] Ricardo Aravena (term: 1 year - start date: 5/12/2026 - 5/12/2027) [TOC-appointed][alternate] Note: TOC Alternates are non-voting members of the TOC Election schedule TAG / TCG Liaisons Karena Angell (@angellk) — TAG Security and Compliance Brandt Keller (@brandtkeller) — TAG Infrastructure, TCG Platform Engineering Faseela K (@kfaseela) — TAG Infrastructure, TAG Operational Resilience, TCG Environmental Sustainability Alex Chircop (@chira001) — TAG Workloads Foundation, TAG Infrastructure, TCG Platform Engineering Kevin Wang (@kevin-wangzefeng) — TCG Artificial Intelligence, TCG Environmental Sustainability Mauricio Salatino (@salaboy) — TAG Developer Experience, TAG Operational Resilience, TCG Artificial Intelligence Mario Fahlandt (@mfahlandt) — TAG Security and Compliance, TAG Operational Resilience, TCG Software Supply Chain Security Chad Beaudin (@chadbeaudin) — TAG Operational Resilience, TAG Workloads Foundation Ahmed Bebars (@abebars) — TAG Developer Experience Jeremy Rickard (@jeremyrickard) — TAG Workloads Foundation, TAG Operational Resilience Joseph Sandoval (@jrsapi) — TAG Developer Experience, TAG Workloads Foundation Projects See the current CNCF projects and a description of project maturity levels (Sandbox, Incubating, Graduated). The CNCF provides a list of services for incubating and graduated projects hosted in the foundation. A subset of these services is also available for Sandbox level projects. Do you want to contribute to a project? We have a guide to get you started. If you would like to know more about the project lifecycle we use, we have outlined the process. If you have any questions or don't know where to start, please open an issue. Meeting Time The TOC meets on the 1st and 3rd Tuesday of every month at 8AM PT (USA Pacific Time; Convert to local time zone). Here is a calendar for all public CNCF events. This calendar is also available on the CNCF Website Meetings can be joined directly form the calendar. Meeting Agenda and Minutes Meeting Agenda and Minutes Archive (2018.10~2024.08) of Meeting Working Doc. This includes minutes from previous meetings. Archive (2016.02~2019.06) of Meeting agenda and presentations. Archive (2016.04~2018.11) of community presentations CNCF TOC Playlist on YouTube Mailing List Public mailing list for the CNCF TOC: cncf-toc@lists.cncf.io The public mailing archive: https://lists.cncf.io/g/cncf-toc Details to join this public mailing list: https://lists.cncf.io/mailman/listinfo/cncf-toc In case you need to reach the CNCF TOC on sensitive issues, please email us at: cncf-private-toc@lists.cncf.io Slack Public CNCF TOC channel: Join the CNCF slack and we are reachable at #toc. Voting This is our voting policy. Only TOC members can cast binding votes. (+1 Binding) Technical Advisory Groups and TOC SubProjects Technical Advisory Groups TAG Developer Experience TAG Infrastructure TAG Operational Resilience TAG Security and Compliance TAG Workloads Foundation TOC SubProjects Contributor Strategy and Advocacy SubProject Mentoring SubProject Technical Advisory Groups - Archived The TOC has approved the formation of TAGs. The following Technical Advisory Groups have been archived: TAG-Security TAG-Storage TAG-App-Delivery TAG-Network TAG-Runtime TAG Contributor Strategy TAG Observability TAG Environmental Sustainability These Technical Advisory Groups have been spun down and replaced with new Technical Advisory Groups and TOC SubProjects, listed above. Updating TAG or SubProject README files To modify the README files for individual TAGs or TOC SubProjects, please do not edit them directly. Instead, the source of truth for these files is the tags.yaml file. To understand the process for updating these READMEs by modifying tags.yaml, please refer to the Updating TOC TAG and SubProject READ
Read the full README on GitHub

What Hacker News says

5 sources
I hear you. The goal of our analytics collection is to know the # of active users of our product. So, we send an event to Google Analytics when a command is run or periodic pings for long running (> 1 hr) commands. You can disable it by setting the flag --enable-analytics=false. You can see further discussion on this matter here: https://github.com/cncf/toc/issues/107#issue-311155675 Lastly, everything is open source. So, you are free to read the code and modify and use your modified version if that's what you prefer. xref: https://github.com/kubedb/operator/blob/0.9.0/pkg/cmds/root....
In Show HN: KubeDB – Kubernetes-ready production-grade databases
The context is that Dragonfly has recently been proposed to the CNCF Sandbox[0]. Checkout the HN previous thread[1]. I've worked on P2P distribution systems and found that not many people are able to reuse these systems because of assumptions about the network that are not consistent across all environments. Eager to hear if anyone besides Alibaba is using Dragonfly as a counterpoint. [0]: https://github.com/cncf/toc/issues/130 [1]: https://news.ycombinator.com/item?id=17303055
In Dragonfly: an intelligent P2P based file distribution system

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.