-
Notifications
You must be signed in to change notification settings - Fork 40.1k
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
Move ncdc to emeritus #126760
Move ncdc to emeritus #126760
Conversation
I am moving myself to emeritus as I am now firmly on the end-user side of things. Signed-off-by: Andy Goldstein <andy.goldstein@gmail.com>
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
/assign @jpbetz @janetkuo @BenTheElder Assigning one person from each SIG |
/lgtm |
LGTM label has been added. Git tree hash: 961d245dd432f894829f27f4f2c23db34fe92aa4
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Docs: https://go.k8s.io/owners
bikeshedding here, but we usually use emeritus_approvers
field (like approvers
) which could be read by tooling 😅
Thank you for PR-ing yourself out when you don't have the time.
I'll make the change. I was following what is in |
👍 I don't think we ever settled on something like this for OWNERS_ALIASES actually ... but we have pretty consistently used cc @kubernetes/sig-contributor-experience |
@BenTheElder ok I made the change everywhere, including OWNERS_ALIASES. Might not be what we want. PTAL & let me know. Thanks! |
Now I see why they were commented out in OWNERS_ALIASES |
Signed-off-by: Andy Goldstein <andy.goldstein@gmail.com>
/lgtm |
LGTM label has been added. Git tree hash: 976f9c1187f513691690cc611a6fff527b2713e2
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: janetkuo, liggitt, ncdc The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
I am moving myself to emeritus as I am now firmly on the end-user side of things.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: