Page MenuHomePhabricator

Improve script sharing/discoverability in Drive/GSuite
Open, Needs TriagePublic

Description

With more scripts running in our Drive/GSuite environment it's also more important that these can be discovered/re-used. It also prevents scripts from being accidentally deleted when documents get converted/deleted.

Drive allows scripts to be either stand-alone files or bound to another file. Bound scripts can do things non-bound cannot whereas non-bound ones can be shared trough team drives.

Scripts can also be published for consumption within the organisation.

The goal of the task is to come up with either a mechanism for more easily discovering scripts, alternatively a best practice around this for ensuring scripts don't get lost.

Event Timeline

Lokal_Profil added a comment.EditedJul 3 2018, 8:41 AM

Of course scripts can also be published on e.g. gist but that serves more of a back-up purpose than anything else.

The background to this was me discovering that we lost the script used in the Måluppfyllnad document and that I realised I couldn't find the script used to trigger e-mail notifications to our board.

Lokal_Profil renamed this task from Improve script sharing/discoverability in Drive to Improve script sharing/discoverability in Drive/GSuite.Jul 3 2018, 8:41 AM
Lokal_Profil added a comment.EditedJul 4 2018, 8:14 AM

Looks as though scripts shared with a group do not show up in the "all projects" tab (or any other tab) at script.google.com for group members. It however shows up if shared with individuals directly.

For non-bound script files these can be placed in a team-drive and discovered that way (does not affect how it shows up in script.google.com)

This task needs some kind of goal/desired result.

This task needs some kind of goal/desired result.

Added

I'm currently leaning towards the recommendation that developed scripts should be backed-up in github.com/Wikimedia-Sverige/scripts:google_drive_scripts/. With a clear description in the README it should be possible to find them afterwards.

Would also make sense to add a version string to the top so that it's easier to check if the github version is up-to-date with what is running on Drive.

@Sebastian_Berlin-WMSE Does the above recommendation seem sensible to you?

Sounds fine, assuming that the colon in the path is a typo :)

Seems like we landed in a decision for this one. So the question becomes.

  1. Are there any additional scripts which should be put in the repo?
  2. Is ther a sensible place on-wiki where this decision can be documented?
  1. I looked through https://script.google.com/home/all, which I think are all the scripts that I have created or done anything with, and found nothing more to add.