You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today the build-tools repository is an amalgamation of three major components:
A docker image with C++ development tooling
A docker image to validate the open-telemetry/opentelemetry-proto repository
Tooling for semantic conventions.
Due to the split ownership model, no single group feels responsible and simple fixes like dependabot PRs have lagged in this repository.
I'd like to propose splitting out components with clear ownership. For Semantic Conventions this would be the tooling around schemas + code generation. We would still build a docker image from the new repository, but ownership would be 100% the domain of semantic-conventions maintainers and would now be part of semconv triage.
Today the
build-tools
repository is an amalgamation of three major components:Due to the split ownership model, no single group feels responsible and simple fixes like dependabot PRs have lagged in this repository.
I'd like to propose splitting out components with clear ownership. For Semantic Conventions this would be the tooling around schemas + code generation. We would still build a docker image from the new repository, but ownership would be 100% the domain of semantic-conventions maintainers and would now be part of semconv triage.
Related: open-telemetry/opentelemetry-cpp#2550
Related: open-telemetry/opentelemetry-specification#3899
The text was updated successfully, but these errors were encountered: