Archiving process for repos in DataSHIELD github

Following up on a comment by @swheater in the recent steering committee meeting the large amount of old repos on DataSHIELD github. Just throwing it out there as a process. We have archived a few older repos (some are public archive some are private archive). I wonder if the public archived repos haven’t been needed/used for X amount of time we switch them to private archive. The repos will be still accessible to admins should we ever require access but it will reduce and tidy up the appearance of the repository to non admins and visitors and we can streamline the repos we actually are still using and maintaining. We can then go through the remaining repos and if they haven’t been used/maintained for X years then we can switch their status to either public archive (visible to visitors) or pprivatearchive (visible to admins). Thoughts and comments please - especially in deciding time duration before changin puclic/private archive status.

Current GitHub repo analysis on the wiki 'datashield' account GitHub repos | DataSHIELD Community Wiki

Thanks Stuart, we should sit down and decide the status for these. Is there an infrastructure meeting prior to the conference? If we could table an early agenda item to confirm the list that will be archived then we can just go and do it (make them public or private archive). I think public archive retains people that have starred/watching it - but if the repo hasn’t been updated for like years and is no longer in use im not sure who would be actively watching/using it…

These is a “Technical Core Group meeting” this Friday (2024-08-16), we could add it to the agenda, but also having it discussed at meeting after the holidays would be good.

Stuart