Re: [Flightgear-devel] The future of terrasync

[Torsten D. <to...@t3...>]

[response to several mails]

Let me try to calm down emotions here.
The technique of the http repository is much simpler than that of the svn
repository and it will be pretty simple to create a local mirror or to
download chunks of data.
With a bit of to-be-developed scripting (python e.g.) there is no need to
download existing data again. I don't know how terramaster works but I am
sure it is easy to adapt to the new http access method.

I apologize to not have everything ready at once and only implement the
transition step-by-step.
The first step was to provide the necessary infrastructure. This is
complete, we have one public master hosted at sourceforge and to privately
donated mirrors.
The second step was to implement the client to access the infrastructure.
This is complete, thanks to James for all the coding.
The third step was to invent and implement a service resolver. This is also
complete.
The fourth step is to test all this and collect feedback. This is what we
currently do.
The next steps depend on the test-results and the feedback.
Those steps will of course contain
- documentation of the service
- creation of the necessary access tools
- a reasonable time of parallel operation of SVN and HTTP

The goal is to completely remove SVN and only use the HTTP repository. I'd
like to reach that goal better sooner than later as we currently have two
single-points of failure for the SVN-service.
The first is the http://scenery.flightgear.org/svn-service web service
(runs on a private web server) and the second is the one-and-only
svn-server available for public access, also hosted on a private server. If
either on of those fails, the SVN-terrasync is dead. I have learned the
hard way that not having a fallback is a bad idea.

I hope this clarifies the process a bit.

Torsten