Some more aspects to affirm Joel's suggestions.
On the translation server we have observed that the
need for people to see certain pages, seems to be
so big that many of them registered for translator
accounts even though they did not want to contribute
to any locale.
On the other hand, it is important for translators to see
ALL parts of the UI - even the side wide admin pages
(unless we decide to exempt them entirely from i18n). For
such SWA tests, the former testing server affordance was
great for translators who could "login" anonymously as
SWA, see a specific message string in context, switch to
the translation server to edit it in the list view,
and be confident that nothing could be seriously spoilt
because everything was flushed for the next day.
The comfort of anonymously logging in as SWA, however,
does not, IMO, justify the danger that this possibility
is abused such that it breaks very early each day. I
would not mind to apply for an admin account of this
server for translation and testing purposes and still
would not insist in setting my personal favorite
password there. Just make the user administration as
convenient for the hoster as possible.
Another argument for setting up such a server again,
is that bug reporting and bug triage would be simplified
again if the "how to reproduce this bug" could again
be answered by "log in to test.openacs.org as ...,
then ...".
