Re: Requiring SCM

Philippe Jausions wrote:

Daniel Convissor wrote:

On Tue, Mar 29, 2005 at 01:47:30PM +0200, Pierre-Alain Joye wrote:

PEAR packages must have a public CVS, I tend to want it in the cvs.php.net/pear repository but cannot be a requirement.

I agree, though don't feel too bad about requiring cvs.php.net. --Dan

Here's something nobody has addressed: who will manage karma for the CVS accounts? I took me months to get proper karma to two packages I help on, and that's only because Lukas took the time to find a member of the PHP group. Otherwise, I think it makes sense to require cvs.php.net. I came across a couple of packages lately that supposedly had their documentation on an "external" web site. But all I found was either a 404 error, the site structure changed or the doc was simply removed...

Let's be sensible folks - blanket rules must allow exceptions. For instance: phpDocumentor existed for several years before it became a part of PEAR. It has a very stable hosting provider, and a flourishing community through phpdoc.org. No need to uproot the whole thing just to make pear clean. However, a 250-line class would do better in cvs.php.net. The point: every situation is unique, but certainly something can be worked out for the majority of them. Greg