There are a lot of questions on SO about Subversion repository organization. Perhaps some experts on the subject could go through these and identify some good candidates for the "canonical questions" that cover most cases, and close the questions that are duplicates? I'd vote to close a few but there's enough hair-splitting differences that I don't feel comfortable doing so.
Here are some of those questions:
- subversion tags and branches
- What is the reasoning behind the recommended layout for Subversion repositories?
- Should I store all projects in one repository or multiple?
- Subversion - is trunk really the best place for the main development?
- How do you organize your version control repository?
- What is a good repository layout for releases and projects in Subversion?
- Shared components throughout all projects, is there a better alternative than svn:externals?
- How Granular are your SVN "projects": one big project containing several releated apps or one "project' per app
- Is a good idea to put all projects in the same trunk?
- Should you have branch, tag and trunk folders even for small projects?
- Folder structure for many projects in one SVN repository?
- Suggestions for setting up a subversion repository
- Subversion Vendor Branches
- Recommend good SVN layout for my project
- SVN Repository Structure - Why is this better?
- Repository Structure with Tortoise SVN Question
- Best practice for structure of Subversion repository working copy?
- How to Structure Subversion Repositories
- How do you arrange several projects in a single SVN server?
