Folder structure for many projects in one SVN repository?

Question

I just created a Google Code SVN repository for storing my school projects and homework, and to allow easy transferring between school and home.

Its default directories i

Answer 1

There is no clear answer to this question as it depends on what suits your projects best.

1. I would use /projectA/trunk layout if there was either a heavy development going on per project and everything needs to be separated since there is not that much connection between it (components/projects that stand alone). However, you could also use one SVN repository per project then. Remember you won't be able to check out all projects using svn co http://..../svn/ because this would also fetch all tags and branches from all projects, not only trunk.
2. /trunk/projectA would certainly be better if your projects/components belong tightly together and you need to tag and branch them from the same revision (like a library belonging very closely to the main project). You can also use svn co http://.../svn/trunk/ to get all projects on their latest trunk revision if you like.

From a maintainability point of view I would almost always prefer the second way; but if your projects get bigger and might prolong, it would be better to use separate repositories per project.

Besides that: Please check if you really need Google Code services for your homework because its purpose is to support OSS. You can always use SVN locally or even through SSH, so you could also put your repositories on an USB stick or some computer that can be accessed remotely; you don't really need hosting for that. There could also be privacy concerns.