README.md

Back to Projects List

Transition to GitHub as authoritative version control system

Key Investigators

• Jean-Christophe Fillion-Robin (Kitware, Inc.)
• Andras Lasso (Queen's University)
• Steve Pieper (Isomics, Inc.)

Project Description

Work toward finalizing the conversion from

Slicer SVN repository mirror mirrored on GitHub

to

GitHub only repository

Objective

1. Objective A. Remove all large binary data from current Slicer source version and filter history removing large data from past commits and restore authorship
2. Objective B. Document how developers can upload binary data, and update release process as needed. (based on ITK great documentation)
3. Objective C. Publish updated repository

Approach and Plan

1. See plan documented on the wiki Labs page. See https://www.slicer.org/wiki/Documentation/Labs/TransitionToGit

Progress and Next Steps

1. Describe specific steps you have actually done.
2. ...
3. ...

Illustrations

Background and References

• ITK documentation
  • ITK Data
  • Uploading binary data in ITK
• CMake ExternalData: Using Large Files with Distributed Version Control
• PR #1158: Reduce source tree size downloading test data from 114MB to 74MB (35% decrease)
• Slicer Wiki: Labs
• git_list_largest_file_from_history
  • git_list_largest_file_from_history.sh
  • slicer_git_history_350_largest_files.txt
• 02_Update_Slicer_CLI_buildsystem_to_download_test_data_from_midas.ipynb