Skip to content
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

Define a Google Group and Process To Administer The Shared Google Drive #308

Closed
jlewi opened this issue Dec 11, 2019 · 5 comments
Closed

Comments

@jlewi
Copy link
Contributor

jlewi commented Dec 11, 2019

We should define a scalable process to move Google Docs Into The Shared Google Drive.

Furthermore, we should be more transparent about who the admins are.

Here's a proposed process

  1. Define a Google Group https://github.com/kubeflow/internal-acls for folks to administer the Google Drive
  2. Change the gdrive permissions to give those folks content management permissions

The process for moving a doc in the drive should then be something like

  1. Assign ownership of the Google doc to the content managers list
  2. Open an issue to transfer the doc
  3. Assign the issue to someone in the content manager list
  4. Content manager should then be able to move the doc into the drive
@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the label kind/feature to this issue, with a confidence of 0.94. Please mark this comment with 👍 or 👎 to give our bot feedback!

Links: app homepage, dashboard and code for this bot.

@jlewi
Copy link
Contributor Author

jlewi commented Mar 14, 2020

I created the Google group: 'drive-content-managers@kubeflow.org`

I gave this google group content manager permission on the folders
"kubeflow(public)"
"Community Meetings"

@jlewi
Copy link
Contributor Author

jlewi commented Mar 14, 2020

#217 will check in an initial file.

Next steps

  • Move most of the current content managers into that group and use that group to administer access
  • Remove existing users; non group content managers
  • Create a doc defining the process for transferring docs to the shared drives.

k8s-ci-robot pushed a commit to kubeflow/internal-acls that referenced this issue Mar 14, 2020
* this is to follow the process defined in kubeflow/community#308 for team drive permission mgmt

* update file name
jlewi pushed a commit to jlewi/internal-acls that referenced this issue Mar 14, 2020
* All of the users being added in this PR already had content manager permission
  this PR is just using a group to grant them that permission.

Related to kubeflow/community#308
k8s-ci-robot pushed a commit to kubeflow/internal-acls that referenced this issue Mar 16, 2020
…up. (#219)

* All of the users being added in this PR already had content manager permission
  this PR is just using a group to grant them that permission.

Related to kubeflow/community#308
@stale
Copy link

stale bot commented Jun 12, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@issue-label-bot
Copy link

Issue-Label Bot is automatically applying the labels:

Label Probability
area/docs 0.60

Please mark this comment with 👍 or 👎 to give our bot feedback!
Links: app homepage, dashboard and code for this bot.

@stale stale bot closed this as completed Jun 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant