hosting packages on external VCS sites

Hi all, I am dismayed to see that a few of our packages that have external hosting of revision control now come up as 404, and some with external documentation come up as 404. This is completely unacceptable. I would like to revise the requirements for allowing external hosting of PEAR package sources or documentation to read that this is only allowed if the package has a *registered domain name* and a substantial history as an external site. This would allow packages like phpDocumentor that have a large userbase outside of PEAR to operate under the assumption that the stability of a registered domain name means the site is not likely to suddenly disappear. 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. By registered domain name, I mean something like "phpdoc.org" or "phpunit.de", not "joe.smith.uk" or even "sourceforge.net" Another possibility would be the immediate removal of a package from the maintainer's control should an external site go caput, rather than requiring a registered domain name. If either possibility is acceptable, this would immediately affect Structures_Graph, which has external documentation that is gone, Services_Google, which has missing external subversion, and probably a few other packages. I haven't gone through all 400+. What do you think? Greg