I'm one of those lurkers, but with the dubious distinction of knowing bugger all (especially about CVS). I can see a way out of this, but would require a bit (cough) more of an admin overhead for some poor sod. It's just an idea, but it sounds like you need a CVS maintainer. The basic idea involves said poor sod reviewing the changes before they are commited to the "stable" CVS, like Linus does with the Linux kernel. The person doing the review would have to know their stuff, but the CVS guy may not. Change submissions could be done in two ways. Either by e-mail to project lead/admin type bod, or by having another CVS tree that can be merged with the "stable" tree. JMac