Switch to an external software repository hosting service
Going forward, hosting NiftyNet on GitHub as the main software repository would be nicer, as this will reduce some of the management and maintenance workload. NiftyNet is already mirrored on GitHub, however it uses the self-hosted GitLab infrastructure for CI/CD.
General tasks for switching from self-hosted GitLab to an external hosting service:
-
CI infrastructure
-
set up server access from outside the host network (e.g. firewall)
- find out KCL policy on this
-
set up server access from outside the host network (e.g. firewall)
- issue tracking
- hooks (e.g. docs)
- workflow
-
NiftyNet model zoo
- option 1: GitHub / GitLab
- option 2: Zenodo (50GB, version control, DOI)
Specific tasks for switching to GitHub:
-
CI infrastructure
- set up a Jenkins server
- set up GitLab.com hook (alternative)
-
issue tracking:
- option 1: deactivate issue tracking on CmicLab, and so force all new issues to be created on GitHub
Specific tasks for switching to GitLab.com:
- hooks (e.g. docs)
Backup plan proposals:
- set up Travis CI for CPU + set up internal nightly builds (i.e. pull code from GitHub and run tests)