I have notes on all of this, but I can't even get the "web team" to fix the Deskzilla login, let alone implement a new "testing application" on the site.
I want to say sorry any inconvenience (related to deskzilla login), that we haven't managed it fix the last outstanding porblem. Afaik, in June (or May) 2006, I heard the first time about the problem. Some weeks later I spent some time testing it myself. The DeskZilla error output was really contra-productive and searching things in bugzilla code mess is a nightmare. After logging the raw data transfer with wireshark & co. wax and I found the real problem, it's bugzilla multilogon-plugin system plus roscms auto-redirect bugzilla plugin. Micheal Wirth tried in sommer to fix it, appearently he is busy with real live and had no time to finish it. I was busy with other parts of ReactOS too and eventually even stopped coding on it to fix and improve several part of the website. This process is still ongoing and I hope that all get back to normal in 3-4 weeks, after the website major update has been finished. I want to mention that there is no "web team" by definition, it's basicly (as of now) aleksey (hardware, server software, svn, etc.), aleksey's friend (helping with server transfer and related tasks) and me (web software). ReactOS has no real "teams" for years, even if the wiki may stats otherwise.
So what does this mean, as soon as I find time, I will either find someone who know how to hack the bugzilla the right way, or do that task myself.
The svn server is unrelated with the ReactOS webserver. In near future, the buildbot/master web interface will be integrated with the reactos.org website though.
Klemens