TRG 7.10 Creation of Repositories

```mermaid

flowchart TD
T((Start)) --> FIST
FIST[1: Define the requirements for a Repo Creation in sig-release] --> A
A[2: Fill up your repository name, description and set the parameters in the template]
A --> B[3: Navigate to the Eclipse Tractus-X repo .eclipsefdn]
B --> C[4: Fork the repository]
C --> D[5: In your fork implement the change in a new line]
D --> E[6: Create a Pull request from fork main to main branch in the .eclipsefdn]
E --> F[7: Wait for a Project Lead to approve the pull request]
F --> G{Approved by Project Lead}
G -- Yes --> H[8: Project lead will merge with `otterdog /merge`]
G -- No --> I[9: Implement changes]
I -- Try Again --> G
I -- Close PR --> J
H --> J(("END"))

```

14.02.2025
- Define rules for core/special repos,
- Tell in the office hour that you will create a new repo

21.02.2025:
- Discuss in the pr which is not yet there

07.02.2025:
- Kafka Extension Incident open our eyes and showed how important would be to have a TRG.

How the alignment be done? (from a process perspective)
- Add a new step -> please request the review from all the committers to the repository
- Announce it in the mail list -> 1 week response time (inspire in the deprecation)
- Office Hour or Committer Meeting announcement
- Importantance: Timeframe and inform everyone!

@ndr-brt @rafaelmag110