Probably not costs
*: We lose advanced formatting; Google Drive is a simple word processor. But do we really need it?
-
-We propose a shared folder into which new design documents are placed. Proposed permissions are:
+{subsection: 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 - Maybe grant Can Comment, as the harm in abuse is pretty minimal.
*: External collaborators - Can Comment (unnecessary if we granted the public this level)
+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?).
+
+On the down side, permission to create or edit documents is very chunky.
+
+{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?).
+
{section: Challenges and Questions}
+{subsection: How do permissions interact?}
+
+I have a shared folder; all of HTCondor can edit it. I create the file FOO in that folder and modify it to grant edit access to someone@example.com. I now change the shared folder to grant edit access to new-team-member@wisc.edu. Does new-team-member end up able to edit FOO? Check.
+
{subsection: What if someone leaves the UW?}
The big problem is maintaining access to files (and maybe even the shared folder) if the owner leaves the UW. It's not clear what will happen to such files or folders. They might stay available. They might disappear.
