[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: Fri, 12 Mar 2010 12:39:15 +0000

On 12 March 2010 11:36, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On Thu, Mar 11, 2010 at 23:56, Simon Large
> <simon.tortoisesvn_at_googlemail.com> wrote:
>> 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?
> yes.
>> Does Google support hook scripts?
> not really. But they have something called "PostCommitWebHooks":
> http://code.google.com/p/support/wiki/PostCommitWebHooks
>> 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.
> Just a notice without a redirect should be enough. Just like svn did:
> http://subversion.tigris.org/
>> 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.
> I agree. Also Drupal is a real pain when it comes to updates.
> We could go for a static setup, with static html/php pages.

+1. If we can add it to the GC repo and get a post-commit hook to
update then even better. We don't have to version everything (which
was a real pain on the old CVS tigris website, with all the generated
PDFs versioned too), just the main pages. Downloadable files could be
uploaded manually.


:       ___
:  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-12 13:39:23 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.