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 #131

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update paper.tex #131

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

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions paper.tex
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@

\abstract{%
This position paper urges decision makers in Germany to establish central RSE units within their institutions.
Focus is not put primarily on the establishment of RSE services in general, as this has been done already elsewhere.
The focus is not put primarily on the establishment of RSE services in general, as this has been done already elsewhere.
Instead, we highlight central RSE units.
Motivations for their existance are discussed, underpinned by working examples both in neighbouring fields as well as outside of Germany.
The heart of this paper is a vision of a central RSE unit, it's structure, and the definition of nine core support modules such a unit may provide.
Expand Down Expand Up @@ -405,13 +405,14 @@ \subsection{Module 8: Software Maintenance Service}%
Software maintenance is an 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.
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.
but academic labour turnover and the disconnect between project funding cycle and target software lifecycle make research software maintenance often rely on the (potentially unpaid) efforts of individuals.

An RSE hub with long term core staff can partially solve this problem by taking over maintenance tasks.
In order for this to be feasible two criteria need to be met:
In order for this to be feasible, three criteria need to be met:
\begin{itemize}
\item The software needs to be developed according to software engineering best practices with a strong emphasis on testing and continuous integration.
\item The RSE hub needs to be involved during the development period either through development or consultation services in order to ensure that best practices are followed and the required knowledge is transferred to the hub.
\item A mechanism for selecting and prioritizing software projects to be maintained needs to be in place.
\end{itemize}

\subsection{Module 9: Communication and Outreach}%
Expand Down
Loading