<div dir="ltr"><div>+1 for the move to github!<br><br></div><div>One small point is that ITK is highly integrated with VNL, the development of which is also coordinated on Github. Frequently, when I start investigating something in ITK, I end up in VNL's codebase. For those of us that flip back and forth between ITK and VNL, this move might help to minimize task switching somewhat.<br><br></div><div>Also, thanks very much to Matt for coordinating this effort!<br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Aug 1, 2017 at 3:56 PM, Bill Lorensen <span dir="ltr"><<a href="mailto:bill.lorensen@gmail.com" target="_blank">bill.lorensen@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">++++1<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
On Tue, Aug 1, 2017 at 10:53 AM, Michael Jackson<br>
<<a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a>> wrote:<br>
> I would like to see the Kitware sponsored projects (Itk, Vtk, ParaView.. )<br>
> ALL use the same mechanisms and host providers. Just lessens the confusion<br>
> on outside developers.<br>
><br>
> But +1 for moving to GitHub.<br>
> --<br>
> Michael A. Jackson<br>
> BlueQuartz Software, LLC<br>
> [e]: <a href="mailto:mike.jackson@bluequartz.net">mike.jackson@bluequartz.net</a><br>
><br>
><br>
> Jon Haitz Legarreta wrote:<br>
>><br>
>> +1 for the transition.<br>
>><br>
>> I'm pretty sure the ITK core devs and maintainers have carefully<br>
>> considered all choices over time. So beyond my personal likings, I guess<br>
>> github beats the rest of the possibilities in terms of the needs and<br>
>> future plans of ITK.<br>
>><br>
>> JON HAITZ<br>
>><br>
>> --<br>
>><br>
>><br>
>> On 1 August 2017 at 16:27, Cory Quammen <<a href="mailto:cory.quammen@kitware.com">cory.quammen@kitware.com</a><br>
>> <mailto:<a href="mailto:cory.quammen@kitware.com">cory.quammen@kitware.<wbr>com</a>>> wrote:<br>
>><br>
>> I don't have much of an opinion on moving ITK to GitHub, but I'd<br>
>> like to address some things Andras mentioned about GitLab and VTK.<br>
>><br>
>><br>
>> About GitHub/Kitware GitLab:<br>
>><br>
>> I heard that VTK is going to move to GitHub, too. Maybe I<br>
>> misunderstood, but make sure to talk to VTK folks before<br>
>> considering moving to GitLab.<br>
>><br>
>><br>
>> I am not aware of any plans to move VTK to GitLab or even any<br>
>> discussion of doing so.<br>
>><br>
>> Anyway, as a very active user but only occasional contributor of<br>
>> VTK, I find VTK GitLab quite frustrating due to that:<br>
>> 1. It is slow. I heard that it's fast when accessed from inside<br>
>> Kitware network, but most community members are outside.<br>
>><br>
>><br>
>> The first few versions were indeed a bit slow, but new updates come<br>
>> out regularly, and the speed is quite snappy. I use it both from<br>
>> within the Kitware network and outside the network and haven't<br>
>> noticed a difference.<br>
>><br>
>> 2. I need to re-learn each time I use it: I review code, submit<br>
>> PR or bug report once in every few months - and each time I need<br>
>> to spend 20-30 minutes extra, just to find out how things work.<br>
>><br>
>><br>
>> Andras<br>
>><br>
>> -----Original Message-----<br>
>> From: Community [mailto:<a href="mailto:community-bounces@itk.org">community-bounces@itk.<wbr>org</a><br>
>> <mailto:<a href="mailto:community-bounces@itk.org">community-bounces@itk.<wbr>org</a>>] On Behalf Of Matt McCormick<br>
>> Sent: Monday, July 31, 2017 7:00 PM<br>
>> To: Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a><br>
>> <mailto:<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.<wbr>com</a>>><br>
>> Cc: Insight-Users <<a href="mailto:insight-users@itk.org">insight-users@itk.org</a><br>
>> <mailto:<a href="mailto:insight-users@itk.org">insight-users@itk.org</a>><wbr>>; Hans Johnson<br>
>> <<a href="mailto:hans-johnson@uiowa.edu">hans-johnson@uiowa.edu</a> <mailto:<a href="mailto:hans-johnson@uiowa.edu">hans-johnson@uiowa.edu</a><wbr>>>;<br>
>> Insight Developers List <<a href="mailto:insight-developers@public.kitware.com">insight-developers@public.<wbr>kitware.com</a><br>
>> <mailto:<a href="mailto:insight-developers@public.kitware.com">insight-developers@<wbr>public.kitware.com</a>>><br>
>> Subject: Re: [ITK] [ITK-dev] [ITK-users] Migration to GitHub<br>
>><br>
>> I have followed VTK's migration to GitLab, and Kitware has done<br>
>> an excellent job with it. That said, I still think GitHub is the<br>
>> better choice for ITK. Also, the technical and social situation<br>
>> has changed in the time since VTK moved to GitLab.<br>
>><br>
>> I think the key factor is "community", and GitHub has the open<br>
>> source community.<br>
>><br>
>> On Mon, Jul 31, 2017 at 6:42 PM, Bill Lorensen<br>
>> <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a> <mailto:<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.<wbr>com</a>>> wrote:<br>
>> > Vtk moved to GitLab. Have you checked with the Kitware folks<br>
>> to see<br>
>> > why they didn't use gitlab? For me, either github or gitlab<br>
>> is great.<br>
>> ><br>
>> > On Jul 31, 2017 6:03 PM, "Johnson, Hans J"<br>
>> <<a href="mailto:hans-johnson@uiowa.edu">hans-johnson@uiowa.edu</a> <mailto:<a href="mailto:hans-johnson@uiowa.edu">hans-johnson@uiowa.edu</a><wbr>>> wrote:<br>
>> >><br>
>> >> 1000 x +1<br>
>> >><br>
>> >> I enthusiastically support this proposal.<br>
>> >><br>
>> >> Hans<br>
>> >><br>
>> >><br>
>> >> On 7/31/17, 4:57 PM, "Insight-users on behalf of Jim Miller"<br>
>> >> <<a href="mailto:insight-users-bounces@itk.org">insight-users-bounces@itk.org</a><br>
>> <mailto:<a href="mailto:insight-users-bounces@itk.org">insight-users-bounces@<wbr>itk.org</a>> on behalf of<br>
>> <a href="mailto:millerjv@gmail.com">millerjv@gmail.com</a> <mailto:<a href="mailto:millerjv@gmail.com">millerjv@gmail.com</a>>> wrote:<br>
>> >><br>
>> >> +1<br>
>> >><br>
>> >> Jim<br>
>> >><br>
>> >> > On Jul 31, 2017, at 5:07 PM, Matt McCormick<br>
>> >> <<a href="mailto:matt.mccormick@kitware.com">matt.mccormick@kitware.com</a><br>
>> <mailto:<a href="mailto:matt.mccormick@kitware.com">matt.mccormick@<wbr>kitware.com</a>>> wrote:<br>
>> >> ><br>
>> >> > Hi folks,<br>
>> >> ><br>
>> >> > We are considering migration of ITK's software process to<br>
>> >> GitHub, and<br>
>> >> > we would like your feedback.<br>
>> >> ><br>
>> >> > As an open-source, community-driven project, mechanisms to<br>
>> >> communicate<br>
>> >> > and interact with the community are a high priority for ITK.<br>
>> >> > Contributing should be as easy as possible. Increasingly<br>
>> over<br>
>> >> the past<br>
>> >> > many years, GitHub has become the de facto place to interact<br>
>> >> for open<br>
>> >> > source development. It is now a hub for:<br>
>> >> ><br>
>> >> > Microsoft<br>
>> >> > Facebook<br>
>> >> > Google<br>
>> >> > The Scientific Python Community<br>
>> >> > The 3D Slicer Community<br>
>> >> ><br>
>> >> > Our InsightSoftwareConsortium GitHub organization [1]<br>
>> already has 67<br>
>> >> > people in it and 74 repositories. There are hundreds of<br>
>> >> projects that<br>
>> >> > depend on ITK on GitHub. Many ITK developers are familiar<br>
>> with the<br>
>> >> > development process on GitHub (i.e the pull request<br>
>> process) and<br>
>> >> > already have an account on this platform. There are also<br>
>> >> advantages to<br>
>> >> > linking issues and commits with other projects and<br>
>> repositories.<br>
>> >> Since<br>
>> >> > ITK thrives on the open-source development idea, everyone<br>
>> who<br>
>> >> wants to<br>
>> >> > help the project should be able to contribute, and<br>
>> therefore it<br>
>> >> should<br>
>> >> > be as easy as possible to start participating in the<br>
>> community.<br>
>> >> ><br>
>> >> > Recently, GitHub's code review capabilities have greatly<br>
>> improved,<br>
>> >> > which make it more feasible to coordinate contributions<br>
>> for a large<br>
>> >> > project like ITK. And, there are many existing<br>
>> GitHub-integrated<br>
>> >> > services that we can leverage.<br>
>> >> ><br>
>> >> > Thanks to resources from the National Library of Medicine<br>
>> and<br>
>> >> > technological advances, it is now feasible to migrate the<br>
>> project's<br>
>> >> > software process to GitHub. There are many infrastructural<br>
>> >> aspects to<br>
>> >> > the migration, and it would take multiple months to<br>
>> complete. Please<br>
>> >> > let us know your thoughts before we embark on the journey.<br>
>> >> ><br>
>> >> ><br>
>> >> > [1]<br>
>><br>
>> --<br>
>> Cory Quammen<br>
>> Staff R&D Engineer<br>
>> Kitware, Inc.<br>
>><br>
><br>
> ______________________________<wbr>_______<br>
> Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a><br>
><br>
> Kitware offers ITK Training Courses, for more information visit:<br>
> <a href="http://www.kitware.com/products/protraining.php" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>products/protraining.php</a><br>
><br>
> Please keep messages on-topic and check the ITK FAQ at:<br>
> <a href="http://www.itk.org/Wiki/ITK_FAQ" rel="noreferrer" target="_blank">http://www.itk.org/Wiki/ITK_<wbr>FAQ</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://public.kitware.com/mailman/listinfo/insight-users" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/insight-users</a><br>
<br>
<br>
<br>
</div></div><span class="im HOEnZb">--<br>
Unpaid intern in BillsBasement at noware dot com<br>
</span><div class="HOEnZb"><div class="h5">______________________________<wbr>_______<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at<br>
<a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>opensource/opensource.html</a><br>
<br>
Kitware offers ITK Training Courses, for more information visit:<br>
<a href="http://www.kitware.com/products/protraining.php" rel="noreferrer" target="_blank">http://www.kitware.com/<wbr>products/protraining.php</a><br>
<br>
Please keep messages on-topic and check the ITK FAQ at:<br>
<a href="http://www.itk.org/Wiki/ITK_FAQ" rel="noreferrer" target="_blank">http://www.itk.org/Wiki/ITK_<wbr>FAQ</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/insight-users" rel="noreferrer" target="_blank">http://public.kitware.com/<wbr>mailman/listinfo/insight-users</a><br>
</div></div></blockquote></div><br></div>