Open jcfr opened 3 years ago
The only other example that I would recommend to consider is the Slicer documentation resources repository, which does not use git hashes but identifies files simply by their name (https://github.com/Slicer/Slicer/releases/tag/docs-resources). This does not provide automatic versioning (so you won't be able to store multiple versions of the same filename in a clean way), but makes it easier to upload files (just edit the release and drag-and-drop a file) and download files (filename is included in the URL).
Since we will soon retire the
slicer.kitware.com
server,I suggest to migrate the data and referenced on the wiki into a GitHub release.Once a new location for the data is setup, I can work with our sysadmin to setup relevant redirects.
Timeline:
Links:
A project like this ones could be created:
@lassoan may have other example of project to reference.