[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: repository location

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Thu, 11 Mar 2010 22:11:44 +0100

On 11.03.2010 20:13, Stefan Fuhrmann wrote:
> On Wed, 10 Mar 2010 19:17:09, Stefan Küng wrote:
>> Some time ago I've created a doc listing the pros and cons of various
>> open source hosting solutions since I'm not very happy with the UI and
>> the limitations on tigris.org.
>> I'd like to propose that we move our repository to Google code. I've
>> listed the reasons why in said document, which you can find here:
>> https://docs.google.com/Doc?docid=0AaqzZMak_nntZGhwNmhjY25fMTQ1Y2pxNHpiNjQ&h
>> l=en
>> For now, I suggest we only move the repository to Google code. Mailing
>> lists and websites can wait for now.
>> Thoughts?
> +1 on moving the repository. The new server should
> be faster and https support is definitely a plus when
> proxies get don't handle webdav/deltaV.
> We may want to keep the old server, though, to have
> a relatively slow test repository.

Sure, I'd like to keep the old repo too. At least for a while.

> +/-0 on moving the mailing lists. For me, they worked
> reasonably well and I use haxx.se archives only, anyways.

We won't move the mailing list right away. But it is up for discussion.

> -0 on moving the download away from SF.net. The only
> problem were reports of occasional corruptions. But
> my impression is that they are rare enough to either
> attribute them to problems outside SF or to expect
> similar issues from any other vendor.

I'd like to keep the downloads on sf.net too. The many mirror servers
are really great for handling the load of our releases.

> -0 on moving tsvn.net. The only reason to move would
> be saving money, right (which is fair enough)?

nonono, we will keep tortoisesvn.net! That's the only place where we
have full control over the server and can write our own PHP pages to
generate e.g. the translation status.

> Generally, it seems that there is no reason to centralize
> everything on one site - having different servers worked
> quite well so far. But on the other hand, I don't have to
> cope with the management overhead. So, take this as
> the personal opinion of an outsider ;)

Moving the repo to google code isn't about centralizing everything on
one place but to get a much better UI and a repo that's actually working
without too many interruptions.


   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-03-11 22:12:52 CET

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.