Bug 447420

Description Simon Kaegi 2014-10-15 12:49:42 EDT

The idea of projects was to narrow down the scope of your work to just the one project/folder you're working on. This is an important concept as for example I have on the order of 50 projects in my workspace. The problem is that the scope is too narrow.

For example, Orion is built from two writable Git repositories. If we were more honest with ourselves and our 3rd party dependencies we'd probably find that there were many more repositories involved. Many of those repositories would be reference-like or read-only but I for one sometimes make modifications so the restriction of a project being one repo really feels artificial.

In addition, I frequently find myself having to hop up and down from projects in the navigator even though I feel that I am working on one thing. On the implementation side I think having the project specific view just adds an extra level of PITA and again is confusing.

What I would propose is that we do away with the project specific view and instead go to a multi-workspace model (e.g. so that we can scope down our work by a multi-folder/repo workspace instead of a single folder project). Although this bug is logged against the client as its ultimately a UX bug there is will be a ton of work to do on the server to make this happen.

I think we will also have to work on a UI to help a user switch/choose and create a new workspace.