CoCC shared drive

[tpepper]

Problem Statement

The CoCC has shared tracking documents which are non-public. Like many earlier artifacts in the community, these are currently in a semi-arbitrary directory on Google Drive owned by a past member of the committee and current document ownership ACLs are a scattered representation of who was accessing each doc at its creation time.

Proposed Solution

We need to have consistent group access control on these across membership changes of the committee. We can do so with a Shared Drive. The drive and all documents in it would be owned by conduct@kubernetes.io. Unlike other shared artifact stores, we desire not having sc owners, but require sc assistance in initial creation.

Cost

Perhaps depending on the projects GSuite status there is cost associated with this request. The volume of data is tiny. These are almost entirely flat text documents, although there's a use case additionally for storing screen shots of point in time Slack/GitHub/other state.

Open Questions

• [ ] How to ensure project has recovery path to ownership of conduct@kubernetes.io, but not risk general read ability on CoCC archive due to unintended config change?
• [ ] Should we change the peribolos config relative to CoCC membership to be in a subdirectory owned by conduct and in a blocked path to add a few more hurdles to accidentally exposing an archive tied to the group membership?

Next Steps

• [ ] Next
• [ ] Steps

Other Considerations, Notes, or References

• [ ] Fixes #
• [ ] xref #

[tpepper]

Bump? @mrbobbytables you mentioned incoming issues would be triaged in regular process. I know this came in with KubeCon, US Thanksgiving, end of year holidays, etc. Would like to get this moving.

[mrbobbytables]

Sorry, this dropped off the radar for me.

/assign

[nikhita]

Funding request - https://github.com/kubernetes/funding/issues/16

[mrbobbytables]

The drive has been provisioned and access has been verified 👍 /close

[k8s-ci-robot]

@mrbobbytables: Closing this issue.

In response to [this](https://github.com/kubernetes/steering/issues/192#issuecomment-771245771): >The drive has been provisioned and access has been verified 👍 >/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.