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

Yaniv, Ziv Rafael (NIH/NLM/LHC) [C] zivrafael.yaniv at nih.gov
Wed Aug 2 11:47:03 EDT 2017


My vote is for GitHub for the same reasons Dženan gave, familiarity and that is where most open source developers interact.

Supporting this with some facts from the git 2016 survey (https://survs.com/report/nz2odu1spl):

Which git hosting site(s) do you use for your project(s)?
GitHub, 84%, 7636
Bitbucket , 42%, 3840
GitLab, 32%, 2917

      my 2 cents
             Ziv






From: Dženan Zukić <dzenanz at gmail.com>
Date: Wednesday, August 2, 2017 at 11:20 AM
Cc: "community at itk.org" <community at itk.org>
Subject: Re: [ITK] [ITK-users] [ITK-dev] Migration to GitHub

More projects in general use GitHub, and more people are familiar with it, myself included. Familiarity alone is enough for my vote!

On Wed, Aug 2, 2017 at 5:39 AM, Timothee Evain <tevain at telecom-paristech.fr<mailto:tevain at telecom-paristech.fr>> wrote:
Hello everyone,

My 2 cents on this brainstorming, if that could help:
Is there any estimation on how well the VTK and ITK communities overlap? I mean, as a mostly ITK user, I came naturally to VTK for all the visualization and 3D modelling tasks given the similarities between both libraries, so even if I can mostly contribute to ITK, there is still chances that I could help on VTK. It may be a biais since I'm working on 3D volumes and not 2D images that can be easily displayed elsewhere, but as far as I'm concerned, I would favor a united framework for ITK, VTK, 3D Slicer, etc. So if the communities are more or less the same people, I would advocate for GitLab (plus, that's open sourced). Since you could authentify people from GitHub credentials, that don't seems a big side-lining.

However, if there is a clear distinction between communities, I think that going for GitHub is the best choice to get access to more people, that are used to GitHub facilities. That would increase chances of involving people into the project.
(Note that I'm not well aware of the implications of using a close-source forge.)

HTH,

Tim

----- Mail original -----
De: "Matt McCormick" <matt.mccormick at kitware.com<mailto:matt.mccormick at kitware.com>>
À: "Sean McBride" <sean at rogue-research.com<mailto:sean at rogue-research.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>>
Envoyé: Mardi 1 Août 2017 23:59:37
Objet: Re: [ITK] [ITK-users]  [ITK-dev] Migration to GitHub

On Tue, Aug 1, 2017 at 5:45 PM, Sean McBride <sean at rogue-research.com<mailto:sean at rogue-research.com>> wrote:
> On Tue, 1 Aug 2017 11:40:25 -0400, Francois Budin said:
>
>>As Matt mentioned, the main reason is because a lot of ITK users already
>>have Github accounts and are familiar with that environment. The idea is
>>really to make is as simple as possible for the community to contribute.
>>Using Gitlab would still require users to have an account on GitLab to push
>>patches. Most ITK users already have a Github account with their own
>>projects, and contributing to ITK just requires cloning the project and
>>creating a pull-request.
>
> The fact that many people are familiar with github and its workflow is indeed a good argument.
>
> But the "using Gitlab would still require users to have an account on GitLab" I think is no argument at all.  Creating a GitLab account is a fast and easy one-time task, the browser can then remember your password, etc.  Everyone is used to having a zillion accounts for all the zillion services we all use.

Yes, this is true.

We already have OAuth sign-in for Gerrit that uses GitHub credentials.
But, the benefits come more from a familiarity with the user interface
and deeper integrations like notifications, user and issue references,
etc.
_____________________________________
Powered by www.kitware.com<http://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
_______________________________________________
Community mailing list
Community at itk.org<mailto:Community at itk.org>
http://public.kitware.com/mailman/listinfo/community
_______________________________________________
Community mailing list
Community at itk.org<mailto:Community at itk.org>
http://public.kitware.com/mailman/listinfo/community

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/community/attachments/20170802/253d9d2a/attachment.html>


More information about the Community mailing list