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

Re: Merge svnraisetc branch to trunk

From: Blair Zajac <blair_at_orcaware.com>
Date: Sun, 10 May 2009 22:34:50 -0700

Gavin Baumanis wrote:
> On 08/05/2009, at 1:36 AM, Blair Zajac wrote:
>
>>> <snip />
>> I'm against removing contrib/ until we have a place to move it to
>> and an
>> infrastructure to support it.
>>
>> Kevin's idea of setting up svn-contrib is a good one. Just if it
>> lives on
>> tigris or code.google.com is a question. I think I'd rather see it
>> on Google Code.
>>
>> Blair
>>
>> ------------------------------------------------------
>> http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2096673
>
> As a relative new-comer I have to ask why would Google Code be a
> better option?
> It seems more sensible to be to have ALL Subversion "stuff" at the
> "home" of Subversion.
> If "I" am looking for something Subversion related I "always" go to
> the Tigris site first to find what I am after - then branch out from
> there if I am can't find what I am looking for.
>
> Though, I could of course be missing something about Google Code - I
> have never used it.
> And if that's the case - I.e Google Code has better API / UI or
> similar - wouldn't the answer be to match the required functionality
> at Tigris?

I'm thinking that more people have Google accounts and the overhead of giving
people access to the svn repository there is probably less than at tigris. But
that is just a hypothesis.

Blair

-- 
Blair Zajac, Ph.D.
CTO, OrcaWare Technologies
<blair_at_orcaware.com>
Subversion training, consulting and support
http://www.orcaware.com/svn/
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2184056
Received on 2009-05-11 07:35:12 CEST

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

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