I think you misunderstood the point. We would not like to split up the stuff and host on different servers. We would better live with a server which is capable of serving our needs (building docs in HTML, PDF, etc., regular building of revcheck info, providing services for translation teams, etc.).
I need to set-up this for real, it 'kinda' works now, but misses some parts (ie. for PDF). I hope get it this done later this week (as soon as I settled in here).
But, I don't see really why we need to have this same box as a testbed for livedocs; I don't really want people messing with the set-up of this machine.
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?
Goba
