It could be considered to deposit the repository in an open science archive with FORCE11 compliant citation and guaranteed persistance of digital artefacts (e.g. Figshare, Zenodo, the Open Science Framework (OSF), and the Computational Modeling in the Social and Ecological Sciences Network (CoMSES Net)).
This ensures persistence of materials even if they were deleted from GitHub.
You can easily set-up Zenodo to sync with a GitHub repository. It will "belong" to the user who first uploaded it to Zenodo, but by adding it to a community, you can then have multiple users who "own" it and are able to modify that archived submission.
This would probably be best uploaded by and limited to the core team for the course.
It could be considered to deposit the repository in an open science archive with FORCE11 compliant citation and guaranteed persistance of digital artefacts (e.g. Figshare, Zenodo, the Open Science Framework (OSF), and the Computational Modeling in the Social and Ecological Sciences Network (CoMSES Net)).
This ensures persistence of materials even if they were deleted from GitHub.
You can easily set-up Zenodo to sync with a GitHub repository. It will "belong" to the user who first uploaded it to Zenodo, but by adding it to a community, you can then have multiple users who "own" it and are able to modify that archived submission.
This would probably be best uploaded by and limited to the core team for the course.