[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: Simon Large <simon.tortoisesvn_at_googlemail.com>
Date: Thu, 11 Mar 2010 22:56:08 +0000

On 10 March 2010 18:17, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> Hi,
> 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&hl=en
> For now, I suggest we only move the repository to Google code. Mailing
> lists and websites can wait for now.

+1 to moving the repo. tigris.org has always been horribly slow, and
guest access a pain.

Does Google provide commit emails?

Does Google support hook scripts?

Can we add a robots.txt to the tigris website to send the crawlers
away? It comes up first in Google, but tortoisesvn.net is second. Or
if we ask tigris.org nicely they might put up a 301 redirect to
tortoisesvn.net in which case all roads will lead to the same place.

Google groups are fine with me. We can get get mail forwarded to
haxx.se as well for continuity of archives. If I want to search,
that's where I always go. I gave up on gmane years ago.

At some stage we might want to re-work the TSVN website. Drupal was
good when we used the interactive FAQ but seems like overkill now. I
think we could use something simpler and cleaner.


:       ___
:  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 23:57:11 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.