From 638ec52f5b6df1fdfc2d83ba6c7497c77bb4bb96 Mon Sep 17 00:00:00 2001
From: Mohammad Akhlaghi <mohammad@akhlaghi.org>
Date: Fri, 1 May 2020 00:39:39 +0100
Subject: Added interesting references by David

David suggested some interesting references in particular about the
problems with Juypyter notebooks that are now added to the long version of
the paper. We'll later decide if/how they can be used.
---
 tex/src/paper-long.tex | 3 +++
 1 file changed, 3 insertions(+)

(limited to 'tex/src/paper-long.tex')

diff --git a/tex/src/paper-long.tex b/tex/src/paper-long.tex
index a897f3d..6d74e17 100644
--- a/tex/src/paper-long.tex
+++ b/tex/src/paper-long.tex
@@ -2536,6 +2536,9 @@ Furthermore, the fact that a Tale is stored as a binary Docker container causes
   \item \citet{menke20} show how software identifability has seen the best improvement, so there is hope!
   \item Nature's collection on papers about reproducibility: \url{https://www.nature.com/collections/prbfkwmwvz}.
   \item Nice links for applying FAIR principles in research software: \url{https://www.rd-alliance.org/group/software-source-code-ig/wiki/fair4software-reading-materials}
+  \item Jupyter Notebooks and problems with reproducibility: \citet{rule18} and \citet{pimentel19}.
+  \item Reproducibility certification \url{https://www.cascad.tech}.
+  \item \url{https://plato.stanford.edu/entries/scientific-reproducibility}.
   \item
 Modern analysis tools are almost entirely implemented as software packages.
 This has lead many scientists to adopt solutions that software developers use for reproducing software (for example to fix bugs, or avoid security issues).
-- 
cgit v1.2.1

