-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Otelecho at risk of removal #2637
Otelecho at risk of removal #2637
Comments
I guess time to fork it has come |
Not necessarily. Several other instrumentations have folks stepping up to own the instrumentation. |
The module is now scheduled for removal, is there a fork being maintained elsewhere? |
I have contributed to |
I would invite you to see the requirements on the issue linked above, and join one of the SIG meetings to let yourself known. |
@asahasrabuddhe did you join yet? |
This issue can be closed thanks to open-telemetry/opentelemetry-go-contrib#6207 |
This issue is to inform the maintainers of the echo library (and users reading issues) that the otelecho library, which allows instrumenting echo with OpenTelemetry lacks a code owner, and has therefore been deprecated and will be removed in a couple months.
See open-telemetry/opentelemetry-go-contrib#5550
There are two main ways this removal can be mitigated. Someone could volunteer to be code owner for this package, or the echo community could take over this package and move it into your repository/organization.
I and the OpenTelemetry Go SIG is available if you have any questions regarding ownership of instrumentation packages.
If you wish to talk to us directly about it, feel free to join our SIG meeting which happens on thursdays.
The text was updated successfully, but these errors were encountered: