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

[chore] Delete language about vendor-specific components and obligated sponsorship #35961

Merged
merged 3 commits into from
Oct 24, 2024

Conversation

djaglowski
Copy link
Member

I propose that we move to a purely voluntary sponsorship requirement going forward.

@djaglowski djaglowski changed the title [chore] Delete language about vendor-specific components and oblicated sponsorship [chore] Delete language about vendor-specific components and obligated sponsorship Oct 23, 2024
@djaglowski djaglowski marked this pull request as ready for review October 23, 2024 17:02
@djaglowski djaglowski requested a review from a team as a code owner October 23, 2024 17:02
Copy link
Contributor

@evan-bradley evan-bradley left a comment

Choose a reason for hiding this comment

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

I think this makes sense at this stage of the project.

I included a suggestion for some phrasing that having a component in contrib isn't essential to having a component the issue opener or their users can leverage for their use cases. I think the fact that so many components are contained in contrib and components living in other repositories aren't widely publicized may lead to an impression that being in contrib is a requirement for having a usable component.

.github/ISSUE_TEMPLATE/new_component.yaml Outdated Show resolved Hide resolved
Copy link
Member

@songy23 songy23 left a comment

Choose a reason for hiding this comment

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

I support

@songy23 songy23 added the documentation Improvements or additions to documentation label Oct 23, 2024
Copy link
Member

@TylerHelmuth TylerHelmuth left a comment

Choose a reason for hiding this comment

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

As OpenTelemetry grows we're seeing more and more component proposals and are experiencing more new components that then get abandoned by their sponsors, leaving the community to pick up the slack. As we are stabilizing more and more collector APIs it becomes more feasible for component authors to maintain components in their own repositories. I agree that we have out-grown this rule.

@djaglowski djaglowski merged commit 7c7b7c8 into open-telemetry:main Oct 24, 2024
168 checks passed
@djaglowski djaglowski deleted the delete-vendor-specific branch October 24, 2024 17:24
@github-actions github-actions bot added this to the next release milestone Oct 24, 2024
sbylica-splunk pushed a commit to sbylica-splunk/opentelemetry-collector-contrib that referenced this pull request Dec 17, 2024
…d sponsorship (open-telemetry#35961)

I propose that we move to a purely voluntary sponsorship requirement
going forward.

---------

Co-authored-by: Evan Bradley <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants