repository topography considerations

[Fletcher Cocquyt <fc...@stanford.edu>]

Hi,
We have several (> 10, < 100) projects in CVS we'd like to migrate from a
flat CVS structure to SVN
We are using mod_auth_kerb to hook into campus Kerberos servers for
authentication - works fine.

We mulled over the implications of these topography choices:
1) All projects in one repo.
	Pros: one location to find everything - less admin overhead
	Cons: does not allow granular (per project auth) via mod_auth_kerb
Location directives since all projects are in the same fsfs location
2) Projects get grouped into their own repos based on logical user groups
	Pros: allows more granular auth per project class
	Cons: Can't easily move projects between repos and maintain history?
(this is not clear - looks like maybe a manual dump and load may work)?

Q: What are the best practices?
How are others deciding these issues?
Thanks, 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Fletcher Cocquyt
Data Center Services
Sr. System Administrator
Information Resources & Technology
School of Medicine Stanford University
650-723-8390, option 6
fcocquyt@stanford.edu




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org