Draft guidelines for archiving scientific software artefacts for ASE conference use case

On this google docs: https://docs.google.com/document/d/1P5G1fLvRZNi_oslwk0-jyapgMOAhA1Q3koCkYRwN2xY/edit?usp=sharing

How do we archive software artefacts associated to conference publications?

• Option A: save code now of a an existing repository
• Option B: software deposit with a new deposit client for each conference

Artefact evaluation examples:

• http://evaluate.inf.usi.ch/artifacts
• https://www.artifact-eval.org/

The first conference for which we are addressing the guidelines:

• https://2019.ase-conferences.org/committee/ase-2019-organizing-committee

---

Migrated from T1728 (view on Phabricator)