On Feb 1, 2004, at 2:59 PM, Gabor Hojtsy wrote:
I don't. You want this to be an official PHP thing, then it should be hosted on an official machine. We can't have each subproject being run by somebody else (if only for security reasons).
That server would only need to cvs checkout data anonymously, and it should be reproduceable on any other machine with the contents stored in cvs.php.net (the modules I have mentioned before, plus the new docweb module, plus a lot of generated data produced by the scripts from the sources anonymously checked out). Since it would only host data already publicly available (though in a more organized form), I don't know what is the problem with it...
Some PHP.net subdomains already hosted on 'foreign' servers:
- wiki.gtk.php.net - vancouver.php.net - sydney.ug.php.net - every PHP.net mirror site
The PHP.net mirror sites are considered to be 'official' as far as I can see, and they seem to be harder to control then doc.php.net would be on a non-systems@ operated machine. The operators of doc.php.net would be those who work closely with the docteam, so they are here to contact and act with if something need to be done.
It might be true however, that most of the members of the docteam are not experienced server operators (including myself), and you might think that it could be a prestige problem for php.net if someone breaks into the server and uses it for some crude goal... That could happen however with any of the above servers, since the administration skills of those operating the above servers have not been tested AFAIK. I would like to point once more that only data available from CVS, and data generated from those files with scripts available from CVS will be hosted on that machine (given that we are not going to have our own bugs reincarnation, which I take for granted for now, as I have stated before).
Someone among the docteam could have the technical skills to operate the server, perhaps some of the senior/leaders.
Just thinking loud, but perhaps system needs some hardware donation to keep up with a new server. If that is the case I could help.
Perhaps a separate machine or separate hard disk... I would be glad to help.
In alternative the new external server could have some security supervision by systems.
Regards
David Costa
