From e1a9cc1ef55b36c737e5b13ba71b2555ab14242e Mon Sep 17 00:00:00 2001 From: Florian Goth Date: Sun, 9 Feb 2025 01:14:50 +0100 Subject: [PATCH 1/2] provide a relate work sentence --- paper.tex | 1 + positionpaper.bib | 29 +++++++++++++++++++++++++++++ 2 files changed, 30 insertions(+) diff --git a/paper.tex b/paper.tex index 5cbbe58..65077cd 100644 --- a/paper.tex +++ b/paper.tex @@ -59,6 +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. +Similar initiaives have been formed in other national contexts (see \autoref{barkerkatz2024,martin2023} and references therein). 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. diff --git a/positionpaper.bib b/positionpaper.bib index d11d5cf..31c16d6 100644 --- a/positionpaper.bib +++ b/positionpaper.bib @@ -177,6 +177,35 @@ @Online{UtrechtRDM urldate = {2024-03-06}, } +@misc{barkerkatz2024, + author = {Barker, Michelle and + Katz, Daniel S.}, + title = {Resources on how to create a research software + engineering (RSE) group (within an organisation) + or association (national, etc) + }, + month = nov, + year = 2024, + publisher = {Zenodo}, + version = {1.0}, + doi = {10.5281/zenodo.14025418}, + url = {https://doi.org/10.5281/zenodo.14025418}, +} + +@misc{martin2023, + author = {Kimberly C. Martin}, + title = {Research Software Engineering Groups in the UK; + Origins, Organisational Context, and Practices - + 'RSE Roadtrip' Planning Document + }, + month = apr, + year = 2023, + publisher = {Zenodo}, + version = {v0.1}, + doi = {10.5281/zenodo.7852661}, + url = {https://doi.org/10.5281/zenodo.7852661}, +} + @TechReport{Utrecht2016a, author = {{Utrecht University}}, title = {Universitair beleidskader onderzoeksdata {U}niversiteit {U}trecht}, From d3d79d20cb1db06c625a167290ad32cc0bec1296 Mon Sep 17 00:00:00 2001 From: CaptainSifff Date: Wed, 12 Feb 2025 17:49:54 +0100 Subject: [PATCH 2/2] Update paper.tex MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Jean-Noël Grad --- paper.tex | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/paper.tex b/paper.tex index 65077cd..01ca604 100644 --- a/paper.tex +++ b/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. -Similar initiaives have been formed in other national contexts (see \autoref{barkerkatz2024,martin2023} and references therein). +Similar initiatives have been formed in other national contexts (see \autocite{barkerkatz2024,martin2023} and references therein). 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.