-
Notifications
You must be signed in to change notification settings - Fork 130
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
Request for a few additional component owners #174
Comments
Yes, I'd be interested! |
@Mrod1598 awesome, can you request membership into the OpenTelemetry github org? here's the instructions: https://github.com/open-telemetry/community/blob/main/community-membership.md#member. you can put myself and @anuraag as the two sponsors. being a member of the OTel org will allow us to assign you as a reviewer for the jmx-metrics component. thx! |
I'd be happy to join the |
@dehaansa Great, please add me as a sponsor! |
Closing, all components except Thanks everyone! |
We would like to have (at least) 2 owners for each component in this repository. The component owners will be automatically assigned to review PRs that touch files in those components.
aws-xray
,jfr-streaming
,maven-extension
, andruntime-attach
have (at least) 2 owners already.jmx-metrics
needs one additional owner - @Mrod1598 would you be interested? @rmfitzpatrick any other recommendations for people we could ask?contrib-samplers
also needs one additional owner - any volunteers?disruptor-processor
currently has no owners - @bogdandrutu are you still interested in this component?The text was updated successfully, but these errors were encountered: