Re: Requiring SCM
| From: | Helgi Þormar | Date: | Tue, 29 Mar 2005 17:17:31 +0000 |
| Subject: | Re: Requiring SCM | ||
| References: | 1 2 3 4 5 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-36956@lists.php.net to get a copy of this message | ||
On Tue, 2005-03-29 at 12:06 -0500, 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
> >
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 :)
Which is btw. one of my main parts in choosing that I like to allow
outside repos also, just so we all have the clear ;)
> 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.
Well we figure something out.
> 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...
We are not talking about that people have to put that in CVS ;-)
Hehe, so this won't help things like getting rid of possible 404 errors.
- Helgi