[ITK-users] [ITK] [ITK-dev] Migration to GitHub
Michael Jackson
mike.jackson at bluequartz.net
Tue Aug 1 10:53:40 EDT 2017
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 at bluequartz.net
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 <cory.quammen at kitware.com
> <mailto:cory.quammen at kitware.com>> 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:community-bounces at itk.org
> <mailto:community-bounces at itk.org>] On Behalf Of Matt McCormick
> Sent: Monday, July 31, 2017 7:00 PM
> To: Bill Lorensen <bill.lorensen at gmail.com
> <mailto:bill.lorensen at gmail.com>>
> Cc: Insight-Users <insight-users at itk.org
> <mailto:insight-users at itk.org>>; Hans Johnson
> <hans-johnson at uiowa.edu <mailto:hans-johnson at uiowa.edu>>;
> Insight Developers List <insight-developers at public.kitware.com
> <mailto:insight-developers at public.kitware.com>>
> 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
> <bill.lorensen at gmail.com <mailto:bill.lorensen at gmail.com>> 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"
> <hans-johnson at uiowa.edu <mailto:hans-johnson at uiowa.edu>> wrote:
> >>
> >> 1000 x +1
> >>
> >> I enthusiastically support this proposal.
> >>
> >> Hans
> >>
> >>
> >> On 7/31/17, 4:57 PM, "Insight-users on behalf of Jim Miller"
> >> <insight-users-bounces at itk.org
> <mailto:insight-users-bounces at itk.org> on behalf of
> millerjv at gmail.com <mailto:millerjv at gmail.com>> wrote:
> >>
> >> +1
> >>
> >> Jim
> >>
> >> > On Jul 31, 2017, at 5:07 PM, Matt McCormick
> >> <matt.mccormick at kitware.com
> <mailto:matt.mccormick at kitware.com>> 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.
>
More information about the Insight-users
mailing list