[VTK ARB] Git-SVN

[Claudio Silva]

Berk,

Thanks for the links. At Utah, we've moved to SVN a few years back,  
and although I have used git a bit, I wouldn't consider myself an  
expert.

As someone that appears to have lots of experience using all these  
tools, what is your personal preference?

Claudio.



On Oct 5, 2009, at 12:24 PM, Berk Geveci wrote:

> I don't think that we should think this in terms of Git vs. SVN. We
> should instead think of it in terms of centralized version control
> (CVS, SVN etc.) vs. distributed version control. These two articles
> are a good summary of the differences between the two:
>
> http://www.ericsink.com/entries/dvcs_dag_1.html
> http://www.ericsink.com/entries/dvcs_dag_2.html
>
> If we decide that distributed version control is the right thing for
> VTK, we can either pick a tool that is well supported on all platforms
> we are interested in (probably Mercurial) or we can wait until one of
> them becomes mature enough before switching.
>
> If we decide that centralized version control is the right thing, we
> should probably switch to SVN as soon as we can. Tracking SVN with Git
> is possible but it is more limited than using Git or Mercurial for
> everything (see the articles above to understand why).
>
> -berk
>
> On Mon, Oct 5, 2009 at 3:33 AM, Paolo Quadrani  
> <p.quadrani at cineca.it> wrote:
>> Dear all,
>> attached you can find a document that make a comparison between Git  
>> and SVN.
>>
>> For new version of our MAF framework we decided to use SVN as main
>> repository for code sharing and then each developer if want can  
>> have its own
>> Git local repository to manage its own history for its local code  
>> changes,
>> and maintain changes also if it has no network connection.
>>
>> Just a comment on code contribution: if someone wants to contribute  
>> with its
>> code, I think that you cannot accept code without documentation (in  
>> doxygen
>> style for example) and the related test class that prove that the  
>> code
>> works.
>>
>> I can propose also that submitting code could be done through a web
>> interface that present a form to be filled with fundamental  
>> information that
>> the code must have and you decide what is important for you and for
>> validating the code. This means that you filter at begin the code  
>> and accept
>> only valid code and don't loose time to review tons of classes sent  
>> via
>> mail.
>> There should be also some pre checks for checking that coding  
>> conventions
>> are respected. For MAF we have some python scripts that check that  
>> classes
>> have the documentation inside and it is written in doxygen style,  
>> scripts
>> that check that code is written respecting the coding convention  
>> and so on.
>>
>> Cheers
>>
>> Paolo Quadrani
>> _________________________________
>> CINECA
>> System and Technology Department
>>
>> Via Magnanelli 6/3  40033
>> Casalecchio di Reno
>> Italy
>>
>>
>>
>>
>>
>> _______________________________________________
>> Arb mailing list
>> Arb at vtk.org
>> http://public.kitware.com/cgi-bin/mailman/listinfo/arb
>>
>>
> _______________________________________________
> Arb mailing list
> Arb at vtk.org
> http://public.kitware.com/cgi-bin/mailman/listinfo/arb