-
Notifications
You must be signed in to change notification settings - Fork 14
partially address the comment #208
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.
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
base: main
Are you sure you want to change the base?
Changes from all commits
dd589e6
a03ee6c
259c703
d0e9f59
78bfe88
0ac1e12
791dc2d
e7a7f96
a1181b4
c557840
5e46c69
afcbada
89bd059
0666456
e687736
4657cae
a0243d2
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -121,6 +121,7 @@ \section{Motivation for central RSE units} | |||||
| Handling this increased complexity whilst ensuring timely delivery requires dedicated RSEs in central RSE units. | ||||||
|
|
||||||
| \subsection{Pooling: a necessary ingredient} | ||||||
| \label{subsec:pooling} | ||||||
| The main focus of this paper lies on central RSE teams since the benefits of RSEs to research in general are described elsewhere, \eg{} in~\autocite{Anzt2021}. | ||||||
| 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 a central point of contact. | ||||||
|
|
@@ -624,6 +625,21 @@ \subsubsection{Growth of the Unit} | |||||
| In addition, SIS offers services in the areas of data science, machine learning, bioinformatics, trusted compute environments, and training and consulting. | ||||||
| \end{mdframed} | ||||||
|
|
||||||
| \subsubsection{Risk Assessment and Opportunities} | ||||||
| Naturally, the presence of a “new” department like an RSE department at an academic institution will lead to a realignment of responsibilities of existing departments. | ||||||
| Stakeholders that might be affected are for example traditional IT centres, libraries, but also RDM units and legal offices. | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
minor reformulation |
||||||
| We argue, that an RSE unit does not aim to replace them, but offers new possibilities to connect these existing institutions and thereby enables an academic insititution to offer a stronger portfolio to its scientists. | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
|
||||||
| Even if the concept of an RSE unit fails at a specific institution, its duties and the employed people can be shifted to the other departments until a new structure has been found. | ||||||
| Governance and organisational location are points that have to be negotiated inividually at each institution and probably also for a lot of employees of the RSE unit in order to fit the needs of the scientists. | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| This comes partially from the aforementioned stakeholders, but also from the necessity, that while the unit is a central infrastructure, | ||||||
| it needs to be able to provide the services of their employees within the agile structures of academic research -- close to the scientists. | ||||||
| Therefore a certain lack of formalised, organisational structures can be expected. | ||||||
|
Comment on lines
+635
to
+637
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What is This - the governance? Agile structures at a university? What are you trying to say here? I think this sounds a little bit vague and that RSEs would like to do stuff. |
||||||
| Finding people for staffing this unit is a challenging tasks, but this is partially addressed through the wide network within the university that the unit forms, and also by further measures described in~\ref{subsec:staff}. | ||||||
| Funding will always be an issue of any newly established structure at a German university. | ||||||
| Initial funding, e. g., by initiatives outside of the university, can jumpstart the unit, ultimately it has to prove its value to the scientists of the university such that the pooling idea we have given~\ref{subsec:pooling} gains traction. | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| While “measuring” the success of the unit certainly has its difficulties but could be tried, ultimately the scientists have to come to the conclusion whether the RSE unit is worthwhile and should be kept. | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
I think this is a tricky one. Presumably an RSE unit needs to generate some form of income which can be used to decide whether it is successful. |
||||||
|
|
||||||
| \subsection{Outsourcing} | ||||||
|
|
||||||
| Another possibility for the realisation of local RSE Service providers is by forming a spin-off and pooling the RSE Skills into an external company, which has benefits but also drawbacks. | ||||||
|
|
@@ -642,7 +658,7 @@ \subsection{Outsourcing} | |||||
| On top of these drawbacks, there are soft factors, like whether an external company is accepted by scientists. | ||||||
|
|
||||||
| \subsection{Staff Acquisition/People} | ||||||
|
|
||||||
| \label{subsec:staff} | ||||||
| RSE units need to be staffed, but where do potential employees come from? | ||||||
| So far, researchers accidentally find themselves in the role of an RSE because they pursued software development as part of their research. | ||||||
| A more deliberate approach with specific RSE education may be necessary to train people in sufficient numbers for central RSE units. | ||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -22,8 +22,10 @@ We thank you very much for your review and the opportunity to improve our manusc | |||||
| > The conclusions are generally consistent with the arguments presented, but somewhat stronger than the evidence allows. Recommendations for investing in central RSE units are justified, but statements suggesting widespread institutional improvements should be more carefully balanced with a discussion of risks, costs, governance challenges, and potential failure modes. | ||||||
|
|
||||||
| **Answer:** | ||||||
| We did not intend to conduct a statistically significant, representative survey of RSE units. Our aim was to collect some feedback that we can use to demmonstrate the breadth of services offered by existing units and to support the selection of service modules we defined. We have replaced the term survey with less formal formulations. | ||||||
|
|
||||||
| The reviewer is right to suggest a more elaborate discussion of risks for an RSE unit and we took the opportunity to write a separate subsusection on risks in the realisation of an RSE unit. | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| However, we also did not intend to conduct a statistically significant, representative survey of RSE units. | ||||||
| Our aim was to collect some feedback that we can use to demmonstrate the breadth of services offered by existing units and to support the selection of service modules we defined. | ||||||
| We have replaced the term survey with less formal formulations. | ||||||
|
|
||||||
| --- | ||||||
|
|
||||||
|
|
@@ -87,5 +89,7 @@ We softened several claims in the paper | |||||
| > Expand the discussion on implementation risks, such as funding instability, unclear governance, overlap with IT/RDM units, and difficulty in recruiting qualified RSE staff. | ||||||
|
|
||||||
| **Answer:** | ||||||
| We thank the reviewer for pointing out this omission and have now added a risk assessmant and opportunities subsubsection in the realisation chapter. | ||||||
| In this paragraph we elaborate on the risks mentioned by the reviewer. | ||||||
|
|
||||||
| --- | ||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -244,7 +244,8 @@ Please see our general answer on this manuscript being an _opinion article._ | |||||
| > You do not discuss risks or failure modes. For example, what happens if a central RSE unit cannot get enough project funding? What if it competes with existing IT or RDM units? Add a short paragraph on risks. | ||||||
|
|
||||||
| **Answer:** | ||||||
|
|
||||||
| We thank the reviewer for pointing out this omission. We have added a subsubsection on risk assessmant in the realisation chapter where we elaborate | ||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
| on the risks mentioned by the reviewer. | ||||||
| --- | ||||||
|
|
||||||
| ### Comment 25 | ||||||
|
|
||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's the creation of a new department that moves responsibilities around. Once it is established things should have settled down.