Create Policy walls around content in Phabricator. Keep the peanut butter out of the chocolate.
Fri, Feb 19
See T13602 for modern followup, recent changes, and plans.
Feb 5 2021
See also PHI1987 for another case of this.
Jun 5 2020
Spaces have been working great for my install. The only real place where they're lacking I think arises from their coarseness/mutual-exclusivity.
Jun 17 2019
Jun 13 2019
May 3 2019
Mar 12 2019
D19549 added Spaces support to projects.
May 31 2018
In Barcelona we're looking at the same problem: how to deactive Spaces? After archiving all spaces, the UI still keeps on showing the Space dropdown with default Space. We would be glad to simplify life of our users, and haven't seen the added value of Spaces as such. If anyone could give us a hint that would be greatly appreciated. Thanks in advance!
Mar 18 2018
Mar 14 2018
Nov 28 2017
Aug 6 2017
I'm going to wontfix this. Functionally, everything is incorrect on the batch editor on a new install, if you have no users, no projects, no spaces. These don't seem to be too confusing to understand.
Jul 10 2017
T4411 discusses some similar issues, although it predates Spaces and focuses on subscribers rather than assignees.
Jul 9 2017
May 29 2017
I had indeed implemented precisely that herald rule once I realized that these diffs were being created without repository info attached. I also added repository.callsign to /etc/arcconfig to eliminate the problem going forward.
We've seen a couple of flavors of this from @swisspol, too. Although the symptom there is a little different (not a policy issue, exactly), the root cause is mostly similar. In particular, we saw:
Mar 26 2017
Mar 13 2017
Mar 8 2017
Feb 13 2017
Feb 2 2017
Jan 6 2017
I'm going to merge this into T11580 because I think that describes what remains here.
Jan 5 2017
- Paste the patch into a $FILE
- cd $PHABRICATOR_SRC
- patch -p1 < $FILE
Dec 13 2016
Sep 14 2016
@devurandom - I am facing a similar problem in my installation regarding "corporate secrets". How to I get this and perhaps other similar patches up and running?
@avivey (this is me testing it again) : Or perhaps the search is just taking .... forever .... XD
I do notice that this is actually in place on this site
what? I'm pretty sure that there's no way to do it at all...
Aug 25 2016
Aug 5 2016
May 24 2016
May 10 2016
@revi This third party tool no longer exists, the two links are broken and the latest commit at https://github.com/haskell-infra/libphutil-haskell removed the changes:
Apr 16 2016
Apr 7 2016
Just to add: in a big organizations Spaces can be used to divide different legal entities in a group (or big departments).
With this use most probably the majority of the users will belong just to one space, and they will just see the (default) "public" space and their own one. That means that in this case the majority of the users will not even need the switch, but just the possibility to configure the default space for new objects to their own one (not the default "public" space).
The user configurable parameter for the default space for the new objects creation can be anyway a first step in implementing then the full functionality of Space switching.
Mar 18 2016
@chad : Thank you for your answer, that is very helpful. I will wait for custom forms on workboards.
I would recommend creating a custom Maniphest form and requiring people who need to create tasks in those spaces, use those forms from the Quick Create menu. Custom forms are not currently available on Workboards, they will be at some point.