Skip to content

docs(operations): adopter submission form link and TAB reference architecture substitution - #2256

Open
angellk wants to merge 1 commit into
cncf:mainfrom
angellk:feat/adopter-interview-guide-update
Open

docs(operations): adopter submission form link and TAB reference architecture substitution#2256
angellk wants to merge 1 commit into
cncf:mainfrom
angellk:feat/adopter-interview-guide-update

Conversation

@angellk

@angellk angellk commented Aug 1, 2026

Copy link
Copy Markdown
Contributor

Summary

Test plan

  • Verify markdown renders correctly
  • Confirm form link resolves
  • Confirm TAB reference architecture link resolves

@caniszczyk

Copy link
Copy Markdown
Contributor

I am 120% supportive of this change to get not only more quality reference architecture but to simplify the overall process of moving levels. We need to ensure that the ref archs are high quality, which they usually are AND that the TOC still has the final say on rejecting a refarch if they don't feel it's up to the quality they desire for an adopter interview.

…architecture substitution

Link the Adopter Submission Form in the triage checklist and adopter
interview section. Add guidance that a published TAB Reference
Architecture may replace an individual adopter interview.

Signed-off-by: Karena Angell <karena.angell@gmail.com>
@angellk
angellk force-pushed the feat/adopter-interview-guide-update branch from c69ef7d to 96907ee Compare August 3, 2026 02:55
@caniszczyk
caniszczyk self-requested a review August 3, 2026 14:05

@kevin-wangzefeng kevin-wangzefeng left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks

@brandtkeller brandtkeller left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In support of the TAB Reference Architecture Substitution callout. lgtm.

@kevin-wangzefeng

Copy link
Copy Markdown
Member

I am 120% supportive of this change to get not only more quality reference architecture but to simplify the overall process of moving levels. We need to ensure that the ref archs are high quality, which they usually are AND that the TOC still has the final say on rejecting a refarch if they don't feel it's up to the quality they desire for an adopter interview.

+1 to Chris's point — the TOC should retain final judgment on whether a reference architecture meets the bar of an adopter interview, even when it's published. Also worth being explicit that the reference architecture need to be officially published (not a draft/work-in-progress submission) to qualify as a substitution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants