search

open-telemetry / opentelemetry-rust-contrib

OpenTelemetry Contrib Packages for Rust
Apache License 2.0
35 stars 34 forks source link

[Bug]: OpenTelemetry Stackdriver exporter build is failing #66

Closed lalitb closed 4 months ago

lalitb commented 4 months ago

What happened?

The crate is excluded from the workspace, and also tests disabled in scripts/test.sh. Include in the workspace once fixed.

API Version

v0.22

SDK Version

v0.22

What component are you working with?

No response

Relevant log output

Refer #64
djc commented 4 months ago

Okay, if there's no capacity/interest in actually fixing this crate, maybe it would be better to move it from this repo to somewhere else?

cijothomas commented 4 months ago

Okay, if there's no capacity/interest in actually fixing this crate, maybe it would be better to move it from this repo to somewhere else?

We could allow per crate owners who can take of the individual crates. https://github.com/open-telemetry/opentelemetry-rust-contrib/issues/36 This is not yet done, simply because of lack of manpower/bandwidth!

djc commented 4 months ago

Okay, if there's no capacity/interest in actually fixing this crate, maybe it would be better to move it from this repo to somewhere else?

We could allow per crate owners who can take of the individual crates. #36 This is not yet done, simply because of lack of manpower/bandwidth!

So lack of manpower/bandwidth is preventing more people from coming on board? Sounds like you might want to reprioritize?

I would actually prefer to just move opentelemetry-stackdriver to another repo since there seems to be little value in being a part of this repository at this point.

cijothomas commented 4 months ago

So lack of manpower/bandwidth is preventing more people from coming on board? Sounds like you might want to reprioritize?

I am not sure I understood this comment. Would you elaborate?

djc commented 4 months ago

I meant that it would make more sense to prioritize the onboarding of more code owners, because it would relieve some of the manpower/bandwidth constraints of the existing maintainer team.

cijothomas commented 4 months ago

I meant that it would make more sense to prioritize the onboarding of more code owners, because it would relieve some of the manpower/bandwidth constraints of the existing maintainer team.

Nothing is blocking any contributor from contributing code to this repo even today! Defining the process takes a lot of time - there is no org wide guidelines from OpenTelemetry, so every repo has defined own processes. We need to steal from one of the repos.