S1 - Public
S2 - Community Liasons, T94108
S3 - Testing space (All users)
S4 - Procurement - Vendor Quote, T93760
S5 - Fundraising-Analysis, T119258
S6 - Ops vendor announcements, T118176
S7 - Annual-Report-Private, T136889
S8 - WMUK Technical Committee, T122436

This problem would be solved if all the space description pages were public.

I've added a table in the task description with a best guessitation about the ACLs that allow them, since most don't have any description on the project pages.

Interesting that S2 and S5-S8 aren't even visible to me but S4 is :)

In T138677#2419835, @demon wrote:

Interesting that S2 and S5-S8 aren't even visible to me but S4 is :)

Ah, S4 allows Administrators with Read permissions. Curious :)

(you must have some fancy ops permissions somewhere, 'cuz I can't see S4 ;) )

In T138677#2419646, @greg wrote:

Setting to Low as we have the table right now so we're probably 95% done :)

I have no idea if its right, its just guesses based on name.

Is S8 actually WMUA Technical Committee or WMUK Technical Committee? If the latter, then it should be renamed to the former.

"A" not "K", I had to guess the titles (since space description pages are still limited by their contents' visibility policy) and screwed that one up. Fixed.

1. Where should this list end up on-wiki? Wikis are for documentation, tasks for work. :)
2. Once decided, make https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Requesting_a_Space mention that additional step.
3. Close this task.

Upstream issue would be also list of all spaces publicly. I personally don't see any reason why they can't - plain list of spaces names doesn't harm anything.

I'm not sure how to update for the fact that S6 is now archived (as it was easier to use a mailing list to track maint-annoucements for ops, rather than importing emails into phab.) I've just added an 'active/inactive' column.

@RobH Does the space contain anything sensitive? Has it ever? (= Can it be opened and reused for something different?)

In T138677#2534123, @Danny_B wrote:

(= Can it be opened and reused for something different?)

Let's not reuse Spaces for different areas/topics. Any content referring to S6 before a "reuse" would suddenly get a highly confusing and misleading context. Thanks!

In T138677#2534127, @Aklapper wrote:

In T138677#2534123, @Danny_B wrote:

(= Can it be opened and reused for something different?)

Let's not reuse Spaces for different areas/topics. Any content referring to S6 before a "reuse" would suddenly get a highly confusing and misleading context. Thanks!

Agreed that we should avoid reusing spaces. Archiving unused ones prevents confusion. I see no reason to re-use an archived space, unless it is re-opened for its initially presumed use. Anything else would lead to confusion as @Aklapper points out; and would require a full audit of a space for re-use. I think its easier to just make a new space, they cost nothing in terms of creation, only 'active' overhead.

I was not talking about reusing any space in general, but particularly only the S6 which seems to be never used and mentioned only in the single task.

Otherwise obviously no-reuse policy applies.