-
Notifications
You must be signed in to change notification settings - Fork 723
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
Migrate pmorie/go-open-service-broker-client to kubernetes-sigs/go-open-service-broker-client #893
Comments
Donated repos need to satisfy some requirements. As per these requirements, the following steps need to be done before the migration:
|
/assign |
Huh, I seem to have missed the mail for this one somehow. Luckily, I've got my CLA fixed over in #894, so there's no action for me to do here at this point. 🎉 |
Any update on this? |
/assign @pmorie For the record, got an lgtm for this on slack - https://kubernetes.slack.com/archives/C232SF3TK/p1563895810010100. I can take care of the OWNERS files, etc post migration but the copyright boilerplate will need to be added pre-migration because of legal rules... |
/lgtm |
any update on this? what else needs to be done? |
kubernetes-retired/go-open-service-broker-client#139 fixes the boilerplate for all files |
Repo has been migrated: https://github.com/kubernetes-sigs/go-open-service-broker-client and relevant teams have been granted access. I have created kubernetes/community#4065 to add the repo to sigs.yaml. Once the PR merges, we can close this issue. |
BAM! Thanks! |
New Repo, Staging Repo, or migrate existing
migrate existing
Requested name for new repository
go-open-service-broker-client
Which Organization should it reside
kubernetes-sigs
If not a staging repo, who should have admin access
the kubernetes-sigs team
service-catalog-admins
If not a staging repo, who should have write access
the kubernetes-sigs team
service-catalog-maintainers
If not a staging repo, who should be listed as approvers in OWNERS
the kubernetes-sigs team
service-catalog-maintainers
If not a staging repo, who should be listed in SECURITY_CONTACTS
jberkhahn
What should the repo description be
A golang client for service brokers implementing the Open Service Broker API
What SIG and subproject does this fall under in sigs.yaml
this is part of the main service catalog project for sig-service-catalog.
it is already in use in the main repo, we're just moving it over to be under control
of the sig
Approvals
Please prove you have followed the appropriate approval process for this new
repo by including links to the relevant approvals (meeting minutes, e-mail
thread, etc.)
this was discussed at the April 22 meeting of SIG Service Catalog: link
pmorie's approval was obtained privately by @jboyd01
Additional context for request
@pmorie will need to involved in moving this
The text was updated successfully, but these errors were encountered: