I recently learned that Project Jupyter has a Google Workspaces account which can provide Google Drive, Calendars, and Groups to sub-projects. I think it would help if we documented this somewhere as a service available to Jupyter sub-projects. This would make it more likely for them to use it.
I believe that these are the policies to document somewhere, and that are already in practice.
- Project Jupyter has a Google Workspace account for use across the entire project.
- ________ (unknown) roles in the organization get "Administrator access" over this account, and are the ones to ask for changes.
- E-mail / accounts
- All Executive Council members get an
@jupyter.org e-mail address.
- We discourage creating accounts for other individuals unless there's a clear need for them to have an account.
- There's a Shared Drive for all subproject, working group, etc. Each of them may have a dedicated folder in this drive if they wish.
- The Steering Council / Leadership of these groups have administrator access to their folder, to give access to the people they wish.
- The Executive Council has visibility over all of these folders.
- Any subproject may create Google Groups to use for communication within their project. A common convention is to have one for a leadership team, and one for the broader team.
- The convention for naming is
<subproject>-<team>@jupyter.org
- Any subproject may create a Google Calendar for their sub-project to use for events.
- They may give admin rights to anybody they wish.
I recently learned that Project Jupyter has a Google Workspaces account which can provide Google Drive, Calendars, and Groups to sub-projects. I think it would help if we documented this somewhere as a service available to Jupyter sub-projects. This would make it more likely for them to use it.
I believe that these are the policies to document somewhere, and that are already in practice.
@jupyter.orge-mail address.<subproject>-<team>@jupyter.org