cncf / cncf/tab

[TAB Meeting][Private] 2026-09-14

Open
#149 0 comments 0 reactions 0 assignees View on GitHub
kind/meeting
Dominant language
Go
Stars
104
Forks
14
Avg merge
5d 23h
Merged PRs (30d)
3

Description

**Host:**
**Note Taker:**

**Recurring Items**
* [LF Antitrust Policy](https://docs.google.com/presentation/d/1tNOOPWqZMMcUQjes7J-Fc8__5vGmNsxtZnfOw6dLlpc/edit?usp=sharing)
* [Review TAB Work Board](https://github.com/orgs/cncf/projects/45/views/6)

**Agenda**
* Minimum depth bar for Reference Architecture and Case Study submissions used as Due Diligence adopter interview substitutes
**Background:** The TOC now lets a published TAB Reference Architecture (and soon, a CNCF Case Study) substitute for an individual adopter interview during project Due Diligence. That only works if RA/case study submissions reliably carry interview grade evidence, and today they don't. Asking the TAB to set a minimum depth bar for submissions.

cncf/toc#2256 (merged) added the original TAB Reference Architecture substitution to the TOC's Due Diligence guide: a project's inclusion in a published RA "may serve as a replacement for an individual adopter interview."

cncf/toc#2282 (open) extends the same substitution to CNCF Case Studies, with the same "may serve as a replacement" language.

Neither the merged DD guide text nor the TAB's own RA submission process currently requires any minimum depth for a submission to count as adopter interview equivalent evidence, and there's no cap on how many of the required interviews a single project can satisfy this way.

***State of open Reference Architecture submissions.** 8 currently open:

| Issue | Project | Opened | Last Activity | Status |
|---|---|---|---|---|
| #99 | Infosys, 5G Telecom Data Platform | 2025-11-24 | 2026-09-09 | Active |
| #119 | NYT, Internal Developer Platform | 2026-03-23 | 2026-06-22 | Stale |
| #128 | Agentic Multi Cloud FinOps | 2026-04-16 | 2026-06-22 | Stale |
| #133 | Durable Workflow Orchestration | 2026-05-29 | 2026-07-06 | Stale |
| #139 | EU Data Sovereignty GitOps Platform | 2026-06-11 | 2026-06-22 | Stale |
| #140 | China Merchants Bank | 2026-07-28 | 2026-09-09 | Active |
| #141 | NB Bank (Bank of Ningbo) | 2026-07-30 | 2026-07-31 | Stale |
| #147 | Ant Group, Kata Sandboxes/Xolis | 2026-08-12 | 2026-09-05 | Active |

Goal: go through each, decide what's actually moving versus what needs to be closed or reassigned, and clear as much of this backlog as we can before KubeCon NA (Nov 9).

_Carried forward from #148 (2026-08-24 meeting had no quorum; 2026-08-31 skipped as a 5th Monday; 2026-09-07 skipped as Labor Day)._

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing cncf/toc#2256 and cncf/toc#2282, then inspect the open Reference Architecture issues listed in this agenda. Done means the TAB has decided the minimum evidence depth, any limit on substitutions, and which submissions should be closed or reassigned before KubeCon NA.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.