Skip to content

[exporter/kinetica] mark Unmaintained #36808

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

Merged

Conversation

TylerHelmuth
Copy link
Member

Description

This exporter was added as a vendor-specific component via #24294. It no longer has its vendor sponsor as a code owner.

Following our Unmaintained guidelines, this component is now considered unmaintained.

@am-kinetica @kyle-sutton please respond if Kinetica is interested in continuing to maintain this component.

Copy link
Contributor

@atoulme atoulme left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed the component and agreeing with the diagnosis.

@TylerHelmuth TylerHelmuth merged commit 7e3d003 into open-telemetry:main Dec 12, 2024
160 checks passed
@TylerHelmuth TylerHelmuth deleted the kineticaexporter-unmaintained branch December 12, 2024 17:39
@github-actions github-actions bot added this to the next release milestone Dec 12, 2024
@am-kinetica
Copy link
Contributor

@TylerHelmuth @atoulme We at Kinetica are certainly interested in maintaining the exporter component and contributing updates and fixes to it. We were off track for some time but do plans around it. What do we have to do ? Thanks.

@TylerHelmuth
Copy link
Member Author

@am-kinetica please follow these instructions to become of the open telemetry org and then you can be a code owner again.

sbylica-splunk pushed a commit to sbylica-splunk/opentelemetry-collector-contrib that referenced this pull request Dec 17, 2024
#### Description

