Open jhlegarreta opened 1 month ago
The itk-module
GitHub repository tag is a good way for repositories to self-identify. It currently lists 74 repositories.
https://github.com/topics/itk-module
We could dynamically generate a page in our docs.itk.org documentation based on those results.
The itk-module GitHub repository tag is a good way for repositories to self-identify. It currently lists 74 repositories.
Can be one way, but there is probably more work that is needed:
Are all these modules that can be eventually included into ITK proper after being integrated into/having dwelled for some time in the remote modules folder? We should maybe make a distinction here between a proper remote and an itk-friend, e.g.
Some of them are forks from the repository that is the actual one being used (even if they are under the ISC or KitwareMedical organizations) e.g.
Some of them are not under the ISC/KitwareMedical/SimpleITK organization, and thus access to them is not guaranteed.
Some of them are not C++, e.g.
Some of them seem to have been integrated into ITK:
Description
There is currently no updated, self-maintained resource to list exhaustively existing remote modules. The ITK remote group in the Doxygen documentation: https://itk.org/Doxygen/html/group__Group-Remote.html
Does not contain the 60+ remotes that have been identified in: https://github.com/InsightSoftwareConsortium/ITK/issues/4748
So it is difficult to know how many and which are the remote modules that can be used with/available to ITK.
Expected information
Have an updated, self-maintained list of all existing ITK remote modules (regardless of their integration stage into the ITK remotes folder). Their integration or status should also be made clear in that resource: this may be drawn automatically (at least partially) from the
*remote.cmake
file of those files for the ones that are included in the ITKRemote
group.Actual information
No resource is available that lists all existing ITK remotes.
Versions
master
.Additional Information
None.