Best practice for creating subversion repositories?

Question

Our team (5-10 developers) plans to adopt Subversion for our .NET (Visual Studio) projects/solutions (VisualSVN Server, TortoiseSVN / VisualSVN).

W

Answer 1

• SVN managment standpoint I prefer 1 repository.
• Programmer standpoint I prefer 1 repository.
• Server Administrator I prefer 1 repostitory.
• Security standpoint it is preferrable not to put all of your eggs in one basket.

Your repository structure will be somewhat unique to your business, and it's products. We keep ours in one repository. Our structure somewhat like this.

• /
  • Projects
    • Project Name
      • trunk
      • branches
      • tags
  • Documentation
    • Project 1
  • Shared Libraries
    • Super string class
  • Small utilities
    • vim enhancement X

Answer 2

We have separate repos for each project; but the main reason is for access reasons plus if the customer wants a copy of their source we can give it to them with history without too much fuss. If you look at the config files in conf it's not that hard to have a universal config file that will work for all of your projects. We do it like this:

[general]
anon-access = none
auth-access = write
password-db = ../../conf/passwd
authz-db = ../../conf/authz

authz:

[groups]
AOS = nathan,mark

[AOS:/]
@AOS = rw
frew = rw

and then of course passwd:

[users]
frew = password
nathan = awesome
mark = station