new repo: kubernetes-csi/csi-driver-image-populator

[kfox1111]

New Repo, Staging Repo, or migrate existing

new repository

Requested name for new repository

csi-driver-image-populator

Which Organization should it reside

kubernetes-csi

If not a staging repo, who should have admin access

@saad-ali @msau42

If not a staging repo, who should have write access

@saad-ali @msau42

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

@saad-ali @msau42 @kfox1111

If a new repo, who should be listed in SECURITY_CONTACTS

@saad-ali @msau42 @kfox1111

What should the repo description be

CSI driver that uses a container image as a volume

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

part of the CSI working group in SIG-storage

Approvals

Discussed and approved on Thursday, Feb 14, 2019, in the sig-storage meeting
Also discussed on the sig-storage group:
https://groups.google.com/forum/#!topic/kubernetes-sig-storage/6_SpwBiaNtI

[spiffxp]

/assign @nikhita
Please give this one a shot

[msau42]

csi-driver-image is a confusing name and it might be interpreted to mean something related to storing container images for the drivers we maintain.

I can't really think of something much better. How about something like:
csi-driver-image-volume
csi-driver-container-image-volume

[kfox1111]

all the storage drivers are under csi-driver-X. so I think csi-driver-image makes sense. But I'm open to either of the other two as well. all of them make sense in one way or the other.

(There are 2 hard problems in computer science. naming things, cache invalidation, and off by one errors 😄 )

[kfox1111]

Are we stuck on naming? Who can pick?

[msau42]

@saad-ali and I brainstormed and came up with:
csi-driver-image-populator

wdyt?

[kfox1111]

wfm

[kfox1111]

Do I need to amend the request?

[msau42]

Sure go ahead and edit the first comment with the updated name

[kfox1111]

✔️

[msau42]

/lgtm

[nikhita]

Created https://github.com/kubernetes-csi/csi-driver-image-populator 🎉

I have also created two PRs:

• Add teams for kubernetes-csi/csi-driver-image-populator #517 - to add GitHub teams for repo admin/write access.
• Add csi-driver-image-populator to kubernetes-csi subproject community#3293 - to add this repo to sigs.yaml.

Once #517 has merged and the postsubmit has run, the new GitHub teams will be created. I'll manually update the collaborators to the repo to provide access to the teams once that's done. :)

---

@kfox1111 I have added you as an approver for the repo, but to be able to use these approval powers, you need to be a member of @kubernetes-csi. Can you please file a membership request for this?

[nikhita]

The new GitHub teams have been created and I have updated repo permissions.

csi-driver-image-populator-admins has admin access and csi-driver-image-populator-maintainers has write access.

I'll close this issue once kubernetes/community#3293 is merged.

[kfox1111]

Ok. I'll file a membership request asap.

Thanks everyone for all the help. :)

[nikhita]

kubernetes/community#3293 has merged. Closing this issue.

/close

[k8s-ci-robot]

@nikhita: Closing this issue.

In response to this:

kubernetes/community#3293 has merged. Closing this issue.

/close

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.