Costs
*: We become reliant on Google (and the UW to keep paying Google)
-*: Editing without access to Google requires Chrome, the foresight to enable offline access in advance, and to have had access to the document while Chrome was connected to Google Drive so it could keep a local copy.
+*: You require internet access to Google to view or edit a design document; offline mode is not supported.
Probably not costs
*: We lose advanced formatting; Google Drive is a simple word processor. But do we really need it?
@@ -19,33 +19,33 @@
{section: Proposal: shared folder}
We create a shared folder into which new design documents are placed. Proposed permissions are:
*: HTCondor dev team: Can Edit - This is full access; people can create documents, delete them, and modify the permissions (although the latter can be removed?). Should only be given to people we trust with similar access to the Wiki and AFS.
-*: Public: Can View
*: Close collaborators: Can Edit
+*: Public: Can View
-The SWAMP team are using this solution.
+It is not possible to set "Can Comment" on a folder, you need to set it on a file-by-file basis. So if comments are desired from people without edit access, it will be need to be added for each file.
-On the up side, access is more closely controlled, and adding a new team member is easy. There is also a single place to find all new design documents (but does anyone care?).
+The SWAMP team are using this solution.
-On the down side, permission to create or edit documents is very chunky.
+On the up side, access is centrally controlled. Adding a new team member is easy. There is also a single place to find all new design documents (but does anyone care?).
-It is not possible to set "Can Comment" on a folder, you need to set it on a file-by-file basis. So if comments are desired from people without edit access, it will be need to be added for each file.
+On the down side, permission to create or edit documents is very chunky. Settings to the folder override settings on individual documents, so it's possible to add someone to the folder permissions and accidentally grant access to a file contained inside that should have more restricted distribution. But, is this a problem in practice? It's similar to the current permissions system on the wiki.
{section: Proposal: individual file management}
Individuals just create their own design documents, perhaps with a title prefix of "Design Document:" so they are easy to find. They are marked as "Public: Can Comment" (risk of abuse is low). If other people need edit access, it's granted on an as-needed basis. (We can also only grant comment access on an as-needed basis in a pinch.) The very rare design document with security ramifications won't be public; people are added as needed.
On the up side, eliminates challenges of the folder being removed, and it's very hard to accidentally or intentionally damage a design document unless you're the original author or were very explicitly granted edit access.
-On the down side, there is no single place to find all new design documents (but does anyone care?).
+On the down side, there is no single place to find all new design documents. Does anyone care? They'll be linked from the individual tickets, similar to how it is today.
{section: Challenges and Questions}
{subsection: Offline support}
-_Does not appear to be allowed for UW Google Apps!_ Alan has a query out to DoIT to confirm.
+UW Google Apps does not have offline support enabled. DoIT says that this is apparently something that could be enabled. Alan has a request to have it enabled, but is not optimistic.
-Untested. Unknown how it handles race conditions. Chrome only.
+Offline support is Chrome only.
-_We really should test this._
+Offline support is untested. In particular, it's not clear how it handles conflicts. Hopefully conflicts are rare, but they will happen occasionally.
https://support.google.com/drive/answer/1628467
@@ -83,8 +83,6 @@
Probably unlikely; how often does someone close their Google account? But there is a risk we'd lose the documents. Proposed: documents must be owned by someone using a UW account. Likely flow: non-UW member creates the file and works on it. Eventually someone from the UW copies the file and that becomes the official copy.
-
-
{section: How to log in}
1: If you want to simultaneously be logged into a personal account, _do so first_. If you use the UW login first, it is difficult to later log into your personal account.
2: https://apps.google.wisc.edu/ - Log in as usual.
