Alternate SVN server
The renaming of OSDN looks like a bad sign for its long-term stability. GitHub is advertising that they support SVN, but they don't - what they have is an API to allow SVN clients to connect to the underlying Git repository, without supporting some features of SVN that we are using and with all the built-in limitations of Git. Given that we probably cannot trust OSDN to continue to host this project into the indefinite future, it'd be good to have an SVN server elsewhere. Most likely, this would be on kharasan, the location of the current private internal SVN server. But it'll require some careful thought as to whether we can, or want to, host a public SVN on that same machine. No critical need to build this instantly, but it should be on the radar.