Skip to content
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

Closed
jmacd opened this issue Jul 2, 2020 · 5 comments
Closed

Make jmacd an OTEPs maintainer (need more OTEPs maintainers) #406

jmacd opened this issue Jul 2, 2020 · 5 comments

Comments

@jmacd
Copy link
Contributor

jmacd commented Jul 2, 2020

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

@carlosalberto
Copy link
Contributor

Sounds great to me.

@bogdandrutu
Copy link
Member

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

@bogdandrutu
Copy link
Member

Also 119 is not ready because it does not have enough approvers.

@bogdandrutu
Copy link
Member

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.

Screen Shot 2020-07-14 at 12 56 47 PM

@lizthegrey
Copy link
Member

Agree, this is a TC decision (and also involves necessarily membership in the TC)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants