Org: Milestone maintainers on kubernetes-sigs

Created on 31 Jan 2019 · 15Comments · Source: kubernetes/org

Organization or repository

e.g. kubernetes-sigs/*

Users effected

All approvers

Describe the issue

Currently kubernetes_sigs is a federated set of repositories that spans multiple sigs. Management of those subprojects is meant to be decentralized and for them to live on their own, possibly with their own lifecycle.

As of today, there is a need to give approvers the ability to set their own milestones but they can not do that given existing permissions model on milestone maintainers.

This is not tenable.

@kubernetes/test-infra-maintainers @kubernetes/sig-contributor-experience-bugs

kinbug sicontributor-experience

Source

timothysc

👍3

All 15 comments

/assign @cblecker @spiffxp

timothysc on 31 Jan 2019

+1 The current workflow requires to either be part of a github group or have complete write access to the repository, as far as I understand. Having approvers be able to set milestone would improve the current workflow *💯and reduce time spent in meetings organizing the backlog.

vincepri on 31 Jan 2019

what do people think about non-approvers who can set milestones? I think I can help triage issues in cluster-api but I am not an approver there.

chuckha on 31 Jan 2019

The plugin scopes /milestone access to a team. Do you have specific repos with specific people in mind. Or does use of the existing kubernetes milestone maintainers team suit your needs

spiffxp on 31 Jan 2019

It’s a pretty easy org wide change but heads up needs to be given. Faster thing to start would be enabling for specific repos

spiffxp on 31 Jan 2019

IMO kubernetes_sigs/* needs this. It's not just one repo, but if I'm calling things out, everything sig-cluster-lifecycle related is my immediate concern.

timothysc on 31 Jan 2019

@timothysc Who should be given permissions to /milestone across the k-sigs org? In k/ that's the release team by default, but as you mention for k-sigs, these subprojects are supposed to be decentralized.

cblecker on 31 Jan 2019

👍1

Bumping this.

It's not just one repo, but if I'm calling things out, everything sig-cluster-lifecycle related is my immediate concern.

Since different subprojects (even under one SIG) might have different people working on it, I guess it makes sense to scope out milestone rights with a repo <-> team mapping. @timothysc wdyt? does that sound ok to you?

nikhita on 4 Mar 2019

:wave: bump

nikhita on 3 Apr 2019

/assign @timothysc
ref https://twitter.com/timothysc/status/1116803681083633664 :upside_down_face:

@timothysc do you think we can close this issue in favour of repo <-> team mapping?

nikhita on 15 Apr 2019

😄1

@nikhita yes!

timothysc on 15 Apr 2019

@timothysc I got here via a Google search on how to make /milestone work in kubernetes-sigs repos, but I don't understand the conclusion to this issue. Can you add a pointer to how we're supposed to make this work? Thanks!