-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[chore] Delete language about vendor-specific components and obligated sponsorship #35961
Conversation
There was a problem hiding this 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.
Co-authored-by: Evan Bradley <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I support
There was a problem hiding this 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.
…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]>
I propose that we move to a purely voluntary sponsorship requirement going forward.