Re: Requiring SCM

Quoting Pierre-Alain Joye <pierre@dotgeek.org>:

Please rephrase, I miss what are your objections :) or is it simply that you do not want to have public SVC as requiremnts for PEAR packages?

Correct.

I would like to force people to use a public sources versions control system for any package available through PEAR.

And I say that I don't think that's a good idea. I think there is a better argument for forcing everyone to use cvs.php.net than there is for this. For one thing, it creates enforcement/policy problems. Consider: - package is proposed. It's in accessible CVS somewhere other than cvs.php.net - package is accepted - one or two releases are made - CVS goes away (hosting dies, lapses, whatever) What do you do now? Sure, you can answer that, but I'd rather not get into the position of *having* to answer it. I don't see the need. -chuck -- "But she goes not abroad in search of monsters to destroy." - John Quincy Adams