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.

Sign up for GitHub

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

Jump to bottom

Prune / update kubernetes-milestone-maintainers GitHub team #241

Closed
justaugustus opened this issue Jul 28, 2018 · 13 comments
Closed

Prune / update kubernetes-milestone-maintainers GitHub team #241

justaugustus opened this issue Jul 28, 2018 · 13 comments
Assignees
@spiffxp @justaugustus @tpepper @AishSundar
Labels
sig/release Categorizes an issue or PR as relevant to SIG Release.

Comments

@justaugustus
Copy link
Member

justaugustus commented Jul 28, 2018 •
edited
Loading

Once we document the process for maintaining the milestone-maintainers GitHub team (kubernetes/community#2424 / #239) and gather some data on who's been actively using /milestone commands, we should prune / update the list as necessary.

/sig release
/assign @tpepper

rel:
@k8s-ci-robot k8s-ci-robot added the sig/release Categorizes an issue or PR as relevant to SIG Release. label Jul 28, 2018
@justaugustus justaugustus changed the title Update milestone-maintainers GitHub team Prune / update milestone-maintainers GitHub team Aug 21, 2018
@justaugustus justaugustus changed the title Prune / update milestone-maintainers GitHub team Prune / update kubernetes-milestone-maintainers GitHub team Aug 21, 2018
@justaugustus justaugustus mentioned this issue Aug 21, 2018
Closed
@justaugustus
Copy link
Member Author

@tpepper -- bump. did we close the loop on this?

@tpepper
Copy link
Member

tpepper commented Sep 29, 2018

I owe a PR or two here still.

@justaugustus
Copy link
Member Author

Bump. Also assigning current RT Lead + Shadow.
/assign @AishSundar @spiffxp

@neolit123
Copy link
Member

+1 this should probably happen every 1-2 cycles.

@justaugustus
Copy link
Member Author

@tpepper @AishSundar @spiffxp -- did we have a chance to take care of cleaning up the kubernetes-milestone-maintainers Github team?

@justaugustus justaugustus mentioned this issue Oct 26, 2018
Closed
7 tasks
@AishSundar
Copy link
Contributor

I wasn't doing anything towards this. At a minimum we can ping folks marked so on this spreadsheet if @tpepper hasn't already.

@justaugustus
Copy link
Member Author

justaugustus commented Oct 28, 2018 •
edited
Loading

Thanks! @AishSundar or @tpepper, can you give me edit access to that sheet? I dropped comments on the relevant people, but I'll also clean the list up once I have access to munge the actual list.

@AishSundar
Copy link
Contributor

I dont have edit access either. Lets wait for @tpepper

@justaugustus
Copy link
Member Author

/assign

@spiffxp
Copy link
Member

spiffxp commented Jan 3, 2019

A modest proposal as we start off a new year: new year, new team. Drop everyone. Add the release team. Add current SIG chairs or TLs. Add back anyone who asks, have them provide rationale.

tpepper pushed a commit to tpepper/kubernetes that referenced this issue Jan 3, 2019
remove unused milestone-maintainers OWNERS_ALIASES entry
34f1fe7 
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: kubernetes/sig-release#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>
@tpepper tpepper mentioned this issue Jan 3, 2019
Merged
@justaugustus
Copy link
Member Author

@spiffxp -- Great idea! I'm in favor of purging the list for the new year. :)

@tpepper
Copy link
Member

tpepper commented Jan 7, 2019

Is it possible to update the Prow "/milestone" command help info, if not already sufficiently clear, to have something like: "If you believe you should be able to issue the /milestone command, please contact your SIG chairs and have them propose you as an additional delegate for this responsibility."

@justaugustus justaugustus mentioned this issue Jan 9, 2019
Merged
@justaugustus
Copy link
Member Author

@tpepper -- Yep! PR here: kubernetes/test-infra#10669

@justaugustus justaugustus mentioned this issue Jan 12, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@spiffxp spiffxp

@justaugustus justaugustus

@tpepper tpepper

@AishSundar AishSundar

Labels
sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@spiffxp @neolit123 @justaugustus @tpepper @AishSundar @k8s-ci-robot