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 the Specification this means taking ownership of the proto related tooling and having a single repository that would be maintained by Specification owners (in addition to the opentelemetry-proto repository).
reyang
added
the
triaged-accepted
The issue is triaged and accepted by the OTel community, one can proceed with creating a PR proposal
label
Feb 28, 2024
svrnm
removed
the
triaged-accepted
The issue is triaged and accepted by the OTel community, one can proceed with creating a PR proposal
label
Apr 22, 2024
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 the Specification this means taking ownership of the proto related tooling and having a single repository that would be maintained by Specification owners (in addition to the opentelemetry-proto repository).
Related: open-telemetry/semantic-conventions#767
Related: open-telemetry/opentelemetry-cpp#2550
The text was updated successfully, but these errors were encountered: