[Bug 576137] Migrating BaSyx to GitHub

Bugzilla Link	576137
Status	REOPENED
Importance	P3 normal
Reported	Sep 21, 2021 04:15 EDT
Modified	Dec 10, 2021 16:30 EDT

Description

Dear all,

we would like to migrate the BaSyx repository (https://git.eclipse.org/r/basyx/basyx) to GitHub. In this migration process, we plan to split the single repository that currently exists into multiple repositories. Additionally, we plan to keep the existing repository as archive and start with a fresh history to reduce repository size.

Our future repository structure should be as follows:
• eclipse-basyx/java-sdk
• eclipse-basyx/java-components
• eclipse-basyx/java-examples
• eclipse-basyx/cpp-sdk
• eclipse-basyx/cpp-components
• eclipse-basyx/dotnet-sdk
• eclipse-basyx/dotnet-components
• eclipse-basyx/dotnet-applications
• eclipse-basyx/dotnet-examples
• eclipse-basyx/applications

To my knowledge, there are two possibilities: joining the existing EclipseFdn organization or creating a new one (eclipse-basyx). Are there any notable differences between both approachs?

Best regards,
Frank