diff --git a/001/Makefile b/001/Makefile
new file mode 100644
index 0000000..9e677fc
--- /dev/null
+++ b/001/Makefile
@@ -0,0 +1,13 @@
+TEX := pdflatex -halt-on-error
+
+TEXDEPS := $(wildcard *.tex) $(wildcard *.bib)
+FIGDEPS := $(wildcard ../figs/*)
+
+all: manuscript.pdf
+
+manuscript.pdf: manuscript.tex Makefile $(TEXDEPS) $(FIGDEPS)
+ $(TEX) $< && bibtex manuscript && $(TEX) $< && $(TEX) $<
+
+clean:
+ rm -f *.aux *.log *.out *.bbl *.blg *.soc *.loc *.glo *.ist *.xwm *.fdb_latexmk *.fls *.synctex.gz *.nlo
+ rm -f manuscript.pdf
diff --git a/001/de-RSE-logo.pdf b/001/de-RSE-logo.pdf
new file mode 100644
index 0000000..9d4b7da
Binary files /dev/null and b/001/de-RSE-logo.pdf differ
diff --git a/001/de-rse.cls b/001/de-rse.cls
new file mode 100644
index 0000000..311852c
--- /dev/null
+++ b/001/de-rse.cls
@@ -0,0 +1,438 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% de-rse.cls, v1.0, 2012/03/26
+% Developed by Stephan Druskat, based on
+% oup-contemporary.cls v1.1
+% Developed by Overleaf
+%
+% This class file enables authors to prepare
+% manuscripts for submission to OUP journals using the
+% 'contemporary' layout.
+%
+% V1.0 Supported journals:
+% - de-RSE
+%
+% V1.1
+% - Moved logos to top level (EM requirements)
+% - Handles missing/empty logo files
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%
+\ProvidesClass{de-rse}[2020/03/26, v1.0]
+
+\newif\if@numrefs
+\newif\if@alpharefs
+
+%% Options for bibliography style
+\DeclareOption{num-refs}{
+ \@numrefstrue
+ \@alpharefsfalse
+}
+\DeclareOption{alpha-refs}{
+ \@numrefsfalse
+ \@alpharefstrue
+}
+
+\DeclareOption*{\PassOptionsToClass{\CurrentOption}{article}}
+
+\ExecuteOptions{num-refs}
+\ProcessOptions\relax
+\LoadClass[twoside,twocolumn]{article}
+
+\RequirePackage[utf8]{inputenc}
+\RequirePackage[T1]{fontenc}
+\RequirePackage{ifpdf}
+\RequirePackage{microtype}
+\RequirePackage{euler}
+\RequirePackage{merriweather}
+\renewcommand{\ttdefault}{lmtt}
+\RequirePackage[italic]{mathastext}
+\RequirePackage{relsize}
+\RequirePackage{ragged2e}
+\RequirePackage{xcolor}
+\RequirePackage{colortbl}
+\RequirePackage{graphicx}
+\RequirePackage{etoolbox,xpatch}
+\RequirePackage{environ}
+\RequirePackage{lastpage}
+\RequirePackage{rotating}
+\RequirePackage{lscape}
+\RequirePackage{afterpage}
+\RequirePackage[absolute]{textpos}
+\RequirePackage{url}
+\RequirePackage{newfloat}
+\RequirePackage{mdframed}
+\RequirePackage{titlesec}
+
+\RequirePackage{siunitx}
+
+\RequirePackage{scrextend}
+\changefontsizes[10.5pt]{7.5pt}
+
+\RequirePackage{calc}
+\RequirePackage{geometry}
+\geometry{includefoot,
+ hmargin=4pc+6.64pt,
+ bottom=2pc+10pt,
+ top=5pc+6pt,
+ headsep=2pc,
+ headheight=17.5pt,
+ footnotesep=1pc+6pt,
+ columnsep=18pt}
+\setlength{\parindent}{12pt}
+
+\RequirePackage[colorlinks,allcolors=black,urlcolor=blue]{hyperref}
+
+\RequirePackage[noblocks]{authblk}
+
+\def\@jname{de-RSE Position Paper}
+\def\@jlogo{example-grid-100x100pt.png}
+
+\newcommand{\jname}[1]{\def\@jname{#1}}
+\newcommand{\jlogo}[1]{\def\@jlogo{#1}}
+
+\def\@jyear{20xx}
+\def\@jvolume{0}
+\def\@papernumber{0}
+\def\@jstartpage{1}
+\def\@reviewfrom{1}
+\def\@reviewto{1}
+\def\@acceptedon{1}
+\def\@publicationurl{1}
+\def\@publicationpidtype{1}
+\def\@publicationpid{1}
+
+\newcommand{\reviewfrom}[1]{\def\@reviewfrom{#1}}
+\newcommand{\reviewto}[1]{\def\@reviewto{#1}}
+\newcommand{\acceptedon}[1]{\def\@acceptedon{#1}}
+\newcommand{\publicationurl}[1]{\def\@publicationurl{#1}}
+\newcommand{\publicationpidtype}[1]{\def\@publicationpidtype{#1}}
+\newcommand{\publicationpid}[1]{\def\@publicationpid{#1}}
+\newcommand{\jyear}[1]{\def\@jyear{#1}}
+\newcommand{\jvolume}[1]{\def\@jvolume{#1}}
+\newcommand{\papernumber}[1]{\def\@papernumber{#1}}
+\newcommand{\jstartpage}[1]{\def\@jstartpage{#1}}
+\newcommand{\leadingzero}[1]{\ifnum #1<10 0\the#1\else\the#1\fi}
+\newcommand{\monthword}[1]{\ifcase#1\or January\or February\or March\or April\or
+ May\or June\or July\or August\or
+ September\or October\or November\or December\fi}
+
+\def\@papercat{Position Paper}
+\def\@runningauthor{}
+\def\@runningtitle{}
+\def\@corraddress{}
+\def\@authnotes{}
+\colorlet{jcolour}{blue!40}
+
+\newcommand{\runningauthor}[1]{\def\@runningauthor{#1}}
+\newcommand{\runningtitle}[1]{\def\@runningtitle{#1}}
+\newcommand{\corraddress}[1]{\def\@corraddress{#1}}
+\newcommand{\authnote}[1]{\appto{\@authnotes}{#1\par}}
+\newcommand{\papercat}[1]{\def\@papercat{#1}}
+
+\jname{de-RSE Position Paper}%
+\jlogo{de-RSE-logo.pdf}%
+\definecolor{jcolour}{RGB}{137,42,105}%
+
+\RequirePackage[flushmargin,bottom,norule]{footmisc}
+\appto{\footnotelayout}{\fontsize{6.5pt}{9.5pt}\selectfont}
+\deffootnote{1.5em}{1.5em}{\thefootnotemark\enspace}
+
+\RequirePackage{fancyhdr}
+\fancyhf{}
+\renewcommand{\headrule}{\color{black!15}\rule{\textwidth}{2pt}}
+\fancyhead[LE]{%
+ \hspace*{12pt}%
+ \fontsize{7.8pt}{10pt}\selectfont%
+ \color{jcolour}%
+ \textbf{\thepage}%
+ \hspace{1em}\raisebox{-0.5pt}{|}\hspace{1em}%
+ \textit{\@jname} \#\num[minimum-integer-digits = 3]{\@papernumber} (\the\year)
+}
+\fancyhead[RO]{%
+ \fontsize{7.8pt}{10pt}\selectfont%
+ \color{jcolour}%
+ \@runningauthor%
+ \hspace{1em}\raisebox{-0.5pt}{|}\hspace{1em}%
+ \textbf{\thepage}%
+ \hspace*{12pt}%
+}
+
+\fancypagestyle{plain}{%
+ \fancyhf{}
+ \renewcommand{\headrule}{}
+ \fancyfoot[R]{%
+ \fontsize{7.8pt}{10pt}\selectfont%
+ \color{jcolour}%
+ \textbf{\thepage}\hspace*{12pt}%
+ }
+}
+
+
+\pagestyle{fancy}
+
+
+\AtBeginDocument{%
+ \newsavebox{\@gscitedetails}
+ \newlength{\@gscitedetailsheight}
+ \newsavebox{\@gsheadbox}
+ \newlength{\@gsheadboxheight}
+ \savebox{\@gscitedetails}{%
+ \parbox{\textwidth-21pc+4pc+6.64pt}{%
+% \normalfont{\itshape\bfseries\@jname}, \@jyear, \@jstartpage--\pageref{LastPage}\par
+% \vspace{\dimexpr 8pt-1em\relax}
+ {\color{black!15}\rule{\linewidth}{2pt}}\par%
+ \vspace{\dimexpr 8pt-1em\relax}%
+ \fontsize{6.5pt}{9.5pt}\bfseries%
+ \textcolor{jcolour}{doi: xx.xxxx/xxxx}\par
+ Manuscript in Preparation\par
+ \@papercat\par
+ \vspace{\dimexpr 8pt-1em\relax}%
+ {\color{black!15}\rule{\linewidth}{2pt}}\par
+ }}%
+ \settototalheight{\@gscitedetailsheight}{\usebox{\@gscitedetails}}%
+ %%%%
+ %\savebox{\@gsheadbox}{%
+ % \parbox{\textwidth-21pc+4pc+6.64pt}{%
+ % \normalfont%
+ % \fontsize{8pt}{9.5pt}\selectfont%
+ % {\itshape\bfseries\@jname}, \@jyear, \@jstartpage--\pageref{LastPage}\par
+ % \vspace{\dimexpr 8pt-1.5pt\relax}%
+ % \usebox{\@gscitedetails}
+ % }%
+ %}%
+ \settototalheight{\@gsheadboxheight}{\usebox{\@gsheadbox}}%
+}
+
+\RequirePackage{alphalph}
+\newalphalph{\fnsymbolmult}[mult]{\@fnsymbol}{5}
+
+\newcounter{authorfn}
+\setcounter{authorfn}{1}
+\newcommand{\authfn}[1]{%
+ \fnsymbolmult{#1}%
+}
+
+\renewcommand\Authands{ and }
+\renewcommand\AB@affilsepx{ and }
+\renewcommand{\Authfont}{\fontsize{8pt}{11pt}\selectfont}
+\renewcommand{\Affilfont}{\fontsize{6pt}{9pt}\selectfont}
+\setlength{\affilsep}{21pt-9pt}
+
+\AtBeginDocument{
+\renewcommand{\@maketitle}{%
+ \textblockorigin{4pc+6.64pt}{4pc+6pt}
+ %%%%
+ \begin{textblock*}{21pc}(0pt,0pt)
+ %\IfFileExists{\@ouplogo}{%
+ % \includegraphics[height=\@gsheadboxheight]{\@ouplogo}%
+ %}{%
+ % \fbox{\begin{minipage}[b][\@gsheadboxheight]{\@gsheadboxheight}
+ % \raggedright
+ % Placeholder for OUP logo \@ouplogo
+ % \end{minipage}}%
+ %}
+ %\hspace{12pt}%
+ %% Do absolutely nothing if \@jlogo is empty string
+ \ifdefempty{\@jlogo}{}{%
+ \IfFileExists{\@jlogo}{%
+ \includegraphics[height=\@gscitedetailsheight]{\@jlogo}
+ }{%
+ \fbox{\begin{minipage}[b][\@gsheadboxheight]{\@gsheadboxheight}%
+ \raggedright Placeholder for journal logo \@jlogo
+ \end{minipage}}%
+ }}
+ \end{textblock*}
+ %%%
+ \begin{textblock*}{\textwidth-21pc}(21pc,0pt)
+ \usebox{\@gsheadbox}
+ \end{textblock*}%
+ %%%
+ \null\vspace*{\dimexpr 10.5pc+11pt-5pc-6pt\relax}%
+ \raggedright%
+ {\fontsize{14pt}{16pt}\selectfont%
+ \ifpdf
+ \textls[200]{\relsize{-1}\MakeUppercase{\@papercat} \#\num[minimum-integer-digits = 3]{\@papernumber} (\leadingzero{\day} \monthword{\the\month)} \the\year)}
+ \else %%% don't use letterspace in latex+dvi
+ \relsize{-1}\MakeUppercase{\@papercat}%
+ \fi%
+ \par}
+ \vspace{\dimexpr 26pt-18pt\relax}
+ {\fontsize{14pt}{20pt}\bfseries\color{jcolour}\@title\par}
+ \vspace{\dimexpr 26pt-13pt\relax}
+ \@author\par
+ \vspace{\dimexpr 15.5pt-1em}
+ {%
+ \renewcommand{\authfn}[1]{%
+ \textsuperscript{\fnsymbolmult{##1}}%
+ }
+ {\fontsize{6.5pt}{9.5pt}\selectfont\@authnotes\par}%
+ }
+ \vspace{\dimexpr 16pt-3pt-1em\relax}
+}
+}
+
+\RequirePackage[style]{abstract}
+\setlength{\absleftindent}{0pt}
+\setlength{\absrightindent}{0pt}
+\setlength{\absparindent}{12pt}
+\setlength{\absparsep}{0pt}
+\setlength{\abstitleskip}{16pt-8pt-\baselineskip}
+\renewcommand{\abstractnamefont}{\fontsize{10pt}{12pt}\bfseries\color{jcolour}}
+\renewcommand{\abstitlestyle}[1]{{\abstractnamefont #1}}
+\renewcommand{\abstracttextfont}{\fontsize{8pt}{11pt}\selectfont}
+\preto{\abstract}{%
+ {\noindent\color{jcolour!40}\rule{\hsize+4pc+6.64pt}{3pt}}\par
+ \vspace*{\dimexpr 23pt-10pt\relax}
+}
+\appto\abstract{\noindent\raggedright\ignorespaces}
+\preto\endabstract{\par}
+
+\newenvironment{keywords}
+{\vspace*{\dimexpr 19pt-8pt-\baselineskip\relax}%
+\noindent\fontsize{8pt}{11pt}\selectfont\textbf{Key words}: \ignorespaces}%
+{\par}
+
+\DeclareFloatingEnvironment[placement=t!,name=kpt]{keypoints}
+
+\xapptocmd{\keypoints}{%
+ \begin{mdframed}[linewidth=1pt,linecolor=black,
+ innerleftmargin=8pt,innerrightmargin=8pt,
+ innertopmargin=16pt-8.2pt,innerbottommargin=6pt]
+ {\fontsize{8.2pt}{10pt}\bfseries Key Points\par}
+}{}{}
+\xpretocmd{\endkeypoints}{\end{mdframed}}{}{}
+
+\xapptocmd{\keypoints*}{%
+ \begin{mdframed}[linewidth=1pt,linecolor=black,
+ innerleftmargin=8pt,innerrightmargin=8pt,
+ innertopmargin=16pt-8.2pt,innerbottommargin=6pt]
+ {\fontsize{8.2pt}{10pt}\bfseries Key Points\par}
+}{}{}
+\xpretocmd{\endkeypoints*}{\end{mdframed}}{}{}
+
+
+\if@twocolumn
+ \NewEnviron{frontmatter}
+ {\twocolumn[%
+ \BODY%
+ \vspace*{\dimexpr 16pt-3pt-1em\relax}
+ {\noindent\color{jcolour!40}\rule{\hsize+4pc+6.64pt}{3pt}}\par
+ \vspace*{\dimexpr 23pt-1em\relax}]%
+ \begin{figure*}[b!]
+ \fontsize{6.5pt}{9.5pt}\selectfont%
+ \hrule%
+ \vspace{\dimexpr 14pt-6.5pt\relax}%
+ Public reviews for this \textit{de-RSE Position Paper} were conducted between \@reviewfrom~and \@reviewto.\par
+ The paper has been accepted as an official position of \textit{de-RSE e.V. -- Society for Research Software} on \@acceptedon.\par
+ The paper is publicly available under the persistent identifier \href{\@publicationurl}{\@publicationpidtype:\@publicationpid}.
+ \end{figure*}
+ }
+\else
+ \NewEnviron{frontmatter}{%
+ \BODY%
+ \vspace*{\dimexpr 16pt-3pt-1em\relax}
+ {\noindent\color{jcolour!40}\rule{\hsize+4pc+6.64pt}{3pt}}\par
+ \vspace*{\dimexpr 23pt-1em\relax}%
+ \begin{figure*}[b!]
+ \fontsize{6.5pt}{9.5pt}\selectfont%
+ \hrule%
+ \vspace{\dimexpr 14pt-6.5pt\relax}%
+ \textbf{Compiled on:} \today.\par
+ Draft manuscript prepared by the author.\par
+ \end{figure*}
+ }
+\fi
+
+\setcounter{secnumdepth}{0}
+\titleformat*{\section}{\fontsize{10pt}{12pt}\bfseries\color{jcolour}}
+\titlespacing*{\section}{0pt}{26.5pt-1em}{16pt-1em}
+\titleformat*{\subsection}{\fontsize{8.5pt}{11pt}\bfseries\color{jcolour}}
+\titlespacing*{\subsection}{0pt}{2pc-1em}{17pt-1em}
+\titleformat*{\subsubsection}{\normalsize\bfseries\slshape}
+\titlespacing*{\subsubsection}{0pt}{\baselineskip}{0pt}
+\titleformat{\paragraph}[runin]{\normalsize\itshape}{\theparagraph}{0pt}{}[.\enspace]
+\titlespacing*{\paragraph}{0pt}{\baselineskip}{0pt}
+ \titleformat{\subparagraph}[runin]{\relsize{-1}\uppercase}{\thesubparagraph}{0pt}{}[.\enspace]
+\titlespacing*{\subparagraph}{0pt}{\baselineskip}{0pt}
+
+\RequirePackage{enumitem}
+\setlist{noitemsep}
+\setlist[itemize]{leftmargin=12pt,topsep=16pt-1em}
+\setlist[enumerate]
+{itemindent=14pt,topsep=16.8pt-1em,
+ label={\roman*.},labelsep=7pt,
+ labelwidth=*,leftmargin=*,align=right}
+
+
+% quotes and epigraphs
+\RequirePackage{quoting}
+\newcommand{\quotefont}{\fontsize{6.5pt}{9.5pt}\selectfont}
+\quotingsetup{vskip=16pt-1em,indentfirst=false,font={quotefont},leftmargin=12pt,rightmargin=12pt}
+
+\renewenvironment{quote}{\begin{quoting}}{\end{quoting}}
+
+\renewenvironment{quotation}{\begin{quoting}}{\end{quoting}}
+
+\newenvironment{epigraph}[1]
+{\begin{quoting}[font={itshape,fontsize{7.5pt}{10.5pt}},vskip=15pt-1em,leftmargin=0pt,rightmargin=0pt]%
+ \def\@quotesource{#1}}
+{\par\vspace{\dimexpr 15pt-1em\relax}{\upshape---\@quotesource}\end{quoting}}
+
+% Space above/below equations
+\g@addto@macro\normalsize{%
+ \setlength\abovedisplayskip{\baselineskip}%
+ \setlength\belowdisplayskip{\baselineskip}%
+ \setlength\abovedisplayshortskip{\baselineskip}%
+ \setlength\belowdisplayshortskip{\baselineskip}%
+}
+
+\RequirePackage{stfloats}
+\RequirePackage{booktabs}
+\RequirePackage{tabularx}
+% Left-, right- and center-aligned auto-wrapping column types
+\newcolumntype{L}{>{\raggedright\arraybackslash}X}
+\newcolumntype{R}{>{\raggedleft\arraybackslash}X}
+\newcolumntype{C}{>{\centering\arraybackslash}X}
+
+\AtBeginEnvironment{tabularx}{%
+ \fontsize{7pt}{10pt}\selectfont
+}
+\AtBeginEnvironment{tabular}{%
+ \fontsize{7pt}{10pt}\selectfont
+}
+
+\setlength{\aboverulesep}{11pt-1em}
+\setlength{\belowrulesep}{11pt-1em}
+\setlength{\heavyrulewidth}{0.5pt}
+\setlength{\lightrulewidth}{0.5pt}
+\arrayrulecolor{jcolour}
+
+
+\newcommand{\tnote}[1]{\textsuperscript{\textit{#1}}}
+\newlist{tablenotes}{itemize}{1}
+\setlist[tablenotes]{label={},labelsep=0pt,leftmargin=0pt,topsep={\dimexpr 12pt-1em\relax}}
+\appto{\tablenotes}{\fontsize{6pt}{9pt}\selectfont}
+
+\RequirePackage[tableposition=top]{caption}
+\DeclareCaptionFont{figcaptionfont}{\fontsize{6pt}{9pt}\selectfont}
+\DeclareCaptionFont{tabcaptionfont}{\fontsize{7pt}{9pt}\selectfont}
+\captionsetup{justification=justified,singlelinecheck=false,labelfont={bf},labelsep=period}
+\captionsetup*[figure]{font=figcaptionfont,skip=10pt}
+\captionsetup*[table]{font=tabcaptionfont,skip=10pt-1em}
+
+% Skips for floats
+\setlength{\floatsep}{1pc+6pt}
+\setlength{\intextsep}{1pc+6pt}
+\setlength{\textfloatsep}{1pc+6pt}
+
+% References
+\if@numrefs
+ \RequirePackage[numbers]{natbib}
+ \bibliographystyle{vancouver-authoryear}
+\fi
+\if@alpharefs
+ \RequirePackage{natbib}
+ \bibliographystyle{dcu}
+\fi
+\setlength{\bibhang}{11pt}
+\setlength{\bibsep}{0pt}
+\renewcommand{\bibnumfmt}[1]{#1.}
diff --git a/001/figures/decision_trees_vers_02.pdf b/001/figures/decision_trees_vers_02.pdf
new file mode 100644
index 0000000..de612cc
Binary files /dev/null and b/001/figures/decision_trees_vers_02.pdf differ
diff --git a/001/figures/drawio/README.md b/001/figures/drawio/README.md
new file mode 100644
index 0000000..ee9dcff
--- /dev/null
+++ b/001/figures/drawio/README.md
@@ -0,0 +1 @@
+These files are here only for convenience. The primary source is already embedded in the respective pdf files one directory level up.
diff --git a/001/figures/drawio/tree_IP_policy.drawio b/001/figures/drawio/tree_IP_policy.drawio
new file mode 100644
index 0000000..8092ec1
--- /dev/null
+++ b/001/figures/drawio/tree_IP_policy.drawio
@@ -0,0 +1 @@
+7Vvbcps6FP0az7QPyQAy2H50HDtNm7Rpk540Tx0ZFFCDERXyrV9/JBDmYmzjlBiaOJnxoK0tgbTWlpYkaIHBZHFBoe9cEwu5LU2xFi1w3tK0Xlflv8KwjAyGJg02xVZkShlu8R8kjYq0TrGFgowjI8Rl2M8aTeJ5yGQZG6SUzLNuj8TN3tWHtryjkhhuTeiiNbd7bDEnsna1TmL/gLDtxHdWjV6UM4Gxs6w4cKBF5ikTGLbAgBLCoqvJYoBc0Xdxv9xfLu/dqyfj4uPX4Df8fvbp7vN/J1Flo32KrJpAkceeXfXP3vVieB98VGbqT+3b1RcHBPaJLpvGlnF/IYt3n0wSyhxiEw+6w8R6RsnUs5CoVeGpxOeKEJ8bVW78hRhbSi7AKSPc5LCJK3PRArMfovipLlMPqZzzhaw5TCzjhMfoMlVIJB/SeUmxMBWXe8SuOyAuoWHrgKWjrtXm9oBR8oRSOYrS6ynKKifmCkf5rGT3S5gCMqUm2tLnkk4MUhuxLX6yPgFIisoS3AtEJog3lDtQ5EKGZ1m+Qxk29sovoQa/kOzYgymqdqRKY6miNYoqoFaqqCmiJLTZjyrqDqqsUWIwUJSDUqI6qMOifUrhMuXgE+yxIFXzjTBwBykLOvH0voynzdzks8Mf6Nv929pWf34RPfGG0mrvVM+WB0q2B6KQkuVyfF/14vNDQN5tBt2pRKClGS7H/8zCM35ps5AZkemRhA+fhIvxe0rijJMgJHyfO6iGv0gy41ouAzFCOIgi0TxBNeJiM6KADamFPZtfX3qMPzYXWFMoHv6GEh9Rxps4ip+CtzN6kOzDcXPBI1feir1r0YpqeWcSf0mFmnu/o1ljWtDQMu3PDWzJsCXGjLmDGbr1YRjBc66ns0NUboZ51MV/0XAyGp3pHUW2OmWP/vYeVGYcarTYOlzIXJCLu65MzhPprCnS5qRks5ELr8rmkpX4rkd2VDCX7JId6zPGZsFR8VwSr8d2KlGjUfoirvjAnHjF+OrNwrfepcYx5kO/dqM4AeqdB047L7/+rHFRUflWQ1ldrnUOq8tjQbRBlx9MvRbW8g1xoLHJMPG4j/h5rjKvtx0WmiGX+JOQm6Oj4t6quFcSO15JF0huVSuQ3PpLSW5Qj7xaDbXaqx5qK9+qa8BQ2x//uT2ZPfns7tOv79eXwyGw7+KG/rubgHuTaOe+cA706lm1W9V1DyTiCikBjpRoICU6ta71joLs5dvhT8cuNmHYjqMg2yHI2u3GCbJ69Vh5OVbxCFb29LPyI7G/Oyhvbx/SoigKRxTsPVJ4UvqkhcfI1GRTcdBTY2AKoTwa1RCYnWxcrtKpuDQOeTQR75ruBrokvj4ivou2Ds9vCG5VbxreRsV4m8R6o6GsgaZh2ymD7Tu+VEaUz6LvywfpWiUUzTCai26lxERB8DYZoDcuurtrDOCaGXkBeu1QGE0LRgDKBOPnLyUjh3cDy2KS7XuPeCgHlDRBF9t8xXTOacDjnhtEp/KFlNuXGRNsWaHcLiJBVoK/FHptJYceWEevXYCe9mLoldK/R/SiYTD3vk2vbvA2a9q/ezPrYXi7cZfhTSGu5eK1aHvhsJBvlrVHyKuZYBsHee8I+WFnZdU4HOSFRy+bJ+WyiINCxFtDrdVTW33lX8R9Dc+yVCi7R1UQ6KAA9fzL6ZWhXjSb5/CIO/EKjpF7QwIcnRKcjwljZFLQy4zkVjiBA31R2WRhiy8IT8cwwOYpL/O0aZmjFHxuk3vfrXpoQG/DeXgKHL2aZQ5PJp8FRufpybeVYPg/
\ No newline at end of file
diff --git a/001/figures/drawio/tree_licensing.drawio b/001/figures/drawio/tree_licensing.drawio
new file mode 100644
index 0000000..6f4e885
--- /dev/null
+++ b/001/figures/drawio/tree_licensing.drawio
@@ -0,0 +1 @@
+7V1bc5s4FP41nmkfkuFu85g4di+b9JbdTbMvHWwUmxaQC3Ji99evxB0hbEwkQ9y6M6k5KBLofOeqI2Wgjr3Nm8BaLW+gDdyBItmbgXo1UBRNkfFPQtjGBFXTY8IicOyYJOeEW+cXSIhSQl07NghLDRGELnJWZeIc+j6YoxLNCgL4VG72AN3yqCtrkYwo5YTbueWCSrM7x0bLmDpShjn9LXAWy3Rk2TDjO56VNk46DpeWDZ8KJHUyUMcBhCj+5m3GwCVzl87L3bvtnXv9w3jz/nP40/rn8q+/P/x7Fnc2PeRXslcIgI9ad/3NvNlM7sL30qP8Tfly/XGphoszWUneDW3TCQM2nr/kEgZoCRfQt9xJTr0M4Nq3AelWwld5m2sIV5goY+J3gNA2AYO1RhCTlshzk7tg46Cvhe/3pKtzPbm62iQ9Rxfb5OLBcd0xdGEQPaVq62Bka5geogD+AIU7kmSakpTdSZmukA59FGy/5oORy/t0MHKRDx1dpWM3nP+ETyFcB3OwY9ITPCErWAC0o52mxg0JRwpgTtj7BkAP4KfEDQLgWsh5LCPeSgRnkbXLfvUTdPCLKFIi48YoeaJtKrpSuYv4SZPfyiGGvxQeIydFwDsAhFqnIJQOAGEFbOOxJJ0G2Az9OGBTDQpsxnHBloz2aLnr5BUGiuEiomFg9Jw5Co2fa5jeOAsjHF3gBrKx2uQ38bcF+f8KkneCa/zzyYo6QoRiOxgZzmyNQM4sYuxs3Nk0HRm/SDx43FVFGnKsE+A+LR0EbldWxPYnbLTLuKYU5YNO/rGwO51e6kMpeb8CPf4cjMRHECCw2QmdGgiYyeVTbp+VVAUtC7ZZl+rBVoLJoZhQO9U/mc65L9xh65+OdIPEWzU8j1tarQjbzmMuRAdKtcKS6g8fa2U0I5cGpXCEJQKV2V4WQx/6gJLZhGS5zsLHl3PMaoDpl0S+HOzXXiQ3PMe2IySy9EEZncIEWdkryBpDjhVhcmw+X7kzYXA/uW2qq0+b47pu9orjhvFSVHdbd7Bits3ow3Q5OZuHNP7YH6gMe2Ug0ufm7uNdg4VFRoczLJH4RaAf7vLieAyZ9jILGJbnd3IadYUIDjNyKCifjHYUv3EoVWa9/9pHeTHqZ9hQ/Rgab/XDDl11Km5RTQpY8SuJy5MMBem1W0CC0sFEGZjy4AK/1Jhc8tFfSady3Knl24WuhWpMPs+t7HnWpuSTV84lyVDUhqpZE6aatS5U80HJaKYazzT3MeJ/I12QKWhY9U59++vTzYN3906+MSz03/IMnqncMwBsDZuZ6gRHmtpMw1azjBQg1YYp7YsgsLaFZivSIBShzNO5567MpwEANvTSBOR8CWFI1Lvr4MCSfBOvoabTiTEe90pDKbTtZjmPCkND0elpfqGrmDTWEWwinmnD8ggE/Fm4ihpIMGAQX5idrzx+1BsP68/OFfab2Vx6+fjlWDP43Pc8aTZ8XoMwTldgRTaDa7RfOA8j9+Ele9VLHkvxhX9zqdizMnFi9t2Q5bJ9lxn2PU1eH8e+67vte2uVugI+ed75HIShQMX4yodZDPG6kOZsLBijZ+YzhcO4h4F0FhD3J8cpKk4Z40bWPCqUAPOljyd5QSYCBZYfPoCA+JQPD05ULkGcSzzZCETjrZHjOr+i9Dt54QXw59taEJ221svyLAlcdJbWY8FlJAouace8tV6vjPufXvY5PcUEshDXJw9FX2ROOY4ts4c+xBo+wzE8bWWoUcqwexdwVL8Q/Sxl+IZ4ZlF2z41XpH9HV6ni8TNqUZjsFrbmkNVN707pXaeJWClcwoDoE9cJkQgm7mBWjTQLk03Kr9WHDGYdtXJIlpQKs67gfO3hN099SwS8lWuR0l16Kcl1nVUIWnCAlItPp1UOjMcTPaILExeKA1mFbZEDkixGXJiLSs+vxFaZxXqpmVWbBgV9KtmrMLQpFhqHlAw1qTIEj15548Z2uTL/Pd1xlNfMDIoFM3n5Xk3JDI+dSgPWcivPld8kOdVwDxL3hd6hNDo3C59RCaIync2oWa2tVugMqfSJopc74lehw8R21aQcHDmcUv0xf2WmSRSDGfkxUW4EuzKiicfHBwSntBeBPzLoig+FEf0dFRl6l3auZW3oUHBtqDiD1rhYdCSxYdRRbWjVMiomYUOxL43GKL8tkkzkjrpA7iFgaruXov2WO4GemNYUuII8MQq42rAlcA3DPNdqXTqVDiMFY1iuX7biXukxhp4HgrlTysS1MNCNswqV7E2S1anPNgizupQ/pumsrIKgwl824+t9cO6Mv1oTlk9v1i5yfjvWa3LvWC/GGa+tsv3tWE6X+feA5Z162e2ySaL3fwr0VZruF4iVMP/tAaa5I2uktXW5VSPaFVfsS6fTn6LdlWEnOO4/JvdDTcxOFI12i9vuRNGolKQm7rwb9vycbDQnHFliAi5uyKKP0Tk6sswube8pZ7h2RrR7EwVDQXvzzDLcdHpLXWPcUsfNHdvWpk4s98Ls29tBUqv66vs6RK/xl+mXyWRnkVdvC3YEBIwqfYKDztomLKpkh42FTlej+3l+jEAVpjQ0vYXzVbmePUhrnra5TloXGvKRVZjyUmDbK/iJcejopZ/WqNLljg1jJ2cmcEHVjnNYOaKqcSnNjkMU+Cs1quy5YiybFs+oXRfPdHuWW7tc3ouIJ3bu1Nl/vJKgDAtdkKpL51LhIzcCH8PGm+ckNkk/SnkQc+cgohVskospRR4U5NPSmmtrBtxPMHSiWmT1agYRgt6gWnuDIF1zvLRWpDNvsyAn+p/PrNCZn/vwW7j1ZtCtWzmQGLWLNWpVFhglDFVq4Thd1SmdDjyohAjC6ngU1qGiR2Ia/p0fO/lV5QvFwazGVBS/dKMc06kpyLvil8oK7//wKw9dyvxSdL3CL53BrxabpPBl/tcxYh2a/4kRdfI/
\ No newline at end of file
diff --git a/001/figures/drawio/tree_new_SW_development.drawio b/001/figures/drawio/tree_new_SW_development.drawio
new file mode 100644
index 0000000..395555d
--- /dev/null
+++ b/001/figures/drawio/tree_new_SW_development.drawio
@@ -0,0 +1 @@
+7Vxbc+I2FP41PIaRr+DHQCBtNrubbdrS9GXHgAA1xvLKcoD++kpGxjdhHLAN3eCd2aBjcWTpfOcqmZbWX67vie0tPuMpdFoqmK5b2l1LVRWla7A/nLLZUjoG2BLmBE1Fp5jwjP6Fghh1C9AU+qmOFGOHIi9NnGDXhROaotmE4FW62ww76VE9ey5GBDHheWI7MNdthKZ0saV21U5M/wWi+SIaWTGt7Z2lHXUWjP2FPcWrBEkbtLQ+wZhuPy3XfejwxYvWZfTrZuQ8vpr3D9/8H/YfvU+/f/nzZsts+J6v7KZAoEuPZv3d+rwejPwH8KZ8V397/LrQ/PmNroq50U20YHDK1k80MaELPMeu7Qxiao/gwJ1CzhawVtznEWOPERVG/AdSuhFgsAOKGWlBl46461OCX2EfO5iEY2r9PmDX7k4kKLbEPTZlsvmLj9U2ouaLGDps3K1TrY1olVwzsbY+DsgEFiyUwAC1yRzSgn6mUBe+igkACpHcQ7yE7ClZBwIdm6K3NEptAfb5rt/uq08YsYmoQCimZoonEmqpRO2IxfZJxbdiWLAPiceISSFY3gEcMdqb7QRiCi3VdNjK9KboLQUo80fANaQ3wy698UNI3LIOiumt45vs05z/VRgKVLaEwIUrbnTgG3SwtwxlOIxG4JxKDdGVDRFxGZMshS3ElnWOHM4pomb0JdYGDu3VAlH47NkhmFbMpKaRP0OOk8D9zOD/ZBoxHPaMDhBzStC317vx/QYJhetCQO4BliWaq9h4qkDQFgnDaYD9EE6B771I085hoeAa0YTRYa2XxJ3Y5PDGmS0OqNrgnCYtvdgwpFWrtCarMk3+8vU0zWUaQYsck4tdmNFZQbIdNHdZc8JEDRm9x/ULsaDjVtxYouk0RKLMHqTRWZsiqwcVWZfosVqbHlt7kXEaDF4Gz3tx8KEkbhw23Y1KXNdqsQXSwOEeh4nFOw1CTQ8zWvCnQf6BpzltkG3ORAkaBxS582sQk9AEPa0Iu2Q0oQm7gLmRIMbs/l+imGPzrZzwrfCS5nQVR0q6WTJU0jsNJWdGGn+aBtogcWUY1pyqRctziuNVijKp0+zYI2I+1YfsPp7xqbgTTDxMbMqQz03cFB4wbSUSuZ/b2qndSzN3kaKdAjkpWJ4I9giCTGM2V2Gn22cTdkc/p2+LPr+k/Jzct+WkCIBl7ak7VuyjJNn88n748Ik8fBs9ddWBMnr+u78EN0pDLspUMjACRqNOqds5B2jOCIDuxSHAtNqqbu2ubjpksQpDlu10c+g4DDOzWZhFw1Vdp74lPGDZ4ID9P8dh+hVmnyDw4b6Uq8ryOOJVCIb8KEK6Fscbcb5KdtdFP7vzVeoBeByVrxCbGeMTeJ6DIMMF4E/M90fdYGZPaEA4sQA2Hxgfu0TwfPioIPm7Vl0LA/JssUkSkDdadu3sL7Rft2AahYZ+adCIxq88L4/dxQQvmZ+w3cn+ss3P7QN0UMIHGFaDPqCrXn1AzTtvkTwLZN6oolvXbfgLgUb2PM3ZoaGA/U4gIabPNiWISRtgV1h1m6IxchDdFIg2x6a/gJNXB/kcX05c6R8zATF+2N3tkdabOhS4h7RDGQ4HZr9fp3vIVER27iLpHmSAqM09KCDvH+7wJOCn7kIZ8doGZF7dpjAnBcYfef4+FSsuvQEwHOYl0O8PjJBemwTUtLFm3jgvgajglZSAXp8EDpSpErrE8++B2rKU1q0SFZ18yJUKzUJF9TYkfOSyGjqGDnbnfsRrgwMSFph8imjAxd8+2o5H9tmBM1pknQlkPsYeh4y4Tnq8HBgustFrGXecU0Dx1g+FjOuL3dLIMEum71oFyJAWg0FulS+sSr47YtAqvw3TktW3Kyy1R0Xfw+cBNDkaTqys31hpGClqpuhdtnquKHwpU4g0GjpJIN+auAg0Fr0scMSm4GkvGFwCis1aUKxlULw79X0AbHlGnePUoSrU7s9+r6lQQSqU85plsV36RLJs96SuVEiKjP3nUz9kXaR6iSuXJvGzHFWpO566VA8WnQI76ME69ZxwUDOOR1MysCobhzGMtoGm6121Y3RNFXTSbPXazjRIMWxcBIY/SBRWGsNdUAuGs8FTzjSWjsK0jCnuNBuFneUA/DGo/Rksb11gzNSy9WPBqGcPyCvGEafNqoJmqf1yWfFttcCly2z8baDUCzu7stq7K9+NF9qqDwzNbGCo5gNDq8lCm7J/w6xsLqBJc4EIL+rxGUH5SP9i5JsppEreRNQala7sFFRm3aNFfbTH0HliixRufWh3Y0wpXkpWneLsFsfC9jiz5XrOf0ulPbZ9NGm7+Lu/WY6x05JsdQhvVJcYsk5fl6iZrJ6d/TGJ6gQhezGkIUGw77zmZbDLxeqSgZGro+W3m4xqZMCa8c/RbL1j/KM+2uA/
\ No newline at end of file
diff --git a/001/figures/drawio/tree_sustainable_software.drawio b/001/figures/drawio/tree_sustainable_software.drawio
new file mode 100644
index 0000000..4fe4370
--- /dev/null
+++ b/001/figures/drawio/tree_sustainable_software.drawio
@@ -0,0 +1 @@
+7V1bc6M2FP41nmkf4uGOeYwdO02btN1m23T7siMbGbPBiAUR2/vrK3G/G9tcvFmSGccchBA637nqiIz42XZ/bwNr84RUaIw4Rt2P+LsRxykTlnxSwsEnSFxA0Gxd9UkJwrP+DQZEJqC6ugqdVEOMkIF1K01cIdOEK5yiAdtGu3SzNTLSd7WAFtyRiQnPK2DAXLMXXcUbnzrh5Jj+C9S1TXhnVlL8M1sQNg46djZARbsEiZ+P+JmNEPa/bfczaNC5C+fl5eHwYjy+Sve/fnC+gr+nv338/Z8bv7PFKZdEj2BDE5/d9WflaT9/cX5l3tjP3F+Pf2x4R7thueDZ8CGcMKiS+QsOkY03SEMmMOYxdWoj11Qh7ZYhR3GbR4QsQmQJ8QvE+BCAAbgYEdIGb43gLNzr+F96+VgMjj4lztztg569g0N4YGL7kLiIHn5Knosv847C69a6YcyQgWzv6XhVhBNVIHQH2+gVJs4wjKIwTHQmBAth87Tm/Ad8cpBrr2DFpAd4wsDWIK5oJ/B+Q8qRBJgD9t5DtIXkSUkDGxoA629pxINAcLSoXXTpn0gnD8IxgYyLQjCiQMQ5hkl34Y80uCqGGPmSGEZM8oB3AgiFnkHI1UdhDjWzGcOUoCZCLJvCawzfEsT2hDZJ7AZtvJRGGyt1i7bgbm/AcINHGHGSQWZmqupvKRRKX12q26drZOIbx8PRLWnAStY+Pkm+acFfI2x8fi/ProOBboIluZjydo13BAcjfhF2Tx7Zv8OZd51UjX1pZykltyNkb7JCakZ6Y9mk0N9tdAyfLeChdEecjLQcZhT0WqS/RaK2WExFmQmeKUH3f04WnDdoY7ivRHoJYpXgcBf7E5HK3CR8CZEpl40Uqk+FMP+9GO2eVBnTtCa7jFtCtcY5U5K5Ikn+/Y/LJJdIBE6zPS2GJjJhRmYDEjB0zSSHK8JqSOhTKl868cNvgxNbXVU9JBbpgzQ6WxNkWUibHiEvyUKBIHOtCbJSCo3LcPBp/lwKhB+K5ULW2+ib5QKb48ApypttUnlH+vpIxHWa/5oz3Ir3k/ORpeYNROjDdm8hin3dyC3Ioi/swn+i1nxdSerXU5DPiu+5kwL8unBrIZAPA/Tjkbx8VR6JJPcLixMC7gQs5PcHC+mqYBGO+xJvpDCqfdkgem+nqSC2JACnOWRs60sX66aWiJlrhLU/VgDLTvqOYKXJoIHa1EBSTQ0ksdelgaSWNNB8TyIUApUfVQFwmQy/mFcALFegALK52cY4LTO5OR880wYVgFxXAQjXpQDkUgVwSa6sUCc8mEd0QnHGrKXM3U9wrI29y12VYID4SjMKCButoeMQAHmHDgbr9Xg8/nnI2FfqO2Fydfqu55z9efruQoenYnG0YX0X+jFH9Z18XQ5PmJDuFhan1D5EEErgJ84idrLsU8TcD9a/T+5/ivD4NGOh9E25+fCLetM4b4uzeqyc1i7SRBnLmV5KEnv5DCGf7kvMhlwlq+G3tg0OiWYWbeBUjDmjEcOQsGxc2fbhuGKw+yNoNl0ZKvrY+t8h6FDWb+h6uG46WMckvEcm1dvgjRLBakUsJOUqVeNeYxRdAYnfb6rkiwmhJzKL9276soDi+QLTJ3Vq+vqN9U/QW2UVO9zJSx4dWj7h+7R8k55z0L04RN3VGNaGxaTxpbDLEoNHiiX6Ls9afqFFyoGNUXWbHJE5cS6Ox1qKKkfidAd1xzU1R4NLKjzUcqp4PBLvhhiy0pCKdQypqHRoSMPV7aZl4wkcltRZIvJNyzgWJ0NvKCo8w08rKw04lqJobU1G4fq0yOH3T2nr3OxmgB79tObdr+LATciorSgV1lF5tZyP4RpRUo/6CpqOF/BpNoRbjyuL2ub0p51OOJtYIkZ2dRL1R1JFWciwvYeMXDWIhpLZzkpmxYwXVFD83mn9pNzAEvFQMlvFclbJsLzvklm5fFFwYHkrLBd6Z3l5YfxgALotoL82bTDpuXTsnScOw3DheOKw8d3Jl8FC6RUWo/qrDD0GoUXM7XAl9dRFy6zuCc1S2aJltn3lomV+Kbbk6q4i55A515n6foQaLZViHIhdi/zV/LQ3s3aJ1BDjxTFoSawWoIuz15wO523VlyhMkbjWTWASkfGqq5aHGwPsnPF4yI4fdQuy2fHCnEGn2fFJec5giBIa4bkkKGlXsO9cwKR8w8pFGvPeKyChH4av9QYJTxjX/iS8fP1rkPBmJDyzUUiQe5Zw5YiED3mAzhLBmYLAaGN9b9AYXqtxJdDIhWlc39CY5KDhLx/SfaFkBgxgmmRWcvkCw9Atp2wuE8wDjuW/qnCt7+nsVlnttJ1fLObSbNam1c6s10y4sZhjRlhIkrLaYkvMYJl8XPsRbi1abeIFXaNMYe8lbtX1MIITjptStlOpYJmCpfkZN7qVJWVJyH/bm/v3MvuSIoa4D4MVJj//csH08+1Nfz5AvUMrl1YygKCkHUdyca5qKsgcM8xikWfBbDYXPXprVoFRarAgAmWSB9m3pDTIg7w/+Z55IGWdtgLL3DUHjhUxhh5P7IUZcI3zPtl8bwFi0T2ehbs7qAenQguaKk1Neqd0k3Srq66XvLThV1e3veIhh262fFiTD9d0XDtIAa42cPVaIylZe5RB2ZG/GyXIJtAhAht7JUxklLY3MMdC5Gn89z5a0Hb85wJb6qeQh4j6sJChrw7jsx3PcODecCvcSTIi/Zv3HkrfeQxy9aRXcUrTo6QnFyPfcfY6bgvDuZ1IBS+viLKPTWvyh9fpw37Offm8uYWb/bdnrM/XFW8QrRtl8MXZ6Tk3UtjRLVuYe6b7x7PfhpQFgUc6KVno8PItwaNw7awIHhmWhPP4CJbQ+JNIkWd7+LslwhhtCyYao6yN2QCLdrbda/S17eMlcPTV2ESfncN2iYwiWxMsMpZMcF3eVNj7ksLTZODRUhFh1RpmH3wg17zmWRAt4rfFgmxNuVhg7sUuWdDLpvdzdjenqs9Hx/c2ZxbGm6wTL3hzRzm8Gy8fz4atvJzBRt2NzayS1stizdd8X7qx+ViNQNsbmwt59d3s8h/kYJCDs+SAHMb/CcVvHv87GX7+Pw==
\ No newline at end of file
diff --git a/001/figures/tree_IP_policy.pdf b/001/figures/tree_IP_policy.pdf
new file mode 100644
index 0000000..75b4a63
Binary files /dev/null and b/001/figures/tree_IP_policy.pdf differ
diff --git a/001/figures/tree_licensing.pdf b/001/figures/tree_licensing.pdf
new file mode 100644
index 0000000..cd5043b
Binary files /dev/null and b/001/figures/tree_licensing.pdf differ
diff --git a/001/figures/tree_new_SW_development.pdf b/001/figures/tree_new_SW_development.pdf
new file mode 100644
index 0000000..ccedf01
Binary files /dev/null and b/001/figures/tree_new_SW_development.pdf differ
diff --git a/001/figures/tree_sustainable_software.pdf b/001/figures/tree_sustainable_software.pdf
new file mode 100644
index 0000000..a708c27
Binary files /dev/null and b/001/figures/tree_sustainable_software.pdf differ
diff --git a/001/manuscript.pdf b/001/manuscript.pdf
new file mode 100644
index 0000000..d60f735
Binary files /dev/null and b/001/manuscript.pdf differ
diff --git a/001/manuscript.tex b/001/manuscript.tex
new file mode 100644
index 0000000..f6a9a8e
--- /dev/null
+++ b/001/manuscript.tex
@@ -0,0 +1,971 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% Please note that whilst this template provides a
+% preview of the typeset manuscript for submission, it
+% will not necessarily be the final publication layout.
+%
+% letterpaper/a4paper: US/UK paper size toggle
+% num-refs/alpha-refs: numeric/author-year citation and bibliography toggle
+
+\documentclass[a4paper,num-refs,numbers,sort&compress]{de-rse}
+
+%%% Journal toggle; only specific options recognised.
+%%% (Only "gigascience" and "general" are implemented now. Support for other journals is planned.)
+\reviewfrom{23 January 2020}
+\reviewto{09 February 2020}
+\acceptedon{03 April 2020}
+\publicationurl{https://arxiv.org/abs/2005.01469}
+\publicationpidtype{arXiv}
+\publicationpid{2005.01469 [cs.GL]}
+
+\usepackage{graphicx}
+\usepackage{siunitx}
+%\usepackage[numbers,sort&compress]{natbib}
+
+% Custom packages
+\usepackage[nonumberlist]{glossaries} % TODO Check if we can put glossary items in the abbreviations section
+% \usepackage{flushend}
+%\usepackage[inline]{enumitem}
+% Set graphics path
+\graphicspath{{figures/}}
+% EO Custom packages
+
+\setlist[itemize]{noitemsep, topsep=0pt, leftmargin=*}
+\DeclareRobustCommand{\doi}[1]{\href{https://dx.doi.org/#1}{\nolinkurl{doi:#1}}}
+\DeclareRobustCommand{\urlhttps}[1]{\href{https://#1}{\nolinkurl{#1}}}
+\DeclareRobustCommand{\arxiv}[1]{\href{https://arxiv.org/abs/#1}{\nolinkurl{arXiv:#1}}}
+% Custom commands
+% Set the Glossary section heading to null
+\renewcommand{\glossarysection}[2][]{}
+
+% Define an fbox with vertical spacing
+\newcommand*{\vsepfbox}[1]{%
+ \begingroup
+ \sbox0{\fbox{#1}}%
+ \setlength{\fboxrule}{0pt}%
+ \mbox{\kern-\fboxsep\fbox{\unhbox0}\kern-\fboxsep}%
+ \endgroup
+}
+
+\newlist{inlinelist}{enumerate*}{1}
+\setlist*[inlinelist,1]{%
+ label=(\arabic*),
+}
+% EO Custom commands
+
+%%% Flushend: You can add this package to automatically balance the final page, but if things go awry (e.g. section contents appearing out-of-order or entire blocks or paragraphs are coloured), remove it!
+% \usepackage{flushend}
+
+\title{An Environment for Sustainable Research Software in Germany and Beyond: Current State, Open Challenges, and Call for Action}
+
+%%% Use the \authfn to add symbols for additional footnotes, if any. 1 is reserved for correspondence emails; then continuing with 2 etc for contributions.
+\author[1,2,\authfn{2}]{Hartwig Anzt} % 0000-0003-2177-952X
+\author[1,\authfn{2}]{Felix Bach} % 0000-0002-5035-7978
+\author[3,4,5,\authfn{2}]{Stephan Druskat} % 0000-0003-4925-7248
+\author[6,7,8,\authfn{2}]{Frank L\"offler} % 0000-0001-6643-6323
+\author[9,\authfn{1},\authfn{2}]{Axel Loewe} % 0000-0002-2487-4744
+\author[10,11\authfn{2}]{Bernhard Y.\ Renard} % 0000-0003-4589-9809
+\author[12,13,\authfn{1}\authfn{2}]{Gunnar Seemann} % 0000-0001-7111-7992
+\author[14,\authfn{2}]{Alexander Struck} % 0000-0002-1173-9228
+\author[15]{Elke Achhammer}
+\author[16]{Piush Aggarwal}
+\author[17]{Franziska Appel}
+\author[18]{Michael Bader}
+\author[19]{Lutz Brusch}
+\author[20]{Christian Busse}
+\author[21]{Gerasimos Chourdakis}
+\author[22]{Piotr W. Dabrowski}
+\author[23]{Peter Ebert}
+\author[24]{Bernd Flemisch}
+\author[25]{Sven Friedl}
+\author[26]{Bernadette Fritzsch}
+\author[27]{Maximilian D.\ Funk}
+\author[3]{Volker Gast}
+\author[28]{Florian Goth}
+\author[29]{Jean-No\"{e}l Grad}
+\author[30]{Sibylle Hermann}
+\author[31]{Florian Hohmann}
+\author[32]{Stephan Janosch}
+\author[33]{Dominik Kutra}
+\author[34]{Jan Linxweiler}
+\author[10,35]{Thilo Muth}
+\author[36]{Wolfgang Peters-Kottig}
+\author[37]{Fabian Rack}
+\author[38]{Fabian H.C.\ Raters}
+\author[39]{Stephan Rave}
+\author[40]{Guido Reina}
+\author[41]{Malte Reißig}
+\author[42,43]{Timo Ropinski}
+\author[44]{Joerg Schaarschmidt}
+\author[45,46,47]{Heidi Seibold}
+\author[48]{Jan P.\ Thiele}
+\author[49]{Benjamin Uekerman}
+\author[50]{Stefan Unger}
+\author[29]{Rudolf Weeber}
+
+
+\affil[1]{Steinbuch Centre for Computing, Karlsruhe Institute of Technology (KIT), Germany}
+\affil[2]{Innovative Computing Lab, University of Tennessee, Knoxville, TN, USA}
+\affil[3]{Department of English Studies, Friedrich Schiller University Jena, Germany}
+\affil[4]{Institute of Software Technology, German Aerospace Center (DLR), Germany}
+\affil[5]{Department of Computer Science, Humboldt-Universit\"at zu Berlin, Germany}
+\affil[6]{Heinz Nixdorf Chair for Distributed Information Systems, Friedrich Schiller University Jena, Germany}
+\affil[7]{Michael Stifel Center Jena, Germany}
+\affil[8]{Center for Computation and Technology, Louisiana State University, Baton Rouge, USA}
+\affil[9]{Institute of Biomedical Engineering, Karlsruhe Institute of Technology (KIT), Germany}
+\affil[10]{Bioinformatics Unit (MF1), Robert Koch Institute, Berlin, Germany}
+\affil[11]{Hasso Plattner Institute, Faculty of Digital Engineering, University of Potsdam, Germany}
+\affil[12]{Institute for Experimental Cardiovascular Medicine, University Heart Centre Freiburg Bad Krozingen, Germany}
+\affil[13]{Faculty of Medicine, University of Freiburg, Freiburg, Germany}
+\affil[14]{Matters of Activity. Image Space Material. Cluster of Excellence at Humboldt-Universität zu Berlin, Germany}
+\affil[15]{Technische Universität München, Germany}
+\affil[16]{Language Technology Lab, Universität Duisburg-Essen, Germany}
+\affil[17]{Leibniz Institute of Agricultural Development in Transition Economies (IAMO), Halle (Saale), Germany}
+\affil[18]{Department of Informatics, Technical University of Munich
+, Germany}
+\affil[19]{Center for Information Services and High Performance Computing (ZIH), Technische Universität Dresden, Germany}
+\affil[20]{Deutsches Krebsforschungszentrum, Heidelberg, Germany}
+\affil[21]{Chair of Scientific Computing in Computer Science, Technical University Munich, Germany}
+\affil[22]{School of Computing, Communication and Business, Hochschule für Technik und Wirtschaft Berlin, Germany}
+\affil[23]{Center for Bioinformatics Saar, Saarland Informatics Campus, Germany}
+\affil[24]{Institute for Modelling Hydraulic and Environmental Systems, University of Stuttgart, Germany}
+\affil[25]{Berlin Institute of Health, Germany}
+\affil[26]{Scientific Computing, Alfred Wegener Institute, Helmholtz Center for Polar and Marine Research Bremerhaven, Germany}
+\affil[27]{Max-Planck-Gesellschaft e.V.}
+\affil[28]{Institut für Theoretische Physik und Astrophysik, Universität Würzburg, Germany}
+\affil[29]{Institut für Computerphysik, University of Stuttgart, Germany}
+\affil[30]{University Library, University of Stuttgart, Germany}
+\affil[31]{Zentrum für Medien-, Kommunikations- und Informationsforschung (ZeMKI), Universität Bremen, Germany}
+\affil[32]{Max Planck Institute of Molecular Cell Biology and Genetics, Dresden, Germany}
+\affil[33]{European Molecular Biology Laboratory, Heidelberg, Germany}
+\affil[34]{Center for Mechanics, Uncertainty and Simulation in Engineering, Technische Universität Braunschweig, Germany}
+\affil[35]{eScience Division, Federal Institute for Materials Research and Testing, Berlin, Germany}
+\affil[36]{Konrad-Zuse-Zentrum für Informationstechnik Berlin (ZIB), Germany}
+\affil[37]{FIZ Karlsruhe - Leibniz Institute for Information Infrastructure, Germany}
+\affil[38]{Department of Economics, University of Goettingen, Germany}
+\affil[39]{Applied Mathematics, University of Münster, Germany}
+\affil[40]{Visualization Research Center, University of Stuttgart, Germany}
+\affil[41]{Institute for Advanced Sustainability Studies e.V.}
+\affil[42]{Institute of Media Informatics, Ulm University, Germany}
+\affil[43]{Department of Science and Technology, Linköping University, Sweden}
+\affil[44]{Institute of Nanotechnology, Karlsruhe Institute of Technology (KIT), Germany}
+\affil[45]{LMU Munich, Germany}
+\affil[46]{Bielefeld University, Germany}
+\affil[47]{Helmholtz Zentrum Munich, Germany}
+\affil[48]{Institute of Applied Mathematics, Leibniz University Hannover, Germany}
+\affil[49]{Energy Technology, Eindhoven University of Technology, The Netherlands}
+\affil[50]{Julius Kühn-Institut (JKI), Federal Research Centre for Cultivated Plants, Quedlinburg, Germany}
+
+
+%%% Author Notes
+\authnote{\authfn{1}axel.loewe@kit.edu, gunnar.seemann@universitaets-herzzentrum.de; \authfn{2}Contributed equally.}
+
+%%% "Short" author for running page header
+\runningauthor{Anzt, Bach, Druskat, Löffler, Loewe, Renard, Seemann, Struck et al.}
+
+%%% The run-on number of this position paper
+\papernumber{1}
+
+% Glossaries
+% \makeglossaries
+\makenoidxglossaries
+
+\newglossaryentry{RPO}
+{
+ name = {research performing organizations},
+ description = {Research groups, departments, faculties, research institutions (universities, research institutions, cross-institutional research groups, etc.), umbrella organizations, such as Helmholtz-Gemeinschaft Deutscher Forschungszentren, Max-Planck-Gesellschaft zur F\"orderung der Wissenschaften, Leibniz-Gemeinschaft, etc}
+}
+\newglossaryentry{RFO}
+{
+ name = {research funding organizations},
+ description = {Public research funding bodies but potentially also companies, foundations, associations, etc}
+}
+
+\newglossaryentry{GeopoliticalUnits}
+{
+ name = {geopolitical units},
+ description = {Governed public units, ranging from cities and councils, over federal states and countries, up to political unions such as the EU. In the context of this paper, the discussion usually focuses on the larger units (countries and political unions)}
+}
+\newglossaryentry{RSE}
+{
+ name = {research software engineers (RSEs)},
+ description = {People creating and maintaining research software; this group ranges from research-focused software developers, to software engineers with a focus on research; other definitions include other roles, such as research software managers}
+}
+\newglossaryentry{DomainResearchers}
+{
+ name = {domain researchers},
+ description = {The people doing the research to advance knowledge in a field}
+}
+
+\newglossaryentry{GeneralPublic}
+{
+ name = {general public},
+ description = {Lay people that do not necessarily have specific insight regarding a research domain}
+}
+\newglossaryentry{ScientificLeaders}
+{
+ name = {research leaders},
+ description = {Heads of research groups, such as professors and other people with staff responsibility}
+}
+\newglossaryentry{Libraries}
+{
+ name = {libraries (also registries, indices)},
+ description = {Infrastructure units of research bodies such as universities, or independent organizations, which gather research outputs and their structured metadata, and provide indices, search, etc}
+}
+\newglossaryentry{InfrastructureUnits}
+{
+ name = {infrastructure units},
+ description = {Computing centers of research bodies such as universities and other research centers, as well as high-performance computing facilities}
+}
+\newglossaryentry{Industry}
+{
+ name = {industry},
+ description = {Companies conducting research or profit from available academic research software which they can directly or indirectly apply to their field}
+}
+\newglossaryentry{OSDevs}{
+ name = {independent (open source) developers},
+ description = {Project-external software developers who are not employed by the institution(s) carrying out the project.}
+}
+% EO Glossaries
+
+\begin{document}
+
+\begin{frontmatter}
+\maketitle
+\begin{abstract}
+Research software has become a central asset in academic research.
+It optimizes existing and enables new research methods, implements and embeds research knowledge,
+and constitutes an essential research product in itself.
+Research software must be sustainable in order to understand, replicate, reproduce, and build upon existing research or conduct new research effectively. In other words, software must be available, discoverable, usable, and adaptable to new needs, both now and in the future.
+Research software therefore requires an environment that supports sustainability.
+
+Hence, a change is needed in the way research software development and maintenance are currently
+motivated, incentivized, funded, structurally and infrastructurally supported, and legally treated.
+Failing to do so will threaten the quality and validity of research.
+In this paper, we identify challenges for research software sustainability
+in Germany and
+beyond, in terms of motivation, selection, research software engineering personnel, funding, infrastructure, and legal aspects.
+Besides researchers, we specifically address political and academic decision-makers to increase awareness of the importance and needs of sustainable research software practices. In particular, we recommend strategies and measures to create an environment for sustainable research software,
+with the ultimate goal
+to ensure that software-driven research is valid, reproducible and sustainable, and that software is recognized as a first class citizen in research.
+This paper is the outcome of two workshops run in Germany in 2019, at deRSE19 - the first International Conference of Research Software Engineers in Germany - and a dedicated DFG-supported follow-up workshop in Berlin.
+\end{abstract}
+
+\begin{keywords}
+Sustainable Software Development; Academic Software; Software Infrastructure; Software Training; Software Licensing; Research Software
+\end{keywords}
+\end{frontmatter}
+
+% %%% Key points will be printed at top of second page
+% \begin{keypoints*}
+% \begin{itemize}
+% \item \hl{This is the first point}
+% \item \hl{This is the second point}
+% \item \hl{One last point.}
+% \end{itemize}
+% \end{keypoints*}
+
+
+\section{Background}
+\label{sec:background}
+\noindent\vsepfbox{
+ \parbox[]{\dimexpr\columnwidth-3\fboxsep-2\fboxrule\relax}{
+ Meet Kim, who is currently a post-grad PhD student in researchonomy at the University of Arcadia (UofA). We will follow Kim’s fictional career in order to understand different aspects of research software sustainability. Note that in Kim's world, many of the changes this paper calls for have already been implemented.
+ \\
+ {\footnotesize (In our example, Kim is a female person. Of course, research software engineers (RSEs) can be any gender.)}
+ }
+}
+
+\noindent Computational analysis of large data sets, computer-based simulations, and software technology in general play a central role for virtually all scientific breakthroughs of at least the 21st century. The first image of a black hole may be the most prominent recent example where astrophysical experiments and the collection and processing of data had to be complemented with sophisticated algorithms and software to enable research excellence~\cite{%TheEventHorizonTelescopeCollaboration2019,TheEventHorizonTelescopeCollaboration2019a,TheEventHorizonTelescopeCollaboration2019b,
+TheEventHorizonTelescopeCollaboration2019c,Nowogrodzki2019%,TheEventHorizonTelescopeCollaboration2019d,TheEventHorizonTelescopeCollaboration2019e
+}. Similarly, it is research software that allows us to get a glimpse of the consequences our actions today have on the climate of tomorrow. However, an implication of computer-based research is that findings and data can only be reproduced, understood, and validated if the software that was used in the research process is sustained and their functionality maintained.
+
+At the same time, sustaining research software, and in particular open research software, comes with a number of challenges. Commercial research software often has revenue flows that can facilitate sustainable software development, maintenance, and documentation as well as the operation of adequate infrastructure. However, a large share of researchers base their research on software that was developed in-house or as a community effort. Many of these software stacks can not be sustained -- often because research software was not a first class deliverable in a research project and hence remained in a prototype state, or because of missing incentives and resources to maintain the software after project funding ended.
+Another fundamental difference to industrial software development is that most developers of academic research software (often doctoral students or postdoctoral researchers) never receive training in sustainable software development~\cite{SSIanalysis}. In particular, as they see themselves usually as the primary user of a software product, there are virtually no incentives to invest in sustainability measures such as code documentation or portability.
+In combination with the predominance of temporary positions in research, this results in a highly inefficient system where millions of lines of code are generated every year that will not be re-used after the termination of the developer's position.
+Part of the problem is the reluctance to accept research software engineering as an academic profession that results in a lack of incentives to produce high-quality software: producing high software quality needs sufficient resources, and although the San Francisco Declaration on Research Assessment (DORA~\cite{DORA}) demands a change in the academic credit system, many institutions base promotion and appointments on traditional metrics like the Hirsch index~\cite{Hirsch2005}.
+It is obvious that an extraordinary amount of idealism is required to write sustainable code including documentation and installation routines, as well as running infrastructure and giving support to others when resources can be used more profitably in writing scientific publications based on fragile prototype software~\cite{bangerth2014quo,Prins2015}.
+
+Thus, one main factor for the poor sustainability of research software is the lack of long-term funding for research software engineers (RSEs)~\cite{RSEdef} who take care of the appropriate architecture, organization, implementation, documentation, and community interaction for the software, paired with the implementation of measures towards making the software sustainable during and beyond the development process~\cite{SSIRSE}.
+
+In this paper, we describe the state of the practice and current challenges for research software sustainability, and suggest measures towards improvements that can solve these challenges.
+The paper is the result of a community effort, with work undertaken during two workshops and subsequent collaborative work across the larger RSE community in Germany.
+It has been initiated during a half-day workshop at the first International Conference for Research Software Engineers in Germany (deRSE19) in Potsdam, Germany on June 5th, 2019~\cite{deRSEconf}, and continued during a dedicated two-day workshop in Berlin, Germany on November 7th and 8th, 2019, which was funded by the German Research Foundation (Deutsche Forschungsgemeinschaft, DFG).
+Subsequently, the draft produced during the latter event was opened up for collaborative discussion by the German RSE community through \textit{de-RSE e.V. - Society for Research Software}.
+%Public reviews were conducted between PLACEHOLDER and PLACEHOLDER.
+%This version of the paper has also been accepted as an official position paper of de-RSE.
+
+We mainly focus on the situation of research software and RSEs in Germany, where funding bodies increasingly acknowledge the importance and value of sustainable research software and related infrastructures.
+The DFG, the largest funding body for fundamental research in Germany, for example, opened a call for sustainable research software development~\cite{DFGcall1} at the end of 2016 and a second call for quality management in research software~\cite{DFGcall2} in June 2019. The first call was oversubscribed by a factor of 10-15, a strong indicator of unmet demand. As another example, the 2019 ``Guidelines for Safeguarding Good Research Practice'' codex of the DFG~\cite{DFGcode} now explicitly lists software side-by-side with other research results and data. The FAIR principles for research data~\cite{Wilkinson2016} provide guidelines for data archiving, but enabling full reproducibility and traceability of research software requires additional steps~\cite{hasselbring2019fair}. In consequence, there are ongoing discussions on whether software should be considered as a specific kind of research data or as a separate entity~\cite{lamprechttowards}.
+
+These positive developments notwithstanding, guidelines and policies for sustainable research software
+development in Germany are unfortunately still lacking, and long-term funding
+strategies are missing. This all leads to unmet requirements and
+unsolved challenges that we want to highlight in this paper by
+elaborating on
+\begin{inlinelist}
+ \item why research software engineering needs to be considered an integral part of academic research;
+ \item how to decide which software to sustain;
+ \item who sustains research software;
+ \item how software can be funded sustainably;
+ \item what infrastructure is needed for sustainable software development; and
+ \item legal aspects of research software development in academia.
+\end{inlinelist}
+While we specifically focus on the research software landscape in
+Germany, we are convinced that many of the analyses, findings, and
+recommendations may carry beyond. We want to address RSEs who are
+experiencing similar challenges and newcomers to the field of research
+software development, but first and foremost political and academic decision makers to
+raise awareness of the importance of and requirements for sustainable software
+development. As a community we work hard on overcoming the challenges of
+software development in an academic setting, but we need support -- and reliable funding options and institutional recognition in particular -- for
+the sake of better research.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{Why Sustainable Research Software in the First Place?}
+\label{sec:motivation}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+%Stephan Druskat (Moderation, stephan.druskat@dlr.de), Florian Goth (fgoth@physik.uni-wuerzburg.de), Jean-Noël Grad (jgrad@icp.uni-stuttgart.de), Dominik Kutra (dominik.kutra@embl.de), Thilo Muth (mutht@rki.de), Fabian H. C. Raters (raters@uni-goettingen.de), Guido Reina (guido.reina@visus.uni-stuttgart.de)
+\noindent\vsepfbox{
+ \parbox[]{\dimexpr\columnwidth-3\fboxsep-2\fboxrule\relax}{
+ After graduation, Kim joins a fixed-term researchonomical research project. For her PhD thesis, she wants to crunch some data. Her colleague recommends learning some Boa, which is an all-purpose programming language often used in researchonomy. Luckily, the UofA runs regular Software Plumbery courses for researchers, including a Boa course. Kim takes the course and gains a solid understanding of the basics of the Hash shell, version control with Tig, and the basics of Boa. She starts writing scripts, which help her a lot with the data processing. Unfortunately, Kim’s scripts are quite slow and actually break after she installs a newer version of Boa. She visits the weekly Code Café organized by her university’s central RSE team. The RSEs not only help her update her scripts but also suggest some changes which speed up the computation by a factor of 25.
+ \\
+ During the next meeting with her PhD supervisor, Kim presents her collection of scripts. The supervisor encourages Kim to create a Boa library from them, as they will be very useful to other researchonomists. Thankfully, Kim’s project PI had applied for 3 RSE person months in their grant, so the project enlists an RSE from the central team. Over the next three months, Kim and the RSE work together to build the library, document it, test it, license it under the permissive Comanche license, update the TigLab repository to let others contribute, introduce automated builds for every code change via a continuous integration platform, and make the library citable. Finally, they release the first major version of the library, named \emph{hal9k} and publish it through the university library’s software portal, where they get a DOI (Digital Object Identifier) for the version as well as a concept DOI for any future versions of the library. Working with the RSE, Kim has gained a good understanding of some methods in software engineering, and she’s thrilled because this also means she’ll be able to get a job with a local tech company once her fixed-term contract has run out.
+ \\
+ Kim passes her PhD - of which \emph{hal9k} is an important part - with flying colors, and soon citations to her library start appearing in the researchonomic literature. To Kim’s surprise, she also reads a blog post about a citizen science maker project which has used \emph{hal9k} to process researchonomic data measured in a neighborhood of her hometown. She is invited to give a talk at the local office of Siren, a global tech company, which look to adopt \emph{hal9k}, and pay Kim a generous speaker honorarium. So generous in fact, that Kim can pay a student assistant for a full year from the money.
+ }
+}
+Our credibility as researchers in society hinges on the notion of proper
+research conduct, also known as ``good research practice''. The
+digitalization of research has introduced complex digital research
+outputs, such as software and data sets. Although first
+recommendations~\cite{katerbow2018}
+and policies~\cite{https://doi.org/10.2312/os.helmholtz.003} exist, they are far from being widely adopted. It is still somewhat unclear how to translate good research practice into good research
+software practice, for example in terms
+of validity and reproducibility, but also pertaining to the responsible use of resources. The damage
+that failing to do so is causing both to the progress of the research community
+and to the credibility of academic research in society is becoming increasingly clear
+with the growth of the replication crisis - while the lack of universally
+agreed-upon and supported good research software practice is not the main
+reason for that crisis, it clearly is a contributing factor.
+
+While it is obvious that software qualifies as a potentially re-usable
+digital artifact, the additional benefit of not just reproducing a given
+scenario, but transferring software use to new problems, domains,
+and/or applications, justifies developing research software with a long-term perspective as \emph{sustainable research software}.
+
+In order to support research, a sustainable software must be correct~\cite{hattonChimeraSoftwareQuality2007,changRetraction2006,matthewsFiveRetractedStructure2007}, validatable, understandable, documented, publicly
+released, adequately published (i.e. in persistently identifiable form
+as software source code~\cite{smithSoftwareCitationPrinciples2016}, and
+potentially in an additional paper which describes the software concept, design decisions, and development rationale),
+actively maintained, and \mbox{(re-)usable}~\cite{meraliComputationalScienceError2010,barnesPublishYourComputer2010,tseComputerCodeMore2010}.
+We also argue that truly sustainable research software must ideally be published under a Free/Libre Open Source Software (FLOSS) license, and follow an open development model, to (1) enable the validation of research results that have been produced using the software, (2) enable the reproducibility of software-based research, (3) enable improvement and (re-) use of the software to support more and better research, and reduce resources to be spent on software development, (4) reduce legal issues (see section below), (5) meet ethical obligations from public funding, and (6) open research software to the general public, i.e., the stakeholder group with arguably the greatest interest in furthering research knowledge and improving research for the benefit of all.
+
+To make software-based research (and with that almost any research)
+reproducible, the used software must continue to exist. Furthermore, it must
+continue to be usable, understandable, and return
+consistent results (or potential changes to results and bug fixes must be clearly documented) in the
+evolving software and hardware environment. Moreover, the software
+should support reuse scenarios to avoid duplication of efforts and
+unneeded drain of resources. Therefore, if research software is publicly
+funded, it should be freely available under a FLOSS license.
+
+Currently, creating and using sustainable research software is not sufficiently incentivized. To evaluate in which area this shortcoming should be addressed, we have identified the following challenges: \label{sec:motivation:challenges}
+
+\begin{itemize}
+\item
+ \textbf{Lack of benefit for the individual}:
+ Currently, the primary motivation for
+ sustainable research software is the common benefit, rather than the
+ individual benefit. It is clearly beneficial for the
+ research community as a whole to direct resources towards sustainable
+ research software, as it enables better and more
+ research by freeing funds for domain research rather than
+ (repetitive) software development. But the developers are often even at a disadvantage (e.g., they publish fewer papers~\cite{bangerth2014quo,Prins2015}), which
+ in turn prevents sustainable research software.
+\item
+ \textbf{Lack of suitable incentive systems}: Contributions to research that are not
+ traditional text-based products (i.e., papers or monographs) are still not sufficiently rewarded, or not rewarded at all, due to the missing implementation of mandatory software citation ~\cite{smithSoftwareCitationPrinciples2016,Hafer2009,Howison2016,Li2017,Li2019,Park2019,Pan2019,Doerr2019,druskatSoftwareDependenciesResearch2019,katzSoftwareCitationImplementation2019}, among other reasons. Interestingly, one third of research software repositories have a lifespan (defined as the time from the first time
+any code was uploaded to the last contribution) of less than one day (median: 15 days~\cite{hasselbring2019fair}), indicating that many codes are only made available publicly for the publication in a journal (as increasingly encouraged or required by journals~\cite{Resnik2019139} and associated with higher impact~\cite{codeImpact}) but are not maintained thereafter.
+\item
+ \textbf{Lack of awareness}: Research software sustainability (see~\cite{Venters2014,Goble2014,Druskat2016,KatzFundamentalsSoftwareSustainability2018}) and its
+ importance is lacking visibility as well as acceptance, and research software
+ engineering in its implementation as sustainable software development
+ and software maintenance is not sufficiently supported, both in
+ Germany and beyond~\cite{SSIRSE,NWOprofile,Casties2019}.
+\item
+ \textbf{Lack of expertise}: Knowledge about how to create, maintain, and
+ support sustainable research software is emerging~\cite{Wilson2014,Stodden2014,Wilson2017} but
+ has not yet permeated related activities within organizations - specifically
+ teaching, mentoring, and consultancy. This lack of expertise can also lead to divergence between
+ software design and community uptake, e.g., if the software fails to meet the needs of the
+ target group, or is insufficiently usable. RSEs
+ combine sustainable software engineering expertise with experience in one or
+ more research domains.
+\item
+ \textbf{Heterogeneous research community}:
+ There are significant differences with respect to how software is developed, published, used, and valued in the different academic disciplines. Additionally, there is even heterogeneity within a community in terms of application and approach.
+ This also makes it hard to train researchers for sustainable software development,
+ as beyond basic training in computational research such as provided by The Carpentries, advanced courses for research software engineering are not widely available (with the notable exception of the CodeRefinery project~\cite{CodeRefinery}).
+ Targeted curricula must be developed and updated regularly, and specialized instructors need to be trained.
+\item
+ \textbf{Lack of impact measures}: It is unclear how to measure the impact
+ of research software with respect to its quality, reusability, and benefit for the research community. This exceeds the
+ implementation of research software citation (which is work in progress~\cite{smithSoftwareCitationPrinciples2016,liSoftwareCitationReuse2016,katzSoftwareCitationImplementation2019,druskatSoftwareDependenciesResearch2019}), and pertains to sustainability and policy studies.
+\item
+ \textbf{Infrastructure issues}: Due to a lack of knowledge about
+ how sustainability features impact the application of research software, there is not yet enough evidence
+ for whether centralized or decentralized facilities should be favored to
+ further research software sustainability~\cite{Kuchinke2016,SuLMaSS,Hexatomic}.
+ This in turn leads to a lack of infrastructure as a whole.
+\item
+ \textbf{Legal issues}: Many obstacles for research software pertain to
+ legal issues, such as applicable licensing and compatibility of licenses~\cite{morinQuickGuideSoftware2012}, and decisions about license types.
+\item
+ \textbf{Funding issues}: Despite some individual initiatives~\cite{katzLookingSoftwareSustainability2015,DFGcall1,DFGcall2,ChanZuckerberg}, funding for the creation, maintenance, and
+ support of sustainable research software is still scarce.
+\item
+ \textbf{Slow adoption of research software engineering as a profession}: Career options for
+ research software work are not fully determined, although career paths are emerging in some regions.
+ Initially, the RSE initiative in the UK has made progress in this area, and RSE groups have been installed in many institutions. In Germany, the
+ US, and the Netherlands, this is still work in progress~\cite{SSIRSE,de-rse,us-rse,nl-rse}. It is also not yet
+ determined how to match research software engineering roles in public
+ institutions with industry roles (see~\cite{rodriguez-sanchezAcademiaFailureRetain2017}).
+\end{itemize}
+
+In summary, the necessary but resource-intensive practice of creating, maintaining, supporting, and funding sustainable
+research software is not yet sufficiently incentivized and enabled by
+research institutions and funding agencies, nor does it align well with
+the publish-or-perish culture that is still prominent in most fields.
+
+Therefore, it is necessary to comprehensively motivate sustainable research software
+practice.
+In the following, we identify stakeholders of research software (see~\cite{Katz2019,Druskat2018,ye2019open}), and explicate their particular motivations for sustainable research software. Subsequently, we
+specify challenges towards satisfying the demands of the individual stakeholders.
+
+\subsection{Stakeholder Motivations for Research Software Sustainability}
+
+While a wide range of stakeholders share interest in sustainable software, we argue that their individual motivation can differ quite significantly:
+
+The \textit{\gls{GeneralPublic}} benefits from research which supports the
+common good, in other terms: creates a better world, faster. Taxpayers
+have an interest in economical use of their tax money, to which
+duplicated or flawed efforts to create research software -- in contrast to software reuse -- is contrary. A subset of this group may be interested in sustainable, i.e., re-usable and understandable, software as part of citizen
+science.
+
+
+\textit{\Gls{DomainResearchers}} benefit from better software to do more, better, and faster research. Sustainable research software supports this through validated functionality (e.g., correct algorithms), the potential for reuse, and general availability. Sustainable software also potentially simplifies building upon previous research results by re-using the involved software to produce additional data or by extending the software's functionality.
+In light of recent updates to definitions of good research practice~\cite{DFGcode}, sustainable research software also allows domain researchers to comply with guidelines and best practices. Additionally, using a software that is sustainable enough to
+establish itself as a standard tool in a field signifies inclusion in a research
+community. Less directly, researchers may benefit from the existence of sustainable standard tools as they yield standard formats, which in
+themselves facilitate reuse of research data.
+
+\textit{\Gls{RSE}} have an intrinsic interest in
+sustainable research software. They create better software for research, which enables more and better research. RSEs have an inherent interest in developing and working with high quality software, as part of professional ethics as well as good research practice. RSEs build their reputation on high quality software and software citation~\cite{smithSoftwareCitationPrinciples2016,druskatSoftwareDependenciesResearch2019}, which will open up new career paths.
+Finally, for RSEs, creating sustainable research
+software is part of an attractive, intellectually challenging, and
+satisfying work environment.
+
+\textit{\Gls{ScientificLeaders}} as well as \textit{\gls{RPO}} mainly focus on the economic aspects and management of research, i.e., available funds, people, and time employed to optimize research output.
+Both need to make sure that their employees continually improve their qualification and generate impact to improve their standing in the various research communities and ensure continued funding.
+Overseeing and enabling the creation of sustainable
+research software advances their visibility in the field and makes
+their research endeavors both more future-proof and more easily
+traceable, reproducible, and verifiable and thus more likely to attract additional resources (including human resources). \textit{\Gls{RPO}} can additionally benefit from sustainable research software if it can be reused in other areas, creating synergies between different research disciplines.
+These synergies typically free resources that can then be used in areas other than software development and maintenance.
+Finally, organizations can gain
+highly competitive positions in terms of funding and hiring opportunities, as well as a reputation for being on the cutting edge of research, through early adoption of research software
+engineering units, and the implementation of sustainable research software
+policy and practice.
+
+\textit{\Gls{RFO}} have inherent interest in -- and directly benefit from -- the existence of sustainable research software as it allows them to direct more resources towards actual research (rather than recreation of software) and increase return on investment.
+At the same time, funding organizations can create incentives for sustainable software by imposing policies that reflect the necessity of research software sustainability and creating respective funding opportunities.
+
+\textit{\Gls{GeopoliticalUnits}} have a strategic interest to be independent of other geopolitical units to ensure that research can continue seamlessly regardless of geopolitical developments and ensuing embargoes on information flow.
+Reuse of sustainable software additionally frees up funding for uses other than software development.
+Well-established, sustainable software systems can also attract researchers and companies in the research and technology sector.
+
+\textit{\Gls{Libraries}} benefit from sustainable research software, as it will undergo a formal publishing process and be properly described in its metadata. Libraries can extend their portfolio beyond text-based research objects and stake claims as organizations harnessing the digitalization of research. In turn, they help to increase visibility and discoverability for research software through their services and advance the competitiveness of their organization or geopolitical unit. In addition, libraries also use research software and would thus benefit directly from a more sustainable research software landscape. Last but not least, by using FLOSS research software, libraries could avoid expensive licenses and often insufficiently adapted commercial software.
+
+\textit{\Gls{InfrastructureUnits}}, such as supercomputing facilities and
+university computing centers, benefit from sustainable software as it makes their daily work in terms of software installation and user support easier. Additionally, they can position themselves at the forefront of research by bundling expertise on the creation and maintenance of sustainable research software and installing research software engineering teams.
+
+\textit{\Gls{Industry}} benefits from sustainable research software, as the
+process of creating and maintaining research software produces a highly-skilled workforce.
+Depending on the employed licensing model, sustainable research software can also be adopted by industry partners to reduce cost in corporate research and development.
+Helping to sustain research software may also enable positive outreach for companies across industry and into society.
+
+\textit{\Gls{OSDevs}} can get involved in research software, even if they
+are not employed by a research institution. This can help them get in contact with
+other developers in the field and may potentially lead to collaborations or job opportunities in research based on this extended experience.
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{How to Decide Which Software to Sustain?}
+\label{sec:selection}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+% Axel Loewe (Moderation) axel.loewe@kit.edu, Hartwig Anzt, Franziska Appel (appel@iamo.de), Lutz Brusch (lutz.brusch@tu-dresden.de), Peter Ebert (peter.ebert@iscb.org), Stephan Fuchs (fuchss@rki.de), Rudolf Weeber (rudolf.weeber@icp.uni-stuttgart.de)
+\subsection{Requirements and Challenges}
+The sustained funding of all existing software efforts is not only impossible but would risk to overly splinter the community and eventually become counterproductive to the efficiency of the research community. Therefore, it is important to agree on a list of transparent criteria that qualify a software product for sustained funding.
+We recognize that defining research software engineering criteria for software evaluation will also lead to activities aiming at optimizing scores to achieve these criteria. Hence, the criteria have to be designed such that all score-pushing effort truly advances the value of the software. Criteria that can be manipulated without effectively adding value, i.e., wasting resources, should be excluded.
+The list of criteria presented in this chapter could be the basis for a structured review process that facilitates an unbiased evaluation of software tools from various fields. Therefore, this list must be general enough to be applied to research software from various research disciplines while also respecting differences between fields (e.g. citation rates between humanities and life sciences). The challenge to do justice to a wide spectrum is e.g. reflected by suggesting criteria comprising different levels~\cite{ChueHong2014}.
+One of the major challenges in the endeavor to define a selection scheme for sustainable funding of research software is to organize a fair and transparent review process. We believe that it is important that the review process is conducted by experts, or teams of experts, that have a strong background both on software engineering as well as on the domain-specific aspects, the latter because certain criteria often exist on a spectrum that is most likely shaped by the specific demands of the respective research community.
+
+\noindent\vsepfbox{
+ \parbox[]{\dimexpr\columnwidth-3\fboxsep-2\fboxrule\relax}{
+ Kim’s PI is happy because Kim writes a longer section on \emph{hal9k} for the final project report and provides a software management plan alongside it, which ticks off a box in the template that the PI had previously worried about. The PI does not want to let Kim go and instead offers her to be co-PI on a follow-up project to test new methods on the data, and integrate them into \emph{hal9k} as well. They are positive that such a project proposal has a good chance to be funded, as they can show impact of their first project via their university's current research information system (CRIS) and through the number of citations of \emph{hal9k} and the publications for which it was used. While they write the proposal, the faculty dean approaches the two to tell them that based on Kim’s work, they will now negotiate about two new RSEs for the central RSE team with the university’s provost for research and plan to consider candidates with a background in researchonomics.
+ \\
+ When they get the decision letter from the research funding organization, Kim and her co-PI are happy to learn that their new project has won the grant. The reviewers specifically point out the value of extending Kim’s Boa library to include the proposed new methods, as well as the significant reuse potential of \emph{hal9k} for the researchonomic community as a direct effect of its well-engineered architecture and modularity. Additionally, they stress that it was really easy to evaluate the software due to the comprehensive test suite, documentation, and example data. In fact, during the first month of the new project, three other researchonomic research projects approach them to ask whether they can contribute to Kim’s library and offer to fund six months of RSE work for this. Kim uses this money to also parallelize \emph{hal9k} together with the RSEs and works with her university’s computing center to offer it as a standard tool for researchonomic supercomputing.
+ }
+}
+\\ \\
+\noindent While an assessment based purely on quantitative metrics would allow for seemingly objective comparisons between programs, the definition of valid and robust quantitative metrics that can be evaluated with reasonable effort is a major challenge. On the other hand, a structured qualitative assessment with scores for groups of criteria can provide a middle ground.
+It is clear that both preparing an application for a review against these criteria from the applicant side as well as the evaluation by the reviewers requires significant effort. We believe that the added value significantly outweighs the investment but appropriate resources need to be factored in.
+Sustainability of research software should be considered from the beginning for new projects. The criteria listed below, or a subset such as the ``good enough'' practices proposed by Wilson et al.~\cite{Wilson2017}, are valuable throughout the development process (including early phases) for almost all types of research software applications. ``Classical'' research funding schemes should acknowledge the need to follow best practices during the development of new software and allow factoring in appropriate resources to design and implement for sustainability. In this section, we focus on the question which software to support in dedicated sustainability funding schemes. For such sustained funding, only software in application class 2 or 3 as defined by Schlauch et al.~\cite{https://doi.org/10.5281/zenodo.1344612}, i.e., with significant use beyond personal or institutional purposes, would likely be considered.
+Excellence as reflected in funded projects, publications, and software adoption, i.e., backing by a community, should be considered during selection. Nevertheless, we believe a good scheme should strike a balance between consolidating the field to few well-established software packages on one side and stimulating innovation and cooperation promoting diversity in terms of more than one monopolistic package on the other side.
+Last but not least, there is an inherent conflict between the long-term goals of sustainability funding a software and the necessary reevaluation to monitor the state of the software over time.
+
+\subsection{Selection Criteria}
+Several evaluation schemes for research software have been proposed before and led to the formulation of first recommendations~\cite{katerbow2018,https://doi.org/10.2312/os.helmholtz.003}. Gomez-Diaz \& Recio suggested the CDUR scheme based on Citation, Dissemination (including aspects like license, web site, contact point), Use, and Research (output)~\cite{GomezDiaz2019}. Lamprecht et al. rephrased the FAIR data principles~\cite{Wilkinson2016} for research software~\cite{lamprechttowards}. Hasselbring et al. found that the adoption of FAIR principles is different between fields with an emphasis on reuse in computer science as opposed to a reproducibility focus in computational science~\cite{hasselbring2019fair}. Fehr et al. collected a set of best practices for the setup and publication of numerical experiments~\cite{Fehr2016}. Jim\'{e}nez et al. boiled it down to four best practices~\cite{Jimnez2017}: public source code, community registry, license, and governance. Hsu et al.~\cite{Hsu2019} proposed a framework of seven sustainability influences (outputs modified, code repository used, champion present, workforce stability, support from other organizations, collaboration/partnership, and integration with policy). They found that the various outputs are widely accessible but not necessarily sustained or maintained. Projects with most sustainability influences often became institutionalized and met required needs of the community~\cite{Hsu2019}. In the field of open source software, the CHAOSS (Community Health Analytics Open Source Software) project has developed metrics to evaluate sustainability~\cite{CHAOSS}. One objective of CHAOSS is to automatically generate project health reports based on software that evaluates the metrics, with most of the metrics already covered. The UK Software Sustainability Institute (SSI) suggested both a subjective tutorial-based and a more objective criteria-based software evaluation scheme~\cite{SSIevaluation}, the latter being available as an online form~\cite{SSIsustain}. ROpenSci~\cite{ROpenSciDevGuide} provides software reviews for R developers, which have been very successful in the community. The review criteria of the Journal of Open Source Software (JOSS)~\cite{JOSSReview} focus on the aspects license, documentation, functionality, and tests. This list of essential items should be fulfilled by all research software that wants to be considered not only for publication but also for sustained funding.
+
+We drew inspiration from all these works and suggest a set of criteria to base reviews for sustainable funding on. This set comprises mandatory, hard criteria that we think have to be fulfilled across domains (highlighted in italics) and additional desirable, soft criteria that can be implemented to different degrees depending on the use case and domain-specific software development requirements. The soft criteria should be evaluated in a structured way by the reviewers with a specific response for each section rather than one running text.
+The fact that most of these criteria will be considered in any software management plan (SMP,~\cite{SSImanage}) highlights its importance for sustainable research software.
+
+\subsubsection{Usage and Impact}
+Requirements qualifying software for sustained funding are
+\begin{inlinelist}
+ \item its \textit{use beyond a single research group},
+ \item the scientific relevance and validity of the software documented in \textit{at least one peer-reviewed scientific publication}. Ideally a paper also describes the scope, performance, and design of the software.
+ \item The use of the software in publications is a measure of impact but quantitative assessment brings about additional challenges~\cite{Li2019}. Therefore, other, potentially domain-specific, impact measures, such as influence on policy and practice as well as use in other software and products should be considered as well to evaluate relevance for academia and society. Considerable attendance at training and networking events can be considered as a proof of use as well.
+ \item A \textit{market analysis} needs to show that the software is important to a user base of relevant size and either unique or one of the main players in a field with several existing solutions. Geographical or political aspects can be considered as well, e.g. to support the maintenance of a European solution. A convergence process of (parts of) a research community towards a specific software stack, i.e., documented transition of several research groups to a common software, would be a strong indicator of impact.
+ \item As community uptake and benefits are a central goal of sustained software funding, outreach and \textit{appropriate training material} for new users of the software are essential.
+\end{inlinelist}
+
+\subsubsection{Software Quality}
+As mandatory criteria of software quality that have to be fulfilled, we consider
+\begin{inlinelist}[resume]
+ \item the \textit{public availability of the source code} in both a code repository and an archive (for long term availability), developed using
+ \item \textit{version control} with meaningful commit messages and linked to an issue tracker (ideally maintained, but at least mirrored on a public platform).
+ \item \textit{Documentation} of the software needs to be publicly available comprising both user documentation (requirements, installation, getting started, user manual, release notes) and developer documentation (with a development guide and API documentation within the code, e.g. using Doxygen)~\cite{Lee2018}.
+ \item The \textit{license} under which the software is distributed must be defined. Publicly funded software
+should be published under a Free/Libre Open Source Software (FLOSS) license
+by default, although exceptions to this might apply (e.g. excluding commercial use).
+\item \textit{Dependencies} on libraries and technologies must be defined.
+\end{inlinelist}
+
+We acknowledge that some additional criteria have to be evaluated under consideration of the research domain. These comprise
+\begin{inlinelist}[resume]
+ \item the availability of examples (comprising input data and reference results),
+ \item mechanisms for extensibility (software modularity) as one aspect of software architecture~\cite{Venters2018} and
+ \item interoperability (APIs / common and open data formats for input and output),
+ \item a test suite (including at least some of the following: unit tests, regression tests, integration tests, end-to-end tests, performance tests; ideally run in an automated fashion in a continuous integration environment),
+ \item tagged releases (considering their frequency, and availability for end users in terms of binary packages for major operating systems, or availability via package managers or containers),
+ \item no large-scale re-implementations for functionality for which good solutions already exist. Many of these aspects require appropriate infrastructure (see page \pageref{sec:infrastructure}).
+\end{inlinelist}
+
+\subsubsection{Maturity}
+The research software applying for sustained funding must have already reached a certain level of maturity (typically class 2 or 3 as defined by Schlauch et al.~\cite{https://doi.org/10.5281/zenodo.1344612}). A mandatory requirement is
+\begin{inlinelist}[resume]
+ \item a comprehensive and up-to-date \textit{software management plan}~\cite{SSImanage}. The software should
+ \item be maintainable with an appropriate amount of resources as detailed in a sustainability section of the software management plan. The software has
+ \item a well maintained website with a clearly defined \textit{point of contact} and a communication channel to inform users about news regarding the software such as new releases. Besides an active user community, sustainable software requires
+ \item a group of developers (i.e., definitely \textit{more than 1 developer}) documented, e.g. by contributions to the code base or participation in documented, public discussions or issue tracking. Another criterion is
+ \item whether potential contributors are invited to participate in a clearly defined process (e.g., a CONTRIBUTING document). The group of developers should have defined a governance model for their project and easy ways for users to provide input regarding their needs.
+\end{inlinelist}
+
+\subsection{Recommendations}
+Given the diversity in the software technology landscape, and the domain-specific software development cultures~\cite{johanson2018software}, some of the above-mentioned criteria have to be evaluated against domain-specific requirements. Therefore, we highly recommend to base the selection process on a combination of
+\begin{inlinelist}
+ \item a software quality-based review and
+ \item a domain-specific scientific review.
+\end{inlinelist}
+In particular, the former should be ideally performed by a central institution (e.g. at funding bodies or other independent agencies such as a software sustainability institute). Only criteria for which improvement truly advances the value of the software should be considered in evaluation schemes, i.e., no criteria that can be gamed.
+After rejecting software not fulfilling the mandatory criteria in a first stage of the review process, the second stage of the selection process should be realized as a transparent procedure ideally allowing the reviewers to interact with the PIs of the software (e.g. remote meetings, forum-like discussions) and put the software quality and development efforts into the domain-specific context. The outcome of this second stage should be a structured review assessing each criterion explicitly and a rating for each of the dimensions \emph{Usage and Impact, Software Quality, and Maturity}.
+For sustained software funding, it is important to audit the performance, relevance, impact, progress, and level of sustainability of funded software after reasonable time frames. Such a reevaluation should revisit the criteria under consideration of evolving software technology and scientific standards, without requiring a completely new proposal being submitted. We envision funding periods of 5 years to provide sufficient security for funded software projects, while allowing for adaptation of the portfolio of funded software to novel research directions and community needs.
+Failure to meet the reevaluation criteria should lead to the decision to phase-out sustainable funding. The phase-out process may come with a 1-year funding program based on a consolidation plan with clear goals regarding the archiving and preservation of the software, documentation, and all existing resources.
+
+
+\section{Who Sustains Research Software?}
+\label{sec:who_sustains}
+
+%\hl{refer to the TU Delft Strategic Open Science Plan}~\cite{delft}\hl{as an ambitious best practice example? Covering aspects professional profile, education, and recognition}
+Research relies on software and software relies on the people developing and maintaining it.
+Sustainable research requires sustainable software, and this in turn requires continuity for those who develop and maintain it.
+
+\subsection{Requirements}
+Possibly the most important demand is the need for an increase in \textit{recognition and awareness} of research software as a first class citizen in research~\cite{Akhmerov2019,ChueHong2019,https://doi.org/10.2312/os.helmholtz.003}.
+For sustainability of research software, long-term commitments of the respective software leads are crucial, but very few \textit{professional RSE profiles} currently exist.
+In consequence, it is essential to create career paths for RSEs that are attractive and include permanency perspectives.
+While creating permanent positions in the German academic system below the faculty level is an actively discussed topic overall~\cite{BayreutherErklaerung}, we specifically focus on the needs originating from the development and maintenance of research software here.
+
+As already mentioned, research software development not only requires domain expertise, but also software development \textit{education, skills, and competencies}.
+Currently, most of the domain researchers developing and maintaining domain-specific software technology never received professional training on software development~\cite{Wilson2014,SSIanalysis}.
+To enhance the productivity and sustainability of computer-based research, it is essential to integrate software development training into the education of domain researchers.
+
+Currently, a significant portion of the existing research software is developed by individuals or in small groups, primarily to serve their own requirements.
+This situation is unsatisfying in terms of collaboration and inefficient in terms of several groups spending resources on generating similar or even the same functionality.
+To enable and promote synergies, it is important to allocate resources for research software development and to build \textit{communities}, as described in~\cite{Katz19community}.
+
+\noindent\vsepfbox{
+ \parbox[]{\dimexpr\columnwidth-3\fboxsep-2\fboxrule\relax}{
+ Kim wants to broaden her research portfolio within researchonomics and applies for postdoctoral positions at other institutions.
+ Her library \emph{hal9k} is growing in popularity within researchonomics, and she wants to continue working on it.
+ As her university has adopted an open science policy, \emph{hal9k} is free software under a Free/Libre Open Source Software (FLOSS) license, and Kim is free to continue her work on the library even after moving away from UofA.
+ Due to her involvement in the creation of \emph{hal9k} as well as her previous success in attracting funding, Kim has the choice between multiple, attractive positions and decides to move to the researchonomics group at Eden University (EdU).
+ She has already extended \emph{hal9k} in multiple directions in the past and plans to continue this work at EdU.
+ Her group leader at EdU would like to continue funding her but due to a law called the Fixed-term Research Contract Bill, EdU is not allowed to extend her contract, and neither third-party funding for her own position nor a permanent position are available.
+ After having developed a now widely-used research tool, several publications in software and paper form, as well as having attracted funding, Kim finds herself looking for a job again.
+ }
+}
+
+\subsection{Challenges}
+We are currently facing a \textit{lack of awareness} for the importance of research software as discussed above. Moreover, there is \textit{little recognition} for the efforts put into software development and maintenance.
+In consequence, software development in academic settings is mostly considered as a means to an end and sustainability is often not considered in project planning and grant proposals and contributes little to progressing research careers~\cite{Scienceguide,DORA}.
+The main challenge here is the continued use of metrics that primarily leverage traditionally published articles and article citation numbers.
+
+In academia, developers of research software are typically domain researchers, and in particular if new areas are explored, the software development process itself has research character.
+Obviously, developing research software requires not only domain knowledge but also software development skills, and the researchers leading the software development process are often domain experts with substantial software development experience, making them extremely valuable members of the research community.
+However, the current academic system in Germany does not provide a defined \textit{RSE role}.
+Limited-term positions are, at least currently within the main German academic system, often effectively the end of their career path, sometimes even a dead end.
+The challenge here is the lack of available permanent positions within the non-professorial academic faculty (``Mittelbau'') in Germany, compounded by a lack of access to
+these few permanent positions for RSEs due to the already mentioned lack of recognition for efforts concerning research software for faculty appointments within domain sciences.
+
+In order to develop sustainable software, researchers need to have the \textit{skills and expertise} to build software that is easy to maintain and extend~\cite{carver2016software}.
+However, most of the researchers are self-taught developers~\cite{Wilson2014,SSIanalysis}.
+Ideally, these skills have to be built into the domain science curricula, which could generally be done in two different ways (or a combination of them).
+One obvious solution attempt are additional courses that focus on these topics.
+The main challenge here is to decide which other topic(s) to possibly drop due to the limited volume of any given curriculum.
+A different approach is to incorporate software-related topics into existing domain science courses.
+While this would provide the benefit of show-casing the usage of specific software skills directly within the domain science, the challenge here is the amount of work necessary to change existing lecture material, let alone the need of the lecturers to acquire those skills themselves in the first place.
+
+As long as the necessary software skills within domain sciences are not yet wide-spread, building a network from those that have acquired relevant skills is difficult.
+\textit{Community} efforts, that concentrate on questions regarding research software, can help to fill this gap.
+Examples of such efforts include the Software Carpentries, national and international RSE societies (e.g., within Germany de-RSE e.V.).
+However, since research software is such an interdisciplinary topic, it is hard to get recognition and find funding within any specific discipline.
+As a result, existing communities often have to rely heavily on volunteers.
+This is challenging, because despite benefits to domain science, volunteers hardly receive recognition for their work ``back home'', i.e., within their domain, underlining again the importance of our first demand.
+
+\subsection{Recommendations}
+Increasing \textit{recognition and awareness} is a challenge that calls for both immediate action and perseverance. Nevertheless, some measures will likely show positive effects comparatively soon.
+
+Similarly to plans for research data management, funding agencies should request that applicants include considerations about how software developed in a project can be sustained beyond the end of the funded project. A follow up on these plans during and after the project lifetime, i.e., a dedicated software management plan, is crucial.
+
+Another recommendation is aimed at decision makers concerning recruitment for academic positions: broaden the definition of research impact beyond traditional scientific publications to also include other impactful results.
+%
+Not all researchers thinking of themselves as RSEs pursue a faculty position as their main career goal.
+However, permanent academic non-faculty positions are rare within the German academic system, also due to the lack of a defined \textit{RSE role}.
+We recommend research institutions to leverage the benefit of dedicated RSEs by establishing attractive long-term career options in the academic environment.
+%
+The long-term solution in order to gain sufficient software development \textit{skills} should be education that is included early in the career path, ideally already at the Bachelor level.
+For the time being however, efforts involving workshops and seminars that provide easy access to hands-on training on software-related questions should be promoted and supported as much as possible.
+
+It is important to provide an environment where \textit{communities} can form and flourish by allocating resources for research software development and for building communities around it~\cite{Katz19community,iaffaldano2019developers,Jimnez2017}.
+The identification with a community of like-minded people and personal action~\cite{dagstuhl} can lead to a permanent establishment of sustainable research software as a valuable research output.
+Thus, research institutions as well as funding agencies should not only be open-minded regarding existing volunteer organizations, but should actively promote the creation of such groups.
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{How can Research Software be Sustainably Funded?}
+\label{sec:funding}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%Bernhard Renard (bernhard.renard@hpi.de), Michael Bader (bader@in.tum.de), Bernd Flemisch (bernd@iws.uni-stuttgart.de), Florian Hohmann (fhohmann@uni-bremen.de), Matthias Katerbow (matthias.katerbow@dfg.de), Timo Ropinski (timo.ropinski@uni-ulm.de), Benjamin Uekermann (uekerman@in.tum.de)
+
+\noindent\vsepfbox{
+ \parbox[]{\dimexpr\columnwidth-3\fboxsep-2\fboxrule\relax}{
+ \emph{Hal9k} has grown into a widely used software in researchonomics, and Kim is proactively asked to apply for - and is subsequently awarded - a permanent RSE position at the institute for researchonomy at UofA, based on her work on the library. She works closely with the central RSE team, but mostly due to bureaucracy and the high demand for her library, Kim does not have enough time to maintain and further develop \emph{hal9k} alone anymore. Together with the dean she develops a course for the researchonomics curriculum which teaches data processing with \emph{hal9k}. As a lesson from her own career, she starts the course with sessions on the Hash shell, version control with Tig, Boa, and two whole sessions on basics of sustainable software development. This is very fruitful, and due to the implementation of a new research software funding scheme at UofA, Kim is able to hire one of the course students, who has shown great RSE skills, straight into a long-term position at her institute, where they focus on the maintenance and development of \emph{hal9k}, work with the computing center to support \emph{hal9k}-based supercomputing on a new, dedicated FGPA cluster, develop training materials for external users, and organize the yearly \emph{hal9k} users and developers conference. Kim gets to travel the world to visit researchonomics groups who are using \emph{hal9k}.
+ }
+}
+
+\subsection{Requirements}
+Sustainable funding for research software boils down to funding the four main pillars enabling sustainable software development:
+\begin{inlinelist}
+ \item Personnel with expertise in research software development;
+ \item Infrastructure for developing, testing, validating, and benchmarking research software, and distributed versioning systems for collaborative software development;
+ \item Training in software design and sustainable software development; and
+ \item Community management and events for creating synergies between research groups and software efforts.
+\end{inlinelist}
+
+\subsection{Challenges}
+Short-term engagement of (young) researchers raises the question of how to maintain a
+constant level of expertise within a developer team and prevent knowledge drain concerning domain knowledge and software engineering skills.
+Conversely, the permanent engagement of qualified personnel requires to offer career perspectives, especially due to the fact that academia competes with
+industry for the same people. A challenge specific to Germany is posed by the
+shortage of permanent positions and by the restrictions for temporary positions
+due to the German \emph{Wissenschaftszeitvertragsgesetz}~\cite{BMJVarbeit}.
+
+Sustainable software development requires hardware technology to develop, test, validate, and benchmark features in a continuous integration cycle. The challenge in this context is the persistent evolution of the hardware landscape. Hence, for creating an environment promoting sustainable software development, it is important to provide access to a wide hardware portfolio and to support a development cycle based on continuous integration.
+
+Expertise in sustainable research software development is a scarce resource, and training is heavily needed as one way of building up more expertise. However, while integrating interdisciplinary software engineering courses into the education curriculum can build up basic skills, some expertise is domain-specific and requires inter-institutional training activities. Furthermore, there exist no financial incentives for creating software-specific documentation and tutorials nor to provide other forms of support.
+
+While the creation of research software communities is one of the major assets in sustaining research software technology, promoting this process requires the installation of new funding instruments. Traditionally, research grants are limited to rather short time frames and support personnel, material, hardware, and to a limited degree also travel and research visits. Creating a research software community however requires funding for community and training events as well as ``virtual hardware'' such as webspace, versioning systems, task-managing systems, and compute cycles. These demands can hardly be met without third-party funding~\cite{Kuchinke2016,chang2007open,Aartsen2018,Gabella2018}.
+
+
+\subsection{Recommendation: Creation of Adequate Funding Schemes}
+
+Funding is a crucial factor for sustaining research software. Currently available sources and instruments are not adequately shaped for the challenges and solutions outlined above. We recommend actions on the individual, organizational, and national level.
+
+Existing project-focused funding instruments on the local, national, and international level need to be complemented with funding instruments specifically designed for research software development and sustained research software maintenance to make research software a first class citizen in the research landscape. For example, software projects enhancing research and fulfilling the sustainability criteria detailed in section~\nameref{sec:selection} on p.~\pageref{sec:selection} may be entitled for sustained funding as long as they live up to the standards and remain a central component of the research landscape.
+
+Computing centers and supercomputing facilities for research need to receive earmarked resources for the support of sustainable software development. This funding is necessary to provide continuous integration services, a hardware portfolio for development, testing and benchmarking software, as well as personnel for training domain researchers in software design and the proper usage of the services.
+
+The creation and maintenance of training materials for general research software engineering education and the software-specific documentation and tutorial creation needs to be reflected in funding opportunities. This can either happen by dedicating modules of research or software grants to providing support and the generation of training material, or by opening funding schemes focusing on interdisciplinary software development education. The latter may include research that looks at research software development as a process to analyze which measures, interactions, and team compositions make research software successful. Additionally, funding instruments fostering the formation of research software communities have to be established.
+\vfill\null
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\section{Which Infrastructure is Needed to Sustain Research Software?}
+\label{sec:infrastructure}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%Felix Bach (Moderation), Piush Aggarwal, Uwe Konrad, Miriam Mehl (miriam.mehl@ipvs.uni-stuttgart.de), Wolfgang Peters-Kottig, Alexander Struck (contact for editors: Alexander.Struck@hu-berlin.de), Philipp Thiele
+\noindent\vsepfbox{
+ \parbox[]{\dimexpr\columnwidth-3\fboxsep-2\fboxrule\relax}{
+ As the \emph{hal9k} community grows, so does the need for infrastructure. Kim and her team collaborate with the National RSE Consortium to set up \emph{hal9k} on the Consortium’s distributed TigHub instance, and organize world-wide access to it via the NRSEC-AAI federation. Going forward, the Consortium’s Research Software Hub - a registry and Software Heritage Archive-based~\cite{softwareheritage} long-term repository for research software on a national level - ingests \emph{hal9k} releases with complete metadata: citation metadata, the \emph{hal9k} provenance graph and computational environment information, ORCID iDs~\cite{ORCiD}, etc. and provides its own DOIs for versions under a concept (umbrella) DOI.
+ The community reviews all code and documentation changes that are contributed to \emph{hal9k} via the central TigHub, and the Hub’s CI system Alfred builds, tests, and pushes new releases automatically to the registered supercomputing clusters.
+ Especially the community efforts become better and more streamlined by the day, as research software development training is now offered as part of most curricula, and skilled RSEs are now much easier to find and hire by research institutions.
+ }
+}
+
+%% ----------------------------------
+\subsection{Project Management Tools}
+\label{sec:infrastructure:PM}
+%% ----------------------------------
+Research software is developed by individual researchers, in small teams within a single institution, or in larger teams distributed across multiple institutions. In particular if software development is distributed across institutions, there exists an urgent need for frameworks and tools enabling collaborative code development, software feature planning, and software management. As research software development typically includes bleeding-edge research and development that the researchers do not want to disclose for a certain time to preserve intellectual property, distributed research software development also needs a global Authentication and Authorization Infrastructure (AAI). We recommend the development and/or deployment of tools for distributed software development and software management as central research infrastructure. An important aspect in this context is the cataloging of research software to reduce the duplication of development efforts. This can efficiently be realized by promoting the registration of all research software with a unique identifier and developing a tool that allows to explore the research software landscape. Research software contributors should have an ORCID iD~\cite{ORCiD} to be uniquely identifiable and referable. While some funding for such tools and software repositories is emerging (e.g. the bio.tools catalogue of bioinformatics tools funded as part of the European ELIXIR project~\cite{bio.tools}), a standardized extension of such efforts to the RSE community as a whole is necessary. However, as the experiences from ELIXIR
+demonstrate, this is a non-trivial effort that requires significant dedicated
+and long-term funding.
+
+\subsection{Developer Training, Motivation, and Knowledge Exchange}
+As elaborated, training in sustainable software development is key to achieve sustainability in research software. At the same time, it is not clear how such training should be facilitated and institutionalized. Furthermore, for deriving software quality standards, evaluating the quality of software, and providing a code review service, central resources are necessary that individuals and groups in the research software landscape can draw from.
+
+We consider Software Carpentry and similar efforts like the creation of the Data Science Academy HIDA~\cite{HIDA} in the Helmholtz Association of German Research Centers helpful solutions to exchange and distribute knowledge. Local chapters of RSE groups and (inter-)national conferences will further foster networking and community building. We strongly recommend the creation of a national Software Sustainability Institute (involving funded positions to establish web platforms and training material) similar to the existing institute in the UK~\cite{UKSoftwareSustainabilityInstitute}, which serves as a national contact for all aspects related to research software. The UK SSI also publishes best practice guidelines~\cite{SoftwareSystemsDevelopmentLifeCycle_SDLC} for research software engineering.
+
+\subsection{Research Software Discovery and Publication}
+Proper software publication and possibilities for the community to find existing software solutions for a given problem are a prerequisite to optimally exploit synergies and avoid redundant development. However, we observe that today, many funding proposals lack a thorough state-of-the-art report of software that could possibly be reused. This is most often caused by insufficient information retrieval strategies, lack of knowledge about relevant repositories, and an abundance of locations where software is collaboratively developed and stored~\cite{Struck2018}. Discovery requires publication in a globally accessible location with appropriate metadata, e.g., Citation File Format (CFF)~\cite{CFF} and CodeMeta~\cite{CodeMeta}. Comprehensive metadata (e.g. contributors, contact, keywords, linked publications, etc.) and publishing platforms have to enable persistent citing, which in turn benefits research evaluation. Selection and curation of software (probably by a data/software librarian) for publication and discovery are certainly challenging.
+
+We consider GitLab or GitHub as collaborative working environments and repositories like Zenodo appropriate publication platforms, because the latter mint DOIs, allow versioning and are publicly funded for long-term access. GitHub, Figshare, and Mendeley Data are examples of commercial enterprises with business cases in the background, which leverage research results. Besides the aforementioned metadata standards, it is advisable to document source code, e.g., using MarkDown (with Doxygen tooling). Metadata and citations play a role in beneficial tools like PIDgraph, DataCite.org, CrossRef, which utilize Persistent Identifiers (PIDs) like DOIs.
+Another solution to discovery are (mostly) disciplinary software indices like swMATH~\cite{swMATH} or the Astronomy Source Code Library~\cite{ASCLnet} as well as language focused systems like CRAN~\cite{CRAN} for \textsf{R}. Most of them started as national endeavors and became platforms of global importance. For Germany, we assume that the Nationale Forschungsdateninfrastruktur (NFDI) will put effort into creating or supporting discovery platforms at a central point that ease information retrieval. At the same time, all stakeholders should be aware of and counteract potential institutional ``fear'' of losing ``their'' data, software, and intellectual property.
+
+Especially in interdisciplinary environments, it would be helpful to have access to a meta software repository index, similar to what re3data~\cite{re3data} does for research data repositories. We recommend the creation of such a meta index covering important (disciplinary) software indexes in order to ease discovery of relevant software locations. Evaluation of discovered software is an unsolved problem. Here, anonymous telemetry of usage may provide information for the selection of relevant software. Publishing software, their dependencies, and environment in containers may also ease evaluation and further reuse. These suggestions require significant investment in long-term infrastructure.
+When publishing research software it is recommended to make use of integration schemes like GitHub with Zenodo or local GitLab instances with publication platforms.
+Such indices and publication outlets may benefit national federated research indexing \& archiving systems, similar to the hierarchy of library catalogs~\cite{KVK}.
+
+\subsection{Archiving}
+Software preservation aims to extend the lifetime of software that is no longer actively maintained. There are different approaches, which vary in the effort required and the likelihood of success. Software archiving is one important aspect of software preservation: the process of storing a copy of a software so that it may be referred to in the future.
+The publication of a certain software version for reference in research articles requires simple ways to archive research software on a long-term basis. Furthermore, its integration with collaborative software development environments such as GitLab or GitHub and with publication repositories is needed to facilitate archiving of referenced software versions based on sustainable frameworks (e.g. Invenio~\cite{Invenio} for GitHub to Zenodo integration).
+
+A challenge for software archiving is the need to (ideally) preserve the runtime environment and all dependencies of the software. This could improve reproducibility, especially when running the software in its original state. If research data are needed to reproduce results, they should also be archived with the software or the publication. Specialized and unique hardware - like high performance computing resources - can be part of the runtime environment, which may not be accessible in the future. To overcome this, an emulation of hardware may be a (challenging) solution. Emulation involves the encapsulation and distribution of the complete hardware and software stacks, including the operating system and driver interdependencies. This can result in intellectual property issues when offered as a service.
+
+There are both local and global approaches to software conservation. One solution to keep the software in an executable state by preserving its context and runtime environment is to use containers such as Docker.
+However, to archive the Docker containers, additional metadata should be added and stored with the software in an archive container format that allows exchange between repositories and exit strategies, such as the BagIt container format~\cite{kunze2018bagit}. Application or platform conservation is also achieved by conservational efforts where unmaintainable (virtual) machines are sandboxed to keep the platform in a secure but running state.
+Another threat is losing project repositories on global platforms like Github or BitBucket. Here, global platforms like Software Heritage~\cite{swHeritage} harvest those repositories and prevent loss by long-term archiving.
+
+
+\section{Legal Aspects}
+
+\noindent\vsepfbox{
+ \parbox[]{\dimexpr\columnwidth-3\fboxsep-2\fboxrule\relax}{
+ More and more industrial partners enter the \emph{hal9k} community, and they bring their lawyers. Together with UofA’s research software task force, the RSE team, the researchonomy institute, the corporate lawyers, and community representatives, Kim decides to create a foundation to govern \emph{hal9k} and its environment: the Fullest Possible Use Foundation for Open Researchonomy, funded by the Ministry of Research and Education and a consortium of corporate partners. As a first step, they re-license \emph{hal9k} under the OSI approved MIT license.
+ }
+}
+
+%Gunnar Seemann (Moderation, Gunnar.Seemann@universitaets-herzzentrum.de), Elke Achhammer (elke.achhammer@tum.de), Sven Friedl (sven.friedl@bihealth.de), Maximilian Funk (maximilian.funk@gv.mpg.de), Fabian Rack (fabian.rack@fiz-karlsruhe.de), Stefan Unger (stefan.unger@julius-kuehn.de)
+
+
+%\subsection{Demands}
+\noindent A common situation in research software creation is that the developer has no knowledge or awareness of legal aspects and therefore did not consider them early enough. Thus, we think the main legal demands for research software development are raising awareness and empowering all levels of responsible persons in academia (from researcher and RSEs over PIs to research performing organizations and research funding organizations) in legal aspects. This will hopefully lead to a general legal certainty before, during, and after the research software development process and thus enable better options for collaborations between universities, non-commercial research institutions, and other national or international partners. Legal aspects always have to be considered regarding the relevant jurisdiction. Though similar issues arise in all jurisdictions, the following will focus on the European and specifically German legal framework.
+
+\subsection{Challenges and Clarifications}
+\subsubsection{Clarification of Rights}
+Software development is a creative activity. The main relevant law governing legal aspects is therefore the copyright law. It regulates the rights and obligations of the parties involved. Chapter 8 of the German Act on Copyright and Related Rights (UrhG) contains specific provisions applicable to computer programs and is based on the EU computer programs directive. Copyright law protecting the creator of software in similar ways exist in nearly all legal systems. It is important for the identification of rights that software, in the sense of (German) law, includes not only the source code but also the design materials~\cite{BMJVurheber69a}. The challenge in the use, distribution, and commercialization of software is to determine the chain of rights and to identify all right holders. The owner of the copyright is not necessarily the owner of the right of use. For Germany, the Copyright Act regulates the rights for employment relationships~\cite{BMJVurheber69b}. In such cases, the right of use is automatically transferred to the employer. This means that in most cases of employed software developers and research staff, the institution holds the rights of use for the software work. This is not automatically the case for students, freelancers, and individual external cooperation partners. Employment and service contracts with contributors could contain regulations regarding the transfer of rights of use. For researchers who conduct free research not subject to directives, in Germany the constitution guarantees freedom of research so that the rights of use for their work remains initially with the natural person. In addition to the rights of the people directly involved, other rights of third parties may also be relevant. Existing source code (e.g., other Free/Libre Open Source Software (FLOSS)), external libraries, and contributions from institutional cooperation partners are published and provided under certain licenses and their conditions must be observed (which, due to incompatibilities even among FLOSS licenses,
+may well mean that individually reusable pieces of software cannot be
+reused together or in a new context). The nature of research careers often brings additional complications to the chain of rights. It happens that researchers take their software with them when they change institutions and develop it further during their career. Here, the former employer may be entitled to some rights of use. In third-party funded projects, in particular with industry but also with public funding, rules regarding rights of use are often defined. Last but not least, the software can also be affected by other (intellectual) property rights such as patents or trademarks. Software itself is usually not patentable but it may implement a technical invention covered by patents. When using or distributing such software, an additional matching patent license may be necessary. Licenses exist (for example: GNU GPL v3) which automatically grant related patent licenses while using the software license. That should be considered when exploitation of the patent is planned.
+
+\subsubsection{Liability}
+Issues of warranty and liability for faulty software must be taken into account. We consider the possibilities of contractual limitation of liability in licenses. Full exclusions of liability are generally invalid in the German law. Limitations of liability usually depend on the form of distribution: The limitation options are larger if the rights of use are granted free of charge, e.g. provision ``as is'' as defined in the BSD 3-clause license.
+
+\subsection{Ideas for Solutions}
+In order to meet the legal challenges mentioned, it is absolutely necessary for the software developer (team) to document the rights chain comprehensively during the software development (see, e.g., supplementary material). Contributions of individual persons must be traceable and their (labor law) status must be named. At best, contracts with rules on the transfer of rights of use should be concluded before work begins. Declarations of assignment of rights can be made for existing works. License conditions for external contributions must be evaluated with regard to further rights of use and possible sub-licensing. Contracts and funding conditions must be conscientiously documented and analyzed with regard to rules on rights of use. In case that different parts of the software are based on different conditions and rights of third parties, individual modules of the new software could be published under different licenses and merged accordingly.
+
+A national research software sustainability institute could be established. This institute supports local research software task forces and thereby respective researchers and research teams in the licensing of research software and related legal issues. For this purpose, a legal help desk will be set up, to which all members of their respective research performing organization can apply. If researchers want to publish the research software under a Free/Libre Open Source Software license, the organization could bundle the necessary rights beforehand. This is particularly useful when teams of researchers, often international, write software. In addition, the sustainability institute may serve as a one-stop-shop for the licensing of research software.
+
+\subsection{Recommendations}
+We see it as an essential part of the sustainability of research to enable the free distribution of research software. There are a variety of open source software licensing models (ranging from permissive to copyleft; for further information, see~\cite{ifrOSS,tldrlegal,morinQuickGuideSoftware2012}). The use of an FSF- or OSI-approved FLOSS license for example would enable a truly free model and also reduce legal issues. We recommend that research funding organizations such as the DFG discuss if they expect publishing all funded software under these licenses, following the paradigm of ``public money, public code''~\cite{publiccode}.
+
+\begin{figure}[tb]
+ \centering
+ \includegraphics[width=\linewidth]{tree_sustainable_software}
+ \caption{\textbf{Decision tree for contributors}. This tree helps to figure out whether the academic institution where the software is developed owns the intellectual property (copyright).}
+ \label{fig:tree1Article}
+\end{figure}
+
+Also for legal aspects, we believe it is important that all (German) research performing organizations install a research software task force, especially since the new DFG Code of Conduct~\cite{DFGcode} was released. Besides organization and bundling of technical and infrastructural support for local RSEs and researchers (see previous sections), this group should organize a local legal help desk, organize educational offers e.g. for the legal topics presented, and (if not implemented yet) develop the software policy of the research performing organization. As an example, with the help of on-boarding processes performed by the research software task force, RSEs should be able to keep the clearance of rights as simple as possible right from the start. One possibility how local legal help desks could structure their work is shown in the decision tree in Fig.~\ref{fig:tree1Article}. A more complete suggestion for decision trees for both legal help desks and interested RSEs can be found in the supplementary material. We suggest that the local task forces build a network with the other research performing organizations for exchange of ideas but also for generating a bottom-up strategy to organize RSE standards for Germany and beyond and possibly be the origin of the aforementioned software sustainability institute.
+
+
+\section{Conclusions}
+% -- Hartwig: Please check whether I include all aspects in the rewritten conclusions. I tried to make it more concise, and give clear advice to the readers (funding bodies)
+We find that the research software ecosystem is notoriously lacking resources despite its strategic importance. If funding and support does not improve, the success story of science based on academic research software may be at stake.
+We recommend the installation of infrastructure that enables sustainable software development including platforms for collaboration, continuous integration, testing, discovery, and long-term preservation.
+We suggest the establishment of a nationwide institution similar to the Software Sustainability Institute (SSI) to provide project consulting and code review services as well as sustainable software development training. We think that sustainable software development should become an integral component of the universities' teaching curriculum.
+We encourage the research funding bodies to reflect the licensing models for academic software development, and to decide whether the ``public money, public code'' paradigm justifies the requirement that all publicly-funded software has to be publicly available under a Free/Libre Open Source Software (FLOSS) license.
+Ultimately, we strongly advise the implementation of funding schemes for sustainably supporting the development and maintenance of research software based on clear and transparent criteria, for creating incentives to produce high quality community software, and for enabling career paths as research software engineer (RSE).
+
+\section{Declarations}
+
+\subsection{Glossary}\label{subsec:glossary}
+
+% \printglossaries
+\printnoidxglossaries
+
+% If abbreviations are used in the text they should be defined in the text at first use, and a list of abbreviations should be provided in alphabetical order.
+
+%\subsection{Ethical Approval (optional)}
+
+%Not applicable
+
+%Manuscripts reporting studies involving human participants, human data or human tissue must:
+
+%\begin{itemize}
+%\item include a statement on ethics approval and consent (even where the need for approval was waived)
+%\item include the name of the ethics committee that approved the study and the committee's reference number if appropriate
+%\end{itemize}
+
+%Studies involving animals must include a statement on ethics approval and have been treated in a humane manner in line with the \href{http://www.nc3rs.org.uk/arrive-guidelines}{ARRIVE guidelines}.
+
+%See our \href{https://academic.oup.com/gigascience/pages/editorial_policies_and_reporting_standards}{editorial policies} for more information.
+
+%If your manuscript does not report on or involve the use of any animal or human data or tissue, this section is not applicable to your submission. Please state ``Not applicable'' in this section.
+
+\subsection{Consent for Publication}
+
+Not applicable
+
+%If your manuscript contains any individual person's data in any form, consent to publish must be obtained from that person, or in the case of children, their parent or legal guardian. All presentations of case reports must have consent to publish. You can use your institutional consent form. You should not send the form to us on submission, but we may request to see a copy at any stage (including after publication). Please also confirm you have followed national guidelines on data collection and release in the place the research was carried out, for example confirming you have Ministry of Science and Technology (MOST) approval in China.
+
+% If your manuscript does not contain any individual person's data, please state ``Not applicable'' in this section.
+
+\subsection{Competing Interests}
+The authors declare that they have no competing interests.
+
+% All financial and non-financial competing interests must be declared in this
+% section. See our
+% \href{https://academic.oup.com/gigascience/pages/editorial\_policies\_and\_reporting_standards}{editorial
+% policies} for a full explanation of competing interests. Where an author gives
+% no competing interests, the listing will read `The author(s) declare that they
+% have no competing interests'. If you are unsure whether you or any of your
+% co-authors have a competing interest please contact the editorial office.
+
+
+\subsection{Funding}
+The authors thank the DFG for funding a meeting (\textit{Rundgespr\"{a}ch}, grants LO
+2093/3-1 and SE 1758/6-1) % TODO Translate according to DFG terminology
+during which the initial draft of this paper has been created. We are particularly grateful for the support from Dr.\ Matthias Katerbow (DFG).
+
+This work was additionally supported by Research Software Sustainability grants funded by the DFG~\cite{DFGfunded}:
+%\begin{itemize}
+ Aggarwal: 390886566; PI: Zesch.
+ Appel: 391099391; PI: Balmann.
+ Bach \& Loewe \& Seemann: 391128822; PIs: Loewe / Scholze / Seemann / Selzer / Streit / Upmeier.
+ Bader: 391134334; PIs: Bader / Gabriel / Frank.
+ Brusch: 391070520; PI: Brusch.
+ Druskat \& Gast: 391160252; PI: Gast / L\"udeling.
+ Ebert: 391137747; PI: Marschall.
+ Flemisch \& Hermann: 391049448; PIs: Boehringer / Flemisch / Hermann.
+ Hohmann: 391054082; PI: Hepp.
+ Goth: 390966303; PI: Assaad.
+ Grad \& Weeber: 391126171; PI: Holm.
+ Kutra: 391125810; PI: Kreshuk.
+ Mehl \& Uekermann: 391150578; PIs: Bungartz / Mehl / Uekermann.
+ Peters-Kottig: 391087700; PIs: Gleixner / Peters-Kottig / Shinano / Sperber.
+ Raters: 39099699; PI: Herwartz.
+ Reina: 391302154; PIs: Ertl / Reina.
+ Muth \& Renard: 391179955; PIs Renard / Fuchs.
+ Ropinski: 391107954; PI: Ropinski.
+%\end{itemize}
+
+
+%% TODO: Register all the funds in FundRef (Perhaps the publisher does this?)
+% All sources of funding for the research reported should be declared. The role of the funding body in the design of the study and collection, analysis, and interpretation of data and in writing the manuscript should be declared. Please use \href{http://www.crossref.org/fundingdata/}{FundRef} to report funding sources and include the award/grant number, and the name of the Principal Investigator of the grant.
+
+
+\subsection{Author's Contributions}
+We are a group of software-providing researchers, RSEs, and infrastructural as well as legal supporters. Initially, a group of representatives of funded projects of the first DFG sustainability call~\cite{DFGfunded} met during the first German RSE conference (deRSE19)~\cite{deRSEconf} in June 2019 in a grass-roots workshop on sustainable research software addressing the software-based research community. During this workshop, we realized that a lot of valuable experience and good ideas are present in the group, and we decided to start working on this paper together with other interested practitioners. We followed the generous invitation of the DFG for the above-mentioned two-day meeting at the Robert Koch Institute in Berlin in November 2019 to sharpen the focus of this paper.\\
+The individual contributions of authors to this work are detailed below, following the \href{https://casrai.org/credit/}{CASRAI CRediT} (Contributor Roles Taxonomy):
+% TODO Authors, please add yourself to this list under Writing - original draft
+\begin{itemize}
+ \item \textbf{Conceptualization:} Anzt, Bach, Druskat, Loewe, Löffler,
+ Renard, Seemann, Struck
+ \item \textbf{Funding acquisition:} Loewe, Seemann
+ \item \textbf{Investigation:} Bach, Druskat, Loewe, Löffler, Renard,
+ Seemann
+ \item \textbf{Project administration:} Loewe, Seemann
+ \item \textbf{Visualization:} Unger, Friedl, Löffler
+ \item \textbf{Writing original draft:} Achhammer, Aggarwal, Anzt, Appel, Bach, Bader, Brusch, Druskat, Ebert, Flemisch, Friedl, Funk, Grad, Goth, Herrmann, Hohmann, Kutra, Linxweiler, Loewe,
+ Löffler, Muth, Peters-Kottig, Rack, Raters, Rave, Reina, Renard, Ropinksi, Schaarschmidt, Seemann, Struck, Thiele, Uekermann, Unger, Weeber
+ \item \textbf{Writing review \& editing:} Anzt, Appel, Bach, Bader, Brusch,
+ Busse, Chourdakis, Dabrowski, Druskat, Friedl, Fritzsch, Funk, Gast, Herrmann, Janosch, Loewe, Löffler, Rack, Reina, Reißig,
+ Renard, Seemann, Seibold, Struck, Thiele, Uekermann,
+\end{itemize}
+
+%\section{Acknowledgements}
+
+
+
+%\section{Authors' information (optional)}
+
+%n/a \hl{We should delete this section}
+
+
+
+%% Specify your .bib file name here, without the extension
+%\bibliographystyle{unsrtnat}
+\bibliography{references}
+
+\clearpage
+
+% remove comment environment to include supplementary material in preprint PDF
+\renewcommand{\thefigure}{S\arabic{figure}}
+\setcounter{figure}{0}
+\section{Supplementary Material}
+\subsubsection{Decision Trees for Legal Topics}
+The decision trees presented here shall help legal help desks and developers to identify risks regarding the mandate of the software. In a perfect world, one would address the legal aspects at the start of a project. It is crucial to know about these to create sustainable software. We strongly recommend to write a documentation of the answers and outcomes. Please keep in mind that only restrictions from copyright law are addressed. In some projects, you might also have to consider patents, trademarks etc.
+
+Before you can publish, use, and/or license a software, you have to check:
+\begin{itemize}
+ \item The policy of the institution (Fig.~\ref{fig:tree0})
+ \item The rights restriction imposed by the persons who ``create'' the software (Fig.~\ref{fig:tree1})
+ \item The rights restriction imposed by the environment (Fig.~\ref{fig:tree1})
+ \item If third-party code is incorporated (Fig.~\ref{fig:tree2})
+\end{itemize}
+
+We also built a tree for the scenario that you have to check for already existing software (Fig.~\ref{fig:tree3}).
+
+\begin{figure}[h!]
+ \centering
+ \includegraphics[scale=0.5]{tree_IP_policy}
+ \caption{\textbf{Policy}. This tree recommends to check closely any policies implemented in the software developers organization.}
+ \label{fig:tree0}
+\end{figure}
+
+\begin{figure}[h!]
+ \centering
+ \includegraphics[scale=0.5]{figures/tree_sustainable_software}
+ \caption{\textbf{Contributors}. This tree helps to find out whether the academic institution where the software development is located is the owner of the intellectual property (copyright).}
+ \label{fig:tree1}
+\end{figure}
+
+\begin{figure}[h!]
+ \centering
+ \includegraphics[scale=0.5]{tree_new_SW_development}
+ \caption{\textbf{Code history}. The code history tree points out tasks for projects that incorporate existing code.}
+ \label{fig:tree2}
+\end{figure}
+
+\begin{figure}[h!]
+ \centering
+ \includegraphics[scale=0.5]{tree_licensing}
+ \caption{\textbf{Licensing}. Depending on the distribution model, open access (OA) or open source software can be selected.}
+ \label{fig:tree3}
+\end{figure}
+
+If the outcome is a prohibition sign, we believe there is no other solution than to rewrite parts of the code or the whole code. If the outcome is a green checkmark, we believe you have the rights which you need to proceed. The other outcomes are self-explaining (e.g. go to legal department).
+
+
+\end{document}
diff --git a/001/references.bib b/001/references.bib
new file mode 100644
index 0000000..1e056bd
--- /dev/null
+++ b/001/references.bib
@@ -0,0 +1,1793 @@
+
+% Journals
+
+% First the Full Name is given, then the abbreviation used in the AMS Math
+% Reviews, with an indication if it could not be found there.
+% Note the 2nd overwrites the 1st, so swap them if you want the full name.
+
+ %{AMS}
+ @String{AMSTrans = "American Mathematical Society Translations" }
+ @String{AMSTrans = "Amer. Math. Soc. Transl." }
+ @String{BullAMS = "Bulletin of the American Mathematical Society" }
+ @String{BullAMS = "Bull. Amer. Math. Soc." }
+ @String{ProcAMS = "Proceedings of the American Mathematical Society" }
+ @String{ProcAMS = "Proc. Amer. Math. Soc." }
+ @String{TransAMS = "Transactions of the American Mathematical Society" }
+ @String{TransAMS = "Trans. Amer. Math. Soc." }
+
+ %ACM
+ @String{CACM = "Communications of the {ACM}" }
+ @String{CACM = "Commun. {ACM}" }
+ @String{CompServ = "Comput. Surveys" }
+ @String{JACM = "J. ACM" }
+ @String{ACMMathSoft = "{ACM} Transactions on Mathematical Software" }
+ @String{ACMMathSoft = "{ACM} Trans. Math. Software" }
+ @String{SIGNUM = "{ACM} {SIGNUM} Newsletter" }
+ @String{SIGNUM = "{ACM} {SIGNUM} Newslett." }
+
+ @String{AmerSocio = "American Journal of Sociology" }
+ @String{AmerStatAssoc = "Journal of the American Statistical Association" }
+ @String{AmerStatAssoc = "J. Amer. Statist. Assoc." }
+ @String{ApplMathComp = "Applied Mathematics and Computation" }
+ @String{ApplMathComp = "Appl. Math. Comput." }
+ @String{AmerMathMonthly = "American Mathematical Monthly" }
+ @String{AmerMathMonthly = "Amer. Math. Monthly" }
+ @String{BIT = "{BIT}" }
+ @String{BritStatPsych = "British Journal of Mathematical and Statistical
+ Psychology" }
+ @String{BritStatPsych = "Brit. J. Math. Statist. Psych." }
+ @String{CanMathBull = "Canadian Mathematical Bulletin" }
+ @String{CanMathBull = "Canad. Math. Bull." }
+ @String{CompApplMath = "Journal of Computational and Applied Mathematics" }
+ @String{CompApplMath = "J. Comput. Appl. Math." }
+ @String{CompPhys = "Journal of Computational Physics" }
+ @String{CompPhys = "J. Comput. Phys." }
+ @String{CompStruct = "Computers and Structures" }
+ @String{CompStruct = "Comput. \& Structures" }
+ @String{CompJour = "The Computer Journal" }
+ @String{CompJour = "Comput. J." }
+ @String{CompSysSci = "Journal of Computer and System Sciences" }
+ @String{CompSysSci = "J. Comput. System Sci." }
+ @String{Computing = "Computing" }
+ @String{ContempMath = "Contemporary Mathematics" }
+ @String{ContempMath = "Contemp. Math." }
+ @String{Crelle = "Crelle's Journal" }
+ @String{GiornaleMath = "Giornale di Mathematiche" }
+ @String{GiornaleMath = "Giorn. Mat." } % didn't find in AMS MR., ibid.
+
+ %IEEE
+ @String{Computer = "{IEEE} Computer" }
+ @String{IEEETransComp = "{IEEE} Transactions on Computers" }
+ @String{IEEETransComp = "{IEEE} Trans. Comput." }
+ @String{IEEETransAC = "{IEEE} Transactions on Automatic Control" }
+ @String{IEEETransAC = "{IEEE} Trans. Automat. Control" }
+ @String{IEEESpec = "{IEEE} Spectrum" } % didn't find in AMS MR
+ @String{ProcIEEE = "Proceedings of the {IEEE}" }
+ @String{ProcIEEE = "Proc. {IEEE}" } % didn't find in AMS MR
+ @String{IEEETransAeroElec = "{IEEE} Transactions on Aerospace and Electronic
+ Systems" }
+ @String{IEEETransAeroElec = "{IEEE} Trans. Aerospace Electron. Systems" }
+
+ @String{IMANumerAna = "{IMA} Journal of Numerical Analysis" }
+ @String{IMANumerAna = "{IMA} J. Numer. Anal." }
+ @String{InfProcLet = "Information Processing Letters" }
+ @String{InfProcLet = "Inform. Process. Lett." }
+ @String{InstMathApp = "Journal of the Institute of Mathematics and
+ its Applications" }
+ @String{InstMathApp = "J. Inst. Math. Appl." }
+ @String{IntControl = "International Journal of Control" }
+ @String{IntControl = "Internat. J. Control" }
+ @String{IntNumerEng = "International Journal for Numerical Methods in
+ Engineering" }
+ @String{IntNumerEng = "Internat. J. Numer. Methods Engrg." }
+ @String{IntSuper = "International Journal of Supercomputing Applications" }
+ @String{IntSuper = "Internat. J. Supercomputing Applic." } % didn't find
+%% in AMS MR
+ @String{Kibernetika = "Kibernetika" }
+ @String{JResNatBurStand = "Journal of Research of the National Bureau
+ of Standards" }
+ @String{JResNatBurStand = "J. Res. Nat. Bur. Standards" }
+ @String{LinAlgApp = "Linear Algebra and its Applications" }
+ @String{LinAlgApp = "Linear Algebra Appl." }
+ @String{MathAnaAppl = "Journal of Mathematical Analysis and Applications" }
+ @String{MathAnaAppl = "J. Math. Anal. Appl." }
+ @String{MathAnnalen = "Mathematische Annalen" }
+ @String{MathAnnalen = "Math. Ann." }
+ @String{MathPhys = "Journal of Mathematical Physics" }
+ @String{MathPhys = "J. Math. Phys." }
+ @String{MathComp = "Mathematics of Computation" }
+ @String{MathComp = "Math. Comp." }
+ @String{MathScand = "Mathematica Scandinavica" }
+ @String{MathScand = "Math. Scand." }
+ @String{TablesAidsComp = "Mathematical Tables and Other Aids to Computation" }
+ @String{TablesAidsComp = "Math. Tables Aids Comput." }
+ @String{NumerMath = "Numerische Mathematik" }
+ @String{NumerMath = "Numer. Math." }
+ @String{PacificMath = "Pacific Journal of Mathematics" }
+ @String{PacificMath = "Pacific J. Math." }
+ @String{ParDistComp = "Journal of Parallel and Distributed Computing" }
+ @String{ParDistComp = "J. Parallel and Distrib. Comput." } % didn't find
+%% in AMS MR
+ @String{ParComputing = "Parallel Computing" }
+ @String{ParComputing = "Parallel Comput." }
+ @String{PhilMag = "Philosophical Magazine" }
+ @String{PhilMag = "Philos. Mag." }
+ @String{ProcNAS = "Proceedings of the National Academy of Sciences
+ of the USA" }
+ @String{ProcNAS = "Proc. Nat. Acad. Sci. U. S. A." }
+ @String{Psychometrika = "Psychometrika" }
+ @String{QuartMath = "Quarterly Journal of Mathematics, Oxford, Series (2)" }
+ @String{QuartMath = "Quart. J. Math. Oxford Ser. (2)" }
+ @String{QuartApplMath = "Quarterly of Applied Mathematics" }
+ @String{QuartApplMath = "Quart. Appl. Math." }
+ @String{RevueInstStat = "Review of the International Statisical Institute" }
+ @String{RevueInstStat = "Rev. Inst. Internat. Statist." }
+
+ %SIAM
+ @String{JSIAM = "Journal of the Society for Industrial and Applied
+ Mathematics" }
+ @String{JSIAM = "J. Soc. Indust. Appl. Math." }
+ @String{JSIAMB = "Journal of the Society for Industrial and Applied
+ Mathematics, Series B, Numerical Analysis" }
+ @String{JSIAMB = "J. Soc. Indust. Appl. Math. Ser. B Numer. Anal." }
+ @String{SIAMAlgMeth = "{SIAM} Journal on Algebraic and Discrete Methods" }
+ @String{SIAMAlgMeth = "{SIAM} J. Algebraic Discrete Methods" }
+ @String{SIAMAppMath = "{SIAM} Journal on Applied Mathematics" }
+ @String{SIAMAppMath = "{SIAM} J. Appl. Math." }
+ @String{SIAMComp = "{SIAM} Journal on Computing" }
+ @String{SIAMComp = "{SIAM} J. Comput." }
+ @String{SIAMMatrix = "{SIAM} Journal on Matrix Analysis and Applications" }
+ @String{SIAMMatrix = "{SIAM} J. Matrix Anal. Appl." }
+ @String{SIAMNumAnal = "{SIAM} Journal on Numerical Analysis" }
+ @String{SIAMNumAnal = "{SIAM} J. Numer. Anal." }
+ @String{SIAMReview = "{SIAM} Review" }
+ @String{SIAMReview = "{SIAM} Rev." }
+ @String{SIAMSciStat = "{SIAM} Journal on Scientific and Statistical
+ Computing" }
+ @String{SIAMSciStat = "{SIAM} J. Sci. Statist. Comput." }
+
+ @String{SoftPracExp = "Software Practice and Experience" }
+ @String{SoftPracExp = "Software Prac. Experience" } % didn't find in AMS MR
+ @String{StatScience = "Statistical Science" }
+ @String{StatScience = "Statist. Sci." }
+ @String{Techno = "Technometrics" }
+ @String{USSRCompMathPhys = "{USSR} Computational Mathematics and Mathematical
+ Physics" }
+ @String{USSRCompMathPhys = "{U. S. S. R.} Comput. Math. and Math. Phys." }
+ @String{VLSICompSys = "Journal of {VLSI} and Computer Systems" }
+ @String{VLSICompSys = "J. {VLSI} Comput. Syst." }
+ @String{ZAngewMathMech = "Zeitschrift fur Angewandte Mathematik und
+ Mechanik" }
+ @String{ZAngewMathMech = "Z. Angew. Math. Mech." }
+ @String{ZAngewMathPhys = "Zeitschrift fur Angewandte Mathematik und Physik" }
+ @String{ZAngewMathPhys = "Z. Angew. Math. Phys." }
+
+% Publishers % ================================================= |
+
+ @String{Academic = "Academic Press" }
+ @String{ACMPress = "{ACM} Press" }
+ @String{AdamHilger = "Adam Hilger" }
+ @String{AddisonWesley = "Addison-Wesley" }
+ @String{AllynBacon = "Allyn and Bacon" }
+ @String{AMS = "American Mathematical Society" }
+ @String{Birkhauser = "Birkha{\"u}ser" }
+ @String{CambridgePress = "Cambridge University Press" }
+ @String{Chelsea = "Chelsea" }
+ @String{ClaredonPress = "Claredon Press" }
+ @String{DoverPub = "Dover Publications" }
+ @String{Eyolles = "Eyolles" }
+ @String{HoltRinehartWinston = "Holt, Rinehart and Winston" }
+ @String{Interscience = "Interscience" }
+ @String{JohnsHopkinsPress = "The Johns Hopkins University Press" }
+ @String{JohnWileySons = "John Wiley and Sons" }
+ @String{Macmillan = "Macmillan" }
+ @String{MathWorks = "The Math Works Inc." }
+ @String{McGrawHill = "McGraw-Hill" }
+ @String{NatBurStd = "National Bureau of Standards" }
+ @String{NorthHolland = "North-Holland" }
+ @String{OxfordPress = "Oxford University Press" } %address Oxford or London?
+ @String{PergamonPress = "Pergamon Press" }
+ @String{PlenumPress = "Plenum Press" }
+ @String{PrenticeHall = "Prentice-Hall" }
+ @String{SIAMPub = "{SIAM} Publications" }
+ @String{Springer = "Springer-Verlag" }
+ @String{TexasPress = "University of Texas Press" }
+ @String{VanNostrand = "Van Nostrand" }
+ @String{WHFreeman = "W. H. Freeman and Co." }
+
+%Entries
+@article{Wilson2017,
+ doi = {10.1371/journal.pcbi.1005510},
+ url = {doi.org/10.1371/journal.pcbi.1005510},
+ year = {2017},
+ month = jun,
+ publisher = {Public Library of Science ({PLoS})},
+ volume = {13},
+ number = {6},
+ pages = {e1005510},
+ author = {Greg Wilson and Jennifer Bryan and Karen Cranston and Justin Kitzes and Lex Nederbragt and Tracy K. Teal},
+ editor = {Francis Ouellette},
+ title = {Good enough practices in scientific computing},
+ journal = {{PLOS} Computational Biology}
+}
+
+@article{Wilson2014,
+ doi = {10.1371/journal.pbio.1001745},
+ url = {doi.org/10.1371/journal.pbio.1001745},
+ year = {2014},
+ month = jan,
+ publisher = {Public Library of Science ({PLoS})},
+ volume = {12},
+ number = {1},
+ pages = {e1001745},
+ author = {Greg Wilson and D. A. Aruliah and C. Titus Brown and Neil P. Chue Hong and Matt Davis and Richard T. Guy and Steven H. D. Haddock and Kathryn D. Huff and Ian M. Mitchell and Mark D. Plumbley and Ben Waugh and Ethan P. White and Paul Wilson},
+ editor = {Jonathan A. Eisen},
+ title = {Best Practices for Scientific Computing},
+ journal = {{PLoS} Biology}
+}
+
+@misc{SSIRSE,
+ author = {Brett, Alys and
+ Croucher, Michael and
+ Haines, Robert and
+ Hettrick, Simon and
+ Hetherington, James and
+ Stillwell, Mark and
+ Wyatt, Claire},
+ title = {{Research Software Engineers: State of the Nation
+ Report 2017}},
+ month = apr,
+ year = 2017,
+ doi = {10.5281/zenodo.495360}
+
+}
+
+@misc{SSIanalysis,
+ author = {Olivier Philippe and
+ Martin Hammitzsch and
+ Stephan Janosch and
+ Anelda van der Walt and
+ Ben van Werkhoven and
+ Simon Hettrick and
+ Daniel S. Katz and
+ Katrin Leinweber and
+ Sandra Gesing and
+ Stephan Druskat and
+ Scott Henwood and
+ Nicholas R. May and
+ Nooriyah P. Lohani and
+ Manodeep Sinha},
+ title = {{softwaresaved/international-survey: Public release
+ for 2018 results}},
+ month = mar,
+ year = 2019,
+ hide_publisher = {Zenodo},
+ version = {2018-v.1.0.2},
+ doi = {10.5281/zenodo.2585783},
+ url = {doi.org/10.5281/zenodo.2585783}
+}
+
+@techreport{https://doi.org/10.5281/zenodo.1344612,
+ doi = {10.5281/ZENODO.1344612},
+ url = {zenodo.org/record/1344612},
+ author = {Schlauch, Tobias and Meinel, Michael and Haupt, Carina},
+ keywords = {research-software-engineering, guidelines},
+ language = {en},
+ title = {{DLR} Software Engineering Guidelines},
+ institution = {Deutsches Zentrum für Luft- und Raumfahrt ({DLR})},
+ hide_publisher = {Zenodo},
+ year = {2018}
+}
+
+@techreport{https://doi.org/10.2312/os.helmholtz.003,
+ doi = {10.2312/OS.HELMHOLTZ.003},
+ url = {gfzpublic.gfz-potsdam.de/pubman/item/escidoc:3951898},
+ author = {Scheliga, Kaja and Pampel, Heinz and Konrad, Uwe and Fritzsch, Bernadette and Schlauch, Tobias and Nolden, Marco and Zu Castell, Wolfgang and Finke, Ants and Hammitzsch, Martin and Bertuch, Oliver and Denker, Michael},
+ language = {eng},
+ title = {Dealing with research software: Recommendations for best practices},
+ institution = {Helmholtz Open Science Coordination Office},
+ year = {2019}
+}
+
+@article{GomezDiaz2019,
+ doi = {10.12688/f1000research.19994.1},
+ url = {doi.org/10.12688/f1000research.19994.1},
+ year = {2019},
+ month = aug,
+ publisher = {F1000 ( Faculty of 1000 Ltd)},
+ volume = {8},
+ pages = {1353},
+ author = {Teresa Gomez-Diaz and Tomas Recio},
+ title = {On the evaluation of research software: the {CDUR} procedure},
+ journal = {F1000Research}
+}
+
+@article{Wilkinson2016,
+ doi = {10.1038/sdata.2016.18},
+ url = {doi.org/10.1038/sdata.2016.18},
+ year = {2016},
+ month = mar,
+ publisher = {Springer Science and Business Media {LLC}},
+ volume = {3},
+ number = {1},
+ pages = {160018},
+ author = {Mark D. Wilkinson and Michel Dumontier and IJsbrand Jan Aalbersberg and Gabrielle Appleton and Myles Axton and Arie Baak and Niklas Blomberg and Jan-Willem Boiten and Luiz Bonino da Silva Santos and Philip E. Bourne and Jildau Bouwman and Anthony J. Brookes and Tim Clark and Merc{\`{e}} Crosas and Ingrid Dillo and Olivier Dumon and Scott Edmunds and Chris T. Evelo and Richard Finkers and Alejandra Gonzalez-Beltran and Alasdair J.G. Gray and Paul Groth and Carole Goble and Jeffrey S. Grethe and Jaap Heringa and Peter A.C 't Hoen and Rob Hooft and Tobias Kuhn and Ruben Kok and Joost Kok and Scott J. Lusher and Maryann E. Martone and Albert Mons and Abel L. Packer and Bengt Persson and Philippe Rocca-Serra and Marco Roos and Rene van Schaik and Susanna-Assunta Sansone and Erik Schultes and Thierry Sengstag and Ted Slater and George Strawn and Morris A. Swertz and Mark Thompson and Johan van der Lei and Erik van Mulligen and Jan Velterop and Andra Waagmeester and Peter Wittenburg and Katherine Wolstencroft and Jun Zhao and Barend Mons},
+ title = {The {FAIR} Guiding Principles for scientific data management and stewardship},
+ journal = {Scientific Data}
+}
+
+@article{Fehr2016,
+ doi = {10.3934/math.2016.3.261},
+ url = {doi.org/10.3934/math.2016.3.261},
+ year = {2016},
+ publisher = {American Institute of Mathematical Sciences ({AIMS})},
+ volume = {1},
+ number = {3},
+ pages = {261--281},
+ author = {J\"{o}rg Fehr and and Jan Heiland and Christian Himpe and Jens Saak},
+ title = {Best practices for replicability, reproducibility and reusability of computer-based experiments exemplified by model reduction software},
+ journal = {{AIMS} Mathematics}
+}
+
+@article{Hsu2019,
+ doi = {10.1371/journal.pone.0222807},
+ url = {doi.org/10.1371/journal.pone.0222807},
+ year = {2019},
+ month = oct,
+ publisher = {Public Library of Science ({PLoS})},
+ volume = {14},
+ number = {10},
+ pages = {e0222807},
+ author = {Leslie Hsu and Vivian B. Hutchison and Madison L. Langseth},
+ editor = {Rashid Mehmood},
+ title = {Measuring sustainability of seed-funded earth science informatics projects},
+ journal = {{PLOS} {ONE}}
+}
+
+@article{Li2019,
+ doi = {10.1016/j.joi.2019.02.007},
+ url = {doi.org/10.1016/j.joi.2019.02.007},
+ year = {2019},
+ month = feb,
+ publisher = {Elsevier {BV}},
+ volume = {13},
+ number = {1},
+ pages = {449--461},
+ author = {Kai Li and Pei-Ying Chen and Erjia Yan},
+ title = {Challenges of measuring software impact through citations: An examination of the lme4 R package},
+ journal = {Journal of Informetrics}
+}
+
+
+@article{Lee2018,
+ doi = {10.1371/journal.pcbi.1006561},
+ url = {doi.org/10.1371/journal.pcbi.1006561},
+ year = {2018},
+ month = dec,
+ publisher = {Public Library of Science ({PLoS})},
+ volume = {14},
+ number = {12},
+ pages = {e1006561},
+ author = {Benjamin D. Lee},
+ editor = {Scott Markel},
+ title = {Ten simple rules for documenting scientific software},
+ journal = {{PLOS} Computational Biology}
+}
+
+@inproceedings{ChueHong2014,
+author = "Neil Chue Hong",
+title = "{Minimal information for reusable scientific software}",
+year = "2014",
+month = "7",
+booktitle = "2nd Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE2)",
+url = "figshare.com/articles/Minimal_information_for_reusable_scientific_software/1112528",
+doi = "10.6084/m9.figshare.1112528.v1"
+}
+
+@article{lamprechttowards,
+ title={Towards FAIR principles for research software},
+ author={Lamprecht, Anna-Lena and Garcia, Leyla and Kuzak, Mateusz and Martinez, Carlos and Arcila, Ricardo and Martin Del Pico, Eva and Dominguez Del Angel, Victoria and van de Sandt, Stephanie and Ison, Jon and Martinez, Paula Andrea and others},
+ journal={Data Science},
+ hide_volume={Preprint},
+ year={2019},
+ hide_pages={1--23},
+ publisher={IOS Press},
+ doi={10.3233/DS-190026}
+}
+
+@misc{hasselbring2019fair,
+ title={FAIR and Open Computer Science Research Software},
+ author={Wilhelm Hasselbring and Leslie Carr and Simon Hettrick and Heather Packer and Thanassis Tiropanis},
+ year={2019},
+ arxiv = {1908.05986},
+ archivePrefix={arXiv},
+ primaryClass={cs.SE},
+ url = {https://arxiv.org/abs/1908.05986}
+}
+
+
+@article{bangerth2014quo,
+ title={Quo Vadis, Scientific Software?},
+ author={Bangerth, Wolfgang and Heister, Timo},
+ journal={SIAM News},
+ volume={47},
+ number={1},
+ pages={8},
+ year={2014},
+ publisher={Citeseer}
+}
+
+@techreport{NWOprofile,
+ title={Raising the Profile of Research Software: Recommendations for Funding Agencies and Research Institutions},
+ author = {Akhmerov, Anton and Cruz, Maria and Drost, Niels and Hof, Cees and Knapen, Tomas and Kuzak, Mateusz and Martinez-Ortiz, Carlos and Turkyilmaz-van der Velden, Yasemin and van Werkhoven, Ben},
+ institution = {NWO (The Netherlands Organisation for Scientific Research)},
+ year = {2019}
+}
+
+@Article{dagstuhl,
+ author = {Alice Allen and Cecilia Aragon and Christoph Becker and Jeffrey Carver and Andrei Chis and Benoit Combemale and Mike Croucher and Kevin Crowston and Daniel Garijo and Ashish Gehani and Carole Goble and Robert Haines and Robert Hirschfeld and James Howison and Kathryn Huff and Caroline Jay and Daniel S. Katz and Claude Kirchner and Katie Kuksenok and Ralf L{\"a}mmel and Oscar Nierstrasz and Matt Turk and Rob van Nieuwpoort and Matthew Vaughn and Jurgen J. Vinju},
+ title = {{Engineering Academic Software (Dagstuhl Perspectives Workshop 16252)}},
+ pages = {1--20},
+ journal = {Dagstuhl Manifestos},
+ ISSN = {2193-2433},
+ year = {2017},
+ volume = {6},
+ number = {1},
+ editor = {Alice Allen et al.},
+ publisher = {Schloss Dagstuhl--Leibniz-Zentrum fuer Informatik},
+ address = {Dagstuhl, Germany},
+ URL = {drops.dagstuhl.de/opus/volltexte/2017/7146},
+ URN = {urn:nbn:de:0030-drops-71468},
+ doi = {10.4230/DagMan.6.1.1},
+ annote = {Keywords: Academic software, Research software, Software citation, Software sustainability}
+}
+
+@ARTICLE{Katz19community,
+author={D. S. {Katz} and L. C. {McInnes} and D. E. {Bernholdt} and A. C. {Mayes} and N. P. C. {Hong} and J. {Duckles} and S. {Gesing} and M. A. {Heroux} and S. {Hettrick} and R. C. {Jimenez} and M. {Pierce} and B. {Weaver} and N. {Wilkins-Diehr}},
+journal={Computing in Science \& Engineering},
+title={Community Organizations: Changing the Culture in Which Research Software Is Developed and Sustained},
+year={2019},
+volume={21},
+number={2},
+pages={8-24},
+keywords={data analysis;grid computing;software development management;software engineering;sustainable development;complex simulations;multiscale modeling;outer-loop analysis;community members;grass-roots organizations;growing technical challenges;social challenges;software productivity;software ecosystems;community organizations;research software;key crosscutting technology;mathematics;computer science;domain-specific science;robust simulations;research fields;focused attention;research communities;scientific software;computer hardware;Software;Organizations;Sustainable development;Computational modeling;Ecosystems;Collaboration;Conferences;research software;scientific software;software ecosystems;software productivity;software sustainability;software community culture},
+doi={10.1109/MCSE.2018.2883051},
+ISSN={1558-366X},
+month={March},}
+
+@article{Sufi2018,
+ doi = {10.7287/peerj.preprints.26849v1},
+ url = {doi.org/10.7287/peerj.preprints.26849v1},
+ year = {2018},
+ month = apr,
+ journal = {{PeerJ Preprints}},
+ volume={6},
+ pages={e26849v1},
+ author = {Shoaib A Sufi and Caroline Jay},
+ title = {Raising the status of software in research: A survey-based evaluation of the Software Sustainability Institute Fellowship Programme}
+}
+
+@article{Venters2018,
+ doi = {10.1016/j.jss.2017.12.026},
+ url = {doi.org/10.1016/j.jss.2017.12.026},
+ year = {2018},
+ month = apr,
+ publisher = {Elsevier {BV}},
+ volume = {138},
+ pages = {174--188},
+ author = {Colin C. Venters and Rafael Capilla and Stefanie Betz and Birgit Penzenstadler and Tom Crick and Steve Crouch and Elisa Yumi Nakagawa and Christoph Becker and Carlos Carrillo},
+ title = {Software sustainability: Research and practice from a software architecture viewpoint},
+ journal = {Journal of Systems and Software}
+}
+
+@article{Jimnez2017,
+ doi = {10.12688/f1000research.11407.1},
+ url = {doi.org/10.12688/f1000research.11407.1},
+ year = {2017},
+ month = jun,
+ publisher = {F1000 ( Faculty of 1000 Ltd)},
+ volume = {6},
+ pages = {876},
+ author = {Rafael C. Jim{\'{e}}nez and Mateusz Kuzak and Monther Alhamdoosh and Michelle Barker and B{\'{e}}r{\'{e}}nice Batut and Mikael Borg and Salvador Capella-Gutierrez and Neil Chue Hong and Martin Cook and Manuel Corpas and Madison Flannery and Leyla Garcia and Josep Ll. Gelp{\'{\i}} and Simon Gladman and Carole Goble and Montserrat Gonz{\'{a}}lez Ferreiro and Alejandra Gonzalez-Beltran and Philippa C. Griffin and Bj\"{o}rn Gr\"{u}ning and Jonas Hagberg and Petr Holub and Rob Hooft and Jon Ison and Daniel S. Katz and Brane Lesko{\v{s}}ek and Federico L{\'{o}}pez G{\'{o}}mez and Luis J. Oliveira and David Mellor and Rowland Mosbergen and Nicola Mulder and Yasset Perez-Riverol and Robert Pergl and Horst Pichler and Bernard Pope and Ferran Sanz and Maria V. Schneider and Victoria Stodden and Rados{\l}aw Suchecki and Radka Svobodov{\'{a}} Va{\v{r}}ekov{\'{a}} and Harry-Anton Talvik and Ilian Todorov and Andrew Treloar and Sonika Tyagi and Maarten van Gompel and Daniel Vaughan and Allegra Via and Xiaochuan Wang and Nathan S. Watson-Haigh and Steve Crouch},
+ title = {Four simple recommendations to encourage best practices in research software},
+ journal = {F1000Research}
+}
+
+@ARTICLE{crowdsourcingDocumentation,
+author={A. {Pawlik} and J. {Segal} and H. {Sharp} and M. {Petre}},
+journal={Computing in Science \& Engineering},
+title={Crowdsourcing Scientific Software Documentation: A Case Study of the NumPy Documentation Project},
+year={2015},
+volume={17},
+number={1},
+pages={28-36},
+keywords={natural sciences computing;software engineering;software packages;scientific software documentation crowdsourcing;NumPy documentation project;scientific software packages;technical infrastructure;community engagement;Documentation;Collaboration;Software development;Crowdsourcing;Computer applications;Scientific computing;Knowledge management;Internet;computer-supported collaborative work;software engineering for Internet projects;knowledge sharing;scientific computing},
+doi={10.1109/MCSE.2014.93},
+ISSN={1558-366X},
+month={Jan},}
+
+@article{bioInfCommunity,
+ author = {Budd, Aidan AND Corpas, Manuel AND Brazas, Michelle D. AND Fuller, Jonathan C. AND Goecks, Jeremy AND Mulder, Nicola J. AND Michaut, Magali AND Ouellette, B. F. Francis AND Pawlik, Aleksandra AND Blomberg, Niklas},
+ journal = {PLOS Computational Biology},
+ publisher = {Public Library of Science},
+ title = {A Quick Guide for Building a Successful Bioinformatics Community},
+ year = {2015},
+ month = {02},
+ volume = {11},
+ url = {doi.org/10.1371/journal.pcbi.1003972},
+ pages = {1-11},
+ abstract = {“Scientific community” refers to a group of people collaborating together on scientific-research-related activities who also share common goals, interests, and values. Such communities play a key role in many bioinformatics activities. Communities may be linked to a specific location or institute, or involve people working at many different institutions and locations. Education and training is typically an important component of these communities, providing a valuable context in which to develop skills and expertise, while also strengthening links and relationships within the community. Scientific communities facilitate: (i) the exchange and development of ideas and expertise; (ii) career development; (iii) coordinated funding activities; (iv) interactions and engagement with professionals from other fields; and (v) other activities beneficial to individual participants, communities, and the scientific field as a whole. It is thus beneficial at many different levels to understand the general features of successful, high-impact bioinformatics communities; how individual participants can contribute to the success of these communities; and the role of education and training within these communities. We present here a quick guide to building and maintaining a successful, high-impact bioinformatics community, along with an overview of the general benefits of participating in such communities. This article grew out of contributions made by organizers, presenters, panelists, and other participants of the ISMB/ECCB 2013 workshop “The ‘How To Guide’ for Establishing a Successful Bioinformatics Network” at the 21st Annual International Conference on Intelligent Systems for Molecular Biology (ISMB) and the 12th European Conference on Computational Biology (ECCB).},
+ number = {2},
+ doi = {10.1371/journal.pcbi.1003972}
+}
+
+@article{bioJScommunity,
+ doi = {10.7554/elife.07009.001},
+ url = {doi.org/10.7554/elife.07009.001},
+ journal = {{eLife} Sciences Publications, Ltd},
+ volume = 4,
+ pages = {e07009},
+ year = 2015,
+ author = {Yachdav, Guy and Goldberg, Tatyana and Wilzbach, Sebastian and Dao, David and Shih, Iris and Choudhary, Saket and Crouch, Steve and Franz, Max and García, Alexander and García, Leyla J and Grüning, Björn A and Inupakutika, Devasena and Sillitoe, Ian and Thanki, Anil S and Vieira, Bruno and Villaveces, José M and Schneider, Maria V and Lewis, Suzanna and Pettifer, Steve and Rost, Burkhard and Corpas, Manuel},
+ title = {Cutting Edge: Anatomy of BioJS, an open source community for the life sciences}
+}
+
+@misc{CFF,
+ author = {Druskat, Stephan and
+ Spaaks, Jurriaan H. and
+ Chue Hong, Neil and
+ Haines, Robert and
+ Baker, James},
+ title = {{C}itation {F}ile {F}ormat ({CFF}) - {S}pecifications},
+ month = nov,
+ year = 2019,
+ hide_publisher = {Zenodo},
+ version = {1.0.3-4},
+ doi = {10.5281/zenodo.3515946},
+ url = {doi.org/10.5281/zenodo.3515946}
+}
+
+@inproceedings{Struck2018,
+ doi = {10.1109/escience.2018.00016},
+ url = {doi.org/10.1109/escience.2018.00016},
+ year = {2018},
+ month = oct,
+ publisher = {{IEEE}},
+ author = {Alexander Struck},
+ title = {Research Software Discovery: An Overview},
+ booktitle = {2018 {IEEE} 14th International Conference on e-Science}
+}
+
+@book{collectiveAction,
+ doi = {10.5281/ZENODO.3454688},
+ url = {zenodo.org/record/3454688},
+ author = {Neylon, Cameron and Belsø, Rene and Bijsterbosch, Magchiel and Cordewener, Bas and Foncel, Jér\^ome and Friesike, Sascha and Fyfe, Aileen and Jacobs, Neil and Katerbow, Matthias and Laakso, Mikael and Sesink, Laurents},
+ keywords = {Open Scholarship, KE, Knowledge Exchange, Collective action, OS Framework, Open Research, Open Science, Scholarly Comms},
+ title = {Open Scholarship and the need for collective action},
+ publisher = {Zenodo},
+ year = {2019}
+}
+
+@misc{RSEdef,
+ author = {Richardson, Chris and Croucher, Mike},
+ title = {Research Software Engineer: A New Career Track?},
+ year = 2018,
+ url = {sinews.siam.org/Details-Page/research-software-engineer-a-new-career-track}
+}
+
+@misc{DORA,
+ title = {San Francisco Declaration on Research Assessment},
+ year = 2012,
+ url = {sfdora.org/read}
+}
+
+@misc{DFGcall1,
+ author = {DFG},
+ title = {Nachhaltigkeit von Forschungssoftware},
+ year = 2016,
+ url = {www.dfg.de/foerderung/info_wissenschaft/2016/info_wissenschaft_16_71}
+}
+
+@misc{DFGcall2,
+ author = {DFG},
+ title = {Qualitätssicherung von Forschungssoftware durch ihre nachhaltige Nutzbarmachung},
+ year = 2019,
+ url = {www.dfg.de/foerderung/info_wissenschaft/info_wissenschaft_19_44}
+}
+
+@misc{DFGcode,
+ author = {DFG},
+ title = {Guidelines for Safeguarding Good Research Practice},
+ year = 2019,
+ url = {www.dfg.de/en/research_funding/principles_dfg_funding/good_scientific_practice}
+}
+
+@misc{DFGfunded,
+ author = {DFG},
+ title = {Geförderte Projekte Ausschreibung Nachhaltigkeit Forschungssoftware},
+ year = 2018,
+ url = {gepris.dfg.de/gepris/suche/projekt/research_software}
+}
+
+@misc{deRSEconf,
+ author = {{de-RSE e.V. - Society for Research Software}},
+ title = {Konferenz für ForschungssoftwareentwicklerInnen in Deutschland},
+ year = 2019,
+ url = {web.archive.org/web/20191213123440/de-rse.org/en/conf2019}
+}
+
+@misc{CHAOSS,
+ author = {CHAOSS},
+ title = {CHAOSS Metrics},
+ year = 2019,
+ url = {chaoss.community/metrics}
+}
+
+@misc{SSIevaluation,
+ author = {Jackson, Mike and Crouch, Steve and Baxter, Rob},
+ title = {Software Evaluation Guide},
+ year = 2019,
+ url = {www.software.ac.uk/resources/guides-everything/software-evaluation-guide}
+}
+
+@misc{SSIsustain,
+ author = {SSI},
+ title = {Online sustainability evaluation},
+ year = 2019,
+ url = {www.software.ac.uk/resources/online-sustainability-evaluation}
+}
+
+@misc{SSImanage,
+ author = {SSI},
+ title = {Writing and using a software management plan},
+ year = 2019,
+ url = {www.software.ac.uk/resources/guides/software-management-plans}
+}
+
+@misc{Scienceguide,
+ author = {{Science Guide}},
+ title = {Room for everyone’s talent},
+ year = 2019,
+ url = {www.scienceguide.nl/wp-content/uploads/2019/11/283.002-Erkennen-en-Waarderen-Position-Paper_EN_web.pdf}
+}
+
+@misc{BMJVarbeit,
+ author = {{Bundesministerium der Justiz und für Verbraucherschutz}},
+ title = {Gesetz über befristete Arbeitsverträge in der Wissenschaft},
+ year = 2017,
+ url = {www.gesetze-im-internet.de/wisszeitvg}
+}
+
+@misc{FUbsc,
+ author = {{Freie Universität Berlin}},
+ title = {Bioinformatics Solution Center},
+ year = 2019,
+ url = {www.bsc.fu-berlin.de}
+}
+
+@misc{deNBI,
+ author = {deNBI},
+ title = {Big Data Exploitation in Life Science},
+ year = 2019,
+ url = {www.denbi.de}
+}
+
+@misc{dariah,
+ author = {DARIAHeu},
+ title = {Digital Research Infrastructure for the Arts and Humanities},
+ year = 2019,
+ url = {www.dariah.eu}
+}
+
+@misc{CodeMeta,
+ author = {{The CodeMeta Project}},
+ title = {The CodeMeta Project},
+ year = 2019,
+ url = {codemeta.github.io}
+}
+
+@misc{swMATH,
+ author = {swMATH},
+ title = {An information service for mathematical software},
+ year = 2019,
+ url = {swmath.org}
+}
+
+@misc{UKSoftwareSustainabilityInstitute,
+ author = {UK Software Sustainability Institute},
+ title = {UK Software Sustainability Institute},
+ year = 2019,
+ url = {https://www.software.ac.uk/}
+}
+
+@misc{SoftwareSystemsDevelopmentLifeCycle_SDLC,
+ author = {UK Software Sustainability Institute},
+ title = {Software Systems Development LifeCycle (SDLC)},
+ year = 2019,
+ url = {https://www.software.ac.uk/resources}
+}
+
+@misc{ASCLnet,
+ author = {{ASCL.net}},
+ title = {Astrophysics Source Code Library},
+ year = 2019,
+ url = {ascl.net}
+}
+
+@misc{BMJVurheber69a,
+ author = {{Bundesministerium der Justiz und für Verbraucherschutz}},
+ title = {§69a subsection (1) UrhG},
+ year = 2014,
+ url = {www.gesetze-im-internet.de/urhg/__69a.html}
+}
+
+@misc{BMJVurheber69b,
+ author = {{Bundesministerium der Justiz und für Verbraucherschutz}},
+ title = {§69b UrhG},
+ year = 2014,
+ url = {www.gesetze-im-internet.de/urhg/__69b.html}
+}
+
+@misc{ifrOSS,
+ author = {ifrOSS},
+ title = {Lizenz Center},
+ year = 2019,
+ url = {ifross.github.io/ifrOSS/Lizenzcenter}
+}
+
+@misc{tldrlegal,
+ author = {tl;drLegal},
+ title = {Software Licenses in Plain English},
+ year = 2019,
+ url = {tldrlegal.com}
+}
+
+@misc{afl,
+ author = {Wikipedia},
+ title = {Academic Free License},
+ year = 2019,
+ url = {en.wikipedia.org/wiki/Academic_Free_License}
+}
+
+@misc{OMNeT,
+ author = {Varga, Andras},
+ title = {OMNeT++ Academic Public License},
+ year = 2019,
+ url = {omnetpp.org/intro/license}
+}
+
+@ARTICLE{Resnik2019139,
+author={Resnik, D.B. and Morales, M. and Landrum, R. and Shi, M. and Minnier, J. and Vasilevsky, N.A. and Champieux, R.E.},
+title={Effect of impact factor and discipline on journal data sharing policies},
+journal={Accountability in Research},
+year={2019},
+volume={26},
+number={3},
+pages={139-156},
+doi={10.1080/08989621.2019.1591277},
+note={cited By 0},
+url={www.scopus.com/inward/record.uri?eid=2-s2.0-85063401897&doi=10.1080%2f08989621.2019.1591277&partnerID=40&md5=5eb680d84267a22d581d3050c35dce2b},
+document_type={Article},
+source={Scopus},
+}
+
+@ARTICLE{codeImpact,
+author={P. {Vandewalle}},
+journal={Computing in Science \& Engineering},
+title={Code Sharing Is Associated with Research Impact in Image Processing},
+year={2012},
+volume={14},
+number={4},
+pages={42-47},
+keywords={image processing;code sharing;research impact;image processing;computational sciences;supplementary materials;Reproducibility of results;Image processing;Research and development;Image processing;Publishing;Signal processing;Scientific computing;Reproducibility of results;Image processing;Research and development;Image processing;Publishing;Signal processing;Scientific computing;scientific computing;image processing;reproducibility of results;scientific publishing;software reusability},
+doi={10.1109/MCSE.2012.63},
+ISSN={1558-366X},
+month={July},}
+
+@article{johanson2018software,
+ title={Software engineering for computational science: Past, present, future},
+ author={Johanson, Arne and Hasselbring, Wilhelm},
+ journal={Computing in Science \& Engineering},
+ year={2018},
+ publisher={IEEE},
+ volume = 20,
+ number = 2,
+ pages = {90-109},
+}
+
+% --
+
+
+@inproceedings{druskatMappingResearchSoftware2018,
+ title = {Mapping the {{Research Software Sustainability Space}}},
+ copyright = {All rights reserved},
+ abstract = {A growing number of largely uncoordinated initiatives focus on research software sustainability. A comprehensive mapping of the research software sustainability space can help identify gaps in their efforts, track results, and avoid duplication of work. To this end, this paper suggests enhancing an existing schematic of activities in research software sustainability, and formalizing it in a directed graph model. Such a model can be further used to define a classification schema which, applied to research results in the field, can drive the identification of past activities and the planning of future efforts.},
+ booktitle = {2018 {{IEEE}} 14th {{International Conference}} on E-{{Science}} (e-{{Science}})},
+ url = {doi.org/10.1109/eScience.2018.00014},
+ doi = {10.1109/eScience.2018.00014},
+ author = {Druskat, Stephan and Katz, Daniel S.},
+ month = oct,
+ year = {2018},
+ keywords = {Conferences,software engineering,Software engineering,classification schema,communities,comprehensive mapping,directed graph model,directed graphs,modeling,Organizations,research software,research software sustainability space,scientific computing,Software,Software measurement,Standards organizations,sustainable development,Sustainable development,uncoordinated initiatives focus,visualization},
+ pages = {25-30},
+ file = {/home/stephan/Zotero/storage/5R84G66B/Druskat and Katz - 2018 - Mapping the Research Software Sustainability Space.pdf;/home/stephan/Zotero/storage/47R5VM23/8588633.html}
+}
+
+@inproceedings{druskatProposalMeasurementDocumentation2016,
+ address = {{Manchester, UK}},
+ title = {A Proposal for the Measurement and Documentation of Research Software Sustainability in Interactive Metadata Repositories},
+ copyright = {All rights reserved},
+ booktitle = {Proceedings of the {{Fourth Workshop}} on {{Sustainable Software}} for {{Science}}: {{Practice}} and {{Experiences}} ({{WSSSPE4}})},
+ url = {ceur-ws.org/Vol-1686},
+ author = {Druskat, Stephan},
+ editor = {Allen, Gabrielle and Carver, Jeffrey and Choi, Sou-Cheng T. and Crick, Tom and Crusoe, Michael R. and Gesing, Sandra and Haines, Robert and Heroux, Michael and Hwang, Lorraine J. and Katz, Daniel S. and Niemeyer, Kyle E. and Parashar, Manish and Venters, Colin C.},
+ month = sep,
+ year = {2016}
+}
+
+@article{smithSoftwareCitationPrinciples2016,
+ title = {Software Citation Principles},
+ volume = {2},
+ issn = {2376-5992},
+ pages = {e86},
+ journal = {PeerJ Computer Science},
+ url = {doi.org/10.7717/peerj-cs.86},
+ doi = {10.7717/peerj-cs.86},
+ author = {Smith, Arfon M. and Katz, Daniel S. and Niemeyer, Kyle E. and {FORCE11 Software Citation Working Group}},
+ year = {2016},
+ file = {/home/stephan/Zotero/storage/MIA8UJBQ/Smith et al. - 2016 - Software citation principles.pdf;/home/stephan/Zotero/storage/QPG7HCLB/cs-86.html}
+}
+
+@article{katzStateSustainableResearch2019,
+ title = {The {{State}} of {{Sustainable Research Software}}: {{Learning}} from the {{Workshop}} on {{Sustainable Software}} for {{Science}}: {{Practice}} and {{Experiences}} ({{WSSSPE5}}.1)},
+ volume = {7},
+ copyright = {Authors who publish with this journal agree to the following terms: Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal. Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal. Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access ). All third-party images reproduced on this journal are shared under Educational Fair Use. For more information on Educational Fair Use , please see this useful checklist prepared by Columbia University Libraries . All copyright of third-party content posted here for research purposes belongs to its original owners. Unless otherwise stated all references to characters and comic art presented on this journal are \textcopyright, \textregistered{} or \texttrademark{} of their respective owners. No challenge to any owner's rights is intended or should be inferred.},
+ issn = {2049-9647},
+ shorttitle = {The {{State}} of {{Sustainable Research Software}}},
+ abstract = {This paper uses the accepted submissions from the Workshop on Sustainable Software for Science: Practice and Experiences (WSSSPE5.1) held in Manchester, UK in September 2017 and the speed blogs written during the event to examine the state of research software. It presents a schematic of the space, then examines coverage in terms of topics, actors, actees, and themes by both the submissions and the blogs.},
+ language = {en},
+ number = {1},
+ urldate = {2019-04-02},
+ journal = {Journal of Open Research Software},
+ url = {openresearchsoftware.metajnl.com/articles/10.5334/jors.242},
+ doi = {10.5334/jors.242},
+ author = {Katz, Daniel S. and Druskat, Stephan and Haines, Robert and Jay, Caroline and Struck, Alexander},
+ month = apr,
+ year = {2019},
+ keywords = {research software,sustainable software},
+ pages = {11},
+ file = {/home/stephan/Zotero/storage/4TPVCLLM/Katz et al. - 2019 - The State of Sustainable Research Software Learni.pdf;/home/stephan/Zotero/storage/IUHF9WFJ/jors.html}
+}
+
+@misc{katzSoftwareCitationImplementation2019,
+ archivePrefix = {arXiv},
+ eprinttype = {arxiv},
+ arxiv = {1905.08674},
+ primaryClass = {cs},
+ title = {Software {{Citation Implementation Challenges}}},
+ author = {Katz, Daniel S. and Bouquin, Daina and Hong, Neil P. Chue and Hausman, Jessica and Jones, Catherine and Chivvis, Daniel and Clark, Tim and Crosas, Merc{\`e} and Druskat, Stephan and Fenner, Martin and Gillespie, Tom and {Gonzalez-Beltran}, Alejandra and Gruenpeter, Morane and Habermann, Ted and Haines, Robert and Harrison, Melissa and Henneken, Edwin and Hwang, Lorraine and Jones, Matthew B. and Kelly, Alastair A. and Kennedy, David N. and Leinweber, Katrin and Rios, Fernando and Robinson, Carly B. and Todorov, Ilian and Wu, Mingfang and Zhang, Qian},
+ copyright = {All rights reserved},
+ abstract = {The main output of the FORCE11 Software Citation working group (www.force11.org/group/software-citation-working-group) was a paper on software citation principles (doi.org/10.7717/peerj-cs.86) published in September 2016. This paper laid out a set of six high-level principles for software citation (importance, credit and attribution, unique identification, persistence, accessibility, and specificity) and discussed how they could be used to implement software citation in the scholarly community. In a series of talks and other activities, we have promoted software citation using these increasingly accepted principles. At the time the initial paper was published, we also provided guidance and examples on how to make software citable, though we now realize there are unresolved problems with that guidance. The purpose of this document is to provide an explanation of current issues impacting scholarly attribution of research software, organize updated implementation guidance, and identify where best practices and solutions are still needed.},
+ urldate = {2019-06-18},
+ journal = {arXiv:1905.08674 [cs]},
+ url = {arxiv.org/abs/1905.08674},
+ month = may,
+ year = {2019},
+ keywords = {Computer Science - Computers and Society,Computer Science - Digital Libraries},
+ file = {/home/stephan/Zotero/storage/47W7PMSE/Katz et al. - 2019 - Software Citation Implementation Challenges.pdf;/home/stephan/Zotero/storage/3EA4ZPXV/1905.html}
+}
+
+@article{liSoftwareCitationReuse2016,
+ title = {Software Citation, Reuse and Metadata Considerations: {{An}} Exploratory Study Examining {{LAMMPS}}},
+ volume = {53},
+ issn = {23739231},
+ shorttitle = {Software Citation, Reuse and Metadata Considerations},
+ language = {en},
+ number = {1},
+ urldate = {2019-08-23},
+ journal = {Proceedings of the Association for Information Science and Technology},
+ url = {doi.wiley.com/10.1002/pra2.2016.14505301072},
+ doi = {10.1002/pra2.2016.14505301072},
+ author = {Li, Kai and Lin, Xia and Greenberg, Jane},
+ year = {2016},
+ pages = {1-10},
+ file = {/home/stephan/Zotero/storage/9QCJFDMK/Li et al. - 2016 - Software citation, reuse and metadata consideratio.pdf}
+}
+
+@article{hattonChimeraSoftwareQuality2007,
+ title = {The {{Chimera}} of {{Software Quality}}},
+ volume = {40},
+ issn = {1558-0814},
+ number = {8},
+ journal = {Computer},
+ doi = {10.1109/MC.2007.292},
+ author = {Hatton, Les},
+ month = aug,
+ year = {2007},
+ keywords = {Automobiles,Computer crashes,Computer simulation,computers and society,computing profession,Costs,Mathematics,Peer to peer computing,Radar,software fault tolerance,software quality,Software quality,Time measurement,Vehicle crash testing},
+ pages = {104-103},
+ file = {/home/stephan/Zotero/storage/ENLV5YRC/4292028.html}
+}
+
+@article{changRetraction2006,
+ title = {Retraction},
+ volume = {314},
+ copyright = {\textcopyright{} 2006 American Association for the Advancement of Science},
+ issn = {0036-8075, 1095-9203},
+ language = {en},
+ number = {5807},
+ urldate = {2019-12-05},
+ journal = {Science},
+ url = {science.sciencemag.org/content/314/5807/1875.2},
+ doi = {10.1126/science.314.5807.1875b},
+ author = {Chang, Geoffrey and Roth, Christopher B. and Reyes, Christopher L. and Pornillos, Owen and Chen, Yen-Ju and Chen, Andy P.},
+ month = dec,
+ year = {2006},
+ pages = {1875-1875},
+ file = {/home/stephan/Zotero/storage/P3UDNZPC/1875.html},
+ pmid = {17185584}
+}
+
+@article{matthewsFiveRetractedStructure2007,
+ title = {Five Retracted Structure Reports: {{Inverted}} or Incorrect?},
+ volume = {16},
+ copyright = {Copyright \textcopyright{} 2007 The Protein Society},
+ issn = {1469-896X},
+ shorttitle = {Five Retracted Structure Reports},
+ language = {en},
+ number = {6},
+ urldate = {2019-12-05},
+ journal = {Protein Science},
+ url = {onlinelibrary.wiley.com/doi/abs/10.1110/ps.072888607},
+ doi = {10.1110/ps.072888607},
+ author = {Matthews, Brian W.},
+ year = {2007},
+ pages = {1013-1016},
+ file = {/home/stephan/Zotero/storage/N6BHUBXU/Matthews - 2007 - Five retracted structure reports Inverted or inco.pdf;/home/stephan/Zotero/storage/87PA3IIL/ps.html}
+}
+
+@article{druskatSoftwareDependenciesResearch2019,
+ title = {Software and {{Dependencies}} in {{Research Citation Graphs}}},
+ author = {Druskat, Stephan},
+ year = {2020},
+ month = mar,
+ volume = {22},
+ pages = {8--21},
+ issn = {1558-366X},
+ doi = {10.1109/MCSE.2019.2952840},
+ url = {https://doi.org/10.1109/MCSE.2019.2952840},
+ abstract = {Following the widespread digitalization of scholarship, software has become essential for research, but the current sociotechnical system of citation does not reflect this sufficiently. Citation provides context for research, but the current model for the respective research citation graphs does not integrate software. In this article, I develop a directed graph model to alleviate this, describe challenges for its instantiation, and give an outlook of useful applications of research citation graphs, including transitive credit.},
+ journal = {Computing in Science \& Engineering},
+ keywords = {Bibliometrics,Citation analysis,citation graphs,Computational modeling,Digital systems,Graphical models,Metadata,Publishing,Scholarship,Sociotechnical systems,Software,software citation,Stakeholders,transitive credit},
+ number = {2}
+}
+
+@article{meraliComputationalScienceError2010,
+ title = {Computational Science: ...{{Error}}},
+ copyright = {2010 Nature Publishing Group},
+ shorttitle = {Computational Science},
+ abstract = {\ldots{}why scientific programming does not compute.},
+ language = {En},
+ urldate = {2019-12-05},
+ journal = {Nature},
+ url = {www.nature.com/articles/467775a},
+ doi = {10.1038/467775a},
+ author = {Merali, Zeeya},
+ month = oct,
+ number = 7317,
+ volume = 467,
+ pages = {775–777},
+ year = {2010},
+ file = {/home/stephan/Zotero/storage/RWCEY9XY/467775a.html}
+}
+
+@article{tseComputerCodeMore2010,
+ title = {Computer Code: More Credit Needed},
+ volume = {468},
+ copyright = {2010 Nature Publishing Group, a division of Macmillan Publishers Limited. All Rights Reserved.},
+ issn = {1476-4687},
+ shorttitle = {Computer Code},
+ language = {en},
+ number = {7320},
+ urldate = {2019-12-05},
+ journal = {Nature},
+ url = {www.nature.com/articles/468037a},
+ doi = {10.1038/468037a},
+ author = {Tse, Herman},
+ month = nov,
+ year = {2010},
+ pages = {37},
+ file = {/home/stephan/Zotero/storage/9NIQGDFD/Tse - 2010 - Computer code more credit needed.pdf;/home/stephan/Zotero/storage/KLRMFSIZ/468037a.html}
+}
+
+@article{barnesPublishYourComputer2010,
+ title = {Publish Your Computer Code: It Is Good Enough},
+ volume = {467},
+ copyright = {2010 Nature Publishing Group},
+ issn = {1476-4687},
+ shorttitle = {Publish Your Computer Code},
+ abstract = {Freely provided working code \textemdash{} whatever its quality \textemdash{} improves programming and enables others to engage with your research, says Nick Barnes.},
+ language = {en},
+ number = {7317},
+ urldate = {2019-12-05},
+ journal = {Nature},
+ url = {www.nature.com/articles/467753a},
+ doi = {10.1038/467753a},
+ author = {Barnes, Nick},
+ month = oct,
+ year = {2010},
+ pages = {753},
+ file = {/home/stephan/Zotero/storage/JI59ZPAA/Barnes - 2010 - Publish your computer code it is good enough.pdf;/home/stephan/Zotero/storage/9BTIY8IK/467753a.html}
+}
+
+
+@article{morinQuickGuideSoftware2012,
+ title = {A {{Quick Guide}} to {{Software Licensing}} for the {{Scientist}}-{{Programmer}}},
+ volume = {8},
+ issn = {1553-7358},
+ language = {en},
+ number = {7},
+ urldate = {2019-12-05},
+ journal = {PLOS Computational Biology},
+ url = {journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1002598},
+ doi = {10.1371/journal.pcbi.1002598},
+ author = {Morin, Andrew and Urban, Jennifer and Sliz, Piotr},
+ month = jul,
+ year = {2012},
+ keywords = {Computer software,Open access publishing,Open source software,Peer review,Scientists,Software development,Software tools,Source code},
+ pages = {e1002598}
+
+}
+
+
+@article{rodriguez-sanchezAcademiaFailureRetain2017,
+ title = {Academia's Failure to Retain Data Scientists},
+ volume = {355},
+ copyright = {Copyright \textcopyright{} 2017, American Association for the Advancement of Science},
+ issn = {0036-8075, 1095-9203},
+ language = {en},
+ number = {6323},
+ urldate = {2019-12-05},
+ journal = {Science},
+ url = {science.sciencemag.org/content/355/6323/357.3},
+ doi = {10.1126/science.aam6116},
+ author = {{Rodr{\'i}guez-S{\'a}nchez}, Francisco and Marwick, Ben and Lazowska, Ed and VanderPlas, Jake},
+ month = jan,
+ year = {2017},
+ pages = {357-358},
+ file = {/home/stephan/Zotero/storage/C2FUWBEI/357.html},
+ pmid = {28126779}
+}
+
+
+@misc{delft,
+ doi = {10.4233/UUID:F2FAFF07-408F-4CEC-BD87-0919C9E4C26F},
+ url = {resolver.tudelft.nl/uuid:f2faff07-408f-4cec-bd87-0919c9e4c26f},
+ author = {Haslinger, I.M.},
+ title = {TU Delft Strategic Plan Open Science 2020-2024: Research and Education in the Open Era},
+ publisher = {Delft University of Technology},
+ year = {2019}
+}
+
+@article{Hirsch2005,
+ doi = {10.1073/pnas.0507655102},
+ year = {2005},
+ month = nov,
+ volume = {102},
+ number = {46},
+ pages = {16569--16572},
+ author = {J. E. Hirsch},
+ title = {An index to quantify an individual{\textquotesingle}s scientific research output},
+ journal = {PNAS}
+}
+
+
+@article{Stodden2014,
+ title = {Best {{Practices}} for {{Computational Science}}: {{Software Infrastructure}} and {{Environments}} for {{Reproducible}} and {{Extensible Research}}},
+ volume = {2},
+ copyright = {Authors who publish with this journal agree to the following terms: Authors retain copyright and grant the journal right of first publication with the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgement of the work's authorship and initial publication in this journal. Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgement of its initial publication in this journal. Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work (See The Effect of Open Access ). All third-party images reproduced on this journal are shared under Educational Fair Use. For more information on Educational Fair Use , please see this useful checklist prepared by Columbia University Libraries . All copyright of third-party content posted here for research purposes belongs to its original owners. Unless otherwise stated all references to characters and comic art presented on this journal are \textcopyright, \textregistered{} or \texttrademark{} of their respective owners. No challenge to any owner's rights is intended or should be inferred.},
+ issn = {2049-9647},
+ shorttitle = {Best {{Practices}} for {{Computational Science}}},
+ abstract = {The goal of this article is to coalesce a discussion around best practices for scholarly research that utilizes computational methods, by providing a formalized set of best practice recommendations to guide computational scientists and other stakeholders wishing to disseminate reproducible research, facilitate innovation by enabling data and code re-use, and enable broader communication of the output of computational scientific research. Scholarly dissemination and communication standards are changing to reflect the increasingly computational nature of scholarly research, primarily to include the sharing of the data and code associated with published results. We also present these Best Practices as a living, evolving, and changing document at wiki.stodden.net/Best\_Practices.},
+ language = {en},
+ number = {1},
+ urldate = {2019-09-04},
+ journal = {Journal of Open Research Software},
+ url = {http://openresearchsoftware.metajnl.com/articles/10.5334/jors.ay},
+ doi = {10.5334/jors.ay},
+ author = {Stodden, Victoria and Miguez, Sheila},
+ month = jul,
+ year = {2014},
+ keywords = {open science,reproducible research,computational science,best practices,code sharing,data sharing,scientific method,archiving,wiki},
+ pages = {e21}
+}
+
+@inproceedings{Venters2014,
+ address = {{Karlskrona, Sweden}},
+ title = {Software {{Sustainability}}: {{The Modern Tower}} of {{Babel}}},
+ volume = {1216},
+ abstract = {The development of sustainable software has been identified as one of the key challenges in the field of computational science and engineering. However, there is currently no agreed definition of the concept. Current definitions range from a composite, non-functional requirement to simply an emergent property. This lack of clarity leads to confusion, and potentially to ineffective and inefficient efforts to develop sustainable software systems. The aim of this paper is to explore the emerging definitions of software sustainability from the field of software engineering in order to contribute to the question, what is software sustainability? The preliminary analysis suggests that the concept of software sustainability is complex and multifaceted with any consensus towards a shared definition within the field of software engineering yet to be achieved.},
+ language = {en},
+ booktitle = {Proceedings of the {{Third International Workshop}} on {{Requirements Engineering}} for {{Sustainable Systems}} Co-Located with 22nd {{International Conference}} on {{Requirements Engineering}} ({{RE}} 2014)},
+ publisher = {{CEUR-WS}},
+ url = {http://ceur-ws.org/Vol-1216/paper2.pdf},
+ author = {Venters, Colin C and Jay, Caroline and Lau, L. M. S. and Griffiths, M. K. and Holmes, V. and Ward, R. R. and Austin, J. and Dibsdale, C. E. and Xu, J.},
+ month = aug,
+ year = {2014},
+ pages = {7-12},
+ file = {/home/stephan/Zotero/storage/R52RKCHI/Venters - Software Sustainability The Modern Tower of Babel.pdf}
+}
+
+@inproceedings{Druskat2016,
+ address = {{Manchester, UK}},
+ title = {A Proposal for the Measurement and Documentation of Research Software Sustainability in Interactive Metadata Repositories},
+ volume = {1686},
+ copyright = {All rights reserved},
+ booktitle = {Proceedings of the {{Fourth Workshop}} on {{Sustainable Software}} for {{Science}}: {{Practice}} and {{Experiences}} ({{WSSSPE4}})},
+ publisher = {{CEUR-WS}},
+ url = {http://ceur-ws.org/Vol-1686/WSSSPE4_paper_20.pdf},
+ author = {Druskat, Stephan},
+ editor = {Allen, Gabrielle and Carver, Jeffrey and Choi, Sou-Cheng T. and Crick, Tom and Crusoe, Michael R. and Gesing, Sandra and Haines, Robert and Heroux, Michael and Hwang, Lorraine J. and Katz, Daniel S. and Niemeyer, Kyle E. and Parashar, Manish and Venters, Colin C.},
+ month = sep,
+ year = {2016}
+}
+
+@article{Goble2014,
+ title = {Better {{Software}}, {{Better Research}}},
+ volume = {18},
+ issn = {1089-7801},
+ abstract = {Modern scientific research isn't possible without software. However, its vital role is often overlooked by funders, universities, assessment committees, and even the research community itself. This is a serious issue that needs urgent attention. This article raises a number of points concerning quality, code review, and openness; development practices and training in scientific computing; career recognition of research software engineers; and sustainability models for funding scientific software. We must get software recognized to be the first-class experimental scientific instrument that it is and get "better software for better research."},
+ number = {5},
+ journal = {IEEE Internet Computing},
+ doi = {10.1109/MIC.2014.88},
+ author = {Goble, C.},
+ month = sep,
+ year = {2014},
+ keywords = {sustainability,scientific software,engineering},
+ pages = {4-8},
+ file = {/home/stephan/Zotero/storage/RWIGL3VN/Goble - 2014 - Better Software, Better Research.pdf;/home/stephan/Zotero/storage/MT7MBYN9/6886129.html}
+}
+
+@misc{KatzFundamentalsSoftwareSustainability2018,
+ title = {Fundamentals of {{Software Sustainability}}},
+ abstract = {This blog post is intended as companion text for a talk I gave at the September 2018 NumFOCUS Project Forum in in New York, though I also hope it stands on its own. To address software sustainabili\ldots{}},
+ language = {en},
+ urldate = {2019-12-13},
+ author = {Katz, Daniel S.},
+ journal = {Daniel S. Katz's blog},
+ url = {web.archive.org/web/20191213110119/danielskatzblog.wordpress.com/2018/09/26/fundamentals-of-software-sustainability},
+ month = sep,
+ year = {2018},
+ file = {/home/stephan/Zotero/storage/NI3JB6SR/fundamentals-of-software-sustainability.html}
+}
+
+@misc{katzLookingSoftwareSustainability2015,
+ archivePrefix = {arXiv},
+ eprinttype = {arxiv},
+ arxiv = {1508.03348},
+ primaryClass = {cs},
+ title = {Looking at {{Software Sustainability}} and {{Productivity Challenges}} from {{NSF}}},
+ abstract = {This paper is a contribution to the Computational Science \& Engineering Software Sustainability and Productivity Challenges (CSESSP Challenges) Workshop (www.nitrd.gov/csessp/), sponsored by the Networking and Information Technology Research and Development (NITRD) Software Design and Productivity (SDP) Coordinating Group, held October 15th-16th 2015 in Washington DC, USA. It introduces the role of software at the National Science Foundation (NSF) and the NSF Software Infrastructure for Sustained Innovation (SI2) program, then describes challenges that the SI2 program has identified, including funding models, career paths, incentives, training, interdisciplinary work, portability, and dissemination, as well as lesson that have been learned.},
+ urldate = {2019-02-01},
+ journal = {arXiv:1508.03348 [cs]},
+ url = {http://arxiv.org/abs/1508.03348},
+ author = {Katz, Daniel S. and Ramnath, Rajiv},
+ month = aug,
+ year = {2015},
+ keywords = {Computer Science - Software Engineering,Computer Science - Computers and Society},
+ file = {/home/stephan/Zotero/storage/ZZCCS9UE/Katz and Ramnath - 2015 - Looking at Software Sustainability and Productivit.pdf;/home/stephan/Zotero/storage/Q9SLMIJ4/1508.html}
+}
+
+@misc{ChanZuckerberg,
+ title = {Essential {{Open Source Software}} for {{Science}}},
+ abstract = {The Chan Zuckerberg Initiative is inviting applications for one-year open source software projects that are essential to biomedical research. This RFA is the first of a series. CZI will invite applications during three distinct cycles, with rounds beginning June 18, 2019; mid-December 2019; and mid-June 2020.},
+ language = {en-US},
+ urldate = {2019-12-13},
+ author = {{Chan Zuckerberg Initiative}},
+ url = {web.archive.org/web/20191213112602/chanzuckerberg.com/rfa/essential-open-source-software-for-science},
+ file = {/home/stephan/Zotero/storage/V6TS2N4R/essential-open-source-software-for-science.html}
+}
+
+@article{Hafer2009,
+ title = {Assessing {{Open Source Software As}} a {{Scholarly Contribution}}},
+ volume = {52},
+ issn = {0001-0782},
+ number = {12},
+ urldate = {2018-05-16},
+ journal = {Commun. ACM},
+ url = {http://doi.acm.org/10.1145/1610252.1610285},
+ doi = {10.1145/1610252.1610285},
+ author = {Hafer, Lou and Kirkpatrick, Arthur E.},
+ month = dec,
+ year = {2009},
+ pages = {126--129},
+ file = {/home/stephan/Zotero/storage/46S98G52/Hafer und Kirkpatrick - 2009 - Assessing Open Source Software As a Scholarly Cont.pdf}
+}
+
+@article{Howison2016,
+ title = {Software in the Scientific Literature: {{Problems}} with Seeing, Finding, and Using Software Mentioned in the Biology Literature},
+ volume = {67},
+ issn = {2330-1643},
+ abstract = {Software is increasingly crucial to scholarship, yet the visibility and usefulness of software in the scientific record are in question. Just as with data, the visibility of software in publications is related to incentives to share software in reusable ways, and so promote efficient science. In this article, we examine software in publications through content analysis of a random sample of 90 biology articles. We develop a coding scheme to identify software ``mentions'' and classify them according to their characteristics and ability to realize the functions of citations. Overall, we find diverse and problematic practices: Only between 31\% and 43\% of mentions involve formal citations; informal mentions are very common, even in high impact factor journals and across different kinds of software. Software is frequently inaccessible (15\%\textendash{}29\% of packages in any form; between 90\% and 98\% of specific versions; only between 24\%\textendash{}40\% provide source code). Cites to publications are particularly poor at providing version information, whereas informal mentions are particularly poor at providing crediting information. We provide recommendations to improve the practice of software citation, highlighting recent nascent efforts. Software plays an increasingly great role in scientific practice; it deserves a clear and useful place in scholarly communication.},
+ number = {9},
+ journal = {Journal of the Association for Information Science and Technology},
+ url = {http://dx.doi.org/10.1002/asi.23538},
+ doi = {10.1002/asi.23538},
+ author = {Howison, James and Bullard, Julia},
+ year = {2016},
+ keywords = {bibliographic citations,biology,journals},
+ pages = {2137--2155}
+}
+
+@article{Park2019,
+ title = {Research Software Citation in the {{Data Citation Index}}: {{Current}} Practices and Implications for Research Software Sharing and Reuse},
+ volume = {13},
+ issn = {1751-1577},
+ shorttitle = {Research Software Citation in the {{Data Citation Index}}},
+ number = {2},
+ urldate = {2019-05-08},
+ journal = {Journal of Informetrics},
+ url = {http://www.sciencedirect.com/science/article/pii/S1751157718302372},
+ doi = {10.1016/j.joi.2019.03.005},
+ author = {Park, Hyoungjoo and Wolfram, Dietmar},
+ month = may,
+ year = {2019},
+ keywords = {Software reuse,Software citation,Research data,Research software,Software sharing},
+ pages = {574-582},
+ file = {/home/stephan/Zotero/storage/TDSHQ26E/Park_Wolfram_JOI_2019.pdf;/home/stephan/Zotero/storage/YKAMWAWU/S1751157718302372.html}
+}
+
+@article{Li2017,
+ title = {How Is {{R}} Cited in Research Outputs? {{Structure}}, Impacts, and Citation Standard},
+ volume = {11},
+ issn = {1751-1577},
+ shorttitle = {How Is {{R}} Cited in Research Outputs?},
+ number = {4},
+ urldate = {2019-05-08},
+ journal = {Journal of Informetrics},
+ url = {http://www.sciencedirect.com/science/article/pii/S1751157717300329},
+ doi = {10.1016/j.joi.2017.08.003},
+ author = {Li, Kai and Yan, Erjia and Feng, Yuanyuan},
+ month = nov,
+ year = {2017},
+ keywords = {Software citation,Bibliometrics,Content analysis,R,Scholarly communication},
+ pages = {989-1002},
+ file = {/home/stephan/Zotero/storage/X75P2PKL/Li et al. - 2017 - How is R cited in research outputs Structure, imp.pdf;/home/stephan/Zotero/storage/KLYGZ3F8/S1751157717300329.html}
+}
+
+
+@article{Pan2019,
+ title = {How Important Is Software to Library and Information Science Research? {{A}} Content Analysis of Full-Text Publications},
+ volume = {13},
+ issn = {1751-1577},
+ shorttitle = {How Important Is Software to Library and Information Science Research?},
+ number = {1},
+ urldate = {2019-05-08},
+ journal = {Journal of Informetrics},
+ url = {http://www.sciencedirect.com/science/article/pii/S1751157718304504},
+ doi = {10.1016/j.joi.2019.02.002},
+ author = {Pan, Xuelian and Yan, Erjia and Cui, Ming and Hua, Weina},
+ month = feb,
+ year = {2019},
+ keywords = {Software,Software citation,Bibliometrics,Scholarly communication,Citation analysis},
+ pages = {397-406},
+ file = {/home/stephan/Zotero/storage/4UVHUUXC/Pan et al. - 2019 - How important is software to library and informati.pdf;/home/stephan/Zotero/storage/6ANR67EV/S1751157718304504.html}
+}
+
+@article{Doerr2019,
+ title = {Giving Software Its Due},
+ volume = {16},
+ copyright = {2019 Springer Nature America, Inc.},
+ issn = {1548-7105},
+ abstract = {Software and algorithm development is crucial for scientific progress; we discuss how to improve the impact and recognition of these tools.},
+ language = {en},
+ number = {3},
+ urldate = {2019-08-23},
+ journal = {Nature Methods},
+ url = {doi.org/10.1038/s41592-019-0350-x},
+ doi = {10.1038/s41592-019-0350-x},
+ author = {Doerr, Allison and Rusk, Nicole and Vogt, Nina and Strack, Rita and Tang, Lei and Arunima, Singh and Marx, Vivien},
+ month = mar,
+ year = {2019},
+ pages = {207-207},
+ file = {/home/stephan/Zotero/storage/VHFGABWE/2019 - Giving software its due.pdf;/home/stephan/Zotero/storage/8W7GPBIF/s41592-019-0350-x.html}
+}
+
+@misc{de-rse,
+ title = {de-{{RSE}}.org - {{Research Software Engineers}} ({{RSEs}}) - {{The}} People behind Research Software},
+ urldate = {2019-12-13},
+ url = {web.archive.org/web/20190325110948/www.de-rse.org/en},
+ author = {{de-RSE e.V. - Society for Research Software}},
+ file = {/home/stephan/Zotero/storage/AH7CDF78/en.html}
+}
+
+@misc{us-rse,
+ title = {{{US}}-{{RSE}}},
+ abstract = {The US Research Software Engineer Association},
+ language = {en},
+ urldate = {2019-12-13},
+ url = {web.archive.org/web/20191213123453/us-rse.org},
+ author = {{The US Research Software Engineer Association}},
+ file = {/home/stephan/Zotero/storage/IVCITZXK/us-rse.org.html}
+}
+
+@misc{nl-rse,
+ title = {The {{Netherlands Research Software Engineer}} Community},
+ abstract = {The community of Research Software Engineers from Dutch universities, knowledge institutes, companies and other relevant organizations for sharing knowledge, organizing meetings and raising awareness for the scientific recognition of research software.},
+ language = {en},
+ urldate = {2019-12-13},
+ journal = {NL-RSE},
+ url = {web.archive.org/web/20191213123459/nl-rse.org},
+ author = {{The Netherlands Research Software Engineer community}},
+ file = {/home/stephan/Zotero/storage/J4SNVYY6/nl-rse.org.html}
+}
+
+
+@article{Katz2019,
+ title = {The {{State}} of {{Sustainable Research Software}}: {{Learning}} from the {{Workshop}} on {{Sustainable Software}} for {{Science}}: {{Practice}} and {{Experiences}} ({{WSSSPE5}}.1)},
+ volume = {7},
+ issn = {2049-9647},
+ shorttitle = {The {{State}} of {{Sustainable Research Software}}},
+ language = {en},
+ number = {1},
+ urldate = {2019-04-02},
+ journal = {Journal of Open Research Software},
+ url = {openresearchsoftware.metajnl.com/articles/10.5334/jors.242},
+ doi = {10.5334/jors.242},
+ author = {Katz, Daniel S. and Druskat, Stephan and Haines, Robert and Jay, Caroline and Struck, Alexander},
+ month = apr,
+ year = {2019},
+ keywords = {research software,sustainable software},
+ pages = {11},
+ file = {/home/stephan/Zotero/storage/4TPVCLLM/Katz et al. - 2019 - The State of Sustainable Research Software Learni.pdf;/home/stephan/Zotero/storage/IUHF9WFJ/jors.html}
+}
+
+@inproceedings{Druskat2018,
+ title = {Mapping the {{Research Software Sustainability Space}}},
+ abstract = {A growing number of largely uncoordinated initiatives focus on research software sustainability. A comprehensive mapping of the research software sustainability space can help identify gaps in their efforts, track results, and avoid duplication of work. To this end, this paper suggests enhancing an existing schematic of activities in research software sustainability, and formalizing it in a directed graph model. Such a model can be further used to define a classification schema which, applied to research results in the field, can drive the identification of past activities and the planning of future efforts.},
+ booktitle = {2018 {{IEEE}} 14th {{International Conference}} on E-{{Science}} (e-{{Science}})},
+ url = {doi.org/10.1109/eScience.2018.00014},
+ doi = {10.1109/eScience.2018.00014},
+ author = {Druskat, Stephan and Katz, Daniel S.},
+ month = oct,
+ year = {2018},
+ keywords = {classification schema,communities,comprehensive mapping,Conferences,directed graph model,directed graphs,modeling,Organizations,research software,research software sustainability space,scientific computing,Software,software engineering,Software engineering,Software measurement,Standards organizations,sustainable development,Sustainable development,uncoordinated initiatives focus,visualization},
+ pages = {25-30},
+ file = {/home/stephan/Zotero/storage/X5KKVTRD/Druskat and Katz - 2018 - Mapping the Research Software Sustainability Space.pdf;/home/stephan/Zotero/storage/64XLPCEV/8588633.html},
+ isbn = {978-1-5386-9156-4}
+}
+
+@misc{publiccode,
+ author = {{Free Software Foundation Europe}},
+ title = {Public Money Public Code},
+ year = 2017,
+ url = {publiccode.eu}
+}
+
+@misc{CClicense,
+ author = {{Creative Commons}},
+ title = {Licenses},
+ year = 2019,
+ url = {creativecommons.org/licenses}
+}
+
+@misc{Invenio,
+ author = {CERN},
+ year = 2019,
+ url = {invenio-software.org}
+}
+
+@misc{BayreutherErklaerung,
+ author = {{Vereinigung der Kanzlerinnen und Kanzler der Universitäten Deutschlands}},
+ title = {Bayreuther Erklärung zu befristeten Beschäftigungsverhältnissen mit wissenschaftlichem und künstlerischem Personal in Universitäten},
+ year = {2019},
+ url = {www.uni-kanzler.de/fileadmin/user_upload/05_Publikationen/2017_-_2010/20190919_Bayreuther_Erklaerung_der_Universitaetskanzler_final.pdf}
+}
+
+@article{KVK,
+ title={KVK - a meta catalog of libraries},
+ author={M{\"o}nnich, Michael W},
+ journal={LIBER Quarterly},
+ volume={11},
+ number={2},
+ pages={121--127},
+ year={2001},
+}
+%publisher={Igitur}
+
+@techreport{kunze2018bagit,
+ title={The bag{I}t file packaging format (v1. 0)},
+ author={Kunze, John and Scancella, John and Adams, Chris and Littman, Justin},
+ HOWPUBLISHED = {Internet Requests for Comments},
+ TYPE="{RFC}",
+ NUMBER=8493,
+ ISSN={2070-1721},
+ year={2018},
+ URL={tools.ietf.org/html/rfc8493},
+ PUBLISHER = "{RFC Editor}",
+ INSTITUTION = "{RFC Editor}",
+ doi={10.17487/RFC8493},
+}
+
+@article{Prins2015,
+ doi = {10.1038/nbt.3240},
+ year = {2015},
+ month = jul,
+ publisher = {Springer Science and Business Media {LLC}},
+ volume = {33},
+ number = {7},
+ pages = {686--687},
+ author = {Pjotr Prins and Joep de Ligt and Artem Tarasov and Ritsert C Jansen and Edwin Cuppen and Philip E Bourne},
+ title = {Toward effective software solutions for big biology},
+ journal = {Nature Biotechnology}
+}
+
+@article{Kuchinke2016,
+ doi = {10.2217/pme.15.43},
+ url = {doi.org/10.2217/pme.15.43},
+ year = {2016},
+ month = jan,
+ publisher = {Future Medicine Ltd},
+ volume = {13},
+ number = {1},
+ pages = {43--55},
+ author = {Wolfgang Kuchinke and Christian Ohmann and Holger Stenzhorn and Alberto Anguista and Stelios Sfakianakis and Norbert Graf and Jacques Demotes},
+ title = {Ensuring sustainability of software tools and services by cooperation with a research infrastructure},
+ journal = {Personalized Medicine}
+}
+
+@inproceedings{chang2007open,
+ title={From Open Source to long-term sustainability: Review of Business Models and Case studies},
+ author={Chang, Victor and Mills, Hugo and Newhouse, Steven},
+ booktitle={Proceedings of the UK e-Science All Hands Meeting 2007},
+ year={2007},
+ organization={University of Edinburgh/University of Glasgow (acting through the NeSC)},
+ url = {eprints.leedsbeckett.ac.uk/649}
+}
+
+@article{Aartsen2018,
+ doi = {10.3389/fmed.2018.00065},
+ url = {doi.org/10.3389/fmed.2018.00065},
+ year = {2018},
+ month = mar,
+ publisher = {Frontiers Media {SA}},
+ volume = {5},
+ pages = 65,
+ author = {Wendy Aartsen and Paul Peeters and Scott Wagers and Bryn Williams-Jones},
+ title = {Getting Digital Assets from Public{\textendash}Private Partnership Research Projects through {\textquotedblleft}The Valley of Death, {\textquotedblright} and Making Them Sustainable},
+ journal = {Frontiers in Medicine}
+}
+
+@article{Gabella2018,
+ doi = {10.12688/f1000research.12989.2},
+ url = {doi.org/10.12688/f1000research.12989.2},
+ year = {2018},
+ month = mar,
+ publisher = {F1000 Research Ltd},
+ volume = {6},
+ pages = {2051},
+ author = {Chiara Gabella and Christine Durinx and Ron Appel},
+ title = {Funding knowledgebases: Towards a sustainable funding model for the {UniProt} use case},
+ journal = {F1000Research}
+}
+
+@misc{iaffaldano2019developers,
+ title={Why do developers take breaks from contributing to OSS projects? A preliminary analysis},
+ author={Iaffaldano, Giuseppe and Steinmacher, Igor and Calefato, Fabio and Gerosa, Marco and Lanubile, Filippo},
+ arxiv={1903.09528},
+ archivePrefix={arXiv},
+ primaryClass={cs.SE},
+ year={2019}
+}
+
+@misc{ye2019open,
+ title={Open Source Software Sustainability Models: Initial White Paper from the Informatics Technology for Cancer Research Sustainability and Industry Partnership Work Group},
+ author={Y. Ye and R. D. Boyce and M. K. Davis and K. Elliston and C. Davatzikos and A. Fedorov and J. C. Fillion-Robin and I. Foster and J. Gilbertson and M. Heiskanen and J. Klemm and A. Lasso and J. V. Miller and M. Morgan and S. Pieper and B. Raumann and B. Sarachan and G. Savova and J. C. Silverstein and D. Taylor and J. Zelnis and G. Q. Zhang and M. J. Becich},
+ year={2019},
+ eprint={1912.12371},
+ archivePrefix={arXiv},
+ primaryClass={q-bio.OT}
+}
+
+@book{carver2016software,
+ title={Software engineering for science},
+ author={Carver, Jeffrey C and Hong, Neil P Chue and Thiruvathukal, George K},
+ year={2016},
+ publisher={CRC Press}
+}
+
+@inproceedings{SuLMaSS,
+ doi = {10.11588/HEIDOK.00026843},
+ url = {dx.doi.org/10.11588/HEIDOK.00026843},
+ author = {Loewe, Axel and Seemann, Gunnar and W\"{u}lfers, Eike Moritz and Huang, Yung-Lin and Sánchez, Jorge and Bach, Felix and Ulrich, Robert and Selzer, Michael},
+ title = {{SuLMaSS} - Sustainable Lifecycle Management for Scientific Software},
+ booktitle= {E-Science-Tage 2019: Data to Knowledge},
+ year = {2019}
+}
+
+@misc{ORCiD,
+ title = {ORCID},
+ year = 2019,
+ url = {orcid.org/}
+}
+
+@misc{katerbow2018,
+ author = {Katerbow, Matthias and
+ Feulner, Georg},
+ title = {Recommendations on the development, use and
+ provision of Research Software},
+ year = 2018,
+ doi = {10.5281/zenodo.1172988},
+ url = {https://doi.org/10.5281/zenodo.1172988}
+}
+
+
+@misc{Akhmerov2019,
+ title = {Making {{Research Software}} a {{First}}-{{Class Citizen}} in {{Research}}},
+ author = {Akhmerov, Anton and Cruz, Maria and Drost, Niels and Hof, Cees and Knapen, Tomas and Kuzak, Mateusz and {Martinez-Ortiz}, Carlos and {Turkyilmaz-van der Velden}, Yasemin},
+ year = {2019},
+ month = apr,
+ doi = {10.5281/zenodo.2647436},
+ url = {https://zenodo.org/record/2647436},
+ urldate = {2020-01-13},
+ abstract = {The authors are listed alphabetically~by order of last name. This presentation was collaboratively prepared for and given~at a meeting with~NWO (The Netherlands Organisation for Scientific Research; the national research council of the Netherlands) on 28 March 2019. Our aim was~to highlight the importance of research software in contemporary research and its relationship to research data, open science, and reproducibility in research.~ Our key messages to NWO: If open science is to lead towards better, more transparent, and reproducible research, then research software, research data and publications need all to be treated on equal footing at the policy level. NWO should make more explicit policies for supporting and evaluating research software. There are some differences when it comes to research software preservation (Software Sustainability) as compared to data preservation, but it shouldn't be more difficult.},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\2LUJ29LJ\\Akhmerov et al. - 2019 - Making Research Software a First-Class Citizen in .pdf},
+ keywords = {FAIR software,open science,research data,research software,RSE,software sustainability}
+}
+
+@misc{ChueHong2019,
+ title = {Making {{Software A First}}-{{Class Citizen}}},
+ author = {Chue Hong, Neil},
+ year = {2019},
+ month = sep,
+ doi = {10.6084/m9.figshare.9862835.v1},
+ url = {https://figshare.com/articles/Making_Software_A_First-Class_Citizen/9862835},
+ urldate = {2020-01-13},
+ abstract = {What are barriers to collaborating internationally on research software? How might we overcome them?},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\BQW3EWUW\\9862835.pdf},
+ keywords = {Research Software,Research Software Engineering,Software Sustainability Institute}
+}
+
+% M87 references
+
+@article{TheEventHorizonTelescopeCollaboration2019,
+ title = {First {{M87 Event Horizon Telescope Results}}. {{I}}. {{The Shadow}} of the {{Supermassive Black Hole}}},
+ author = {{The Event Horizon Telescope Collaboration} and Akiyama, Kazunori and Alberdi, Antxon and Alef, Walter and Asada, Keiichi and Azulay, Rebecca and Baczko, Anne-Kathrin and Ball, David and Balokovi{\'c}, Mislav and Barrett, John and Bintley, Dan and Blackburn, Lindy and Boland, Wilfred and Bouman, Katherine L. and Bower, Geoffrey C. and Bremer, Michael and Brinkerink, Christiaan D. and Brissenden, Roger and Britzen, Silke and Broderick, Avery E. and Broguiere, Dominique and Bronzwaer, Thomas and Byun, Do-Young and Carlstrom, John E. and Chael, Andrew and Chan, Chi-kwan and Chatterjee, Shami and Chatterjee, Koushik and Chen, Ming-Tang and Chen, Yongjun and Cho, Ilje and Christian, Pierre and Conway, John E. and Cordes, James M. and Crew, Geoffrey B. and Cui, Yuzhu and Davelaar, Jordy and Laurentis, Mariafelicia De and Deane, Roger and Dempsey, Jessica and Desvignes, Gregory and Dexter, Jason and Doeleman, Sheperd S. and Eatough, Ralph P. and Falcke, Heino and Fish, Vincent L. and Fomalont, Ed and {Fraga-Encinas}, Raquel and Freeman, William T. and Friberg, Per and Fromm, Christian M. and G{\'o}mez, Jos{\'e} L. and Galison, Peter and Gammie, Charles F. and Garc{\'i}a, Roberto and Gentaz, Olivier and Georgiev, Boris and Goddi, Ciriaco and Gold, Roman and Gu, Minfeng and Gurwell, Mark and Hada, Kazuhiro and Hecht, Michael H. and Hesper, Ronald and Ho, Luis C. and Ho, Paul and Honma, Mareki and Huang, Chih-Wei L. and Huang, Lei and Hughes, David H. and Ikeda, Shiro and Inoue, Makoto and Issaoun, Sara and James, David J. and Jannuzi, Buell T. and Janssen, Michael and Jeter, Britton and Jiang, Wu and Johnson, Michael D. and Jorstad, Svetlana and Jung, Taehyun and Karami, Mansour and Karuppusamy, Ramesh and Kawashima, Tomohisa and Keating, Garrett K. and Kettenis, Mark and Kim, Jae-Young and Kim, Junhan and Kim, Jongsoo and Kino, Motoki and Koay, Jun Yi and Koch, Patrick M. and Koyama, Shoko and Kramer, Michael and Kramer, Carsten and Krichbaum, Thomas P. and Kuo, Cheng-Yu and Lauer, Tod R. and Lee, Sang-Sung and Li, Yan-Rong and Li, Zhiyuan and Lindqvist, Michael and Liu, Kuo and Liuzzo, Elisabetta and Lo, Wen-Ping and Lobanov, Andrei P. and Loinard, Laurent and Lonsdale, Colin and Lu, Ru-Sen and MacDonald, Nicholas R. and Mao, Jirong and Markoff, Sera and Marrone, Daniel P. and Marscher, Alan P. and {Mart{\'i}-Vidal}, Iv{\'a}n and Matsushita, Satoki and Matthews, Lynn D. and Medeiros, Lia and Menten, Karl M. and Mizuno, Yosuke and Mizuno, Izumi and Moran, James M. and Moriyama, Kotaro and Moscibrodzka, Monika and M{\"u}ller, Cornelia and Nagai, Hiroshi and Nagar, Neil M. and Nakamura, Masanori and Narayan, Ramesh and Narayanan, Gopal and Natarajan, Iniyan and Neri, Roberto and Ni, Chunchong and Noutsos, Aristeidis and Okino, Hiroki and Olivares, H{\'e}ctor and {Ortiz-Le{\'o}n}, Gisela N. and Oyama, Tomoaki and {\"O}zel, Feryal and Palumbo, Daniel C. M. and Patel, Nimesh and Pen, Ue-Li and Pesce, Dominic W. and Pi{\'e}tu, Vincent and Plambeck, Richard and PopStefanija, Aleksandar and Porth, Oliver and Prather, Ben and {Preciado-L{\'o}pez}, Jorge A. and Psaltis, Dimitrios and Pu, Hung-Yi and Ramakrishnan, Venkatessh and Rao, Ramprasad and Rawlings, Mark G. and Raymond, Alexander W. and Rezzolla, Luciano and Ripperda, Bart and Roelofs, Freek and Rogers, Alan and Ros, Eduardo and Rose, Mel and Roshanineshat, Arash and Rottmann, Helge and Roy, Alan L. and Ruszczyk, Chet and Ryan, Benjamin R. and Rygl, Kazi L. J. and S{\'a}nchez, Salvador and {S{\'a}nchez-Arguelles}, David and Sasada, Mahito and Savolainen, Tuomas and Schloerb, F. Peter and Schuster, Karl-Friedrich and Shao, Lijing and Shen, Zhiqiang and Small, Des and Sohn, Bong Won and SooHoo, Jason and Tazaki, Fumie and Tiede, Paul and Tilanus, Remo P. J. and Titus, Michael and Toma, Kenji and Torne, Pablo and Trent, Tyler and Trippe, Sascha and Tsuda, Shuichiro and van Bemmel, Ilse and {van Langevelde}, Huib Jan and {van Rossum}, Daniel R. and Wagner, Jan and Wardle, John and Weintroub, Jonathan and Wex, Norbert and Wharton, Robert and Wielgus, Maciek and Wong, George N. and Wu, Qingwen and Young, Ken and Young, Andr{\'e} and Younsi, Ziri and Yuan, Feng and Yuan, Ye-Fei and Zensus, J. Anton and Zhao, Guangyao and Zhao, Shan-Shan and Zhu, Ziyan and Algaba, Juan-Carlos and Allardi, Alexander and Amestica, Rodrigo and Anczarski, Jadyn and Bach, Uwe and Baganoff, Frederick K. and Beaudoin, Christopher and Benson, Bradford A. and Berthold, Ryan and Blanchard, Jay M. and Blundell, Ray and Bustamente, Sandra and Cappallo, Roger and {Castillo-Dom{\'i}nguez}, Edgar and Chang, Chih-Cheng and Chang, Shu-Hao and Chang, Song-Chu and Chen, Chung-Chen and Chilson, Ryan and Chuter, Tim C. and Rosado, Rodrigo C{\'o}rdova and Coulson, Iain M. and Crawford, Thomas M. and Crowley, Joseph and David, John and Derome, Mark and Dexter, Matthew and Dornbusch, Sven and Dudevoir, Kevin A. and Dzib, Sergio A. and Eckart, Andreas and Eckert, Chris and Erickson, Neal R. and Everett, Wendeline B. and Faber, Aaron and Farah, Joseph R. and Fath, Vernon and Folkers, Thomas W. and Forbes, David C. and Freund, Robert and {G{\'o}mez-Ruiz}, Arturo I. and Gale, David M. and Gao, Feng and Geertsema, Gertie and Graham, David A. and Greer, Christopher H. and Grosslein, Ronald and Gueth, Fr{\'e}d{\'e}ric and Haggard, Daryl and Halverson, Nils W. and Han, Chih-Chiang and Han, Kuo-Chang and Hao, Jinchi and Hasegawa, Yutaka and Henning, Jason W. and {Hern{\'a}ndez-G{\'o}mez}, Antonio and {Herrero-Illana}, Rub{\'e}n and Heyminck, Stefan and Hirota, Akihiko and Hoge, James and Huang, Yau-De and Impellizzeri, C. M. Violette and Jiang, Homin and Kamble, Atish and Keisler, Ryan and Kimura, Kimihiro and Kono, Yusuke and Kubo, Derek and Kuroda, John and Lacasse, Richard and Laing, Robert A. and Leitch, Erik M. and Li, Chao-Te and Lin, Lupin C.-C. and Liu, Ching-Tang and Liu, Kuan-Yu and Lu, Li-Ming and Marson, Ralph G. and {Martin-Cocher}, Pierre L. and Massingill, Kyle D. and Matulonis, Callie and McColl, Martin P. and McWhirter, Stephen R. and Messias, Hugo and {Meyer-Zhao}, Zheng and Michalik, Daniel and Monta{\~n}a, Alfredo and Montgomerie, William and {Mora-Klein}, Matias and Muders, Dirk and Nadolski, Andrew and Navarro, Santiago and Neilsen, Joseph and Nguyen, Chi H. and Nishioka, Hiroaki and Norton, Timothy and Nowak, Michael A. and Nystrom, George and Ogawa, Hideo and Oshiro, Peter and Oyama, Tomoaki and Parsons, Harriet and Paine, Scott N. and Pe{\~n}alver, Juan and Phillips, Neil M. and Poirier, Michael and Pradel, Nicolas and Primiani, Rurik A. and Raffin, Philippe A. and Rahlin, Alexandra S. and Reiland, George and Risacher, Christopher and Ruiz, Ignacio and {S{\'a}ez-Mada{\'i}n}, Alejandro F. and Sassella, Remi and Schellart, Pim and Shaw, Paul and Silva, Kevin M. and Shiokawa, Hotaka and Smith, David R. and Snow, William and Souccar, Kamal and Sousa, Don and Sridharan, T. K. and Srinivasan, Ranjani and Stahm, William and Stark, Anthony A. and Story, Kyle and Timmer, Sjoerd T. and Vertatschitsch, Laura and Walther, Craig and Wei, Ta-Shun and Whitehorn, Nathan and Whitney, Alan R. and Woody, David P. and Wouterloot, Jan G. A. and Wright, Melvin and Yamaguchi, Paul and Yu, Chen-Yu and Zeballos, Milagros and Zhang, Shuo and Ziurys, Lucy},
+ year = {2019},
+ month = apr,
+ volume = {875},
+ pages = {L1},
+ issn = {2041-8213},
+ doi = {10.3847/2041-8213/ab0ec7},
+ url = {http://stacks.iop.org/2041-8205/875/i=1/a=L1?key=crossref.8b277503073a0a9e72958f0aba518652},
+ urldate = {2020-01-20},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\FFDYIEMS\\The Event Horizon Telescope Collaboration et al. - 2019 - First M87 Event Horizon Telescope Results. I. The .pdf},
+ journal = {The Astrophysical Journal},
+ number = {1}
+}
+
+@article{TheEventHorizonTelescopeCollaboration2019a,
+ title = {First {{M87 Event Horizon Telescope Results}}. {{II}}. {{Array}} and {{Instrumentation}}},
+ author = {{The Event Horizon Telescope Collaboration} and Akiyama, Kazunori and Alberdi, Antxon and Alef, Walter and Asada, Keiichi and Azulay, Rebecca and Baczko, Anne-Kathrin and Ball, David and Balokovi{\'c}, Mislav and Barrett, John and Bintley, Dan and Blackburn, Lindy and Boland, Wilfred and Bouman, Katherine L. and Bower, Geoffrey C. and Bremer, Michael and Brinkerink, Christiaan D. and Brissenden, Roger and Britzen, Silke and Broderick, Avery E. and Broguiere, Dominique and Bronzwaer, Thomas and Byun, Do-Young and Carlstrom, John E. and Chael, Andrew and Chan, Chi-kwan and Chatterjee, Shami and Chatterjee, Koushik and Chen, Ming-Tang and Chen, Yongjun and Cho, Ilje and Christian, Pierre and Conway, John E. and Cordes, James M. and Crew, Geoffrey B. and Cui, Yuzhu and Davelaar, Jordy and De Laurentis, Mariafelicia and Deane, Roger and Dempsey, Jessica and Desvignes, Gregory and Dexter, Jason and Doeleman, Sheperd S. and Eatough, Ralph P. and Falcke, Heino and Fish, Vincent L. and Fomalont, Ed and {Fraga-Encinas}, Raquel and Friberg, Per and Fromm, Christian M. and G{\'o}mez, Jos{\'e} L. and Galison, Peter and Gammie, Charles F. and Garc{\'i}a, Roberto and Gentaz, Olivier and Georgiev, Boris and Goddi, Ciriaco and Gold, Roman and Gu, Minfeng and Gurwell, Mark and Hada, Kazuhiro and Hecht, Michael H. and Hesper, Ronald and Ho, Luis C. and Ho, Paul and Honma, Mareki and Huang, Chih-Wei L. and Huang, Lei and Hughes, David H. and Ikeda, Shiro and Inoue, Makoto and Issaoun, Sara and James, David J. and Jannuzi, Buell T. and Janssen, Michael and Jeter, Britton and Jiang, Wu and Johnson, Michael D. and Jorstad, Svetlana and Jung, Taehyun and Karami, Mansour and Karuppusamy, Ramesh and Kawashima, Tomohisa and Keating, Garrett K. and Kettenis, Mark and Kim, Jae-Young and Kim, Junhan and Kim, Jongsoo and Kino, Motoki and Koay, Jun Yi and Koch, Patrick M. and Koyama, Shoko and Kramer, Michael and Kramer, Carsten and Krichbaum, Thomas P. and Kuo, Cheng-Yu and Lauer, Tod R. and Lee, Sang-Sung and Li, Yan-Rong and Li, Zhiyuan and Lindqvist, Michael and Liu, Kuo and Liuzzo, Elisabetta and Lo, Wen-Ping and Lobanov, Andrei P. and Loinard, Laurent and Lonsdale, Colin and Lu, Ru-Sen and MacDonald, Nicholas R. and Mao, Jirong and Markoff, Sera and Marrone, Daniel P. and Marscher, Alan P. and {Mart{\'i}-Vidal}, Iv{\'a}n and Matsushita, Satoki and Matthews, Lynn D. and Medeiros, Lia and Menten, Karl M. and Mizuno, Yosuke and Mizuno, Izumi and Moran, James M. and Moriyama, Kotaro and Moscibrodzka, Monika and M{\"u}ller, Cornelia and Nagai, Hiroshi and Nagar, Neil M. and Nakamura, Masanori and Narayan, Ramesh and Narayanan, Gopal and Natarajan, Iniyan and Neri, Roberto and Ni, Chunchong and Noutsos, Aristeidis and Okino, Hiroki and Olivares, H{\'e}ctor and {Ortiz-Le{\'o}n}, Gisela N. and Oyama, Tomoaki and {\"O}zel, Feryal and Palumbo, Daniel C. M. and Patel, Nimesh and Pen, Ue-Li and Pesce, Dominic W. and Pi{\'e}tu, Vincent and Plambeck, Richard and PopStefanija, Aleksandar and Porth, Oliver and Prather, Ben and {Preciado-L{\'o}pez}, Jorge A. and Psaltis, Dimitrios and Pu, Hung-Yi and Ramakrishnan, Venkatessh and Rao, Ramprasad and Rawlings, Mark G. and Raymond, Alexander W. and Rezzolla, Luciano and Ripperda, Bart and Roelofs, Freek and Rogers, Alan and Ros, Eduardo and Rose, Mel and Roshanineshat, Arash and Rottmann, Helge and Roy, Alan L. and Ruszczyk, Chet and Ryan, Benjamin R. and Rygl, Kazi L. J. and S{\'a}nchez, Salvador and {S{\'a}nchez-Arguelles}, David and Sasada, Mahito and Savolainen, Tuomas and Schloerb, F. Peter and Schuster, Karl-Friedrich and Shao, Lijing and Shen, Zhiqiang and Small, Des and Sohn, Bong Won and SooHoo, Jason and Tazaki, Fumie and Tiede, Paul and Tilanus, Remo P. J. and Titus, Michael and Toma, Kenji and Torne, Pablo and Trent, Tyler and Trippe, Sascha and Tsuda, Shuichiro and {van Bemmel}, Ilse and {van Langevelde}, Huib Jan and {van Rossum}, Daniel R. and Wagner, Jan and Wardle, John and Weintroub, Jonathan and Wex, Norbert and Wharton, Robert and Wielgus, Maciek and Wong, George N. and Wu, Qingwen and Young, Andr{\'e} and Young, Ken and Younsi, Ziri and Yuan, Feng and Yuan, Ye-Fei and Zensus, J. Anton and Zhao, Guangyao and Zhao, Shan-Shan and Zhu, Ziyan and Algaba, Juan-Carlos and Allardi, Alexander and Amestica, Rodrigo and Bach, Uwe and Beaudoin, Christopher and Benson, Bradford A. and Berthold, Ryan and Blanchard, Jay M. and Blundell, Ray and Bustamente, Sandra and Cappallo, Roger and {Castillo-Dom{\'i}nguez}, Edgar and Chang, Chih-Cheng and Chang, Shu-Hao and Chang, Song-Chu and Chen, Chung-Chen and Chilson, Ryan and Chuter, Tim C. and Rosado, Rodrigo C{\'o}rdova and Coulson, Iain M. and Crawford, Thomas M. and Crowley, Joseph and David, John and Derome, Mark and Dexter, Matthew and Dornbusch, Sven and Dudevoir, Kevin A. and Dzib, Sergio A. and Eckert, Chris and Erickson, Neal R. and Everett, Wendeline B. and Faber, Aaron and Farah, Joseph R. and Fath, Vernon and Folkers, Thomas W. and Forbes, David C. and Freund, Robert and {G{\'o}mez-Ruiz}, Arturo I. and Gale, David M. and Gao, Feng and Geertsema, Gertie and Graham, David A. and Greer, Christopher H. and Grosslein, Ronald and Gueth, Fr{\'e}d{\'e}ric and Halverson, Nils W. and Han, Chih-Chiang and Han, Kuo-Chang and Hao, Jinchi and Hasegawa, Yutaka and Henning, Jason W. and {Hern{\'a}ndez-G{\'o}mez}, Antonio and {Herrero-Illana}, Rub{\'e}n and Heyminck, Stefan and Hirota, Akihiko and Hoge, James and Huang, Yau-De and Impellizzeri, C. M. Violette and Jiang, Homin and Kamble, Atish and Keisler, Ryan and Kimura, Kimihiro and Kono, Yusuke and Kubo, Derek and Kuroda, John and Lacasse, Richard and Laing, Robert A. and Leitch, Erik M. and Li, Chao-Te and Lin, Lupin C.-C. and Liu, Ching-Tang and Liu, Kuan-Yu and Lu, Li-Ming and Marson, Ralph G. and {Martin-Cocher}, Pierre L. and Massingill, Kyle D. and Matulonis, Callie and McColl, Martin P. and McWhirter, Stephen R. and Messias, Hugo and {Meyer-Zhao}, Zheng and Michalik, Daniel and Monta{\~n}a, Alfredo and Montgomerie, William and {Mora-Klein}, Matias and Muders, Dirk and Nadolski, Andrew and Navarro, Santiago and Nguyen, Chi H. and Nishioka, Hiroaki and Norton, Timothy and Nystrom, George and Ogawa, Hideo and Oshiro, Peter and Oyama, Tomoaki and Padin, Stephen and Parsons, Harriet and Paine, Scott N. and Pe{\~n}alver, Juan and Phillips, Neil M. and Poirier, Michael and Pradel, Nicolas and Primiani, Rurik A. and Raffin, Philippe A. and Rahlin, Alexandra S. and Reiland, George and Risacher, Christopher and Ruiz, Ignacio and {S{\'a}ez-Mada{\'i}n}, Alejandro F. and Sassella, Remi and Schellart, Pim and Shaw, Paul and Silva, Kevin M. and Shiokawa, Hotaka and Smith, David R. and Snow, William and Souccar, Kamal and Sousa, Don and Sridharan, T. K. and Srinivasan, Ranjani and Stahm, William and Stark, Antony A. and Story, Kyle and Timmer, Sjoerd T. and Vertatschitsch, Laura and Walther, Craig and Wei, Ta-Shun and Whitehorn, Nathan and Whitney, Alan R. and Woody, David P. and Wouterloot, Jan G. A. and Wright, Melvin and Yamaguchi, Paul and Yu, Chen-Yu and Zeballos, Milagros and Ziurys, Lucy},
+ year = {2019},
+ month = apr,
+ volume = {875},
+ pages = {L2},
+ issn = {2041-8213},
+ doi = {10.3847/2041-8213/ab0c96},
+ url = {http://stacks.iop.org/2041-8205/875/i=1/a=L2?key=crossref.1a66e2fa88999479a30a11f3a0b1ead5},
+ urldate = {2020-01-20},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\3MJG3ELN\\The Event Horizon Telescope Collaboration et al. - 2019 - First M87 Event Horizon Telescope Results. II. Arr.pdf},
+ journal = {The Astrophysical Journal},
+ number = {1}
+}
+
+@article{TheEventHorizonTelescopeCollaboration2019b,
+ title = {First {{M87 Event Horizon Telescope Results}}. {{III}}. {{Data Processing}} and {{Calibration}}},
+ author = {{The Event Horizon Telescope Collaboration} and Akiyama, Kazunori and Alberdi, Antxon and Alef, Walter and Asada, Keiichi and Azulay, Rebecca and Baczko, Anne-Kathrin and Ball, David and Balokovi{\'c}, Mislav and Barrett, John and Bintley, Dan and Blackburn, Lindy and Boland, Wilfred and Bouman, Katherine L. and Bower, Geoffrey C. and Bremer, Michael and Brinkerink, Christiaan D. and Brissenden, Roger and Britzen, Silke and Broderick, Avery E. and Broguiere, Dominique and Bronzwaer, Thomas and Byun, Do-Young and Carlstrom, John E. and Chael, Andrew and Chan, Chi-kwan and Chatterjee, Shami and Chatterjee, Koushik and Chen, Ming-Tang and Chen, Yongjun and Cho, Ilje and Christian, Pierre and Conway, John E. and Cordes, James M. and Crew, Geoffrey B. and Cui, Yuzhu and Davelaar, Jordy and De Laurentis, Mariafelicia and Deane, Roger and Dempsey, Jessica and Desvignes, Gregory and Dexter, Jason and Doeleman, Sheperd S. and Eatough, Ralph P. and Falcke, Heino and Fish, Vincent L. and Fomalont, Ed and {Fraga-Encinas}, Raquel and Friberg, Per and Fromm, Christian M. and G{\'o}mez, Jos{\'e} L. and Galison, Peter and Gammie, Charles F. and Garc{\'i}a, Roberto and Gentaz, Olivier and Georgiev, Boris and Goddi, Ciriaco and Gold, Roman and Gu, Minfeng and Gurwell, Mark and Hada, Kazuhiro and Hecht, Michael H. and Hesper, Ronald and Ho, Luis C. and Ho, Paul and Honma, Mareki and Huang, Chih-Wei L. and Huang, Lei and Hughes, David H. and Ikeda, Shiro and Inoue, Makoto and Issaoun, Sara and James, David J. and Jannuzi, Buell T. and Janssen, Michael and Jeter, Britton and Jiang, Wu and Johnson, Michael D. and Jorstad, Svetlana and Jung, Taehyun and Karami, Mansour and Karuppusamy, Ramesh and Kawashima, Tomohisa and Keating, Garrett K. and Kettenis, Mark and Kim, Jae-Young and Kim, Junhan and Kim, Jongsoo and Kino, Motoki and Koay, Jun Yi and Koch, Patrick M. and Koyama, Shoko and Kramer, Michael and Kramer, Carsten and Krichbaum, Thomas P. and Kuo, Cheng-Yu and Lauer, Tod R. and Lee, Sang-Sung and Li, Yan-Rong and Li, Zhiyuan and Lindqvist, Michael and Liu, Kuo and Liuzzo, Elisabetta and Lo, Wen-Ping and Lobanov, Andrei P. and Loinard, Laurent and Lonsdale, Colin and Lu, Ru-Sen and MacDonald, Nicholas R. and Mao, Jirong and Markoff, Sera and Marrone, Daniel P. and Marscher, Alan P. and {Mart{\'i}-Vidal}, Iv{\'a}n and Matsushita, Satoki and Matthews, Lynn D. and Medeiros, Lia and Menten, Karl M. and Mizuno, Yosuke and Mizuno, Izumi and Moran, James M. and Moriyama, Kotaro and Moscibrodzka, Monika and M{\"u}ller, Cornelia and Nagai, Hiroshi and Nagar, Neil M. and Nakamura, Masanori and Narayan, Ramesh and Narayanan, Gopal and Natarajan, Iniyan and Neri, Roberto and Ni, Chunchong and Noutsos, Aristeidis and Okino, Hiroki and Olivares, H{\'e}ctor and {Ortiz-Le{\'o}n}, Gisela N. and Oyama, Tomoaki and {\"O}zel, Feryal and Palumbo, Daniel C. M. and Patel, Nimesh and Pen, Ue-Li and Pesce, Dominic W. and Pi{\'e}tu, Vincent and Plambeck, Richard and PopStefanija, Aleksandar and Porth, Oliver and Prather, Ben and {Preciado-L{\'o}pez}, Jorge A. and Psaltis, Dimitrios and Pu, Hung-Yi and Ramakrishnan, Venkatessh and Rao, Ramprasad and Rawlings, Mark G. and Raymond, Alexander W. and Rezzolla, Luciano and Ripperda, Bart and Roelofs, Freek and Rogers, Alan and Ros, Eduardo and Rose, Mel and Roshanineshat, Arash and Rottmann, Helge and Roy, Alan L. and Ruszczyk, Chet and Ryan, Benjamin R. and Rygl, Kazi L. J. and S{\'a}nchez, Salvador and {S{\'a}nchez-Arguelles}, David and Sasada, Mahito and Savolainen, Tuomas and Schloerb, F. Peter and Schuster, Karl-Friedrich and Shao, Lijing and Shen, Zhiqiang and Small, Des and Sohn, Bong Won and SooHoo, Jason and Tazaki, Fumie and Tiede, Paul and Tilanus, Remo P. J. and Titus, Michael and Toma, Kenji and Torne, Pablo and Trent, Tyler and Trippe, Sascha and Tsuda, Shuichiro and {van Bemmel}, Ilse and {van Langevelde}, Huib Jan and {van Rossum}, Daniel R. and Wagner, Jan and Wardle, John and Weintroub, Jonathan and Wex, Norbert and Wharton, Robert and Wielgus, Maciek and Wong, George N. and Wu, Qingwen and Young, Andr{\'e} and Young, Ken and Younsi, Ziri and Yuan, Feng and Yuan, Ye-Fei and Zensus, J. Anton and Zhao, Guangyao and Zhao, Shan-Shan and Zhu, Ziyan and Cappallo, Roger and Farah, Joseph R. and Folkers, Thomas W. and {Meyer-Zhao}, Zheng and Michalik, Daniel and Nadolski, Andrew and Nishioka, Hiroaki and Pradel, Nicolas and Primiani, Rurik A. and Souccar, Kamal and Vertatschitsch, Laura and Yamaguchi, Paul},
+ year = {2019},
+ month = apr,
+ volume = {875},
+ pages = {L3},
+ issn = {2041-8213},
+ doi = {10.3847/2041-8213/ab0c57},
+ url = {http://stacks.iop.org/2041-8205/875/i=1/a=L3?key=crossref.4bc7c8d9162e227c42bd2377945bd0ed},
+ urldate = {2020-01-20},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\M7HM8D2Y\\The Event Horizon Telescope Collaboration et al. - 2019 - First M87 Event Horizon Telescope Results. III. Da.pdf},
+ journal = {The Astrophysical Journal},
+ number = {1}
+}
+
+@article{TheEventHorizonTelescopeCollaboration2019c,
+ title = {First {{M87 Event Horizon Telescope Results}}. {{IV}}. {{Imaging}} the {{Central Supermassive Black Hole}}},
+ author = {{The Event Horizon Telescope Collaboration} and Akiyama, Kazunori and Alberdi, Antxon and Alef, Walter and Asada, Keiichi and Azulay, Rebecca and Baczko, Anne-Kathrin and Ball, David and Balokovi{\'c}, Mislav and Barrett, John and Bintley, Dan and Blackburn, Lindy and Boland, Wilfred and Bouman, Katherine L. and Bower, Geoffrey C. and Bremer, Michael and Brinkerink, Christiaan D. and Brissenden, Roger and Britzen, Silke and Broderick, Avery E. and Broguiere, Dominique and Bronzwaer, Thomas and Byun, Do-Young and Carlstrom, John E. and Chael, Andrew and Chan, Chi-kwan and Chatterjee, Shami and Chatterjee, Koushik and Chen, Ming-Tang and Chen, Yongjun and Cho, Ilje and Christian, Pierre and Conway, John E. and Cordes, James M. and Crew, Geoffrey B. and Cui, Yuzhu and Davelaar, Jordy and De Laurentis, Mariafelicia and Deane, Roger and Dempsey, Jessica and Desvignes, Gregory and Dexter, Jason and Doeleman, Sheperd S. and Eatough, Ralph P. and Falcke, Heino and Fish, Vincent L. and Fomalont, Ed and {Fraga-Encinas}, Raquel and Freeman, William T. and Friberg, Per and Fromm, Christian M. and G{\'o}mez, Jos{\'e} L. and Galison, Peter and Gammie, Charles F. and Garc{\'i}a, Roberto and Gentaz, Olivier and Georgiev, Boris and Goddi, Ciriaco and Gold, Roman and Gu, Minfeng and Gurwell, Mark and Hada, Kazuhiro and Hecht, Michael H. and Hesper, Ronald and Ho, Luis C. and Ho, Paul and Honma, Mareki and Huang, Chih-Wei L. and Huang, Lei and H. Hughes, David and Ikeda, Shiro and Inoue, Makoto and Issaoun, Sara and James, David J. and Jannuzi, Buell T. and Janssen, Michael and Jeter, Britton and Jiang, Wu and Johnson, Michael D. and Jorstad, Svetlana and Jung, Taehyun and Karami, Mansour and Karuppusamy, Ramesh and Kawashima, Tomohisa and Keating, Garrett K. and Kettenis, Mark and Kim, Jae-Young and Kim, Junhan and Kim, Jongsoo and Kino, Motoki and Koay, Jun Yi and Koch, Patrick M. and Koyama, Shoko and Kramer, Michael and Kramer, Carsten and Krichbaum, Thomas P. and Kuo, Cheng-Yu and Lauer, Tod R. and Lee, Sang-Sung and Li, Yan-Rong and Li, Zhiyuan and Lindqvist, Michael and Liu, Kuo and Liuzzo, Elisabetta and Lo, Wen-Ping and Lobanov, Andrei P. and Loinard, Laurent and Lonsdale, Colin and Lu, Ru-Sen and MacDonald, Nicholas R. and Mao, Jirong and Markoff, Sera and Marrone, Daniel P. and Marscher, Alan P. and {Mart{\'i}-Vidal}, Iv{\'a}n and Matsushita, Satoki and Matthews, Lynn D. and Medeiros, Lia and Menten, Karl M. and Mizuno, Yosuke and Mizuno, Izumi and Moran, James M. and Moriyama, Kotaro and Moscibrodzka, Monika and M{\"u}ller, Cornelia and Nagai, Hiroshi and Nagar, Neil M. and Nakamura, Masanori and Narayan, Ramesh and Narayanan, Gopal and Natarajan, Iniyan and Neri, Roberto and Ni, Chunchong and Noutsos, Aristeidis and Okino, Hiroki and Olivares, H{\'e}ctor and Oyama, Tomoaki and {\"O}zel, Feryal and Palumbo, Daniel C. M. and Patel, Nimesh and Pen, Ue-Li and Pesce, Dominic W. and Pi{\'e}tu, Vincent and Plambeck, Richard and PopStefanija, Aleksandar and Porth, Oliver and Prather, Ben and {Preciado-L{\'o}pez}, Jorge A. and Psaltis, Dimitrios and Pu, Hung-Yi and Ramakrishnan, Venkatessh and Rao, Ramprasad and Rawlings, Mark G. and Raymond, Alexander W. and Rezzolla, Luciano and Ripperda, Bart and Roelofs, Freek and Rogers, Alan and Ros, Eduardo and Rose, Mel and Roshanineshat, Arash and Rottmann, Helge and Roy, Alan L. and Ruszczyk, Chet and Ryan, Benjamin R. and Rygl, Kazi L. J. and S{\'a}nchez, Salvador and {S{\'a}nchez-Arguelles}, David and Sasada, Mahito and Savolainen, Tuomas and Schloerb, F. Peter and Schuster, Karl-Friedrich and Shao, Lijing and Shen, Zhiqiang and Small, Des and Sohn, Bong Won and SooHoo, Jason and Tazaki, Fumie and Tiede, Paul and Tilanus, Remo P. J. and Titus, Michael and Toma, Kenji and Torne, Pablo and Trent, Tyler and Trippe, Sascha and Tsuda, Shuichiro and {van Bemmel}, Ilse and {van Langevelde}, Huib Jan and {van Rossum}, Daniel R. and Wagner, Jan and Wardle, John and Weintroub, Jonathan and Wex, Norbert and Wharton, Robert and Wielgus, Maciek and Wong, George N. and Wu, Qingwen and Young, Andr{\'e} and Young, Ken and Younsi, Ziri and Yuan, Feng and Yuan, Ye-Fei and Zensus, J. Anton and Zhao, Guangyao and Zhao, Shan-Shan and Zhu, Ziyan and Farah, Joseph R. and {Meyer-Zhao}, Zheng and Michalik, Daniel and Nadolski, Andrew and Nishioka, Hiroaki and Pradel, Nicolas and Primiani, Rurik A. and Souccar, Kamal and Vertatschitsch, Laura and Yamaguchi, Paul},
+ year = {2019},
+ month = apr,
+ volume = {875},
+ pages = {L4},
+ issn = {2041-8213},
+ doi = {10.3847/2041-8213/ab0e85},
+ url = {http://stacks.iop.org/2041-8205/875/i=1/a=L4?key=crossref.f93f0b1565bb46b48cb890351d9fef13},
+ urldate = {2020-01-20},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\ZRNQ5PRS\\The Event Horizon Telescope Collaboration et al. - 2019 - First M87 Event Horizon Telescope Results. IV. Ima.pdf},
+ journal = {The Astrophysical Journal},
+ number = {1}
+}
+
+@article{TheEventHorizonTelescopeCollaboration2019d,
+ title = {First {{M87 Event Horizon Telescope Results}}. {{V}}. {{Physical Origin}} of the {{Asymmetric Ring}}},
+ author = {{The Event Horizon Telescope Collaboration} and Akiyama, Kazunori and Alberdi, Antxon and Alef, Walter and Asada, Keiichi and Azulay, Rebecca and Baczko, Anne-Kathrin and Ball, David and Balokovi{\'c}, Mislav and Barrett, John and Bintley, Dan and Blackburn, Lindy and Boland, Wilfred and Bouman, Katherine L. and Bower, Geoffrey C. and Bremer, Michael and Brinkerink, Christiaan D. and Brissenden, Roger and Britzen, Silke and Broderick, Avery E. and Broguiere, Dominique and Bronzwaer, Thomas and Byun, Do-Young and Carlstrom, John E. and Chael, Andrew and Chan, Chi-kwan and Chatterjee, Shami and Chatterjee, Koushik and Chen, Ming-Tang and Chen, Yongjun and Cho, Ilje and Christian, Pierre and Conway, John E. and Cordes, James M. and Crew, Geoffrey B. and Cui, Yuzhu and Davelaar, Jordy and De Laurentis, Mariafelicia and Deane, Roger and Dempsey, Jessica and Desvignes, Gregory and Dexter, Jason and Doeleman, Sheperd S. and Eatough, Ralph P. and Falcke, Heino and Fish, Vincent L. and Fomalont, Ed and {Fraga-Encinas}, Raquel and Friberg, Per and Fromm, Christian M. and G{\'o}mez, Jos{\'e} L. and Galison, Peter and Gammie, Charles F. and Garc{\'i}a, Roberto and Gentaz, Olivier and Georgiev, Boris and Goddi, Ciriaco and Gold, Roman and Gu, Minfeng and Gurwell, Mark and Hada, Kazuhiro and Hecht, Michael H. and Hesper, Ronald and Ho, Luis C. and Ho, Paul and Honma, Mareki and Huang, Chih-Wei L. and Huang, Lei and Hughes, David H. and Ikeda, Shiro and Inoue, Makoto and Issaoun, Sara and James, David J. and Jannuzi, Buell T. and Janssen, Michael and Jeter, Britton and Jiang, Wu and Johnson, Michael D. and Jorstad, Svetlana and Jung, Taehyun and Karami, Mansour and Karuppusamy, Ramesh and Kawashima, Tomohisa and Keating, Garrett K. and Kettenis, Mark and Kim, Jae-Young and Kim, Junhan and Kim, Jongsoo and Kino, Motoki and Koay, Jun Yi and Koch, Patrick M. and Koyama, Shoko and Kramer, Michael and Kramer, Carsten and Krichbaum, Thomas P. and Kuo, Cheng-Yu and Lauer, Tod R. and Lee, Sang-Sung and Li, Yan-Rong and Li, Zhiyuan and Lindqvist, Michael and Liu, Kuo and Liuzzo, Elisabetta and Lo, Wen-Ping and Lobanov, Andrei P. and Loinard, Laurent and Lonsdale, Colin and Lu, Ru-Sen and MacDonald, Nicholas R. and Mao, Jirong and Markoff, Sera and Marrone, Daniel P. and Marscher, Alan P. and {Mart{\'i}-Vidal}, Iv{\'a}n and Matsushita, Satoki and Matthews, Lynn D. and Medeiros, Lia and Menten, Karl M. and Mizuno, Yosuke and Mizuno, Izumi and Moran, James M. and Moriyama, Kotaro and Moscibrodzka, Monika and Mul\"ler, Cornelia and Nagai, Hiroshi and Nagar, Neil M. and Nakamura, Masanori and Narayan, Ramesh and Narayanan, Gopal and Natarajan, Iniyan and Neri, Roberto and Ni, Chunchong and Noutsos, Aristeidis and Okino, Hiroki and Olivares, H{\'e}ctor and Oyama, Tomoaki and {\"O}zel, Feryal and Palumbo, Daniel C. M. and Patel, Nimesh and Pen, Ue-Li and Pesce, Dominic W. and Pi{\'e}tu, Vincent and Plambeck, Richard and PopStefanija, Aleksandar and Porth, Oliver and Prather, Ben and {Preciado-L{\'o}pez}, Jorge A. and Psaltis, Dimitrios and Pu, Hung-Yi and Ramakrishnan, Venkatessh and Rao, Ramprasad and Rawlings, Mark G. and Raymond, Alexander W. and Rezzolla, Luciano and Ripperda, Bart and Roelofs, Freek and Rogers, Alan and Ros, Eduardo and Rose, Mel and Roshanineshat, Arash and Rottmann, Helge and Roy, Alan L. and Ruszczyk, Chet and Ryan, Benjamin R. and Rygl, Kazi L. J. and S{\'a}nchez, Salvador and {S{\'a}nchez-Arguelles}, David and Sasada, Mahito and Savolainen, Tuomas and Schloerb, F. Peter and Schuster, Karl-Friedrich and Shao, Lijing and Shen, Zhiqiang and Small, Des and Sohn, Bong Won and SooHoo, Jason and Tazaki, Fumie and Tiede, Paul and Tilanus, Remo P. J. and Titus, Michael and Toma, Kenji and Torne, Pablo and Trent, Tyler and Trippe, Sascha and Tsuda, Shuichiro and {van Bemmel}, Ilse and {van Langevelde}, Huib Jan and {van Rossum}, Daniel R. and Wagner, Jan and Wardle, John and Weintroub, Jonathan and Wex, Norbert and Wharton, Robert and Wielgus, Maciek and Wong, George N. and Wu, Qingwen and Young, Andr{\'e} and Young, Ken and Younsi, Ziri and Yuan, Feng and Yuan, Ye-Fei and Zensus, J. Anton and Zhao, Guangyao and Zhao, Shan-Shan and Zhu, Ziyan and Anczarski, Jadyn and Baganoff, Frederick K. and Eckart, Andreas and Farah, Joseph R. and Haggard, Daryl and {Meyer-Zhao}, Zheng and Michalik, Daniel and Nadolski, Andrew and Neilsen, Joseph and Nishioka, Hiroaki and Nowak, Michael A. and Pradel, Nicolas and Primiani, Rurik A. and Souccar, Kamal and Vertatschitsch, Laura and Yamaguchi, Paul and Zhang, Shuo},
+ year = {2019},
+ month = apr,
+ volume = {875},
+ pages = {L5},
+ issn = {2041-8213},
+ doi = {10.3847/2041-8213/ab0f43},
+ url = {https://iopscience.iop.org/article/10.3847/2041-8213/ab0f43},
+ urldate = {2020-01-20},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\EAJEGL2E\\The Event Horizon Telescope Collaboration et al. - 2019 - First M87 Event Horizon Telescope Results. V. Phys.pdf},
+ journal = {The Astrophysical Journal},
+ number = {1}
+}
+
+@article{TheEventHorizonTelescopeCollaboration2019e,
+ title = {First {{M87 Event Horizon Telescope Results}}. {{VI}}. {{The Shadow}} and {{Mass}} of the {{Central Black Hole}}},
+ author = {{The Event Horizon Telescope Collaboration} and Akiyama, Kazunori and Alberdi, Antxon and Alef, Walter and Asada, Keiichi and Azulay, Rebecca and Baczko, Anne-Kathrin and Ball, David and Balokovi{\'c}, Mislav and Barrett, John and Bintley, Dan and Blackburn, Lindy and Boland, Wilfred and Bouman, Katherine L. and Bower, Geoffrey C. and Bremer, Michael and Brinkerink, Christiaan D. and Brissenden, Roger and Britzen, Silke and Broderick, Avery E. and Broguiere, Dominique and Bronzwaer, Thomas and Byun, Do-Young and Carlstrom, John E. and Chael, Andrew and Chan, Chi-kwan and Chatterjee, Shami and Chatterjee, Koushik and Chen, Ming-Tang and Chen, Yongjun and Cho, Ilje and Christian, Pierre and Conway, John E. and Cordes, James M. and Crew, Geoffrey B. and Cui, Yuzhu and Davelaar, Jordy and De Laurentis, Mariafelicia and Deane, Roger and Dempsey, Jessica and Desvignes, Gregory and Dexter, Jason and Doeleman, Sheperd S. and Eatough, Ralph P. and Falcke, Heino and Fish, Vincent L. and Fomalont, Ed and {Fraga-Encinas}, Raquel and Friberg, Per and Fromm, Christian M. and G{\'o}mez, Jos{\'e} L. and Galison, Peter and Gammie, Charles F. and Garc{\'i}a, Roberto and Gentaz, Olivier and Georgiev, Boris and Goddi, Ciriaco and Gold, Roman and Gu, Minfeng and Gurwell, Mark and Hada, Kazuhiro and Hecht, Michael H. and Hesper, Ronald and Ho, Luis C. and Ho, Paul and Honma, Mareki and Huang, Chih-Wei L. and Huang, Lei and Hughes, David H. and Ikeda, Shiro and Inoue, Makoto and Issaoun, Sara and James, David J. and Jannuzi, Buell T. and Janssen, Michael and Jeter, Britton and Jiang, Wu and Johnson, Michael D. and Jorstad, Svetlana and Jung, Taehyun and Karami, Mansour and Karuppusamy, Ramesh and Kawashima, Tomohisa and Keating, Garrett K. and Kettenis, Mark and Kim, Jae-Young and Kim, Junhan and Kim, Jongsoo and Kino, Motoki and Koay, Jun Yi and Koch, Patrick M. and Koyama, Shoko and Kramer, Michael and Kramer, Carsten and Krichbaum, Thomas P. and Kuo, Cheng-Yu and Lauer, Tod R. and Lee, Sang-Sung and Li, Yan-Rong and Li, Zhiyuan and Lindqvist, Michael and Liu, Kuo and Liuzzo, Elisabetta and Lo, Wen-Ping and Lobanov, Andrei P. and Loinard, Laurent and Lonsdale, Colin and Lu, Ru-Sen and MacDonald, Nicholas R. and Mao, Jirong and Markoff, Sera and Marrone, Daniel P. and Marscher, Alan P. and {Mart{\'i}-Vidal}, Iv{\'a}n and Matsushita, Satoki and Matthews, Lynn D. and Medeiros, Lia and Menten, Karl M. and Mizuno, Yosuke and Mizuno, Izumi and Moran, James M. and Moriyama, Kotaro and Moscibrodzka, Monika and M{\"u}ller, Cornelia and Nagai, Hiroshi and Nagar, Neil M. and Nakamura, Masanori and Narayan, Ramesh and Narayanan, Gopal and Natarajan, Iniyan and Neri, Roberto and Ni, Chunchong and Noutsos, Aristeidis and Okino, Hiroki and Olivares, H{\'e}ctor and Oyama, Tomoaki and {\"O}zel, Feryal and Palumbo, Daniel C. M. and Patel, Nimesh and Pen, Ue-Li and Pesce, Dominic W. and Pi{\'e}tu, Vincent and Plambeck, Richard and PopStefanija, Aleksandar and Porth, Oliver and Prather, Ben and {Preciado-L{\'o}pez}, Jorge A. and Psaltis, Dimitrios and Pu, Hung-Yi and Ramakrishnan, Venkatessh and Rao, Ramprasad and Rawlings, Mark G. and Raymond, Alexander W. and Rezzolla, Luciano and Ripperda, Bart and Roelofs, Freek and Rogers, Alan and Ros, Eduardo and Rose, Mel and Roshanineshat, Arash and Rottmann, Helge and Roy, Alan L. and Ruszczyk, Chet and Ryan, Benjamin R. and Rygl, Kazi L. J. and S{\'a}nchez, Salvador and {S{\'a}nchez-Arguelles}, David and Sasada, Mahito and Savolainen, Tuomas and Schloerb, F. Peter and Schuster, Karl-Friedrich and Shao, Lijing and Shen, Zhiqiang and Small, Des and Sohn, Bong Won and SooHoo, Jason and Tazaki, Fumie and Tiede, Paul and Tilanus, Remo P. J. and Titus, Michael and Toma, Kenji and Torne, Pablo and Trent, Tyler and Trippe, Sascha and Tsuda, Shuichiro and {van Bemmel}, Ilse and {van Langevelde}, Huib Jan and {van Rossum}, Daniel R. and Wagner, Jan and Wardle, John and Weintroub, Jonathan and Wex, Norbert and Wharton, Robert and Wielgus, Maciek and Wong, George N. and Wu, Qingwen and Young, Andr{\'e} and Young, Ken and Younsi, Ziri and Yuan, Feng and Yuan, Ye-Fei and Zensus, J. Anton and Zhao, Guangyao and Zhao, Shan-Shan and Zhu, Ziyan and Farah, Joseph R. and {Meyer-Zhao}, Zheng and Michalik, Daniel and Nadolski, Andrew and Nishioka, Hiroaki and Pradel, Nicolas and Primiani, Rurik A. and Souccar, Kamal and Vertatschitsch, Laura and Yamaguchi, Paul},
+ year = {2019},
+ month = apr,
+ volume = {875},
+ pages = {L6},
+ issn = {2041-8213},
+ doi = {10.3847/2041-8213/ab1141},
+ url = {http://stacks.iop.org/2041-8205/875/i=1/a=L6?key=crossref.16035f8759f88c0c0f8825f9e42aad6e},
+ urldate = {2020-01-20},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\AV4XZSXM\\The Event Horizon Telescope Collaboration et al. - 2019 - First M87 Event Horizon Telescope Results. VI. The.pdf},
+ journal = {The Astrophysical Journal},
+ number = {1}
+}
+
+
+@misc{Casties2019,
+ title = {{{DH Research Software Engineers}} - {{For We Are Many}}},
+ author = {Casties, Robert and Czmiel, Alexander and Damerow, Julia and Ionov, Max and Mero{\~n}o Pe{\~n}uela, Albert and Ranford, Steve and Smith, Catherine and Vogl, Malte},
+ year = {2019},
+ month = jul,
+ url = {http://web.archive.org/web/20190829122818/https://dh-tech.github.io/dhrse-whitepaper/},
+ urldate = {2020-01-20},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\7445T738\\dhrse-whitepaper.html},
+ journal = {DHTech},
+ language = {en}
+}
+
+
+
+@misc{CodeRefinery,
+ title = {{{CodeRefinery}} - {{Lessons}}},
+ author = {{The CodeRefinery Project}},
+ url = {http://web.archive.org/web/20180531130106/http://coderefinery.org/lessons/},
+ urldate = {2020-01-20},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\98GS5J5Q\\lessons.html}
+}
+
+@inproceedings{Hexatomic,
+ title = {{Infrastrukturstrategien f{\"u}r nachhaltige Forschungssoftware in befristeten Projekten}},
+ author = {Druskat, Stephan and Krause, Thomas and L{\"u}deling, Anke and Gast, Volker},
+ year = {2019},
+ month = jun,
+ address = {{Potsdam, Germany}},
+ booktitle={deRSE19 - Conference for Research Software Engineers in Germany.},
+ url = {https://doi.org/10.6084/m9.figshare.11277764.v1},
+ copyright = {CC-BY 4.0},
+ language = {German},
+ type = {{Poster}}
+}
+
+@article{ison2016tools,
+ title={Tools and data services registry: a community effort to document bioinformatics resources},
+ author={Ison, Jon and Rapacki, Kristoffer and M{\'e}nager, Herv{\'e} and Kala{\v{s}}, Mat{\'u}{\v{s}} and Rydza, Emil and Chmura, Piotr and Anthon, Christian and Beard, Niall and Berka, Karel and Bolser, Dan and others},
+ journal={Nucleic acids research},
+ volume={44},
+ number={D1},
+ pages={D38--D47},
+ year={2016},
+ publisher={Oxford University Press}
+}
+
+
+
+@incollection{ROpenSciDevGuide,
+ title = {Software Peer Review, Why? What?},
+ shorttitle = {Ropensci/Dev\_guide},
+ booktitle = {{{rOpenSci Packages}}: {{Development}}, {{Maintenance}}, and {{Peer Review}}},
+ author = {{rOpenSci} and Anderson, Brooke and Chamberlain, Scott and Krystalli, Anna and Mullen, Lincoln and Ram, Karthik and Ross, Noam and Salmon, Ma{\"e}lle and Vidoni, Melina},
+ year = {2019},
+ month = jan,
+ publisher = {{Zenodo}},
+ doi = {10.5281/zenodo.2554759},
+ url = {https://doi.org/10.5281/zenodo.2554759},
+ urldate = {2020-03-17},
+ abstract = {rOpenSci Packages: Development, Maintenance, and Peer Review},
+ file = {/home/stephan/src/zotero/storage/2LEBU8XR/2554759.html}
+}
+
+@misc{JOSSReview,
+ title = {Review Criteria - JOSS documentation},
+ authors = {The JOSS project},
+ url = {http://web.archive.org/web/20200317125049/https://joss.readthedocs.io/en/latest/review_criteria.html}
+
+}
+
+
+@article{softwareheritage,
+ title = {Building the Universal Archive of Source Code},
+ author = {Abramatic, Jean-Fran{\c c}ois and Di Cosmo, Roberto and Zacchiroli, Stefano},
+ year = {2018},
+ month = sep,
+ volume = {61},
+ pages = {29--31},
+ issn = {0001-0782},
+ doi = {10.1145/3183558},
+ url = {https://doi.org/10.1145/3183558},
+ urldate = {2020-03-17},
+ abstract = {A global collaborative project for the benefit of all.},
+ journal = {Communications of the ACM},
+ number = {10}
+}
+
+
+
+@article{bio.tools,
+ title = {Tools and Data Services Registry: A Community Effort to Document Bioinformatics Resources},
+ shorttitle = {Tools and Data Services Registry},
+ author = {Ison, Jon and Rapacki, Kristoffer and M{\'e}nager, Herv{\'e} and Kala{\v s}, Mat{\'u}{\v s} and Rydza, Emil and Chmura, Piotr and Anthon, Christian and Beard, Niall and Berka, Karel and Bolser, Dan and Booth, Tim and Bretaudeau, Anthony and Brezovsky, Jan and Casadio, Rita and Cesareni, Gianni and Coppens, Frederik and Cornell, Michael and Cuccuru, Gianmauro and Davidsen, Kristian and Vedova, Gianluca Della and Dogan, Tunca and {Doppelt-Azeroual}, Olivia and Emery, Laura and Gasteiger, Elisabeth and Gatter, Thomas and Goldberg, Tatyana and Grosjean, Marie and Gr{\"u}ning, Bj{\"o}rn and {Helmer-Citterich}, Manuela and Ienasescu, Hans and Ioannidis, Vassilios and Jespersen, Martin Closter and Jimenez, Rafael and Juty, Nick and Juvan, Peter and Koch, Maximilian and Laibe, Camille and Li, Jing-Woei and Licata, Luana and Mareuil, Fabien and Mi{\v c}eti{\'c}, Ivan and Friborg, Rune M{\o}llegaard and Moretti, Sebastien and Morris, Chris and M{\"o}ller, Steffen and Nenadic, Aleksandra and Peterson, Hedi and Profiti, Giuseppe and Rice, Peter and Romano, Paolo and Roncaglia, Paola and Saidi, Rabie and Schafferhans, Andrea and Schw{\"a}mmle, Veit and Smith, Callum and Sperotto, Maria Maddalena and Stockinger, Heinz and Va{\v r}ekov{\'a}, Radka Svobodov{\'a} and Tosatto, Silvio C.E. and {de la Torre}, Victor and Uva, Paolo and Via, Allegra and Yachdav, Guy and Zambelli, Federico and Vriend, Gert and Rost, Burkhard and Parkinson, Helen and L{\o}ngreen, Peter and Brunak, S{\o}ren},
+ year = {2016},
+ month = jan,
+ volume = {44},
+ pages = {D38-D47},
+ issn = {0305-1048},
+ doi = {10.1093/nar/gkv1116},
+ url = {https://doi.org/10.1093/nar/gkv1116},
+ urldate = {2020-03-17},
+ abstract = {Life sciences are yielding huge data sets that underpin scientific discoveries fundamental to improvement in human health, agriculture and the environment. In support of these discoveries, a plethora of databases and tools are deployed, in technically complex and diverse implementations, across a spectrum of scientific disciplines. The corpus of documentation of these resources is fragmented across the Web, with much redundancy, and has lacked a common standard of information. The outcome is that scientists must often struggle to find, understand, compare and use the best resources for the task at hand., Here we present a community-driven curation effort, supported by ELIXIR\textemdash{}the European infrastructure for biological information\textemdash{}that aspires to a comprehensive and consistent registry of information about bioinformatics resources. The sustainable upkeep of this Tools and Data Services Registry is assured by a curation effort driven by and tailored to local needs, and shared amongst a network of engaged partners., As of November 2015, the registry includes 1785 resources, with depositions from 126 individual registrations including 52 institutional providers and 74 individuals. With community support, the registry can become a standard for dissemination of information about bioinformatics resources: we welcome everyone to join us in this common endeavour. The registry is freely available at https://bio.tools.},
+ file = {C\:\\Users\\drus_st\\Zotero\\storage\\7WZ34URP\\Ison et al. - 2016 - Tools and data services registry a community effo.pdf},
+ journal = {Nucleic Acids Research},
+ number = {Database issue},
+ pmcid = {PMC4702812},
+ pmid = {26538599}
+}
+
+
+@misc{HIDA,
+title = {HIDA},
+url = {http://web.archive.org/web/20200317175916/https://www.helmholtz-hida.de/}
+}
+
+@misc{CRAN,
+title = {The Comprehensive R Archive Network (CRAN)},
+url = {cran.r-project.org}
+}
+
+@misc{re3data,
+title = {re3data.org -- Registry of Research Data Repositories},
+url = {www.re3data.org},
+doi = {10.17616/R3D}
+}
+
+@article{Nowogrodzki2019,
+ doi = {10.1038/d41586-019-02046-0},
+ url = {https://doi.org/10.1038/d41586-019-02046-0},
+ year = {2019},
+ month = jul,
+ publisher = {Springer Science and Business Media {LLC}},
+ volume = {571},
+ number = {7763},
+ pages = {133--134},
+ author = {Anna Nowogrodzki},
+ title = {How to support open-source software and stay sane},
+ journal = {Nature}
+}
+
+@misc{swHeritage,
+title = {Software Heritage},
+url = {www.softwareheritage.org}
+}
diff --git a/001/vancouver-authoryear.bst b/001/vancouver-authoryear.bst
new file mode 100644
index 0000000..f4b72c8
--- /dev/null
+++ b/001/vancouver-authoryear.bst
@@ -0,0 +1,1812 @@
+%% natbib-compatible BibTeX bibliography style `vancouver-authoryear'
+%% v1.1 2017/07/2012 Remove sorting by authors' names
+%%
+%% Use
+%%
+%% \usepackage{natbib}
+%% \bibliographystyle{vancouver-authoryear}
+%%
+%% and cite references with (e.g.)
+%%
+%% \cite{smith77} % to get a "[1]" in the text
+%% \citep{smith77} % to get a "[1]" in the text
+%% \citet{smith77} % to get a "Smith [1]" in the text
+%% \citeauthor{smith77} % to get a "Smith" in the text
+%%
+%% The changes below are inspired by similar changes made to
+%% splncs03.bst by Maurizio "Titto" Patrignani of
+%% Dipartimento di Informatica e Automazione Universita' Roma Tre.
+%% Unfortunately, splncs03.bst was not compatible with natbib (because it
+%% was not built with author-year capability).
+%%
+%% This is derived from `splncsnat.bst',
+%---------------------------------------------------------------------
+
+ENTRY
+ { address
+ assignee % for patents
+ author
+ booktitle % for articles in books
+ chapter % for incollection, esp. internet documents
+ cartographer % for maps
+ day
+ edition
+ editor
+ eid
+ howpublished
+ institution % for technical reports
+ inventor % for patents
+ journal
+ key
+ month
+ note
+ number
+ organization
+ pages
+ part
+ publisher
+ school
+ series
+ title
+ type
+ url
+ volume
+ word
+ year
+ }
+ {}
+ { label extra.label sort.label short.list }
+INTEGERS { output.state before.all mid.sentence after.sentence after.block }
+FUNCTION {init.state.consts}
+{ #0 'before.all :=
+ #1 'mid.sentence :=
+ #2 'after.sentence :=
+ #3 'after.block :=
+}
+%% Declaration of string variables
+STRINGS { s t}
+FUNCTION {output.nonnull}
+{ 's :=
+ output.state mid.sentence =
+ { ", " * write$ }
+ { output.state after.block =
+ { add.period$ write$
+ newline$
+ "\newblock " write$
+ }
+ { output.state before.all =
+ 'write$
+ { " " * write$ }
+ if$
+ }
+ if$
+ mid.sentence 'output.state :=
+ }
+ if$
+ s
+}
+FUNCTION {output}
+{ duplicate$ empty$
+ 'pop$
+ 'output.nonnull
+ if$
+}
+
+FUNCTION {output.check}
+{ 't :=
+ duplicate$ empty$
+ { pop$ "empty " t * " in " * cite$ * warning$ }
+ 'output.nonnull
+ if$
+}
+
+%FUNCTION {fin.entry}
+%{ duplicate$ empty$
+% 'pop$
+% 'write$
+% if$
+% newline$
+%}
+%
+FUNCTION {fin.entry}
+{ add.period$
+ write$
+ newline$
+}
+
+FUNCTION {new.block}
+{ output.state before.all =
+ 'skip$
+ { after.block 'output.state := }
+ if$
+}
+
+FUNCTION {new.sentence}
+{ output.state after.block =
+ 'skip$
+ { output.state before.all =
+ 'skip$
+ { after.sentence 'output.state := }
+ if$
+ }
+ if$
+}
+
+FUNCTION {add.blank}
+{ " " * before.all 'output.state :=
+}
+
+FUNCTION {no.blank.or.punct}
+{ "" * before.all 'output.state :=
+}
+
+FUNCTION {add.semicolon}
+{
+ ";" *
+ no.blank.or.punct
+}
+
+FUNCTION {date.block}
+{
+ "." *
+ no.blank.or.punct
+}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% LOGICAL `NOT', `AND', AND `OR' %
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% Logical 'not':
+% If the first element on the stack is A then this function
+% does the following:
+% push { #0 }
+% push { #1 }
+% So now the first 3 elements of the stack are
+% { #1 } { #0 } A
+% The first 3 are popped and subjected to 'if':
+% If A > 0 then { #0 } is executed, else { #1 } is executed:
+% if A > 0
+% then 0
+% else 1
+% So consider integers as logicals, where 1 = true and 0 = false,
+% then this does
+% (if A then false else true)
+% which is a logical 'not'.
+
+FUNCTION {not}
+{ { #0 }
+ { #1 }
+ if$
+}
+FUNCTION {and}
+{ 'skip$
+ { pop$ #0 }
+ if$
+}
+FUNCTION {or}
+{ { pop$ #1 }
+ 'skip$
+ if$
+}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% GENERAL PURPOSE FUNCTIONS FOR FORMATTING %
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% issues warning if field is empty
+% call with
+% "field" field warning.if.empty
+% Note that the first field must be between quotes
+% because it is the fieldname for use in the warning message.
+%
+
+FUNCTION {warning.if.empty}
+{ empty$
+ { "No " swap$ * " in " * cite$ * warning$ }
+ { pop$ }
+ if$
+}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+ %
+ % encloses string in pre- and postfix string
+ % call with
+ % prefix postfix S enclose.check
+ % delivers empty string if S empty
+ %
+FUNCTION {enclose.check}
+{ duplicate$ empty$
+ { pop$ pop$ pop$
+ ""
+ }
+ { swap$ * * }
+ if$
+}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+%
+% emphasizes top of stack
+% call with
+% string" emphasize.check
+%
+
+FUNCTION {emphasize.check}
+{ "\Bem{" swap$
+ "}" swap$
+ enclose.check
+}
+
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+ %
+ % brackets top of stack
+ % call with
+ % "string" bracket.check
+ %
+FUNCTION {bracket.check}
+{ "[" swap$
+ "]" swap$
+ enclose.check
+}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+ %
+ % parenthesizes top of stack
+ % call with
+ % "string" parenthesize
+ %
+FUNCTION {parenthesize.check}
+{ "(" swap$
+ ")" swap$
+ enclose.check
+}
+
+STRINGS {z}
+
+FUNCTION {remove.dots}
+{ 'z := % expects string on top of the stack, pops the string and assigns it to variable z
+ "" % push empty string
+ { z empty$ not } % returns 0 if variable z is empty
+ { z #1 #1 substring$ % push the first character of variable z
+ z #2 global.max$ substring$ 'z := % assigns the 2nd to last character of variable z to variable z
+ duplicate$ "\" = % pushes 1 if the last character is "\", otherwise 0
+ { * % concatenates the last 2 literals
+ z #1 #1 substring$ % push the first character of variable z
+ z #2 global.max$ substring$ 'z := % assigns the 2nd to last character of variable z to variable z
+ * % concatenates the last 2 literals, i.e. every character, even a dot, following a "\" will be printed
+ }
+ { duplicate$ "." = % pushes 1 if the last character is ".", otherwise 0
+ 'pop$ % pushes the pop$ function
+ { * } % concatenates the last 2 literals
+ if$ % pops the last character if it is a dot, otherwise concatenates it with the string on top of the stack
+ }
+ if$
+ }
+ while$
+}
+
+INTEGERS {l}
+FUNCTION{string.length}
+{
+ #1 'l :=
+ { duplicate$ duplicate$ #1 l substring$ = not }
+ { l #1 + 'l := }
+ while$
+ pop$ l
+}
+
+STRINGS {replace find text}
+INTEGERS {find_length}
+FUNCTION {find.replace}
+{
+ 'replace :=
+ 'find :=
+ 'text :=
+ find string.length 'find_length :=
+ ""
+ { text empty$ not }
+ { text #1 find_length substring$ find =
+ {
+ replace *
+ text #1 find_length + global.max$ substring$ 'text :=
+ }
+ { text #1 #1 substring$ *
+ text #2 global.max$ substring$ 'text :=
+ }
+ if$
+ }
+ while$
+}
+
+FUNCTION {new.block.checka}
+{ empty$
+ 'skip$
+ 'new.block
+ if$
+}
+
+FUNCTION {new.block.checkb}
+{ empty$
+ swap$ empty$
+ and
+ 'skip$
+ 'new.block
+ if$
+}
+
+FUNCTION {new.sentence.checka}
+{ empty$
+ 'skip$
+ 'new.sentence
+ if$
+}
+
+FUNCTION {new.sentence.checkb}
+{ empty$
+ swap$ empty$
+ and
+ 'skip$
+ 'new.sentence
+ if$
+}
+
+FUNCTION {field.or.null}
+{ duplicate$ empty$
+ { pop$ "" }
+ 'skip$
+ if$
+}
+
+FUNCTION {emphasize}
+{ skip$ }
+
+FUNCTION {tie.or.space.prefix}
+{ duplicate$ text.length$ #3 <
+ { "~" }
+ { " " }
+ if$
+ swap$
+}
+
+FUNCTION {capitalize}
+{ "u" change.case$ "t" change.case$ }
+
+FUNCTION {space.word}
+{ " " swap$ * " " * }
+
+ % Here are the language-specific definitions for explicit words.
+ % Each function has a name bbl.xxx where xxx is the English word.
+ % The language selected here is ENGLISH
+
+FUNCTION {bbl.and}
+{ "and"}
+
+FUNCTION {bbl.etal}
+{ "et~al." }
+
+FUNCTION {bbl.editors}
+{ "editors" }
+
+FUNCTION {bbl.editor}
+{ "editor" }
+
+FUNCTION {bbl.cartographers}
+{ "cartographers" }
+
+FUNCTION {bbl.cartographer}
+{ "cartographer" }
+
+FUNCTION {bbl.inventors}
+{ "inventors" }
+
+FUNCTION {bbl.inventor}
+{ "inventor" }
+
+FUNCTION {bbl.assignees}
+{ "assignees" }
+
+FUNCTION {bbl.assignee}
+{ "assignee" }
+
+FUNCTION {bbl.edby}
+{ "edited by" }
+
+FUNCTION {bbl.edition}
+{ "ed." }
+
+FUNCTION {bbl.volume}
+{ "vol." }
+
+FUNCTION {bbl.of}
+{ "of" }
+
+FUNCTION {bbl.number}
+{ "no." }
+
+FUNCTION {bbl.nr}
+{ "no." }
+
+FUNCTION {bbl.in}
+{ "in" }
+
+FUNCTION {bbl.pages}
+{ "p." }
+
+FUNCTION {bbl.page}
+{ "p." }
+
+FUNCTION {bbl.chapter}
+{ "chap." }
+
+FUNCTION {bbl.techrep}
+{ "Tech. Rep." }
+
+FUNCTION {bbl.mthesis}
+{ "Master's thesis" }
+
+FUNCTION {bbl.phdthesis}
+{ "Ph.D. thesis" }
+
+FUNCTION {bbl.first}
+{ "1st" }
+
+FUNCTION {bbl.second}
+{ "2nd" }
+
+FUNCTION {bbl.third}
+{ "3rd" }
+
+FUNCTION {bbl.fourth}
+{ "4th" }
+
+FUNCTION {bbl.fifth}
+{ "5th" }
+
+FUNCTION {bbl.st}
+{ "st" }
+
+FUNCTION {bbl.nd}
+{ "nd" }
+
+FUNCTION {bbl.rd}
+{ "rd" }
+
+FUNCTION {bbl.th}
+{ "th" }
+
+MACRO {jan} {"Jan."}
+
+MACRO {feb} {"Feb."}
+
+MACRO {mar} {"Mar."}
+
+MACRO {apr} {"Apr."}
+
+MACRO {may} {"May"}
+
+MACRO {jun} {"Jun."}
+
+MACRO {jul} {"Jul."}
+
+MACRO {aug} {"Aug."}
+
+MACRO {sep} {"Sep."}
+
+MACRO {oct} {"Oct."}
+
+MACRO {nov} {"Nov."}
+
+MACRO {dec} {"Dec."}
+
+MACRO {acmcs} {"ACM Comput. Surv."}
+
+MACRO {acta} {"Acta Inf."}
+
+MACRO {cacm} {"Commun. ACM"}
+
+MACRO {ibmjrd} {"IBM J. Res. Dev."}
+
+MACRO {ibmsj} {"IBM Syst.~J."}
+
+MACRO {ieeese} {"IEEE Trans. Software Eng."}
+
+MACRO {ieeetc} {"IEEE Trans. Comput."}
+
+MACRO {ieeetcad}
+ {"IEEE Trans. Comput. Aid. Des."}
+
+MACRO {ipl} {"Inf. Process. Lett."}
+
+MACRO {jacm} {"J.~ACM"}
+
+MACRO {jcss} {"J.~Comput. Syst. Sci."}
+
+MACRO {scp} {"Sci. Comput. Program."}
+
+MACRO {sicomp} {"SIAM J. Comput."}
+
+MACRO {tocs} {"ACM Trans. Comput. Syst."}
+
+MACRO {tods} {"ACM Trans. Database Syst."}
+
+MACRO {tog} {"ACM Trans. Graphic."}
+
+MACRO {toms} {"ACM Trans. Math. Software"}
+
+MACRO {toois} {"ACM Trans. Office Inf. Syst."}
+
+MACRO {toplas} {"ACM Trans. Progr. Lang. Syst."}
+
+MACRO {tcs} {"Theor. Comput. Sci."}
+
+FUNCTION {eng.ord}
+{ duplicate$ "1" swap$ *
+ #-2 #1 substring$ "1" =
+ { bbl.th * }
+ { duplicate$ #-1 #1 substring$
+ duplicate$ "1" =
+ { pop$ bbl.st * }
+ { duplicate$ "2" =
+ { pop$ bbl.nd * }
+ { "3" =
+ { bbl.rd * }
+ { bbl.th * }
+ if$
+ }
+ if$
+ }
+ if$
+ }
+ if$
+}
+
+FUNCTION {bibinfo.check}
+{ swap$
+ duplicate$ missing$
+ {
+ pop$ pop$
+ ""
+ }
+ { duplicate$ empty$
+ {
+ swap$ pop$
+ }
+ { swap$
+ pop$
+ }
+ if$
+ }
+ if$
+}
+
+FUNCTION {bibinfo.warn}
+{ swap$
+ duplicate$ missing$
+ {
+ swap$ "missing " swap$ * " in " * cite$ * warning$ pop$
+ ""
+ }
+ { duplicate$ empty$
+ {
+ swap$ "empty " swap$ * " in " * cite$ * warning$
+ }
+ { swap$
+ pop$
+ }
+ if$
+ }
+ if$
+}
+INTEGERS { nameptr namesleft numnames }
+
+
+STRINGS { bibinfo}
+
+FUNCTION {format.names}
+{ 'bibinfo :=
+ duplicate$ empty$ 'skip$ {
+ "." ". " find.replace 's :=
+ "" 't :=
+ #1 'nameptr :=
+ s num.names$ 'numnames :=
+ numnames 'namesleft :=
+ { namesleft #0 > }
+ { s nameptr
+ "{vv~}{ll}{ f{}}{ jj}"
+ format.name$
+ remove.dots
+ bibinfo bibinfo.check
+ 't :=
+ nameptr #1 >
+ {
+ nameptr #6
+ #1 + =
+ numnames #6
+ > and
+ { "others" 't :=
+ #1 'namesleft := }
+ 'skip$
+ if$
+ namesleft #1 >
+ { ", " * t * }
+ {
+ "," *
+ s nameptr "{ll}" format.name$ duplicate$ "others" =
+ { 't := }
+ { pop$ }
+ if$
+ t "others" =
+ {
+ " " * bbl.etal *
+ }
+ { " " * t * }
+ if$
+ }
+ if$
+ }
+ 't
+ if$
+ nameptr #1 + 'nameptr :=
+ namesleft #1 - 'namesleft :=
+ }
+ while$
+ } if$
+}
+
+FUNCTION {format.names.org}
+{ 'bibinfo :=
+ duplicate$ empty$ 'skip$ {
+ 's :=
+ "" 't :=
+ #1 'nameptr :=
+ s num.names$ 'numnames :=
+ numnames 'namesleft :=
+ { namesleft #0 > }
+ { s nameptr
+ "{ff~}{vv~}{ll}"
+ format.name$
+ bibinfo bibinfo.check
+ 't :=
+ nameptr #1 >
+ {
+ namesleft #1 >
+ { "; " * t * }
+ {
+ ";" *
+ s nameptr "{ll}" format.name$ duplicate$ "others" =
+ { 't := }
+ { pop$ }
+ if$
+ t "others" =
+ {
+ " " * bbl.etal *
+ }
+ { " " * t * }
+ if$
+ }
+ if$
+ }
+ 't
+ if$
+ nameptr #1 + 'nameptr :=
+ namesleft #1 - 'namesleft :=
+ }
+ while$
+ } if$
+}
+
+FUNCTION {format.names.ed}
+{
+ format.names
+}
+FUNCTION {format.key}
+{ empty$
+ { key field.or.null }
+ { "" }
+ if$
+}
+
+FUNCTION {format.authors}
+{
+ author "author" format.names
+ %%"." " " "author" find.replace format.names
+}
+
+FUNCTION {format.organizations}
+{ organization "organization" format.names.org
+}
+
+FUNCTION {get.bbl.editor}
+{ editor num.names$ #1 > 'bbl.editors 'bbl.editor if$ }
+
+FUNCTION {get.bbl.cartographer}
+{ cartographer num.names$ #1 > 'bbl.cartographers 'bbl.cartographer if$ }
+
+FUNCTION {get.bbl.inventor}
+{ inventor num.names$ #1 > 'bbl.inventors 'bbl.inventor if$ }
+
+FUNCTION {get.bbl.assignee}
+{ assignee num.names$ #1 > 'bbl.assignees 'bbl.assignee if$ }
+
+FUNCTION {format.editors}
+{ editor "editor" format.names duplicate$ empty$ 'skip$
+ {
+ "," *
+ " " *
+ get.bbl.editor
+ *
+ }
+ if$
+}
+
+FUNCTION {format.assignees}
+{ assignee "assignee" format.names.org duplicate$ empty$ 'skip$
+ {
+ "," *
+ " " *
+ get.bbl.assignee
+ *
+ }
+ if$
+}
+
+FUNCTION {format.cartographers}
+{ cartographer "cartographer" format.names duplicate$ empty$ 'skip$
+ {
+ "," *
+ " " *
+ get.bbl.cartographer
+ *
+ }
+ if$
+}
+
+FUNCTION {format.inventors}
+{ inventor "inventor" format.names duplicate$ empty$ 'skip$
+ {
+ "," *
+ " " *
+ get.bbl.inventor
+ *
+ }
+ if$
+}
+
+FUNCTION {format.note}
+{
+ url empty$
+ 'skip$
+ { "\urlprefix\url{" url * "}" * output }
+ if$
+ note empty$
+ { "" }
+ { note #1 #1 substring$
+ duplicate$ "{" =
+ 'skip$
+ { output.state mid.sentence =
+ { "l" }
+ { "u" }
+ if$
+ change.case$
+ }
+ if$
+ note #2 global.max$ substring$ * "note" bibinfo.check
+ }
+ if$
+}
+
+FUNCTION {format.title}
+{ title
+%%duplicate$ empty$ 'skip$
+%% { "t" change.case$ }
+%%if$
+ "title" bibinfo.check
+}
+
+
+FUNCTION {author.editor.key.full}
+{ author empty$
+ { editor empty$
+ { key empty$
+ { cite$ #1 #3 substring$ }
+ 'key
+ if$
+ }
+ { editor }
+ if$
+ }
+ { author }
+ if$
+}
+
+FUNCTION {author.key.full}
+{ author empty$
+ { key empty$
+ { cite$ #1 #3 substring$ }
+ 'key
+ if$
+ }
+ { author }
+ if$
+}
+
+FUNCTION {editor.key.full}
+{ editor empty$
+ { key empty$
+ { cite$ #1 #3 substring$ }
+ 'key
+ if$
+ }
+ { editor }
+ if$
+}
+
+FUNCTION {make.full.names}
+{ type$ "book" =
+ type$ "inbook" =
+ or
+ 'author.editor.key.full
+ { type$ "proceedings" =
+ 'editor.key.full
+ 'author.key.full
+ if$
+ }
+ if$
+}
+
+FUNCTION {output.bibitem}
+{ newline$
+ "\bibitem[{" write$
+ label write$
+ ")" make.full.names duplicate$ short.list =
+ { pop$ }
+ { * }
+ if$
+ "}]{" * write$
+ cite$ write$
+ "}" write$
+ newline$
+ ""
+ before.all 'output.state :=
+}
+
+FUNCTION {n.dashify}
+{
+ 't :=
+ ""
+ { t empty$ not }
+ { t #1 #1 substring$ "-" =
+ { t #1 #2 substring$ "--" = not
+ { "--" *
+ t #2 global.max$ substring$ 't :=
+ }
+ { { t #1 #1 substring$ "-" = }
+ { "-" *
+ t #2 global.max$ substring$ 't :=
+ }
+ while$
+ }
+ if$
+ }
+ { t #1 #1 substring$ *
+ t #2 global.max$ substring$ 't :=
+ }
+ if$
+ }
+ while$
+}
+
+FUNCTION {word.in}
+{ bbl.in capitalize
+ ":" *
+ " " * }
+
+FUNCTION {format.journal.date}
+{
+ month "month" bibinfo.check
+ duplicate$ empty$
+ year "year" bibinfo.check duplicate$ empty$
+ {
+ swap$ 'skip$
+ { "there's a month but no year in " cite$ * warning$ }
+ if$
+ *
+ }
+ { swap$ 'skip$
+ {
+ " " * swap$
+ }
+ if$
+ *
+ remove.dots
+ }
+ if$
+ duplicate$ empty$
+ 'skip$
+ {
+ before.all 'output.state :=
+ after.sentence 'output.state :=
+ }
+ if$
+}
+
+FUNCTION {format.date}
+{
+ no.blank.or.punct
+ ";"
+ duplicate$ empty$
+ year "year" bibinfo.check duplicate$ empty$
+ { swap$ 'skip$
+ { "there's a month but no year in " cite$ * warning$ }
+ if$
+ *
+ }
+ { swap$ 'skip$
+ {
+ swap$
+ " " * swap$
+ }
+ if$
+ *
+ }
+ if$
+}
+
+FUNCTION {format.btitle}
+{ title "title" bibinfo.check
+ duplicate$ empty$ 'skip$
+ {
+ }
+ if$
+}
+
+FUNCTION {either.or.check}
+{ empty$
+ 'pop$
+ { "can't use both " swap$ * " fields in " * cite$ * warning$ }
+ if$
+}
+
+FUNCTION {format.bvolume}
+{ volume empty$
+ { "" }
+ { bbl.volume volume tie.or.space.prefix
+ "volume" bibinfo.check * *
+ series "series" bibinfo.check
+ duplicate$ empty$ 'pop$
+ { swap$ bbl.of space.word * swap$
+ emphasize * }
+ if$
+ "volume and number" number either.or.check
+ }
+ if$
+}
+
+FUNCTION {format.number.series}
+{ volume empty$
+ { number empty$
+ { series field.or.null }
+ { output.state mid.sentence =
+ { bbl.number }
+ { bbl.number capitalize }
+ if$
+ number tie.or.space.prefix "number" bibinfo.check * *
+ series empty$
+ { "there's a number but no series in " cite$ * warning$ }
+ { bbl.in space.word *
+ series "series" bibinfo.check *
+ }
+ if$
+ }
+ if$
+ }
+ { "" }
+ if$
+}
+
+FUNCTION {format.edition}
+{ edition duplicate$ empty$ 'skip$
+ {
+% convert.edition
+ output.state mid.sentence =
+ { "l" }
+ { "t" }
+ if$ change.case$
+ "edition" bibinfo.check
+ " " * bbl.edition *
+ }
+ if$
+}
+INTEGERS { multiresult }
+FUNCTION {multi.page.check}
+{ 't :=
+ #0 'multiresult :=
+ { multiresult not
+ t empty$ not
+ and
+ }
+ { t #1 #1 substring$
+ duplicate$ "-" =
+ swap$ duplicate$ "," =
+ swap$ "+" =
+ or or
+ { #1 'multiresult := }
+ { t #2 global.max$ substring$ 't := }
+ if$
+ }
+ while$
+ multiresult
+}
+
+FUNCTION {format.pages}
+{ pages duplicate$ empty$ 'skip$
+ { duplicate$ multi.page.check
+ {
+ bbl.pages swap$
+ n.dashify
+ }
+ {
+ bbl.page swap$
+ }
+ if$
+ tie.or.space.prefix
+ "pages" bibinfo.check
+ * *
+ }
+ if$
+}
+
+FUNCTION {format.journal.pages}
+{ pages duplicate$ empty$ 'pop$
+ { swap$ duplicate$ empty$
+ { pop$ pop$ format.pages }
+ {
+ ":" *
+ swap$
+ n.dashify
+ "pages" bibinfo.check
+ *
+ }
+ if$
+ }
+ if$
+}
+
+FUNCTION {format.vol.num}
+{ volume field.or.null
+ duplicate$ empty$ 'skip$
+ {
+ "volume" bibinfo.check
+ }
+ if$
+ number "number" bibinfo.check duplicate$ empty$ 'skip$
+ {
+ swap$ duplicate$ empty$
+ { "there's a number but no volume in " cite$ * warning$ }
+ 'skip$
+ if$
+ swap$
+ "(" swap$ * ")" *
+ }
+ if$ *
+}
+
+FUNCTION {format.vol.num.pages}
+{ volume field.or.null
+ duplicate$ empty$ 'skip$
+ {
+ "volume" bibinfo.check
+ }
+ if$
+ number "number" bibinfo.check duplicate$ empty$ 'skip$
+ {
+ swap$ duplicate$ empty$
+ { "there's a number but no volume in " cite$ * warning$ }
+ 'skip$
+ if$
+ swap$
+ "(" swap$ * ")" *
+ }
+ if$ *
+ format.journal.pages
+}
+
+FUNCTION {format.chapter.pages}
+{ chapter empty$
+ 'format.pages
+ { type empty$
+ { bbl.chapter }
+ { type "l" change.case$
+ "type" bibinfo.check
+ }
+ if$
+ chapter tie.or.space.prefix
+ "chapter" bibinfo.check
+ * *
+ pages empty$
+ 'skip$
+ { ", " * format.pages * }
+ if$
+ }
+ if$
+ }
+
+ FUNCTION {format.booktitle}
+ {
+ booktitle "booktitle" bibinfo.check
+ }
+
+ FUNCTION {format.in.ed.booktitle}
+ { format.booktitle duplicate$ empty$ 'skip$
+ {
+ editor "editor" format.names.ed duplicate$ empty$ 'pop$
+ {
+ "," *
+ " " *
+ get.bbl.editor
+ ". " *
+ * swap$
+ * }
+ if$
+ word.in swap$ *
+ }
+ if$
+ }
+
+ FUNCTION {format.in.ed.title}
+ { format.title duplicate$ empty$ 'skip$
+ {
+ editor "editor" format.names.ed duplicate$ empty$ 'pop$
+ {
+ "," *
+ " " *
+ get.bbl.editor
+ ". " *
+ * swap$
+ * }
+ if$
+ word.in swap$ *
+ }
+ if$
+ }
+
+ FUNCTION {empty.misc.check}
+ { author empty$ title empty$ howpublished empty$
+ month empty$ year empty$ note empty$
+ and and and and and
+ { "all relevant fields are empty in " cite$ * warning$ }
+ 'skip$
+ if$
+ }
+FUNCTION {format.thesis.type}
+ { type duplicate$ empty$
+ 'pop$
+ { swap$ pop$
+ "t" change.case$ "type" bibinfo.check
+ }
+ if$
+}
+FUNCTION {format.tr.number}
+{
+ number "number" bibinfo.check
+ %%type duplicate$ empty$
+ %%{ pop$ bbl.techrep }
+ %%'skip$
+ %%if$
+ %%"type" bibinfo.check
+ %%swap$ duplicate$ empty$
+ %%{ pop$ "t" change.case$ }
+ %%{ tie.or.space.prefix * * }
+ %%if$
+}
+
+FUNCTION {format.org.or.pub}
+{ 't :=
+ ""
+ address empty$ t empty$ and
+ 'skip$
+ {
+ address "address" bibinfo.check *
+ t empty$
+ 'skip$
+ { address empty$
+ 'skip$
+ { ": " * }
+ if$
+ t *
+ }
+ if$
+ }
+ if$
+}
+
+FUNCTION {format.publisher.address}
+{ publisher "publisher" bibinfo.warn format.org.or.pub
+}
+
+FUNCTION {format.organization.address}
+{ organization "organization" bibinfo.check format.org.or.pub
+}
+
+FUNCTION {format.institution.address}
+{ institution "institution" bibinfo.check format.org.or.pub
+}
+FUNCTION {format.article.crossref}
+{
+ word.in
+ " \cite{" * crossref * "}" *
+}
+FUNCTION {format.book.crossref}
+{ volume duplicate$ empty$
+ { "empty volume in " cite$ * "'s crossref of " * crossref * warning$
+ pop$ word.in
+ }
+ { bbl.volume
+ capitalize
+ swap$ tie.or.space.prefix "volume" bibinfo.check * * bbl.of space.word *
+ }
+ if$
+ " \cite{" * crossref * "}" *
+}
+FUNCTION {format.incoll.inproc.crossref}
+{
+ word.in
+ " \cite{" * crossref * "}" *
+}
+FUNCTION {misc}
+{ output.bibitem
+ format.authors "author" output.check
+ format.editors "author and editor" output.check
+ format.title "title" output.check
+ type missing$
+ { skip$ }
+% { format.type "type" output.check }
+ { "type" output.check }
+ %%{ inbrackets type output }
+ if$
+ new.block
+ format.publisher.address output
+ format.date "year" output.check
+ new.block
+ format.note output
+ new.block
+ howpublished new.block.checka
+ howpublished "howpublished" bibinfo.check output
+% output.web.refs % urlbst
+ fin.entry
+ empty.misc.check
+}
+
+FUNCTION {article}
+{ output.bibitem
+ format.authors "author" output.check
+ organization empty$
+ 'skip$
+ { author empty$
+ {
+ format.organizations "organization" output.check
+ }
+ {
+ "; " *
+ no.blank.or.punct
+ format.organizations "organization" output.check
+ }
+ if$
+ }
+ if$
+ new.block
+ format.title "title" output.check
+ type missing$
+ { skip$ }
+ { "type" output.check }
+ if$
+ new.block
+ journal
+ remove.dots
+ "journal" bibinfo.check
+ "journal" output.check
+ format.journal.date "year" output.check
+ add.semicolon
+ format.vol.num.pages output
+ new.block
+ format.note output
+% output.web.refs % urlbst
+ fin.entry
+}
+
+FUNCTION {book}
+{ output.bibitem
+ author empty$
+ { editor empty$
+ { format.organizations "organization" output.check }
+ { format.editors "author and editor" output.check }
+ if$
+ }
+ { format.authors output.nonnull
+ "author and editor" editor either.or.check
+ }
+ if$
+ new.block
+ format.btitle "title" output.check
+ format.bvolume output
+ new.block
+ format.edition output
+ new.sentence
+ author empty$ not
+ editor empty$ not
+ and
+ { format.editors "author and editor" output.check }
+ 'skip$
+ if$
+ format.number.series output
+ format.publisher.address output
+ format.date "year" output.check
+ new.block
+ format.note output
+% output.web.refs % urlbst
+ fin.entry
+}
+FUNCTION {booklet}
+{ misc }
+
+FUNCTION {dictionary}
+{ output.bibitem
+ format.booktitle "booktitle" output.check
+ format.bvolume output
+ new.block
+ format.edition output
+ new.sentence
+ format.publisher.address output
+ format.date "year" output.check
+ format.btitle "title" output.check
+ add.semicolon
+ add.blank
+ format.pages "pages" output.check
+ new.block
+ format.note output
+% output.web.refs % urlbst
+ fin.entry
+}
+
+FUNCTION {inbook}
+{ output.bibitem
+ format.authors "author" output.check
+ new.block
+ chapter "chapter" output.check
+ new.block
+ format.in.ed.title "title" output.check
+ format.bvolume output
+ format.edition output
+ new.sentence
+ format.number.series output
+ format.publisher.address output
+ format.date "year" output.check
+ date.block
+ add.blank
+ format.pages "pages" output.check
+ new.block
+ format.note output
+% output.web.refs % urlbst
+ fin.entry
+}
+
+FUNCTION {incollection}
+{ output.bibitem
+ format.authors "author" output.check
+ new.block
+ format.title "title" output.check
+ new.block
+ format.in.ed.booktitle "booktitle" output.check
+ format.bvolume output
+ format.edition output
+ new.sentence
+ format.number.series output
+ format.publisher.address output
+ format.date "year" output.check
+ date.block
+% add.blank
+ format.pages "pages" output.check
+ new.block
+ format.note output
+ fin.entry
+}
+FUNCTION {inproceedings}
+{ output.bibitem
+ format.authors "author" output.check
+ new.block
+ format.title "title" output.check
+ new.block
+ format.in.ed.booktitle "booktitle" output.check
+ format.bvolume output
+ new.sentence
+ format.number.series output
+ publisher empty$
+ { format.organization.address output }
+ { organization "organization" bibinfo.check output
+ format.publisher.address output
+ }
+ if$
+ format.date "year" output.check
+ date.block
+ add.blank
+ format.pages "pages" output.check
+ new.block
+ format.note output
+% output.web.refs % urlbst
+ fin.entry
+}
+FUNCTION {conference} { inproceedings }
+FUNCTION {manual}
+{ output.bibitem
+ format.authors output
+ author format.key output
+% add.colon
+ new.block
+ format.btitle "title" output.check
+ organization address new.block.checkb
+ organization "organization" bibinfo.check output
+ address "address" bibinfo.check output
+ format.edition output
+ format.date "year" output.check
+ % new.block ++++ REMOVED (to get comma before note)
+ format.note output
+ fin.entry
+}
+
+FUNCTION {phdthesis}
+{ output.bibitem
+ format.authors "author" output.check
+ new.block
+ format.btitle "title" output.check
+ new.block
+ "PhD thesis" format.thesis.type output.nonnull
+ school "school" bibinfo.warn output
+% address "address" bibinfo.check output
+ format.date "year" output.check
+% new.block
+% format.note output
+% output.web.refs % urlbst
+ fin.entry
+}
+
+FUNCTION {proceedings}
+{ output.bibitem
+ format.editors output
+ editor format.key output
+% add.colon
+ new.block
+ format.btitle "title" output.check
+ format.bvolume output
+ new.sentence
+ format.number.series output
+ publisher empty$
+ { format.organization.address output }
+ { organization "organization" bibinfo.check output
+ format.publisher.address output
+ }
+ if$
+ format.date "year" output.check
+ % new.block ++++ REMOVED (to get comma before note)
+ format.note output
+ fin.entry
+}
+
+FUNCTION {techreport}
+{ output.bibitem
+ format.authors "author" output.check
+ new.block
+ format.title
+ "title" output.check
+ new.block
+ format.institution.address output
+ format.date "year" output.check
+% format.tr.number output.nonnull
+% new.block
+% format.note output
+% output.web.refs % urlbst
+ fin.entry
+}
+
+FUNCTION {unpublished}
+{ output.bibitem
+ format.authors "author" output.check
+ author format.key output
+% add.colon
+ new.block
+ format.title "title" output.check
+ format.date "year" output.check
+ % new.block ++++ REMOVED (to get comma before note)
+ format.note "note" output.check
+ fin.entry
+}
+
+FUNCTION {default.type} { misc }
+READ
+FUNCTION {sortify}
+{ purify$
+ "l" change.case$
+}
+INTEGERS { len }
+FUNCTION {chop.word}
+{ 's :=
+ 'len :=
+ s #1 len substring$ =
+ { s len #1 + global.max$ substring$ }
+ 's
+ if$
+}
+FUNCTION {format.lab.names}
+{ 's :=
+ "" 't :=
+ s #1 "{vv~}{ll}" format.name$
+ s num.names$ duplicate$
+ #2 >
+ { pop$
+ " " * bbl.etal *
+ }
+ { #2 <
+ 'skip$
+ { s #2 "{ff }{vv }{ll}{ jj}" format.name$ "others" =
+ {
+ " " * bbl.etal *
+ }
+ { bbl.and space.word * s #2 "{vv~}{ll}" format.name$
+ * }
+ if$
+ }
+ if$
+ }
+ if$
+}
+
+FUNCTION {author.key.label}
+{ author empty$
+ { key empty$
+ { cite$ #1 #3 substring$ }
+ 'key
+ if$
+ }
+ { author format.lab.names }
+ if$
+}
+
+FUNCTION {author.editor.key.label}
+{ author empty$
+ { editor empty$
+ { key empty$
+ { cite$ #1 #3 substring$ }
+ 'key
+ if$
+ }
+ { editor format.lab.names }
+ if$
+ }
+ { author format.lab.names }
+ if$
+}
+
+FUNCTION {editor.key.label}
+{ editor empty$
+ { key empty$
+ { cite$ #1 #3 substring$ }
+ 'key
+ if$
+ }
+ { editor format.lab.names }
+ if$
+}
+
+FUNCTION {calc.short.authors}
+{ type$ "book" =
+ type$ "inbook" =
+ or
+ 'author.editor.key.label
+ { type$ "proceedings" =
+ 'editor.key.label
+ 'author.key.label
+ if$
+ }
+ if$
+ 'short.list :=
+}
+
+FUNCTION {calc.label}
+{ calc.short.authors
+ short.list
+ "("
+ *
+ year duplicate$ empty$
+ { pop$ "????" }
+ 'skip$
+ if$
+ *
+ 'label :=
+}
+
+FUNCTION {sort.format.names}
+{ 's :=
+ #1 'nameptr :=
+ ""
+ s num.names$ 'numnames :=
+ numnames 'namesleft :=
+ { namesleft #0 > }
+ { s nameptr
+ "{ll{ }}{ ff{ }}{ jj{ }}"
+ format.name$ 't :=
+ nameptr #1 >
+ {
+ " " *
+ namesleft #1 = t "others" = and
+ { "zzzzz" * }
+ { t sortify * }
+ if$
+ }
+ { t sortify * }
+ if$
+ nameptr #1 + 'nameptr :=
+ namesleft #1 - 'namesleft :=
+ }
+ while$
+}
+
+FUNCTION {sort.format.title}
+{ 't :=
+ "A " #2
+ "An " #3
+ "The " #4 t chop.word
+ chop.word
+ chop.word
+ sortify
+ #1 global.max$ substring$
+}
+FUNCTION {author.sort}
+{ author empty$
+ { key empty$
+ { "to sort, need author or key in " cite$ * warning$
+ ""
+ }
+ { key sortify }
+ if$
+ }
+ { author sort.format.names }
+ if$
+}
+FUNCTION {author.editor.sort}
+{ author empty$
+ { editor empty$
+ { key empty$
+ { "to sort, need author, editor, or key in " cite$ * warning$
+ ""
+ }
+ { key sortify }
+ if$
+ }
+ { editor sort.format.names }
+ if$
+ }
+ { author sort.format.names }
+ if$
+}
+FUNCTION {editor.sort}
+{ editor empty$
+ { key empty$
+ { "to sort, need editor or key in " cite$ * warning$
+ ""
+ }
+ { key sortify }
+ if$
+ }
+ { editor sort.format.names }
+ if$
+}
+FUNCTION {presort}
+{ calc.label
+ % label sortify
+ % " "
+ % *
+ % type$ "book" =
+ % type$ "inbook" =
+ % or
+ % 'author.editor.sort
+ % { type$ "proceedings" =
+ % 'editor.sort
+ % 'author.sort
+ % if$
+ % }
+ % if$
+ % #1 entry.max$ substring$
+ % 'sort.label :=
+ % sort.label
+ % *
+ % " "
+ % *
+ % title field.or.null
+ % sort.format.title
+ % *
+ % #1 entry.max$ substring$
+ % 'sort.key$ :=
+}
+
+ITERATE {presort}
+SORT
+STRINGS { last.label next.extra }
+INTEGERS { last.extra.num number.label }
+FUNCTION {initialize.extra.label.stuff}
+{ #0 int.to.chr$ 'last.label :=
+ "" 'next.extra :=
+ #0 'last.extra.num :=
+ #0 'number.label :=
+}
+FUNCTION {forward.pass}
+{ last.label label =
+ { last.extra.num #1 + 'last.extra.num :=
+ last.extra.num int.to.chr$ 'extra.label :=
+ }
+ { "a" chr.to.int$ 'last.extra.num :=
+ "" 'extra.label :=
+ label 'last.label :=
+ }
+ if$
+ number.label #1 + 'number.label :=
+}
+FUNCTION {reverse.pass}
+{ next.extra "b" =
+ { "a" 'extra.label := }
+ 'skip$
+ if$
+ extra.label 'next.extra :=
+ extra.label
+ duplicate$ empty$
+ 'skip$
+ { "{\natexlab{" swap$ * "}}" * }
+ if$
+ 'extra.label :=
+ label extra.label * 'label :=
+}
+EXECUTE {initialize.extra.label.stuff}
+ITERATE {forward.pass}
+REVERSE {reverse.pass}
+FUNCTION {bib.sort.order}
+{ sort.label
+ " "
+ *
+ year field.or.null sortify
+ *
+ " "
+ *
+ title field.or.null
+ sort.format.title
+ *
+ #1 entry.max$ substring$
+ 'sort.key$ :=
+}
+% ITERATE {bib.sort.order}
+% SORT
+FUNCTION {begin.bib}
+{ preamble$ empty$
+ 'skip$
+ { preamble$ write$ newline$ }
+ if$
+ "\begin{thebibliography}{" number.label int.to.str$ * "}" *
+ write$ newline$
+ "\providecommand{\natexlab}[1]{#1}"
+ write$ newline$
+ "\providecommand{\url}[1]{\texttt{#1}}"
+ write$ newline$
+% "\providecommand{\urlprefix}{URL }" ++++ EMPTIED by default
+ "\providecommand{\urlprefix}{}"
+ write$ newline$
+}
+EXECUTE {begin.bib}
+EXECUTE {init.state.consts}
+ITERATE {call.type$}
+FUNCTION {end.bib}
+{ newline$
+ "\end{thebibliography}" write$ newline$
+}
+EXECUTE {end.bib}
+%% End of customized bst file
+%%
+%% End of file `splncsnat.bst'.