Having spent a while creating new repos (klog, yaml etc) and helping
with cloud provider extraction and fair share of proposing updates to
dependencies, i'd like to volunteer to help with taking care of
dependencies and in the upcoming activities at the "code organization"
subproject of sig-arch. Oh, forgot to mention working on the sig-release
subproject on vetting licenses. Please let me know if i have enough
karma to be on dep-approvers.
Change-Id: I0aca458b768800cb1148577c3cc238e6138d50e0
The k/k top level OWNERS_ALIASES entry for milestone-maintainers
is unused. Currently everything around milestone maintanence
continues to happen via the kubernetes-milestone-maintainers GitHub
group (see: https://github.com/kubernetes/sig-release/issues/241 for
similar cleaning up effort there). The hope is in the future this will
move to in repo yaml and Peribolos, but in the meantime this duplicated
and unused list only adds to confusion.
Signed-off-by: Tim Pepper <tpepper@vmware.com>
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.
Add ravi to sig scheduling approvers
**What this PR does / why we need it**:
According to the requirement of Approver at community-membership.md, I meet the following requirements so I'd like to add myself as an approver of scheduler.
I have :
- Authored more than ~40 commits to k/k repository and 22 commits in kube-incubator/descheduler.
- Been co-maintainer on descheduler.
- Been a reviewer for more than 3 months.
- Reviewed/helped in reviewing more than 70 PRs.
- Been helping new contributors in getting upto speed and guide them on performance aspects of the kube-scheduler.
As an approver,
- I agree to only approve familiar PRs
- I agree to be responsive to review/approve requests as per community expectations
- I agree to continue my reviewer work as per community expectations
- I agree to continue my contribution, e.g. PRs, mentor contributors
```release-note
NONE
```
/cc @bsalamat @k82cn @aveshagarwal
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.
Remove ncdc from sig-node-reviewers
**What this PR does / why we need it**: Remove myself from the sig-node-reviewers alias - I'm not active in sig-node.
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #
**Special notes for your reviewer**:
**Release note**:
```release-note
NONE
```
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>.
Add myself to milestone-maintainers
**What this PR does / why we need it**:
Add myself to milestone-maintainers and sort the list alphabetically. I'm already in kubernetes/kubernetes-milestone-maintainers team.
**Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*:
Fixes #
**Special notes for your reviewer**:
**Release note**:
```release-note
NONE
```
Michael Michael