repository orgnization

[Joi Ellis]

I manage a CVS repository which I've used to store all of my projects
for the past two years.  Recently my manager asked me to migrate this
repository from my own workstation over to a company server so that
everyone in our Engineering group can use it.

I use JBuilder with my CVS repository, and the structure I have is simple:
  
  CVSROOT/module1
  CVSROOT/module2
  CVSROOT/module3
  ...

Each module is a single JBuilder project.

The guys are migrating code from an ancient SourceSafe server into my
repository, and they are building a tree-structure with their stuff:

  CVSROOT/Engineering/Libs
  CVSROOT/Engineering/APi
  CVSROOT/Engineering/Firmware/i386
  CVSROOT/Engineering/Firmware/strongarm

They're calling each of these "separate modules", but in actuality
they're creating one big cvs module called 'Engineering'.  They aren't using
the CVSROOT/CVSROOT/modules file at all.  None of these people have any
experience building or managing a repository.

They're also demanding that I move all of my existing modules into a
section of their tree, and the fact that this breaks JBuilder and the
other cvs-related tools I've been using for two years has no impact on
them what-so-ever.  Apparently the sight of my java code in the repository
offends their C/C++ sensibilities. :p

I'm ready to delete my modules from the repository and create a new one
just for myself so that I can continue to function and they can do whatever
they like with their VSS-wannabe CVS design.

I looked around in the CVS FAQ and the best-practices stuff looking for
guidelines on repository layout, but I couldn't find anything.

I haven't done much with branching, release tags, etc etc.  Besides the
obvious inability to refer to anything by a logical module name, what
other problems are the guys going to run into, if any?  (I already know
that at least some cvs applications like JBuilder won't grok nested modules.)

-- 
Joi Ellis                    Software Engineer
Aravox Technologies          address@hidden, address@hidden

No matter what we think of Linux versus FreeBSD, etc., the one thing I
really like about Linux is that it has Microsoft worried.  Anything
that kicks a monopoly in the pants has got to be good for something.
           - Chris Johnson