Re: hosting packages on external VCS sites

Hi, Gregory Beaver wrote:

This would mean that if a user is unwilling to host their code at cvs.php.net, we would no longer be willing to host their code at pear.php.net, and that external documentation is simply not allowed unless it is a manual at a registered domain name.

If an external source code repository goes belly-up, one can continue working on the package starting with latest release on PEAR website. So this is a non-issue *unless* said releases are gone, too. Thus our first goal is to prevent PHPUnit situations in the future. The docs are a different issue, but as Lukas already mentioned, we need to define the basic requirements first. Also, maybe it is possible to setup some mirroring service for external docs?