On Mon, Jul 31, 2017 at 8:07 PM, Nick Cullen wrote:
> As a new user, I think this is a no brainer.
>
Thanks for the feedback, Nick.
>
> Along those lines, I'm not sure if this email-chain users list is the main
> way the community asks questions (maybe I'm missing some
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
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
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
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
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
+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