This exporter was added as a vendor-specific component via
open-telemetry#24294.
It [no longer has its vendor sponsor as a code
owner](open-telemetry#36229).

Following our [Unmaintained
guidelines](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained),
this component is now considered unmaintained.

@am-kinetica @kyle-sutton please respond if Kinetica is interested in
continuing to maintain this component.
mterhar pushed a commit to mterhar/opentelemetry-collector-contrib that referenced this pull request Dec 19, 2024
#### Description

This exporter was added as a vendor-specific component via
open-telemetry#24294.
It [no longer has its vendor sponsor as a code
owner](open-telemetry#36229).

Following our [Unmaintained
guidelines](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained),
this component is now considered unmaintained.

@am-kinetica @kyle-sutton please respond if Kinetica is interested in
continuing to maintain this component.
AkhigbeEromo pushed a commit to sematext/opentelemetry-collector-contrib that referenced this pull request Jan 13, 2025
#### Description

This exporter was added as a vendor-specific component via
open-telemetry#24294.
It [no longer has its vendor sponsor as a code
owner](open-telemetry#36229).

Following our [Unmaintained
guidelines](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained),
this component is now considered unmaintained.

@am-kinetica @kyle-sutton please respond if Kinetica is interested in
continuing to maintain this component.
zeck-ops pushed a commit to zeck-ops/opentelemetry-collector-contrib that referenced this pull request Apr 23, 2025
#### Description

This exporter was added as a vendor-specific component via
open-telemetry#24294.
It [no longer has its vendor sponsor as a code
owner](open-telemetry#36229).

Following our [Unmaintained
guidelines](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained),
this component is now considered unmaintained.

@am-kinetica @kyle-sutton please respond if Kinetica is interested in
continuing to maintain this component.
@am-kinetica
Copy link
Contributor

am-kinetica commented Apr 23, 2025

@TylerHelmuth - I think I have already become a member. What do I need to do to remove the unmaintained status ?
open-telemetry/community#2592 (comment)

@TylerHelmuth
Copy link
Member Author

@am-kinetica please open a PR to change its status

atoulme pushed a commit that referenced this pull request May 15, 2025
<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
By definition, the [unmaintained
status](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained)
means that the component "does not have an active code owner." This PR
moves code owners of two components (the `kinetica` and `opensearch`
exporters) to emeritus.

`exporter/kinetica`: @TylerHelmuth was listed as the active code owner,
but [moved the exporter to
unmaintained](#36808).

`exporter/opensearch`: This component was marked unmaintained as a part
of
#35781.
It looks like there's an effort to add new code owners (which is great
to see), but that does not include @Aneurysm9, the user currently listed
as the code owner.

_This PR also adds the `seeking_new: true` flag to all unmaintained
components as per the
[documentation](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained),
"Components that are unmaintained are actively seeking contributors to
become code owners."._

The reason for this change is the listed code owners in component
READMEs do not match the `.github/CODEOWNERS` file. This is because the
build tool generating the CODEOWNERS file [does not check for code
owners of unmaintained
components](https://github.com/open-telemetry/opentelemetry-go-build-tools/blob/6bdbad9c2432ef2c34105a2c65357ffa2d86666d/githubgen/codeowners.go#L48).
This follows the definition of unmaintained so I believe we should
follow the definition here rather than modify the build tool.

_Credit to @pjanotti for pointing out this discrepancy_
seongpil0948 pushed a commit to seongpil0948/opentelemetry-collector-contrib that referenced this pull request May 16, 2025
)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
By definition, the [unmaintained
status](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained)
means that the component "does not have an active code owner." This PR
moves code owners of two components (the `kinetica` and `opensearch`
exporters) to emeritus.

`exporter/kinetica`: @TylerHelmuth was listed as the active code owner,
but [moved the exporter to
unmaintained](open-telemetry#36808).

`exporter/opensearch`: This component was marked unmaintained as a part
of
open-telemetry#35781.
It looks like there's an effort to add new code owners (which is great
to see), but that does not include @Aneurysm9, the user currently listed
as the code owner.

_This PR also adds the `seeking_new: true` flag to all unmaintained
components as per the
[documentation](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained),
"Components that are unmaintained are actively seeking contributors to
become code owners."._

The reason for this change is the listed code owners in component
READMEs do not match the `.github/CODEOWNERS` file. This is because the
build tool generating the CODEOWNERS file [does not check for code
owners of unmaintained
components](https://github.com/open-telemetry/opentelemetry-go-build-tools/blob/6bdbad9c2432ef2c34105a2c65357ffa2d86666d/githubgen/codeowners.go#L48).
This follows the definition of unmaintained so I believe we should
follow the definition here rather than modify the build tool.

_Credit to @pjanotti for pointing out this discrepancy_
johnleslie pushed a commit to johnleslie/opentelemetry-collector-contrib that referenced this pull request May 23, 2025
)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
By definition, the [unmaintained
status](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained)
means that the component "does not have an active code owner." This PR
moves code owners of two components (the `kinetica` and `opensearch`
exporters) to emeritus.

`exporter/kinetica`: @TylerHelmuth was listed as the active code owner,
but [moved the exporter to
unmaintained](open-telemetry#36808).

`exporter/opensearch`: This component was marked unmaintained as a part
of
open-telemetry#35781.
It looks like there's an effort to add new code owners (which is great
to see), but that does not include @Aneurysm9, the user currently listed
as the code owner.

_This PR also adds the `seeking_new: true` flag to all unmaintained
components as per the
[documentation](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained),
"Components that are unmaintained are actively seeking contributors to
become code owners."._

The reason for this change is the listed code owners in component
READMEs do not match the `.github/CODEOWNERS` file. This is because the
build tool generating the CODEOWNERS file [does not check for code
owners of unmaintained
components](https://github.com/open-telemetry/opentelemetry-go-build-tools/blob/6bdbad9c2432ef2c34105a2c65357ffa2d86666d/githubgen/codeowners.go#L48).
This follows the definition of unmaintained so I believe we should
follow the definition here rather than modify the build tool.

_Credit to @pjanotti for pointing out this discrepancy_
johnleslie pushed a commit to johnleslie/opentelemetry-collector-contrib that referenced this pull request May 23, 2025
)

<!--Ex. Fixing a bug - Describe the bug and how this fixes the issue.
Ex. Adding a feature - Explain what this achieves.-->
#### Description
By definition, the [unmaintained
status](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained)
means that the component "does not have an active code owner." This PR
moves code owners of two components (the `kinetica` and `opensearch`
exporters) to emeritus.

`exporter/kinetica`: @TylerHelmuth was listed as the active code owner,
but [moved the exporter to
unmaintained](open-telemetry#36808).

`exporter/opensearch`: This component was marked unmaintained as a part
of
open-telemetry#35781.
It looks like there's an effort to add new code owners (which is great
to see), but that does not include @Aneurysm9, the user currently listed
as the code owner.

_This PR also adds the `seeking_new: true` flag to all unmaintained
components as per the
[documentation](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/component-stability.md#unmaintained),
"Components that are unmaintained are actively seeking contributors to
become code owners."._

The reason for this change is the listed code owners in component
READMEs do not match the `.github/CODEOWNERS` file. This is because the
build tool generating the CODEOWNERS file [does not check for code
owners of unmaintained
components](https://github.com/open-telemetry/opentelemetry-go-build-tools/blob/6bdbad9c2432ef2c34105a2c65357ffa2d86666d/githubgen/codeowners.go#L48).
This follows the definition of unmaintained so I believe we should
follow the definition here rather than modify the build tool.

_Credit to @pjanotti for pointing out this discrepancy_
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants