1. CVS accessed via SSH. Using passwd file in CVSROOT, administered with cvspadm or cvsadmin (link down – 22092004).
    Rationale: Why CVS not subversion? Well, I've used CVS… SSH for greater security over pserver's numerous security vulnerabilities. I also don't want the restriction of one system user for one CVS user.
  2. CVS commit notification using activitymail or log_accum, sending emails to a Mailman list.
    Rationale: I've used log_accum.pl and happy with it. We want to raise visibility of commits. Mailman allows developers to subscribe to commit emails, or view archives.
  3. Web-based access via CVSWeb or ViewCVS
    Rationale: Well, we want to be able to access the files via a browser too, don't we?
  4. Maven-based build system
    Rationale: Hell, Maven is so much cooler and more extensible than Ant.
  5. Daily build with AntHill OS
    Rationale: Raises project visibility, runs unit tests, open-source. AntHill provides easy way to change build schedule (no messing with crontabs) and also provides web access to build logs and version incrementing (with cvs tagging). You'll have to use an Ant wrapper for Maven to get AntHill to run Maven build scripts.

That's it for now. A pretty modest list, and nothing too difficult to implement.

Comments Off on Ideal Development Management System