Integrate some remote modules into ITK proper

[dzenanz]

Some remote modules have been in use for a long time, and should be integrated into the main repository (i.e. https://github.com/InsightSoftwareConsortium/ITK/). Some examples are https://github.com/InsightSoftwareConsortium/ITKSplitComponents/issues/50 and https://github.com/InsightSoftwareConsortium/ITKFastBilateral/issues/2.

I think there are more, and we should review the complete list. Better candidates are the remote modules with just one or two filters.

Then there are some rarely used/unused ones, such as https://github.com/KitwareMedical/MultipleImageIterator. I think we should deprecate that one, and schedule it for removal in ITK6. Are there any more?

[dzenanz]

It would be appreciated if there are any volunteers for helping with this.

[hjmjohnson]

I would also vote for putting effort into the following to get them upto quality levels where they can be included in the toolkit:

AdaptiveDenoising AnisotropicDiffusionLBR GenericLabelInterpolator

MGHIO <--- On the fence about this one.

[dzenanz]

I thought that maintenance of MGHIO was shared with Slicer, and therefore isn't a good candidate for integration?

[hjmjohnson]

Slicer now uses MGHIO directly as an ITK remote module. Maintenance is done as an ITK remote module. I would think that adding it directly to the main repo would simplify the efforts of maintaining the codebase.

[dzenanz]

OK. It also doesn't have a lot of files, so it should be simple from that point of view.

I guess we could/should use a merge style which preserves file history for all the remotes we decide to merge.

[dyollb]

I would offer to help merge ITKLabelErodeDilate into ITK proper (if you agree it is a good candidate). Some instructions would be appreciated.

[dzenanz]

@dyollb maybe wait until we integrate one or two remotes in order to see how to do it.