-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/zipkin][exporter/zipkin] Add codeowners to zipkin components #20269
Comments
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping |
I'm happy to be a code owner for this, but I would appreciate some extra hands on this. |
Incidentally, I've just dipped my toes in these two components, fixed some docs issues:
Given that there are currently no code owners at all, I'm willing to help @MovieStoreGuy with it |
I can help out as well 👍 |
Let me raise a PR to include the three of us. |
Component(s)
exporter/zipkin, receiver/zipkin
Describe the issue you're reporting
The zipkin components do not have explicit codeowners besides the approvers. It would be best to have several members of the community step up to become explicit codeowners of those components, as we distribute them with the core and contrib distributions.
The text was updated successfully, but these errors were encountered: