Rename kubernetes-sigs/federation-v2 to kubernetes-sigs/kubefed

pmorie commented 5 years ago

New Repo, Staging Repo, or migrate existing

This request is to rename the kubernetes-sigs/federation-v2 repository to kubernetes-sigs/kubefed. This decision was made by the Federation WG, a subproject of SIG multicluster during the May 1 2019 working group meeting. Notice was previously provided to the SIG mailing list with a tentative date of May 15 2019.

Requested name for new repository

kubefed

Which Organization should it reside

kubernetes-sigs

If not a staging repo, who should have admin access

existing list

If not a staging repo, who should have write access

existing list

If not a staging repo, who should be listed as approvers in OWNERS

existing list

If not a staging repo, who should be listed in SECURITY_CONTACTS

existing list

What should the repo description be

by default we will set it to "created due to (link to this issue)"; should be inapplicable because this is a rename

What SIG and subproject does this fall under in sigs.yaml

This is the rename of an existing repository, which is a subproject of SIG multicluster.

Approvals

This decision was made by the Federation WG, a subproject of SIG multicluster during the May 1 2019 working group meeting
Notice was previously provided to the SIG mailing list with a tentative date of May 15 2019.

Authoritative requirements are here: https://git.k8s.io/community/github-management/kubernetes-repositories.md

tl;dr (but really you should read the linked doc, this may be stale)

If this is a core repository, then sig-architecture must approve
If this is a SIG repository, then this must follow the procedure spelled out in that SIG's charter

Additional context for request

Any additional information or context to describe the request.

cblecker commented 5 years ago

/assign

Shouldn't be a problem renaming this whenever you're ready. I have #819 to update the groups, and I've verified there aren't any other prow configs that need to be moved.

pmorie commented 5 years ago

@cblecker Thanks. I think we are good to pull the trigger now. We are near the reasonable end of the working day now, and the working group would get an extra full working day with this finished if we were to do it now.

cblecker commented 5 years ago

Rename complete. Just need sigs.yaml updated, and then this can be closed.

nikhita commented 5 years ago

sigs.yaml is updated.

/close

k8s-ci-robot commented 5 years ago

@nikhita: Closing this issue.

In response to [this](https://github.com/kubernetes/org/issues/818#issuecomment-493326989): >sigs.yaml is updated. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

kubernetes / org