This project is being hosted by SourceForge.net.
This is their logo:
There haven't been that many questions, actually. The only question we have been genuinely asked so far is:
Some CVS users may be offended at being monitored by something called "CVS Cop." Couldn't you call it something a little nicer?
We were considering calling it fuzzy-pink-bunny-slippers just so CVS users wouldn't find it personally offensive, but our concern over the matter quickly subsided.
Actually, users don't need to know that something called CVS Cop is there. It's in the background. They just need to know that they weren't allowed to check something in and why.
Why should I use CVS Cop?
CVS Cop is useful if you have a relatively complex set of rules you want to apply to CVS usage, like one or more super-users, special rules for certain directories, modules, file or tag names, or if you want more than one external script to be launched in one phase on CVS's back end.
How hard is it to maintain?
Not very. You have to be able to follow what happens in the configuration file (see the front page for an example), which is a rather simple XML, and you need to have a reasonable understanding of regular expressions in order to define match rules. Several examples are provided in the documentation.
So is it Cvscop, cvscop, CVScop, CVSCop, or CVS Cop?
Under what license is it available?
CVS Cop is distributed under the GNU General Public License, version 2.
What is all of this SQL stuff?
One of the original tasks for CVS Cop was to track CVS activity via a mysql database. Since then, we've moved on to using Bonsai instead, which is a much better idea.
In other words, it's an old feature that needs to be removed.