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

Matt McCormick matt.mccormick at kitware.com
Tue Aug 1 17:59:37 EDT 2017


On Tue, Aug 1, 2017 at 5:45 PM, Sean McBride <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

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

Kitware offers ITK Training Courses, for more information visit:
http://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-developers


More information about the Community mailing list