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

add info on archiving community repos #3203

Merged
merged 1 commit into from Feb 7, 2019

Conversation

@kikisdeliveryservice
Copy link
Contributor

kikisdeliveryservice commented Feb 5, 2019

Add info on moving sig repo into archives when a SIG is retired.
Closes: #3189

cc: @castrojo

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Feb 5, 2019

Hi @kikisdeliveryservice. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@k8s-ci-robot k8s-ci-robot added the size/XS label Feb 5, 2019

@k8s-ci-robot k8s-ci-robot requested review from calebamiles and grodrigues3 Feb 5, 2019

@kikisdeliveryservice

This comment has been minimized.

Copy link
Contributor Author

kikisdeliveryservice commented Feb 5, 2019

/sig contributor-experience

@@ -103,6 +103,7 @@ The process for closing a SIG/WG is as follows:
- Move all appropriate github repositories to an appropriate archive or a repo outside of the Kubernetes org
- Each subproject a SIG owns must transfer ownership to a new SIG, outside the project, or be retired
- File an issue with kubernetes/org if multiple repos that need to be retired
- Existing SIG repos in kubernetes/community will be moved into kubernetes/community/archive

This comment has been minimized.

@nikhita

nikhita Feb 5, 2019

Member

Perhaps Move the existing SIG directory to the [archive](/archive) in kubernetes/community?

This comment has been minimized.

@castrojo

castrojo Feb 5, 2019

Contributor

Yes it'd be better if we were explicit here.

This comment has been minimized.

@kikisdeliveryservice

kikisdeliveryservice Feb 5, 2019

Author Contributor

Thanks will do!

This comment has been minimized.

@kikisdeliveryservice

kikisdeliveryservice Feb 5, 2019

Author Contributor

Done.

@nikhita

This comment has been minimized.

Copy link
Member

nikhita commented Feb 5, 2019

@kikisdeliveryservice kikisdeliveryservice force-pushed the kikisdeliveryservice:issue-3189 branch from 7ee56f7 to 8ce0421 Feb 5, 2019

@@ -103,6 +103,7 @@ The process for closing a SIG/WG is as follows:
- Move all appropriate github repositories to an appropriate archive or a repo outside of the Kubernetes org
- Each subproject a SIG owns must transfer ownership to a new SIG, outside the project, or be retired
- File an issue with kubernetes/org if multiple repos that need to be retired
- Move the existing SIG directory into the [archive](/archive) in kubernetes/community

This comment has been minimized.

@cblecker

cblecker Feb 6, 2019

Member

This shouldn't be a subpoint of the github repo one. It falls under Update sigs.yaml to reflect the removal of the SIG/WG

This comment has been minimized.

@kikisdeliveryservice

kikisdeliveryservice Feb 6, 2019

Author Contributor

Done.

@kikisdeliveryservice kikisdeliveryservice force-pushed the kikisdeliveryservice:issue-3189 branch from 8ce0421 to 698a1cf Feb 6, 2019

@castrojo

This comment has been minimized.

Copy link
Contributor

castrojo commented Feb 7, 2019

/ok-to-test

@castrojo

This comment has been minimized.

Copy link
Contributor

castrojo commented Feb 7, 2019

/lgtm
/approve

Thanks for your help on this!

@k8s-ci-robot k8s-ci-robot added the lgtm label Feb 7, 2019

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

k8s-ci-robot commented Feb 7, 2019

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: castrojo, kikisdeliveryservice

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 03a4359 into kubernetes:master Feb 7, 2019

3 checks passed

cla/linuxfoundation kikisdeliveryservice authorized
Details
pull-community-verify Job succeeded.
Details
tide In merge pool.
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment