Afterwards, need to update https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Type_of_project to list acl* with Policy+Red and to adjust reality to the rules anyway (Need to kill the use of Flag+Green which is partially my fault; should be a default briefcase one and archived when done if it's not an epic anyway).

In T90491#1088363, @Aklapper wrote:

Afterwards, need to update https://www.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Type_of_project to list acl* with Policy+Red and to adjust reality to the rules anyway (Need to kill the use of Flag+Green which is partially my fault; should be a default briefcase one and archived when done if it's not an epic anyway).

agreed on the first point, need to update that in general. I have a task for it somewhere...disagree on the death of the flag :D Willing to chat about it before we drop the hammer? (hangout)

Might also make T77228: Let non-members watch projects a tad easier if I get https://secure.phabricator.com/T6183 correctly?

The way launchpad dealt with this was just by having separate teams.
Example:

• Anyone could just projectX and watch the bugs, join the mailing list, whatever
• Joining projectX-committers was limited to invite only.

This proves useful when you have people trying to understand what's going on when they want to participate in a project (they join that project, like everyone else) but separates out the policy-bits without colliding in the namespace.

In T90491#1133346, @greg wrote:

The way launchpad dealt with this was just by having separate teams.

....which looks like what this task is meant to do. Ignore me.

/me moves along

Maybe I'm late in the discussion here and you guys are set - but prefixing the Project with acl* moves it to the top of the list of projects a user is a member of (particularly in Dashboard panels). This strikes me as a usability issue as it's going to be the project a user interacts with the least and is taking up valuable real estate.

I would suggest that projects such as this that are not super active use naming conventions that move them to the bottom of alphabetized list.

In T90491#1151638, @atgo wrote:

Maybe I'm late in the discussion here and you guys are set - but prefixing the Project with acl* moves it to the top of the list of projects a user is a member of (particularly in Dashboard panels). This strikes me as a usability issue as it's going to be the project a user interacts with the least and is taking up valuable real estate.

I would suggest that projects such as this that are not super active use naming conventions that move them to the bottom of alphabetized list.

Thought about it a bit, idk about doing zacl to artificially lower it in people's project list. This is kind of a fuzzy thing atm anyway, and limited subset are going to end up with acl duties. I never really use the "what projects am I in" interface so it had not occurred to me.

It's certainly not the end of the world, but my team for sure mostly uses the "projects I am in" on the dashboard. We have a lot of projects spread among fundraising.

In T90491#1151638, @atgo wrote:

prefixing the Project with acl* moves it to the top of the list of projects a user is a member of (particularly in Dashboard panels).

Dedicated task for tackling that: T95950: List acl* projects at the bottom of project lists