review TPA-RFC-32 (nextcloud#1)

policy/tpa-rfc-32-nextcloud-root-level-folders-migration.md

@@ -45,6 +45,11 @@ table below:
 | ?              | Metrics Team         | Metrics Team         |
 | Sysadmin       | TPA Team             | TPA Team             |
 
+TODO: @gaba? add the name of those current folders
+
+TODO: what happens to those existing folders, do we move content? who
+does that? what's the timeline?
+
 ## Create "TPI" and  "Common" shared folders
 
 We'll create a shared folder named "Common", shared with all Nextcloud user
@@ -57,6 +62,11 @@ groups, and a "TPI" folder shared with all TPI employees and contrators.
  * **TPI** would host documents of interest to TPI personnel, such as holiday
    calendars and the employee handbook
 
+TODO: this touches on the account policy, which is to be discussed in
+https://gitlab.torproject.org/tpo/tpa/nextcloud/-/issues/10 -
+regardless of that policy, maybe we *don't* want to have a "common"
+folder and instead a "tor-internal" folder?
+
 ## Set system-wide default incoming shared folder to "Incoming"
 
 Currently when a Nextcloud user shared documents or folders with another user
@@ -75,14 +85,14 @@ folder. It will not move existing files and folders, however.
 ## Scope
 
 The scope of this proposal is the Nextcloud instance at
-https://nc.torproject.net
+https://nc.torproject.net.
 
 ## Affected users
 
 All users of the Nextcloud instance.
 
-Our Riseup counterpart for Nextcloud administration will be required to
-manually create a handful of folder on the server.
+Our Nextcloud external providers will be required to manually create a
+handful of folders on the server.
 
 # Costs
 
@@ -93,6 +103,9 @@ There are no costs associated with this proposal, apart from the labor costs.
 This proposal should be approved by the current team of Nextcloud
 administrators.
 
+TODO: shouldn't this pass through tor-internal to confirm it will
+satisfy people's concerns about this problem?
+
 # Status
 
 This proposal is currently in the `draft` state.