[Trac] Scope of a "project" or a "repository"

[Nigel Metheringham]

Hi,

A fairly newbie question, and possibly more subversion than trac - and
indeed it feels like one thats got good potential for religious flame
wars...

I have used CVS for years.  That was basically set up as one repository
per political organisation (ie I have one at work and one for each other
group I work with), and each project was a module within the repository.

With subversion, and so with trac, I am having trouble deciding whether
a svn repository maps to a project (CVS module) or to a multi-project
(CVS repository).

I can see advantages and drawbacks with either approach, and I can see
that for some projects (with synergy between the projects) there are
definite arguments for putting several projects into a repository, but
with the SVN idea that a changeset applies across the whole repository
you get the feel there may be overhead and unnecessary "bleed" between
projects (ie trac would show changesets you don't care about for
example).

I'd appreciate comments...

	Nigel.
-- 
[ Nigel Metheringham           Nigel.Metheringham at InTechnology.co.uk ]
[ - Comments in this message are my own and not ITO opinion/policy - ]