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

2017-07-31 Thread Bill Lorensen
Yes, at least they all use git... On Mon, Jul 31, 2017 at 8:43 PM, Andras Lasso wrote: > Yes, processes are different. But it helps if at least tools are the same. > > > > Andras > > > > From: Bill Lorensen > Sent: Monday, July 31, 2017 20:33 > To: Andras Lasso > Cc: Matt McCormick; Insight-User

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

2017-07-31 Thread Bill Lorensen
Andras, Each of our systems, VTK, ITK and Slicer use a different process. I am only comfortable with the one that I am currently using. If I change from VTK to Slicer, I need to relearn. Even from VTK to ITK I have to relearn a bit. Until we all use the same process, we will have these issues. An

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

2017-07-31 Thread Bill Lorensen
Here are comments I made 3 years ago on the VTK discussion about changing VTK's code review process. - Berk, I think we need to reach out to potential developers. Especially those outside of Kitware(and their paying customers) and the long term VTK developers outside Kitware. Those co

Re: [ITK-dev] Migration to GitHub

2017-07-31 Thread Sean McBride
On Mon, 31 Jul 2017 17:07:44 -0400, Matt McCormick said: >We are considering migration of ITK's software process to GitHub, and >we would like your feedback. My 2 cents: - I'd be happy to see a move away from gerrit. - I'd prefer a move to a Kitware-hosted GitLab, like VTK did. - GitHub is nic

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

2017-07-31 Thread Bill Lorensen
I agree. I argued against gitlab but lost... +1 for this move. On Mon, Jul 31, 2017 at 7:00 PM, Matt McCormick wrote: > 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

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

2017-07-31 Thread Matt McCormick
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

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

2017-07-31 Thread Bill Lorensen
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" wrote: > 1000 x +1 > > I enthusiastically support this proposal. > > Hans > > > On 7/31/17, 4:57 PM, "Insight-use

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

2017-07-31 Thread Johnson, Hans J
1000 x +1 I enthusiastically support this proposal. Hans On 7/31/17, 4:57 PM, "Insight-users on behalf of Jim Miller" wrote: +1 Jim > On Jul 31, 2017, at 5:07 PM, Matt McCormick wrote: > > Hi folks, > > We are considering migration of ITK's software

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

2017-07-31 Thread Jim Miller
+1 Jim > On Jul 31, 2017, at 5:07 PM, Matt McCormick > 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 ar

[ITK-dev] Migration to GitHub

2017-07-31 Thread Matt McCormick
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