-
Notifications
You must be signed in to change notification settings - Fork 242
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
Make jmacd an OTEPs maintainer (need more OTEPs maintainers) #406
Comments
Sounds great to me. |
The rule says that only TC members can be maintainers of oteps, so this request should be to make you a TC member which can be discussed in a TC meeting |
Also 119 is not ready because it does not have enough approvers. |
The only PR that is ready to be merged is open-telemetry/oteps#108 which has a comment at the end that more work is coming, so I think the problem is not the maintainers, but reviews. |
Agree, this is a TC decision (and also involves necessarily membership in the TC) |
See #329
I would like to nominate myself as a new OTEPs maintainer since we have not finished the per-signal codeownership changes. I am not sure if the community rules allow this, so I'm filing an issue.
The OTEPs that should merge are
open-telemetry/oteps#108
open-telemetry/oteps#113
open-telemetry/oteps#117
open-telemetry/oteps#118
open-telemetry/oteps#119
The text was updated successfully, but these errors were encountered: