Re: [ITK-users] [ITK] [ITK-dev] Migration to GitHub

I would like to see the Kitware sponsored projects (Itk, Vtk, ParaView.. 
) ALL use the same mechanisms and host providers. Just lessens the 
confusion on outside developers.

But +1 for moving to GitHub.
-- 
Michael A. Jackson
BlueQuartz Software, LLC
[e]: mike.jackson-o71+U35G4LUGVr8H/[email protected]


Jon Haitz Legarreta wrote:
> +1 for the transition.
>
> I'm pretty sure the ITK core devs and maintainers have carefully
> considered all choices over time. So beyond my personal likings, I guess
> github beats the rest of the possibilities in terms of the needs and
> future plans of ITK.
>
> JON HAITZ
>
> --
>
>
> On 1 August 2017 at 16:27, Cory Quammen <[email protected]
> <mailto:[email protected]>> wrote:
>
>     I don't have much of an opinion on moving ITK to GitHub, but I'd
>     like to address some things Andras mentioned about GitLab and VTK.
>
>
>         About GitHub/Kitware GitLab:
>
>         I heard that VTK is going to move to GitHub, too. Maybe I
>         misunderstood, but make sure to talk to VTK folks before
>         considering moving to GitLab.
>
>
>     I am not aware of any plans to move VTK to GitLab or even any
>     discussion of doing so.
>
>         Anyway, as a very active user but only occasional contributor of
>         VTK, I find VTK GitLab quite frustrating due to that:
>         1. It is slow. I heard that it's fast when accessed from inside
>         Kitware network, but most community members are outside.
>
>
>     The first few versions were indeed a bit slow, but new updates come
>     out regularly, and the speed is quite snappy. I use it both from
>     within the Kitware network and outside the network and haven't
>     noticed a difference.
>
>         2. I need to re-learn each time I use it: I review code, submit
>         PR or bug report once in every few months - and each time I need
>         to spend 20-30 minutes extra, just to find out how things work.
>
>
>         Andras
>
>         -----Original Message-----
>         From: Community [mailto:[email protected]
>         <mailto:[email protected]>] On Behalf Of Matt McCormick
>         Sent: Monday, July 31, 2017 7:00 PM
>         To: Bill Lorensen <[email protected]
>         <mailto:[email protected]>>
>         Cc: Insight-Users <[email protected]
>         <mailto:[email protected]>>; Hans Johnson
>         <[email protected] <mailto:[email protected]>>;
>         Insight Developers List <insight-developers-61JfyZBJ/[email protected]
>         <mailto:insight-developers-61JfyZBJ/[email protected]>>
>         Subject: Re: [ITK] [ITK-dev] [ITK-users] Migration to GitHub
>
>         I have followed VTK's migration to GitLab, and Kitware has done
>         an excellent job with it. That said, I still think GitHub is the
>         better choice for ITK. Also, the technical and social situation
>         has changed in the time since VTK moved to GitLab.
>
>         I think the key factor is "community", and GitHub has the open
>         source community.
>
>         On Mon, Jul 31, 2017 at 6:42 PM, Bill Lorensen
>         <[email protected] <mailto:[email protected]>> wrote:
>          > Vtk moved to GitLab.  Have you checked with the Kitware folks
>         to see
>          > why they didn't use gitlab?  For me, either github or gitlab
>         is great.
>          >
>          > On Jul 31, 2017 6:03 PM, "Johnson, Hans J"
>         <[email protected] <mailto:[email protected]>> wrote:
>          >>
>          >> 1000 x +1
>          >>
>          >> I enthusiastically support this proposal.
>          >>
>          >> Hans
>          >>
>          >>
>          >> On 7/31/17, 4:57 PM, "Insight-users on behalf of Jim Miller"
>          >> <[email protected]
>         <mailto:[email protected]> on behalf of
>         [email protected] <mailto:[email protected]>> wrote:
>          >>
>          >>     +1
>          >>
>          >>     Jim
>          >>
>          >> > On Jul 31, 2017, at 5:07 PM, Matt McCormick
>          >> <[email protected]
>         <mailto:[email protected]>> wrote:
>          >> >
>          >> > Hi folks,
>          >> >
>          >> > We are considering migration of ITK's software process to
>          >> GitHub, and
>          >> > we would like your feedback.
>          >> >
>          >> > As an open-source, community-driven project, mechanisms to
>          >> communicate
>          >> > and interact with the community are a high priority for ITK.
>          >> > Contributing should be as easy as possible. Increasingly over
>          >> the past
>          >> > many years, GitHub has become the de facto place to interact
>          >> for open
>          >> > source development. It is now a hub for:
>          >> >
>          >> >  Microsoft
>          >> >  Facebook
>          >> >  Google
>          >> >  The Scientific Python Community
>          >> >  The 3D Slicer Community
>          >> >
>          >> > Our InsightSoftwareConsortium GitHub organization [1]
>         already has 67
>          >> > people in it and 74 repositories. There are hundreds of
>          >> projects that
>          >> > depend on ITK on GitHub. Many ITK developers are familiar
>         with the
>          >> > development process on GitHub (i.e the pull request
>         process) and
>          >> > already have an account on this platform. There are also
>          >> advantages to
>          >> > linking issues and commits with other projects and
>         repositories.
>          >> Since
>          >> > ITK thrives on the open-source development idea, everyone who
>          >> wants to
>          >> > help the project should be able to contribute, and
>         therefore it
>          >> should
>          >> > be as easy as possible to start participating in the
>         community.
>          >> >
>          >> > Recently, GitHub's code review capabilities have greatly
>         improved,
>          >> > which make it more feasible to coordinate contributions
>         for a large
>          >> > project like ITK. And, there are many existing
>         GitHub-integrated
>          >> > services that we can leverage.
>          >> >
>          >> > Thanks to resources from the National Library of Medicine and
>          >> > technological advances, it is now feasible to migrate the
>         project's
>          >> > software process to GitHub. There are many infrastructural
>          >> aspects to
>          >> > the migration, and it would take multiple months to
>         complete. Please
>          >> > let us know your thoughts before we embark on the journey.
>          >> >
>          >> >
>          >> > [1]
>
>     --
>     Cory Quammen
>     Staff R&D Engineer
>     Kitware, Inc.
>

_____________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html

Kitware offers ITK Training Courses, for more information visit:
http://www.kitware.com/products/protraining.php

Please keep messages on-topic and check the ITK FAQ at:
http://www.itk.org/Wiki/ITK_FAQ

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/insight-users