I myself would be fine with a different testbed. Our first goal is to make regular builds work again for the often requested formats (including PDF).
Then if it is done, it would be nice to set up a server with public web accessibility to host stuff which helps documentation authors and translators cope with our system (revcheck outputs, readable build logs, maybe even websites hosted on that machine containing information for translation teams, or at least links to the team websites - now every team has its website elsewhere, etc). This should be the basis for the documentation team website, which would host the dochowto too. Given that maintaining yet another machine to publicly test livedocs might not be a good idea, this machine would be able to serve as a testbed for livedocs too.
Now what do you think about this two server setup suggestion?
I have a server that will be ready soon available for your use... you need to draw up some guidelines for using it however, as it wouldn't be under the immediate purview of the php systems team - so we'd need to know the sorts of things you plan to do - i think it'd be ok to add plain user accounts for php documentors - but we'd need to limit those who get sudo.
The main problem is that the doc guys have no experitse in setting up a server (properly, securely, etc). This is why we have asked for a machine and an administrator first. Mehdi had managed to get a machine, so that it is not a problem. We rather need someone to set up stuff on that server (or an existing one for that matter :). We probably only need to adjust cron jobs and vhost settings on that docteam website.
Goba
