Python: Repository splitting

[WeihanLi]

Currently, we placed all the support across languages/frameworks in one repo, is it possible to split by language?

As a dotnet developer, I only care about the dotnet-related changes, and no need to download the python/java implementations, but since it's all in one repo, I had to fetch them all.

Besides, there are more and more connectors, is it possible to split non-core connectors into another repository/solution? So that we could maintain the core framework and functions easily, and extensions in another or extensions in another solution file?

For multiple languages/frameworks support, I like the open-telemetry repository organization more.

https://github.com/open-telemetry

They put up the Specifications in a repo, and for the language-specific implementation, separate into different repositories, and core implementation for the spec in one repository, some extensions out of spec maintained in another repo.

Thoughts?

[RogerBarreto]

@markwallace-microsoft Good opportunity for an ADR on our decisions for keeping all in once.

[moonbox3]

This ADR goes into the decisions to keep it in one repo right now.

[moonbox3]

Going to close this issue right now as the ADR I linked to is where we currently stand. Thanks for asking, @WeihanLi.

[WeihanLi]

seeing #6820, maybe worth another decision