Skip to content
New issue

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

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Update paper.tex #56

Merged
merged 2 commits into from
Apr 12, 2024
Merged

Update paper.tex #56

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c93ffc
Update paper.tex
pancetta Apr 12, 2024
e58d0a5
Restore consists of
dokempf Apr 12, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions paper.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,11 +49,13 @@ \section{Introduction}
%We follow here the definition: “Research Software includes source code files, algorithms, scripts, computational workflows and executables that were created during the research process or for a research purpose”, with full definition and discussion provided in~\autocite{Gruenpeter2021}.

The number of people developing software in academia is constantly rising~\autocite{Hannay2009, Hettrick2015}.
Research Software Engineering consists of actions necessary to create, adapt, or maintain Research Software or train others to do so.
Research Software Engineering are actions necessary to create, adapt or maintain Research Software or train others to do so.
These actions are very diverse and so are the environments they are performed in.
This position paper focuses on (groups of) research software engineers and researchers who require RSE for their research.
We advocate the establishment and support of dedicated, central RSE groups in German research organizations, with clearly defined tasks, contact points, and, in particular, sustained funding.
We provide an overview of the various task these teams have and discuss potential realization strategies, learning from already existing examples of such an RSE unit.

\subsection{Terminology}
Before we motivate the topic of this position paper further, we first introduce the terminology used throught this work.
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” is also defined somewhat differently within the community.
Expand Down Expand Up @@ -81,6 +83,10 @@ \subsection{Terminology}
We refer by researchers to all others involved in research or in research supporting organizations such as \eg libraries,
hence those that are at most sporadically performing RSE actions.

Furthermore, we will use the general term \textbf{RSE Hub} for the central RSE team throughout this paper.
These RSE Hubs can take the form of, e.g., full RSE departments, smaller RSE groups, Open Source Program Office (OSPOs), virtually across multiple units or combined under one single leader, depending on the evironment of the particular research organization under consideration.
All of these implementations are considered here, taking into account the large variety of research environments in Germany.

\section{Motivation}


Expand Down
Loading