Merge branch 'main' into 79-hub-and-spoke

Author: mhagdorn

paper.tex

@@ -59,7 +59,7 @@ \section{Introduction}
 This position paper focuses on groups of research software engineers that provide their services for an entire research organisation or at least a substantial part of it.
 
 We advocate the establishment and support of dedicated, central RSE groups in German research organisations, with clearly defined tasks, contact points, and, in particular, sustained funding, for the benefit of all researchers in their organisation.
-We provide an overview of the various task these teams have and discuss potential realisation strategies, learning from already existing RSE units.
+We provide an overview of the various tasks these teams have and discuss potential realisation strategies, learning from already existing RSE units.
 
 Depending on the national research environments and processes that readers are familiar with, the notion of the terms \emph{software} and \emph{research} might differ.
 The term “research software” has also no single definition within the community.
@@ -93,7 +93,7 @@ \section{Motivation for central RSE units}
 For an overview of typical tasks of RSEs and the competencies required, see~\autocite{goth_foundational_competencies_2024}, especially section\ 4.4:\ “RSE tasks and responsibilities”.
 
 \subsection{Pooling: a necessary ingredient}
-The main focus of this paper lies on central RSE teams since the benefits of RSEs to research are described elsewhere [REF].
+The main focus of this paper lies on central RSE teams since the benefits of RSEs to research are described elsewhere **TODO: [REF]**.
 The main advantages of central RSE units all stem from the pooling of resources.
 There are at least three aspects to RSE pooling that research institutions can benefit from: funding, diverse knowledge, and support contacts.
 The first, pooling of \textbf{funding}, allows organisations to invest in building up institutional knowledge by supporting RSEs to become experts.
@@ -448,7 +448,7 @@ \subsection{Module 8: Software Maintenance Service}%
 
 In contrast to research data, the long-term availability and usability of research software requires more than an adequate archiving method:
 Software maintenance is the ongoing change process of software after its release.
-It includes  both fixing  bugs that are discovered in the software and adapting the software to changes in the execution environment such as hardware, operating system, toolchain and software dependencies.
+It includes  both fixing bugs that are discovered in the software and adapting the software to changes in the execution environment such as hardware, operating system, toolchain and software dependencies.
 In the scientific community there is a demand for long term maintenance of research software,
 but academic labour turnover and missing funding schemes make research software maintenance often rely on the (potentially unpaid) efforts of individuals.