-
Notifications
You must be signed in to change notification settings - Fork 705
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
Please create repo kubernetes-sigs/etcdadm #308
Comments
I can’t tell clearly from the KEP.. are we forking an existing project? |
@cblecker yes. I believe this is the current canonical source: https://github.com/platform9/etcdadm |
@justinsb can you confirm? rules for importing/donating code is different than a new repo with newly created code. |
@cblecker Platform9 would like to donate the code. We can transfer the repo the kubernetes-sigs org, or duplicate the repo (and outstanding issues). |
Can you please review the rules for donated repositories, and speak to each of the requirements?: https://github.com/kubernetes/community/blob/master/github-management/kubernetes-repositories.md#rules-for-new-repositories also, please add me as an admin to the current repo |
@cblecker Absolutely.
Although it does not appear in the rules, I realize that--where possible--the use of the same dependencies as k/k is important, too; @justinsb was kind enough to submit one patch getting etcdadm closer to this goal. [0]
|
I'm ready to go on this.. The one issue is that @dlipovetsky is not a member of the kubernetes or kubernetes-sigs orgs, so I will not be able to provide repo access after the transfer. Would you like to get this corrected first? |
@cblecker Thank you for the heads up. I'm submitting an issue to request membership to both, and I'll post an update here. |
@cblecker I'm now a member of the @kubernetes and @kubernetes-sigs orgs. One question: Do I need to create an |
@cblecker Anything else we need to take care of? |
/assign |
@dlipovetsky Sorry for the delay in this. I've completed the transfer. You don't need an I've opened #569 to add you to the right teams to get that access.. as soon as that gets merged, you should be good to go. Can you update sigs.yaml with the new repo? (cc: @justinsb ) |
@cblecker No problem. Thanks for your help! I'll try updating sigs.yaml |
@dlipovetsky bumping this, can you create a PR to update sigs.yaml with this new repo? We can close this issue once it gets merged. :) |
@nikhita Thanks for the gentle reminder. PR opened! |
kubernetes/community#3439 merged 🎉 Closing. |
@nikhita: Closing this issue. In response to this:
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. |
New Repo, Staging Repo, or migrate existing
New Repo
Requested name for new repository
etcdadm
Which Organization should it reside
kubernetes-sigs
If not a staging repo, who should have admin access
justinsb, dlipovetsky & sig-cluster-lifecycle chairs (roberthbailey, luxas, timothysc)
If not a staging repo, who should have write access
justinsb, dlipovetsky
If a new repo, who should be listed as approvers in OWNERS
justinsb, dlipovetsky
If a new repo, who should be listed in SECURITY_CONTACTS
justinsb, dlipovetsky
What should the repo description be
tooling & automation for kubernetes etcd clusters
What SIG and subproject does this fall under in sigs.yaml
etcdadm is a new subproject of sig-cluster-lifecycle
Approvals
kubernetes/community#2835
Additional context for request
n/a
/area github-repo
The text was updated successfully, but these errors were encountered: