[exporter/opensearch] Component maintenance

[atoulme]

Component(s)

exporter/opensearch

Describe the issue you're reporting

A high number of issues related to the opensearch exporter are open without feedback from codeowners consistently.

Would codeowners please work through the list and provide guidance to contributors?
Here is a search with all active issues and PRs: exporter/opensearch

[github-actions]

Pinging code owners:

• exporter/opensearch: @Aneurysm9 @MitchellGale @MaxKsyunz @YANG-DB

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[VihasMakwana]

Although I'm not a code owner, I'll do my best to tackle these issues.

[atoulme]

I have not heard back. At the last SIG meeting, I brought up this issue and received the advice to directly update the component as unmaintained. If anyone wants to open a PR for this, please go ahead, or I will given time.

[atoulme]

I still have not heard back. I will move this component to unmaintained and it will be removed after a period of time unless codeowners chime in.

[vmmusings]

Hi @atoulme, I am a maintainer in opensearch project. What should I do to become codeowner of this exporter?

[codeboten]

@vamsi-amazon thanks for reaching out, the best thing to do is to get involved by looking at the open issues/prs exporter/opensearch

To become a code owner, you'll need to become a member of the opentelemetry github organization, see more details here: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CONTRIBUTING.md#becoming-a-code-owner

[atoulme]

This is still not resolved. As the component was marked unmaintained on 11/6/24, it will be removed after 5/6/25.

@vmvault please see the comment by @codeboten