I read through all the docs I could find, but was unable to determine the best practices for how phabricator is designed to work with larger subversion repositories.

Unlike with git, it is common that svn administrators create one huge svn repository across the entire organisation. That helps later on with copying and moving files between projects and is just easier to organise. For example http://svn.apache.org/viewvc/ has close to 2 million commits in one project.

My instinct is to set up diffusion with a single repository rather than one per project. And the 'owners' module seems to be able to create a relationship between users and paths within a repository. However I am not clear what the relationship is between projects and repositories... I couldn't find one, but clearly it would be useful (for example to show all commits related to one project).

So, could you please clarify in the documentation as to what the best practices approach is here for how to set up phabicrator diffusion. git will tend to force you to one repository per project (since that's the only way to do access control), but svn will naturally go the other way.

Also, clarify around how arcanist will relate actions to projects when operating against a working copy would be useful in the documentation.

I hope you don't mind me putting this request for documentation as a new task since I could not find a better place to raise this issue. Thanks.