Re: requiring cvs

Lukas Smith wrote:

I also tend to agree here. I don't know if it's a god idea to change that rule at this stage. However I think we should require that the CVS is public so that we can make incremental backups of the CVS (or even sync it over to pear CVS). This is especially important if a package that is not in CVS ever becomes orphaned. Just a thought.

I like the idea of syncing to PEAR CVS. It lets the package developer keep it where they want, but still lets the rest of us have one common place for everything. I'm sure someone more familiar with CVS than I could come up with a bunch of cool things to do with this. Either way, the CVS portion of the manual was never completed, so a lot of people probably don't know how to check anything out anyway. -- Marshall Roch