Description Kevin McGuire 2001-10-10 21:38:32 EDT

How to support large CVS development.

Issues:
1.  We need to examine and rethink our mapping of our projects and CVS
2.  In CVS sometimes you have modules and sometimes not so we can't rely on
	them for defining a project.
3.  Taking the entire root set as projects also doesn't match how most lay out their data. 
	As a result, you must load in more than you want.
4.  Some CVS houses have recursive projects (projects in projects) but this is unlikely to
	be supported, least of all by core.

Requirements:
1.  Be able to checkout just a subtree of a project.  Presumably we'ld still need to load the parent
	directory structure and the project meta files.  Side issue: how do we know what the metafiles are?

2.  Be able to define 'arbitrary' directories as being projects.  The catch here is that you could
	not have resources above this directory which you'ld want to version manage.
	Q: How to 'remember' where the projects are?  Modules/aliases?


NOTES: