Skip to content
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

[blog] Notice about removal of Go Contrib modules and call for Code Owners #4502

Closed
pellared opened this issue May 17, 2024 · 6 comments · Fixed by #4543
Closed

[blog] Notice about removal of Go Contrib modules and call for Code Owners #4502

pellared opened this issue May 17, 2024 · 6 comments · Fixed by #4543
Assignees

Comments

@pellared
Copy link
Member

pellared commented May 17, 2024

Desired feature or idea:

The Go SIG plans to remove deprecate and remove Contrib modules (instrumentation libraries, resource detectors, samplers, propagators) that have no Code Owners unless we find some.

We think that it may be good to have some public announcement (blog post?) so that:

  1. users will be notified that some modules are not maintained and they are going to be removed
  2. we might actually find devs who would like to be code owners so some modules will not get removed

I think it would be good if the blog post would

Additional context:

Example deprecation PR:

Example blog post content:

The Go maintainers identified that some Contrib modules do not have any Code Owner. Because of this the following modules are planned to be deprecated and later removed:

For each module, the removal is planned for no sooner than August 21, 2024 unless a Code Owner is found.

@pellared
Copy link
Member Author

CC @open-telemetry/go-approvers

@theletterf
Copy link
Member

@svrnm Did we publish similar call to actions / calls for volunteers in the past?

@svrnm
Copy link
Member

svrnm commented May 22, 2024

@svrnm Did we publish similar call to actions / calls for volunteers in the past?

I don't think so, but I am OK with doing that

@dmathieu
Copy link
Member

Should it be something we do across several languages rather than just Go?

@svrnm
Copy link
Member

svrnm commented May 23, 2024

Should it be something we do across several languages rather than just Go?

I am OK with having it for go only, other SIGs can follow up with their own call to action whenever they are ready. Although if other SIGs want to do it jointly we can have it, maybe you check in #otel-maintainers

@theletterf
Copy link
Member

Draft is ready for review! #4543

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants