They are summarised below, pick the one that fits you best. There are several ways to ensure your code is archived, depending on your preferred workflow, and where it is hosted. Step 2: save your code in Software Heritage It is now an accepted practice to also add markdown versions of the README file, but please keep the AUTHORS and LICENSE files as plain text.

(optionally) add a codemeta.json file containing machine readable metadata (can be produced using the CodeMeta Generator.

a LICENSES directory containing all the licenses used in your project, and an SPDX compliant copyright header in all your source code files (see the REUSE instructions for details and tools).

a LICENSE file at the root of your project, or.

add license information in one of the two recommended ways.

This page provides a concise checklist to do so seamlessly using Software Heritage.

Archiving and referencing properly your source code an important step to support Open Science and to comply with the Know Your Software principle (KYSW).

File archives tool