[Insight-developers] Best practices for contributing to ITK

[Hans Johnson]

Dan,

I was reading chapter 5 of ProGit while writing this example  :).  In this
simple case, I think that many of Git¹s powerful features are not needed.

Hans



On 7/30/10 2:14 PM, "Daniel Blezek" <Blezek.Daniel at mayo.edu> wrote:

> Hi Hans,
> 
>   I took a look at your proposed workflow.  I too have been learning a git,
> and found the chapter in the ProGit book very helpful for understanding the
> ways in which git can be used by development teams.  The workflow you outlined
> is more-or-less what we would have done in CVS (minus the branching).  I would
> suggest having a look into this chapter on Git.
> 
> http://progit.org/book/ch5-0.html
> 
> I have to admit I don¹t really know what would work out the best for ITK, but
> I think there is much power in Git that we should leverage.
> 
> Best,
> -dan
> 
> 
> On 7/30/10 12:56 PM, "Hans Johnson" <hans-johnson at uiowa.edu> wrote:
> 
>> As I¹m learning git, I realized that some documentation about the best
>> practices for contributing to ITK would be useful.
>> 
>> I¹ve put together the start of a ³Git²-centric contribution best practices
>> guideline at:
>>  
>> http://www.itk.org/Wiki/ITKContribute
>> 
>> I would really appreciate if someone could look this over and comment on if I
>> am taking the right approach.
>> 
>> =========================
>> The hope that I have is that Mantis can act as a resource for identifying who
>> is working on the various tasks involved in the ITKv4 update, and eliminate
>> the potential for duplicate efforts.
>> 
>> I¹ve spend most of yesterday and today making MANY MANY changes to my local
>> repository, and I hope to be able to contribute them to the git repository
>> once the dashboards are in working order.
>> 
>> Regards,
>> Hans

-- 
Hans J. Johnson, Ph.D.
Assistant Professor
200 Hawkins Drive
T205 BT, The University of Iowa
Iowa City, IA 52242

hans-johnson at uiowa.edu
PHONE: 319 353 8587

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.itk.org/mailman/private/insight-developers/attachments/20100730/de70a732/attachment.htm>