views:

134

answers:

2

Have one application in SVN (on unfuddle.com). Want to add a new application (related to, but independent of the existing one).

Today I have: repo1/root/app1

Should I add the new application in a new repository or in a new folder ?

i.e. should I use option1:
repo1/root/app1
repo1/root/app2

or option2:
repo1/root/app1
repo2/root/app2

?

+4  A: 

Do like you want and what makes less hassle. Both decisions can be reverted: The directory in the repository can be extracted and imported to a new repository, or the separate repository can be imported into the first one. I don't think any of the approaches is significant better. So choose freely. I think your decision will mainly be influenced by the question, who has access to project1 and project2. If this are the same users you are fine with one repository.

At work we are a little team (less than 10 developers) and have chosen to put all projects into the same repository with different subdirectories.

EDIT: As I talked about someone else about it, I discovered one problem: The possibility to freely move projects between repositories is limited to users, which have administrative access to the repository. As someone who decides if a projects gets a directory or a repository of it's own administrative access is likely. But if you cannot the repository in this way, it gets hard or impossible to later move the project to another repository. In this case this question has to be considered more carefully.

Mnementh
+1  A: 

On my own work, if they are somewhat related I usually put them in the same repo in a different folder, but if they are not related in any way then I usually put them in different repos. I think its mostly a matter of choice unless you're working on a large project with many many MB of files.

Petriborg