Skip to content

Add a risk section - #208

Open
CaptainSifff wants to merge 26 commits into
mainfrom
186-reviewer-2---conclusions---comment-2
Open

Add a risk section#208
CaptainSifff wants to merge 26 commits into
mainfrom
186-reviewer-2---conclusions---comment-2

Conversation

@CaptainSifff

Copy link
Copy Markdown
Collaborator

Not sure about the position in the text.

Still the question is, if we want to dedicate a risk section.

@CaptainSifff CaptainSifff linked an issue Jun 26, 2026 that may be closed by this pull request
Comment thread paper.tex Outdated
Comment thread paper.tex Outdated
dokempf and others added 6 commits June 29, 2026 16:45
Co-authored-by: axel-loewe <52000348+axel-loewe@users.noreply.github.com>
Co-authored-by: axel-loewe <52000348+axel-loewe@users.noreply.github.com>
Comment thread paper.tex Outdated
Comment on lines +624 to +625
that while the unit is a central infrastructure, it needs to be able within
the agile structures of academic research, therefore a certain lack of structures is expected.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this part of the sentence is not clear

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried my hand at clarifying it... Not sure I succeeded.

Comment thread paper.tex Outdated
Comment thread paper.tex Outdated
Florian Goth and others added 6 commits July 2, 2026 17:18
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
@dokempf

dokempf commented Jul 3, 2026

Copy link
Copy Markdown
Collaborator

Meeting: General concept of risk section is good, we should review for language. Also do not write "subsubsection", but just "subsection" to the reviewers.

Comment thread paper.tex Outdated
Comment thread paper.tex Outdated

@mhagdorn mhagdorn left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apart from the minor suggestions I think we need to sharpen the sentence about governance.

The other issue is on measuring success. I presume that an RSE unit will need to attract external funding, through work on projects (we do have an entire section on that). The risk is then, failure to attract enough funding. At this stage the institution would need to decide whether they want to keep the RSE unit.

Comment thread review_answers/review_1_answers.md Outdated
Comment thread review_answers/review_2_answers.md Outdated
Comment thread paper.tex Outdated
Comment thread paper.tex Outdated
Comment thread paper.tex Outdated
Comment thread paper.tex Outdated
Comment thread paper.tex Outdated
Comment on lines +635 to +637
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.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The 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.

Comment thread paper.tex Outdated
Comment thread paper.tex Outdated
dokempf and others added 6 commits July 30, 2026 15:03
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
dokempf and others added 3 commits July 30, 2026 15:05
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
Co-authored-by: Magnus Hagdorn <magnus.hagdorn@charite.de>
@dokempf dokempf changed the title partially address the comment Add a risk section Jul 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Reviewer 1 - Conclusions Reviewer 2 - Conclusions - comment 2 Reviewer 1 - Limitations - comment 5

5 participants