Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add link to core infrastructures checklist #240

Merged
merged 1 commit into from
Dec 22, 2020
Merged

Add link to core infrastructures checklist #240

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion best_practices/checklist.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,13 @@ Additional steps depend on the goal of the software (zero or more can apply):
* [I'm expecting users](#im-expecting-users)
* [I'm expecting contributors](#im-expecting-contributors)

A more thorough checklist is the [Core Infrastructures Initiative Badge Best Practices Badge Program](https://bestpractices.coreinfrastructure.org/en/criteria/0). This list is not aimed at research software, and the criteria (for example those focused on security) might go beyond what is necessary. However the aim is **not** to show perfect compliance, but rather to be transparent about the state of the code while providing the necessary guidance on which aspects could be improved.

## I'm publishing a paper

* Add a [CITATION.cff file](documentation.md#software-citation)
* [Make your software citable](../citable_software/making_software_citable.md)
* Cite DOI in paper
* Cite DOI in paper

## I'm expecting users

Expand Down