Re: Requiring SCM

Sounds pretty good, although I would prefer that external CVS repo's are hosted/managed/owned... by a community, rather than an individual or single company (means that the community will pickup maintance of the server if something goes wrong)., and that the code commit's emails are being reviewed by more than just the author... which probably rules out a few of the ones on your list... In reality we probably need svn.php.net..... Regards Alan On Tue, 2005-03-29 at 14:03 -0500, Davey Shafik wrote: > Pierre-Alain Joye wrote: > > On Tue, 29 Mar 2005 12:23:40 -0500 > > chuck@horde.org (Chuck Hagenbuch) wrote: > > > > > >>Quoting HelgiÞormar <helgi@trance.is>: > >> > >> > >>>IMHO it's bad if we only make people use cvs.php.net, because I > >>>don't want to force say Horde packages to have part of their > >>>packages on cvs.php.net and the rest on cvs.horde.org, that > >>>would just be inconvenient for them :) > >> > >>I'd be quite happy to move all of the packages maintained by Horde > >> folks to a Horde channel and not have any of them on cvs.php.net. > > > > > > You just got the reason why I said: "Cannot be a requirement". My > > thought was in the direction of Horde and some other well maintained > > projects. > > > > --Pierre > > > I wonder if perhaps this is the solution: > > * You must use a Publically available RCS (I'm using that instead of SCM > as I know this acro :) > > * You should use cvs.php.net. Though Exceptions will be made (see below) > > * Exceptions will be made for code not originally started for PEAR (i.e. > Horde, Cerebral Cortex, Savant etc). We should also think up some other > reasons for this, but honestly, I think this is the only reason :) > > > * If you are not using cvs.php.net somebody with karma should commit a > README document with the information for getting to your RCS into > cvs.php.net/pear > > So we can have a pear/Some_Horde_Package in CVS, and in there a README > for the cvs.horde.org (or whatever :) > > - Davey >