I like using red for Private. At least for me red is a "seriously pay attention" color in a UI.

Do we really have to set in stone the colors used? Teams should be able to pick the color for their team so they can pick it out of the mess, right? For instance, I already picked purple-ish for Release-Engineering-Team because I want to be able to distinguish it from all the other projects out there (and since tasks can be in multiple projects, this will be useful).

There are 10 colors to choose from, and there will be hundreds of projects. Do the math and see how long will it take until you don't recognize your own labels within the rainbow anymore. How long until the many color codes become meaningless.

I'd rather stick to single color-icon-purpose combinations, because then these labels act as actual labels, providing a quick visual hint of what a task is associated with.

If I could vote for any grouping to get its own color it would be "people" because it is used for policy type stuff and has the most distinctness because of it

+1 to proposal above. And the argument "I want to be able to distinguish my project from all the other projects" becomes a bit meaningless if enough people say that and when we run out of colors that humans can distinguish... ;)

Ok, then one color for Team as well. I could propose purple and that would a) respect Greg's color and b) completely ruin his initial point. Yet purple does look good in there, because it is distinctive but not too far from the default blue Project.

But but but... the number of projects on any given Task or Mock or whatever will not be hundreds, it'll be 1 or 2 or 3. In that limited space, you're more likely to have a unique color.

Of course there will be a rainbow of undistinguishable color patterns on the big list of projects, but again, on any given task or diff or whatever, it'll help.

The 'one color per type of thing' will make the colors of projects on an individual task or diff or whatever, by definition, not helpful/distinguishable.

If people are moving between projects and spaced on phabricator, color should have consistent meaning across areas. I'd seriously suggest we "set these in stone" at a foundation level

Ok, I appear to be outnumbered :)

So, just to be clear, this isn't "at a foundation level" this is at a phab-wide and thus community level. You all get to deal with the complaints of any community project like pywikipediabot and their requests for a different color (or just doing it themselves). :)

(ugh, how do I remove Release-Engineering-Team from this mock?)

maybe I'm colorblind (I don't *think* I am) but the new mockup makes the team and project look the same color… which is confusing…

psss...I don't think anyone changed the color yet :)

Maybe I'm doing something wrong. I have uploaded two versions and they appear in "Mock History" above, but the one that appears by default is still the first one, not the last.

See the last version: https://phabricator.wikimedia.org/M4/6/

Ah, wait. Turns out that new versions are not picked as default automatically. You have to edit the Mockup to decide which one is shown. Well, kinda makes sense if you are aware of this.

Fixed.

looks go to me now.