Okay, before seting this up, I'll point to what I think should be the installation, so we can agree on the structure, before doing anything, now that the data is safe and tron admin is alive and answering.
I'd just install a main subversion server in:
Other projects in simutrans could get also their own svn repo, that's no problem.
I'd send the root passwords to prissi and dwachs, so there is more than one person capable of fixing things up if we fall into disaster again.
I'd use "svnserve" for this, the server shipped with subversion. I'd copy the pre-commit hooks tron has, who'd need to send them to me, or tron can be allowed to log into the server and setup the server himself.
As for backup, I'd just propose any member that has a server on the internet that wants to set up a mirror, setup read-only mirrors in their own machines, and post the info in some descriptive page. Having two RW mirrors (both in isaac's machines, or not) it's more complicated, and can give lots of problems in the future if they lose sync.
It's also very important we have mirrors outside isaac's servers, because you never know what can happen to his ISP, and we have to have a plan for those situations, even if they are extremely unlikely to happen.
About github, I'd designate one master git-svn repo, prissi's or dwachs one, that's able to push patches into the "official" svn repo, given previous approval of them. git pushes should go to them, they'd the be official git repo. This way we can get useful modifications from github pushed into subversion, from github users.
I'd keep the revision numbers for now, but someone should study where are revision numbers used atm and design a new system to stop using them.
What do you think?
As soon as we get to some agreement, we can start the tests.