Resolve my confusion about SVN “projects” on a remote repository?

Let's see if this helps: a Subversion repository is the deamon/server process that responds to your svn client commands. Also, the whole content accessible via a single server might be regarded as the repository A project is nothing more than a simple folder within the whole subversion hosted content In facts, that's pretty much the reason why you use the layout as you described: if you want to have different branches or tags, you "copy" the whole project in a new location under the tags or branches folders, "creating" a separated project to host that separated codebase. And it's also the reason why TortoiseSVN (and any SVN client) cannot care less of your repository layout: they only need to know the absolute remote URL associated to your local files and they're absolutely fine with it Usually, in order to have multiple project in a single SVN repository you create a base folder per each project and then the normal layout as you already know it within, like: svn_root/ | |\-> projectA | | | \->trunk | \->tags | \->branches | \-> projectB | \->trunk \->tags \->branches As there's no such a thing as a subversion "project" formal definition, just think of them as xp-dev logical entities and create two separated projects, one per each project you have :-) EDIT: updated to clearly state what the suggestion is.

Let's see if this helps: a Subversion repository is the deamon/server process that responds to your svn client commands. Also, the whole content accessible via a single server might be regarded as the repository. A project is nothing more than a simple folder within the whole subversion hosted content.In facts, that's pretty much the reason why you use the layout as you described: if you want to have different branches or tags, you "copy" the whole project in a new location under the tags or branches folders, "creating" a separated project to host that separated codebase.

And it's also the reason why TortoiseSVN (and any SVN client) cannot care less of your repository layout: they only need to know the absolute remote URL associated to your local files and they're absolutely fine with it. Usually, in order to have multiple project in a single SVN repository you create a base folder per each project and then the normal layout as you already know it within, like: svn_root/ | |\-> projectA | | | \->trunk | \->tags | \->branches | \-> projectB | \->trunk \->tags \->branches As there's no such a thing as a subversion "project" formal definition, just think of them as xp-dev logical entities and create two separated projects, one per each project you have :-) EDIT: updated to clearly state what the suggestion is.

– TMC Mar 11 at 9:08 I'm saying it's best to create 2 separated projects. It makes even more sense if you're using tools such as xp-dev because "projects" are meaningful entities there, as they are used to provide management features or views on your versioned content. – skuro Mar 11 at 9:36 1 While I agree that everything in this answer is true as it applies to Subversion, the OP question was asking about projects as they apply to Codesion (and other remote repositories) in particular.

A project in Codesion can contain 1 each of Subversion/GIT/CVS repositories. After the Subversion repository is added to a Codesion project, it can then be organized into Subversion "projects" as described in this answer. – NightOwl888 Jun 4 at 20:08.

The other reply is correct. In the example you place a 'project' is just another folder. However, let me expand it in the Codesion context as you mentioned Codesion.

: You can have one Codesion Project, with one Repository.... so you can have: (CompanyProjectX is just a folder here) MyCodesionProjectRepo | |\-> CompanyProjectA | \trunk \branches \tags |\-> CompanyProjectB | \trunk \branches \tags Or you can also have 2 Codesion Projects (ea with it's own repo): MyCodesionProjectRepoA | \trunk \branches \tags MyCodesionProjectRepoB | \trunk \branches \tags As recommended by the other answer, it's probably better to create a repository (or Codesion Project) per your company/organization projects cheers! Tona.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.