NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
--Larry Wall in perl.c from the perl source code
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Re: layout (Score:1)
While it's a different situation, when I was setting up my CPAN repository on googlecode, what I thought about was how I (or others) would use SVK to work with the code. What parts of the repository would I mirror locally?
Putting the trunk too high up would mean I'd be mirroring everything or else having to separately mirror a trunk, tags, and branches if I only wanted to work on a single module.
So, better for me was a module-first layout
Given your description, the lowest pain structure for your teams is probably team centric, but with the possibility of merging to a common point over time.
I also like the suggestion above to be module-centric but disambiguate by team name.
As modules are renamed to be uniquely named, that's easy to change. (Hooray for Subversion directory renames).
-- xdg
Reply to This