define and document the end user groups we want to (re)form

[rochaporto]

Following the discussions in Atlanta.

Things we would also like to have:

• Create a schema for healthy agendas that will keep end users engaged

[rochaporto]

From the notes:

• Keeping end user groups healthy
• Should we have regular scheduled sessions/topics covering end user feedback on specific projects?
  • How are projects picked in a fair way?
• Establish a healthy agenda, recurring topics
• Track / sessions dedicated to end user groups at kubecon

[rochaporto]

https://github.com/cncf/tab?tab=readme-ov-file#contribution

End user groups that can be taken as a starting point:

• Public sector end user group
• Platform Engineering TCG
• Research

Other possible groups:

• Transportation (died out)
• Telco

Do we need multiple groups or should we start with a single one and split later? Some groups seem quite specialized (public sector, research). On the other hand, some things (data science, notebooks, ...) are now valid for most businesses.

Next steps:

• Summarize the options above (multiple groups + one big group)
• Attach chairs to each of them, responsible to keep agendas going - consider org diversity requirements on leadership
• Each group can regularly report at the TAB public meeting (3rd monday)