-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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/azureblob] Update codeowners #23394
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
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 Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
I am working towards OpenTelemetry membership |
I will be happy to be a sponsor if you're looking for a member to sponsor you. Thanks! |
Thanks a lot! |
@mx-psi could you please be a sponsor for my membership? |
@eedorenko Sure :) please send me the link to the issue I have to sponsor and I will gladly do so |
Thanks a lot! |
Component(s)
receiver/azureblob
Describe the issue you're reporting
Please see #20868 for context.
The azureblobreceiver is lucky to count @eedorenko as codeowner, however they are not currently registered as a member of OpenTelemetry.
Please work towards a resolution:
If no action is taken by January 2024, I will open a PR to remove them from the codeowners, and after a delay for their review, eventually will merge the PR.
The text was updated successfully, but these errors were encountered: