Compile a list of cross cutting task in Tractus-X for the committer meeting

[SebastianBezold]

We do work on a lot of things, that are relevant for Tractus-X as a project, that are potentially unknown to the rest of the committer group.

We need to compile a list of these tasks, to share it in the committer meeting.
This will give us the chance to identify really important topics, that we need to share knowledge about

[FaGru3n]

just want to add some points

• System Team Tasks QG-Checks Stuff, keep it or optimising
• Releasing Plan and Knowledge
• Permission Guidelines
• Awareness raising (Guides how you should act as a committer)
• Mindset to feel responsible for all content within Eclipse Tractus-X
• Workflow Overview
• QG-Checker for the Release
• TRG Maintaining

[SebastianBezold]

System Team specifics

• Automated quality checks (the go code + dashboarding + PR check action)
• "Collecting" charts to the eclipse-tractusx/charts repo
• Docusaurus (how does it work)
• Consortia Infra stack and maintainence (keep in mind, that Tractus-X does not maintain infra)

Committer responsibilities

• TRG/QG check (depending on our release process, that has to be defined)
• Drive TRG alignment, introducing new ones
• cross-cutting support (maybe focus on project contributor, repo creation)
• Project website content
• otterdog
• Dash (how to use, language differences, how to handle and track IP issues)

Misc

• EF contacts? Credentials (DockerHub, SwaggerHub, Nexus to come)
• Legal stuff (Copyright and License deep dive)
• Manage catenax-ng (may become relevant, IF we would opt for persistent environment like we have for consorita)

[tom-rm-meyer-ISST]

List of things we considered a knowledge transfer would be beneficial for:

• App Dashboard -> derive postgres versions for Release
• Automation of quality checks -> at least go code + pr check action @tom-rm-meyer-ISST
• Docusaurus knowledge -> there is no team responsible, no one understands the whole setup; responsiblity is needed