Repository layouts

[jsiegmund]

Hello,

for the instantiation of our newly bought source control application I'm trying to create a "this-makes-sence" layout for the repository. I'd like to ask current users who are using sourcecontrol for a longer time than we are how their repository layout looks like. I already read the best practices at http://support.sourcegear.com/viewtopic.php?p=5183, but that doesn't provide a good layout yet.

If I understand it well you cannot import a project from another repository in another project? Since we use a custom build framework with default building bricks for almost every project that would mean I cannot divide those projects into different repositories, right?

So I thought of the following layout:

Code: Select all

- Progress Repository (with coming Fortress release)
- Microsoft Repository
  - Win apps
     - Projects (unfinished) 
     - Products (finished & supported)
     - Archive (old unused projects)
  - Web apps
     - Projects
     - Products
     - Archive
  - Library
     - Framework
     - External

Any positive/negative comments on this layout? I'm very curious about your opinions!

[Beth]

If I understand it well you cannot import a project from another repository in another project?

You could use our export import tool to pull in another project and its entire history. If you don't need the history, you can perform a get to disk from one repository and then add the files to the other repository or add them to the other project in VS if you are using IDE integration.