Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Accept "An Environment for Sustainable Research Software in Germany and Beyond: Current State, Open Challenges, and Call for Action" as an official position of de-RSE e.V. #1
In order to add a review to this draft, you need to be logged in to GitHub.
Please make all comments and all change suggestions in the document found under the Files change (5) tab above! You will have to resolve the diff first before you can see the document text.
In your review, you can either leave a comment on one or more lines, or suggest a change in the text "directly" (see gif below).
Once you are finished with your review, please submit it (see gif below).
Many thanks for reviewing this position draft!
…ny-and-beyond/manuscript.md Co-Authored-By: axel-loewe <firstname.lastname@example.org>
StephanJanosch left a comment
I found 31 places in the text which I commented on or suggested a change.
In general the university perspective with being a domain researcher going towards RSE seems to be more prominent, than the perspective of an computer scientist entering a domain in a non university.
Huge thanks for that position paper
MakisH left a comment •
I read through the complete text, it looks great! Thank you all for the hard work! I really liked the story segments and I would be really interested in studying "M.Sc. RSE". I think it also gives a clear substance in the goals of the RSE movement, which felt a bit abstract until now.
From my point of view, I only found a problem with a reference ("Europe 2019"). Other than that, the link style in the references is inconsistent: some have a link as
…ny-and-beyond/manuscript.md Co-Authored-By: Stephan Janosch <StephanJanosch@users.noreply.github.com>
…ny-and-beyond/manuscript.md addition accepted Co-Authored-By: Stephan Druskat <email@example.com>
…ny-and-beyond/manuscript.md Co-Authored-By: Stephan Druskat <firstname.lastname@example.org>
@Knarff If you can approve this, we could merge and tag as the "community-reviewed pre-preprint version".
Thanks everyone for partaking in this, and also for working out together that GitHub PR reviews may not be the best tooling for dealing with such large documents. We've made it still!