rseng-archiving

# Archiving research software and data A git forge is a workspace, not an archive: repositories get renamed, deleted, force-pushed and orphaned, and a URL in a paper has a half-life. Archiving puts an immutable, independently hosted, persistently identified copy of the work somewhere designed to outlive projects, labs and platforms. It is cheap (minutes per release), and it is what makes "the code is available" true in ten years. Distinct roles: rseng-publishing-releasing covers making releases; this skill covers making them permanent. ## The two-pillar default For any research software worth citing, do both - they solve different problems: - Software Heritage archives the SOURCE HISTORY: submit a save request for the repository (web form or API - no account needed) and the full history is preserved in the universal archive. Every commit, directory and file gets an intrinsic SWHID (persistent, content-derived, verifiable) that resolves at archive.softwareheritage.org regardless of what happens to the forge. Re-save at releases; heavily referenced repos are also crawled automatically, but an explicit save is a guarantee. - Zenodo archives the RELEASE ARTIFACT with a citable DOI: deposit the release tarball (the forge integration can do this automatically per release), get a version DOI plus a concept DOI covering all versions, and wire the DOI back into CITATION.cff and the README (rseng-citation-metadata). Zenodo is CERN-backed and free for researc...