-
Notifications
You must be signed in to change notification settings - Fork 283
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
Component owners- mention component owners in PRs #1715
Comments
I think the gap here is that folks should first become OpenTelemetry Member? Probably good to enforce it. |
I am not sure if it sufficient, last status only @atshaw43 and @zivaninstana are not part of this group. Ref: #1201 |
@Kielek do you have a concrete example that folks are already OpenTelemetry Members but the issue cannot be assigned to them? I might be able to help if you can provide a repro. |
@reyang, I am pretty sure that I saw such PRs, but I cannot find anything like this, probably one of these accounts were involved in the requests. @atshaw - received invitation (twice) open-telemetry/community#1629 Both never accepted. |
I will accept, I just need to see where the request is sent |
Sorry, no request, invitation |
Please send it again, I will accept. I am really keen on continuing to contribute. |
@zivaninstana, please check all you email account associated with GitHub account. Invitation will be expired after some time, so please do not postpone this activity. |
Thank you folks. I just accepted an invitation. I really look forward to working with you. |
Created #1822 to (temporarily) remove @atshaw from component owners until he can fully on-board with Open Telemetry Community |
Originally posted by @Kielek in #1713 (comment)
The text was updated successfully, but these errors were encountered: