-
Notifications
You must be signed in to change notification settings - Fork 210
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
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
…eam drive permission mgmt
I created the Google group: 'drive-content-managers@kubeflow.org` I gave this google group content manager permission on the folders |
#217 will check in an initial file. Next steps
|
* this is to follow the process defined in kubeflow/community#308 for team drive permission mgmt * update file name
* 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
…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
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 is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
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
The process for moving a doc in the drive should then be something like
The text was updated successfully, but these errors were encountered: