toc

toc copied to clipboard

I would like to help lead the new cross-TAG Domain Technical Reviews Working Group per the KubeCon EU TOC/TAG session, March 20. Thank you to @TheFoxAtWork for the notes on DTRs.

Note: This is intended to be a long term working group.

Why a Domain Technical Review?

The primary objectives of a Domain Technical Review (DTR) are to ensure the overall quality and robustness of the project, identify any potential weaknesses or areas for improvement, and provide actionable feedback to the project maintainers. This process helps maintain the high standards of excellence associated with CNCF projects and fosters innovation and collaboration within the cloud native ecosystem.

Who is involved in a Domain Technical Review

A Domain Technical Review (DTR) is a collaboration between a project, one or more CNCF Technical Advisory Groups (TAGs) and the CNCF Technical Oversight Committee (TOC).

The DTR Working Group should have a representative from each TAG to inform the DTR guidelines - as well as CNCF TOC represention.

What is a Domain Technical Review

A Domain Technical Review is an engagement by the project and the TAG(s) to fully explore the project in the context of cloud native and the specific domain(s). The Domain Technical Review is to be a comprehensive assessment of a project aimed at evaluating, within the CNCF ecosystem:

• The domain specific technical merits of the project
• Cloud native design principles
• Adherence to domain specific best practices

What are the goals the DTR Working Group

• Provide well structured guidance for the DTR that provides consistency across the TAGs
• Identify the domain specific best practices that inform the DTRs - in collaboration with the CNCF TAG(s) and CNCF TOC
• Avoid presentations by projects without active discussion or feedback from TAG expertise to improve and align the project with CNCF practices

What are the non-goals of the DTR Working Group

• To be determined by the working group and approved by the TOC

cc: @TheFoxAtWork @amye @Riaankl @mrbobbytables

Thanks @angellk ! Would you write up the scope of the DTR effort so others interested in it understand what we're looking to cover here? adding this to the Issue title and primary comment? I've assigned you the issue.

@angellk checking in here wrt updating this issue for the group?

Thanks for the proposal! In relation with this issue https://github.com/cncf/toc/issues/1279 Should we also specify that this is intended to be a long lived Working Group?

I can help and join this working group on behalf of TAG-Runtime. Thanks for organizing!

Happy to help on behalf of TAG-Network.

Raising my hand ✋🏼 from TAG Security. Will eventually hand it off to one of our terrific tech leads

Hi Folks - I am interested in contributing to the DTR working group from TAG Observability.

It looks like we have quorum! I'll set up the kick-off meeting and invite you all.

Happy to join too - TAG Environmental Sustainability

Please join the #wg-dtr slack channel on CNCF slack - we'll coordinate the kick-off meeting there!

:wave: on behalf of End-User TAB

Thank you everyone for the continued momentum with the DTRs.

Please comment and review on the General Technical Questions document.

Starting this week we have been going into deeper technical domain reviews: Storage and Security

Next week: Runtimes and TBD

Please check the slack channel for questions/updates/meeting times.

It would be great to highlight that DTRs help make the process timeline more predictable for projects moving through stages. In a certain way, this helps projects prepare a stronger case, and recruits people in the DTR as champions for the project.