Call for Submissions: deRSE25 Post-Conference Proceedings
In the series of german deRSE conferences, we are again planning to compile and publish a post-conference proceedings volume to capture the wealth of knowledge and experiences presented during the event.
Submission Guidelines:
All contributors to the deRSE25 conference are invited to submit a journal-length version of their conference contribution for inclusion in this special proceedings volume. The extended submissions should provide a more in-depth exploration of the presented contributions, offering additional details and insights. We explicitly encourage contributors of similar topics to consider teaming up for joint papers, to leverage synergies and impact.
Review Process:
All submissions will undergo a rigorous peer-review process. The reviewers will evaluate the submissions based on their relevance, significance, technical soundness and quality of presentation. Feedback from the reviewers will be provided to authors to facilitate improvements and enhance the final publication. Please note that we expect all authors to be willing to contribute to the reviewing process, that is, we might ask you to review other submissions in your area of expertise.
Publication Venue:
Accepted submissions will be published in the diamond open-access journal ECEASST (Electronic Communications of the European Association for Software Science and Technology). There will be no cost to the authors for the publication of their work.
Important Dates:
- Submissions: until 18th May 2025
- Review Period: until 14th July 2025
- Notification of Acceptance: until 31st July 2025
- Finalisation of possible second review round ~September 2025
- Final publication of Journal: End of 2025
Submission Instructions:
Submissions must be prepared using the ECEASST template. There is no strict page limit, but please consult with the volume editors if your submission is shorter than six or longer than 25 pages.
To be considered for the volume, submissions must be uploaded through the ECEASST system by the submission deadline (see “Important Dates”).
Volume Editors
For inquiries and additional information, please contact the proceedings editors
at derse25-postproceedings@listserv.dfn.de.
The volume editors are:
- Florian Goth (florian.goth@uni-wuerzburg.de)
- René Caspart (rene.caspart@kit.edu)
- Oliver Karras (oliver.Karras@tib.eu)
- Jan Linxweiler (j.linxweiler@tu-braunschweig.de)
- Florian Thiery (florian.thiery@leiza.de)
- Joachim Wuttke (j.wuttke@fz-juelich.de)
Questions and Answers
Who can submit?
Any author with an accepted contribution at deRSE25 is eligible to submit.
Just to clarify: A poster is also eligible?
Yes. All accepted contributions — including posters, demos, workshops, and hackathons — are invited, as long as they provide scientific value for the RSE community.
Can I change the list of authors?
Yes, you may update the author list. However, please ensure that the presenting authors are included in the proceedings submission.
Should the title of the paper be the same as the title of the talk?
Not necessarily. While the topics should align, the titles can differ. You may also combine multiple deRSE25 contributions into a single paper if they share a common theme.
Can we combine contributions from previous years with ones from this year's conference?
Yes, as long as the earlier material has not been published before.
Can we contribute some kind of "success story" paper about the RSE work carried out on the software portfolio we work on, or RSE community building efforts? Possibly using a completed or ongoing RSE grant as the starting point for the manuscript, e.g. a milestone report.
Yes, provided that you include evaluation data or other evidence of impact. The paper should contribute to the RSE field and not merely be a grant report.
Can I publish a paper about my software?
In general, yes. However, for software papers, we encourage submissions to JOSS (Journal of Open Source Software). Publishing in ECEASST might limit your ability to later submit the same software to JOSS or similar venues. If your paper focuses more on results, methodology, or novel ideas related to the software, ECEASST could be a suitable choice.
Why the journal ECEASST was chosen?
For several reasons. It operates under a Diamond Open Access model, meaning there are no fees for authors. Additionally, it is well-recognized in the academic community, being indexed in major databases such as Scopus and DBLP. ECEASST is hosted by Berlin Universities Publishing, which is bound to maintain its open-access status. The deRSE24 post-conference proceedings have already been published by ECEASST. Finally, the journal also has a direct connection to the conference through Anna-Lena Lamprecht, one of the PC members, who is actively involved in its editorial work.
When will a template be released?
The template is alread available here. It is provided in LaTeX format but can be converted to Word if necessary. Submissions must be uploaded as PDFs.
How does the review process look like?
Each paper will undergo three reviews: At least one review by a "senior" RSE or RSE researcher. One or two reviews by peers with expertise in a similar domain (contributors of other papers).
Is it a rejection/acceptance or a major revision?
In addition to acceptance and rejection, papers may be requested to undergo minor or major revisions. After acceptance, a copyediting phase will follow, which might involve additional edits.
How long should the paper be?
Papers should be between 6 and 25 pages. If you require more space, please contact the editors in advance.
How should I report issues with the journal, template, or submission process?
Please send any issues via email to derse25-postproceedings@listserv.dfn.de
Notes for reviewers:
- You will have 1 week to accept the review
- You have three weeks to perform the review
- the review asks a set of guided questions. So it is advised, to look into the review template before going through the paper.
- Use of AI systems: Remember, the contributions of authors are still their intellectual property. Ask yourself, if your intended use of an AI system for your review could violate these rights. (also see DFG)
