WIP: Add draft CNCF TAG Infrastructure Charter

[xing-yang]

This is from this doc: https://docs.google.com/document/d/1Icu0Gz-NX1zJBOkp4nThTqT_o-BLGABPTShR94GMrRk/edit?tab=t.0#heading=h.z7nikj46tsbw
We are still working on it. WIP doc is here: https://docs.google.com/document/d/1AJOLnb-YZgZrOHLPRCbN8P7UGh4u0lfiJ3NadQc6BRk/edit?tab=t.0

[aojea]

I think we should aggregate all the Network sub-sub-domains under Network as we do in the other areas: DNS, LoadBlancing and Service Mesh are part of Network

Suggested change

	- Network
	- DNS
	- Compute
	- Service Mesh
	- Infrastructure Lifecycle (includes Infrastructure-as-Code)
	- Edge
	- Sovereignty
	- Load Balancing
	- Network
	- Compute
	- Infrastructure Lifecycle (includes Infrastructure-as-Code)
	- Edge
	- Sovereignty

[rochaporto]

The list comes from the original definition in:
https://www.cncf.io/blog/2025/05/07/10-years-in-cloud-native-toc-restructures-technical-groups/

and also in the TAG presentation:
https://docs.google.com/presentation/d/1yXHP0tPiAS8Mnzo0K2ntHGn3Y2TwzYkYYT0BGUWry-k/edit?slide=id.g32e9d35ac66_0_386#slide=id.g32e9d35ac66_0_386

We might want to keep explicit so it's clear what is and what isn't in scope in this and other TAGs.

[aojea]

yeah, my confusion comes from that , since Network is a general concept that covers all the others, that is why I asked, since Network is at the same level of the others instead of being a parent

[aojea]

Suggested change

The TAG Infrastructure charter is directly aligned with the CNCF TOC charter. The TOC is the technical governing body responsible for maintaining the technical vision and driving common practices across projects. The TOC's vision is problem-centric, encouraging projects to solve challenges faced by adopters. By focusing on fundamental infrastructure problems such as Data, Storage, Network, Compute, and Service Mesh, the TAG Infrastructure directly addresses significant problems faced by cloud native adopters and projects in building and managing their underlying infrastructure. The TAG's work in defining practices, conducting assessments (as shown in example Subprojects and Initiatives), and potentially creating guidelines contributes to driving common practices across the ecosystem, as mandated by the TOC. The TAG's work in defining best practices, frameworks, and performing assessments contributes to driving common practices and aligning projects within the ecosystem, as mandated by the TOC.

The TAG Infrastructure charter is directly aligned with the CNCF TOC charter. The TOC is the technical governing body responsible for maintaining the technical vision and driving common practices across projects. The TOC's vision is problem-centric, encouraging projects to solve challenges faced by adopters. By focusing on fundamental infrastructure problems such as Data, Storage, Network and Compute the TAG Infrastructure directly addresses significant problems faced by cloud native adopters and projects in building and managing their underlying infrastructure. The TAG's work in defining practices, conducting assessments (as shown in example Subprojects and Initiatives), and potentially creating guidelines contributes to driving common practices across the ecosystem, as mandated by the TOC. The TAG's work in defining best practices, frameworks, and performing assessments contributes to driving common practices and aligning projects within the ecosystem, as mandated by the TOC.

[aojea]

these last two senteces " and potentially creating guidelines contributes to driving common practices across the ecosystem, as mandated by the TOC. The TAG's work in defining best practices, frameworks, and performing assessments contributes to driving common practices and aligning projects within the ecosystem, as mandated by the TOC." repeat "as mandated by the TOC, it seems we can rephrase it to make more clear.