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).
As much as I'd like to see this project expedited, as well, I agree with Derick, here. It would be nice to have an independent server, but we can't risk the possibility of its admins becoming "rogue", and dirtying the php.net domain.
umh but if there are 4-5 administrators the possibility that they *all* join the dark force is kind of limited isn't it ? If you have the new box protected by lids (http://www.lids.org/)
and regularly monitored & updated it should be fairly secure. I am sure that among the docs team there are at least few expert server administrators.
I am not sure that there are expert server admins among the currently active members of the docteam.... But we might also be able to organize this new vhost by putting this all up on the server of some already working PHP.net mirror site to a different vhost (Damien [fr.php.net] comes to mind, and Cece [hu.php.net]). Since these servers are already part of some trusted group (official mirror sites), it might be easier for systems@ to agree that doc.php.net will be set up on one of these machines.
Far fetched, maybe.. but systems should be controlled by the systems team.system could have access to the new machine and run some routine security checks. Or someone could donate a new box/hard disk to system if that helps. Of course systems should be available to run the necessary changes and positive to the idea.
If I would be a real member of systems@ I would not be keen on doing security checks on a server, where I don't know how things are set up, and I know anyone could change the settings anytime without myself knowing about it... This makes looking for the server a lot harder, and a lot more time consuming IMHO.
Goba
