Dissemination of the competencies preprint

[jngrad]

Where to advertise the preprint (feel free to edit my post to add new outlets):

• de-RSE mailing list call for contributions on 2023-11-23 by @CaptainSifff
• ReSA November newsletter on 2023-11-24 by @CaptainSifff
• local RSE chapters mailing lists:
  • strRSE on 2023-11-23 by @jngrad
  • MUC-RSE (@MakisH)
  • other RSE mailing lists? (maybe @jcohen02, @annalenalamprecht)
• blog posts and resource lists:
  • ReSA guidelines page on 2023-11-23 by @CaptainSifff
• talks, seminars, workshops:
  • deRSE/GI 'categories of research software' meeting on 2023-11-27 by @jpthiele
  • ICP Stuttgart group seminar on 2023-11-06 by @jngrad

[jpthiele]

Also @jlinx and me Monday/Tuesday at the deRSE/GI 'categories of research software' meeting.

[CaptainSifff]

Since I just received an E-Mail that the ReSA deadline is Nov21 for the arxiv link, I decided I will try to upload this sunday(19.11)

[CaptainSifff]

I think I will go for: cs.CY since their arxiv classification has education in it.

[CaptainSifff]

@MakisH , @jngrad , @jpthiele , @jcohen02 , @jlinx This would be the latex preview at arxiv arxiv.pdf .

[CaptainSifff]

OK, arxiv recommends cs.se ....

[CaptainSifff]

so, everything is prepared, I will wait a bit more until I press the submit button.

[MakisH]

Already looks very good! Nitpicking here (but I guess that's my task here):

• https://github.com/CaptainSifff/paper_teaching-learning-RSE/pull/210 is ready and a very nice addition that helps the reader.
• I only now realized, but the Contribution details should be an unnumbered section: https://github.com/CaptainSifff/paper_teaching-learning-RSE/pull/213

And with this, I promise to not report anything else.

Edit: And after these are fixed may I say: press it, Kim! (referring of course to our RSE persona)

[CaptainSifff]

Oh well... does anyone know if arxiv caches the pdfs...?

[CaptainSifff]

ok, figured it out... needs gls files acr files and acn files now.

[jpthiele]

Ahh glossary output files. Makes sense

[CaptainSifff]

submitted!

[CaptainSifff]

Today we are in "On hold" status.

[CaptainSifff]

back to submitted!

[jpthiele]

And published! https://arxiv.org/abs/2311.11457

[CaptainSifff]

Resa newsletter should work out, they have the information.

[CaptainSifff]

Announced on the de-RSE ML , once moderation has passed....

[CaptainSifff]

We got a prominent spot...: https://www.researchsoft.org/guidelines/

[CaptainSifff]

I will talk about this paper at SE24 in Linz: https://se2024.se.jku.at/

[CaptainSifff]

We made it to the GI-Radar! Issue 351. the archive is here: https://gi-radar.de/archiv/

[CaptainSifff]

@jpthiele Now I have registered for the MMS days.

[CaptainSifff]

Flo is at MMS days with these slides. goth-mmsdays2024.pdf

[CaptainSifff]

A new arxiv version: https://arxiv.org/abs/2311.11457

[jngrad]

• Jean-Noël Grad, blog post about deRSE24 and RSE competencies, April 11 2024, CoE MultiXscale (EuroHPC JU) (link)
• Samantha Wittke, Event report - Research Software Engineering: Bridging Knowledge Gaps, Nordic-RSE in person conference 2024, May 30-31 2024, Aalto University, Espoo, Finland (book of abstracts)

[jpthiele]

At RSECon24 (03.-05. August) there will be a workshop for forming a special interest group within SocRSE and we will have a lightning talk to present our work.

[jpthiele]

At US-RSE (15.-17. October) we will have a workshop (similar to deRSE24 in terms of questions I'd say) . I also handed in a talk and a poster but they are under review for now.

[CaptainSifff]

arxiv is now uploaded.

[CaptainSifff]

some dates from the arxiv mail:

[CaptainSifff]

Your replacement is scheduled to be announced at Wed, 14 Aug 2024 00:00:00 GMT. The abstract will appear in the subsequent mailing as displayed below, except that the submission identifier will be replaced by the official arXiv identifier. Updates before Tue, 13 Aug 2024 18:00:00 GMT will not delay announcement.

If you have a problem that you are not able to resolve through the web interface, contact [email protected] with a description of the issue and reference the submission identifier.

arXiv admin

---

\ arXiv:submit/5787844 From: Florian Goth [email protected] Date: Sun, 19 Nov 2023 23:44:57 GMT (65kb,D) Date (revised v2): Fri, 12 Apr 2024 17:05:31 GMT (115kb,D) Date (revised v3): Mon, 12 Aug 2024 14:54:07 EST (136kb,D)

Title: Foundational Competencies and Responsibilities of a Research Software Engineer Authors: Florian Goth, Renato Alves, Matthias Braun, Leyla Jael Castro, Gerasimos Chourdakis, Simon Christ, Jeremy Cohen, Stephan Druskat, Fredo Erxleben, Jean-No"el Grad, Magnus Hagdorn, Toby Hodges, Guido Juckeland, Dominic Kempf, Anna-Lena Lamprecht, Jan Linxweiler, Frank L"offler, Michele Martone, Moritz Schwarzmeier, Heidi Seibold, Jan Philipp Thiele, Harald von Waldow, Samantha Wittke Categories: cs.SE cs.CY physics.comp-ph Comments: 34 pages, public repository for feedback here: https://github.com/the-teachingRSE-project/competencies License: http://creativecommons.org/licenses/by/4.0/ \ The term Research Software Engineer, or RSE, emerged a little over 10 years ago as a way to represent individuals working in the research community but focusing on software development. The term has been widely adopted and there are a number of high-level definitions of what an RSE is. However, the roles of RSEs vary depending on the institutional context they work in. At one end of the spectrum, RSE roles may look similar to a traditional research role. At the other extreme, they resemble that of a software engineer in industry. Most RSE roles inhabit the space between these two extremes. Therefore, providing a straightforward, comprehensive definition of what an RSE does and what experience, skills and competencies are required to become one is challenging. In this community paper we define the broad notion of what an RSE is, explore the different types of work they undertake, and define a list of fundamental competencies as well as values that define the general profile of an RSE. On this basis, we elaborate on the progression of these skills along different dimensions, looking at specific types of RSE roles, proposing recommendations for organisations, and giving examples of future specialisations. An appendix details how existing curricula fit into this framework. \