[FEATURE] Proactively archive ROR repos #363
Description
Describe the problem you would like to solve
Our POSI v2 self-audit identified proactive software archiving as a potential area for improvement. Software Heritage already archives our repositories, but this happens passively through their crawling process rather than through any intentional action on our part. We could be more deliberate about this, e.g. for repositories like ror-api, trigger archival on each new release.
Describe the solution you'd like
- Use the Software Heritage "Save Code Now" API to programmatically request archival of our repositories upon new releases. For ror-api and possibly other repositories, integrate this into our release workflows (e.g., via a GitHub Action that calls the Save Code Now endpoint when a new release is tagged).
- Audit which of our repositories are currently archived in Software Heritage and at what frequency, and determine whether coverage gaps exist.
- Establish a policy for which repositories should be proactively archived and at what cadence (e.g., on every release, on a schedule, etc.).
Who would benefit from this feature?
Developers, infrastructure sustainability stakeholders, and the broader research community invested in the long-term availability of ROR as open infrastructure.
Additional information
- Software Heritage "Save Code Now" documentation: https://www.softwareheritage.org/how-to-archive-reference-code/ and https://docs.softwareheritage.org/devel/apidoc/swh.web.save_code_now.origin_save.html