MASON-INTEREST-L Archives

August 2010

MASON-INTEREST-L@LISTSERV.GMU.EDU

Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Date:
Thu, 19 Aug 2010 14:44:01 -0400
MIME-version:
1.0 (Apple Message framework v936)
Reply-To:
MASON Multiagent Simulation Toolkit <[log in to unmask]>
Content-type:
text/plain; charset=US-ASCII; format=flowed; delsp=yes
Subject:
From:
Sean Luke <[log in to unmask]>
In-Reply-To:
Content-transfer-encoding:
7bit
Parts/Attachments:
text/plain (36 lines)
I believe there's a very significant advantage in terms of open source  
reputation, for using a major repository facility rather than rolling  
your own.  Indeed, one of the grants ECJ received early on was  
predicated on migrating to one of these facilities!

Sean

On Aug 19, 2010, at 2:29 PM, P. Chewning Toulmin wrote:

> Can't you just install Subversion on GMU's system?  What other  
> advantages are there to using Google Code other than Subversion?
>
> Quoting Mark Coletti <[log in to unmask]>:
>
>> On Thu, Aug 19, 2010 at 2:13 PM, Sean Luke <[log in to unmask]> wrote:
>>
>>> We've been given the green light by folks at Google to migrate  
>>> MASON from
>>> java-dev to Google Code.  I am inclined to do so, not the least of  
>>> which
>>> because it gives us the easiest path to upgrade from CVS to SVN.   
>>> Google
>>> Code also supports Mercurial, but I'm not sure that'd be of much  
>>> benefit to
>>> us.  Opinions?
>>>
>>>
>> I'm all for it.  Maybe people would be less reluctant to use  
>> branches if we
>> were using Subversion.  ;)
>>
>> Cheers,
>>
>> Mark
>>

ATOM RSS1 RSS2