-
Notifications
You must be signed in to change notification settings - Fork 96
March Newsletter #1690
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
Merged
Merged
March Newsletter #1690
Changes from 12 commits
Commits
Show all changes
24 commits
Select commit
Hold shift + click to select a range
ba5e9bc
March Newsletter
TinasheMTapera b309235
Update _posts/2025-03-28-katz-community-travel-funds-report.md
danielskatz 743ecc5
Update _posts/newsletters/2025-03-28-newsletter.md
danielskatz d4938f1
Update _posts/newsletters/2025-03-28-newsletter.md
danielskatz 72a3a8b
Update _posts/newsletters/2025-03-28-newsletter.md
danielskatz 6e8ffe4
Update _posts/newsletters/2025-03-28-newsletter.md
danielskatz 21e5a38
Update _posts/2025-03-28-katz-community-travel-funds-report.md
danielskatz 08f5b92
Update _posts/2025-03-28-katz-community-travel-funds-report.md
danielskatz 3264d1a
Update _posts/2025-03-28-katz-community-travel-funds-report.md
danielskatz 9496091
Update _posts/2025-03-28-katz-community-travel-funds-report.md
danielskatz 67f1017
Update _posts/2025-03-28-katz-community-travel-funds-report.md
danielskatz 36fb005
Update _posts/newsletters/2025-03-28-newsletter.md
danielskatz 01fa8c3
Update _posts/2025-03-28-katz-community-travel-funds-report.md
danielskatz 1e3737b
Update _posts/2025-03-28-katz-community-travel-funds-report.md
danielskatz 4cc19a2
Addresses @sandragesing's content feedback, adds events leading up fr…
TinasheMTapera e850618
Fixes mislabelled headings
TinasheMTapera 328cd72
aesthetic improvements
TinasheMTapera c3feaf6
Adds the unicorn fundraiser, escience conference, and emojis
TinasheMTapera cfd3812
adds link to unicorn drive
TinasheMTapera 21b0c66
Fix order
TinasheMTapera f5cc4ed
Remove empowerment post
TinasheMTapera 36c13ae
Add @sandragesing 's photos from DC and format photo wrapping
TinasheMTapera d6a7d06
typo
TinasheMTapera 207e742
Fix image alignments
TinasheMTapera File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,35 @@ | ||
--- | ||
layout: post | ||
title: "Daniel Katz' Community and Travel Funds Report: deRSE25" | ||
tags: [community-awards, usrse, conference, travel-fund, talk, poster] | ||
author: Tinashe Michael Tapera | ||
--- | ||
|
||
I'm thankful to have been partially supported by US-RSE's Community and Travel Funds program, using a grant from the Alfred P Sloan foundation, to attend the [2025 German RSE Conference (deRSE25)](https://events.hifis.net/e/derse25), which was co-located with the 2025 German Software Engineering Conference (SE25). While at the conference in Karlsruhe, Germany, I presented one talk and one poster. | ||
|
||
Talk title: _Katz, D. S., Clifford, B., Hunter Kesling, K., Chard, K., & Babuji, Y. (2025, February 25). **Research Software Phases, Sustainability, and RSEs.** 5th conference for Research Software Engineering in Germany (deRSE25), Karlsruhe, Germany. Zenodo. <https://doi.org/10.5281/zenodo.14922563> | ||
|
||
> Research software projects often are initially funded by a grant that supports development of the software. But when the grant ends, the projects have to shift to another model to support the required software maintenance, if the software is going to continue being used. This talk will look at the Parsl project and its effort to become sustainable, across a set of project phases. It will also look at the different kinds of RSE work that have taken place during the project. These activities, phases, and developer types appear to be useful concepts for planning or studying other research software projects, or research software as a whole. The talk will be partly aimed at finding others who want to collaborate on understanding how general these results are, and how much they can benefit other projects. | ||
|
||
After the talk, a few people came up to me to say that they had similar experiences, and we started discussing a collaborative paper to look at three such projects. | ||
|
||
The poster, which was also presented at US-RSE'24 in Albuquerque, was: _Yehudi, Y., Cashman, M., Felderer, M., Goedicke, M., Hasselbring, W., Katz, D. S., Löffler, F., Müller, S., & Rumpe, B. (2025). **Towards Defining Lifecycles and Categories of Research Software.** deRSE25 Conference, Karlsruhe. Zenodo. <https://doi.org/10.5281/zenodo.15002661> | ||
danielskatz marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
> Research software comes in many forms at various stages of development. Traditional software engineering models often fall short in meeting the unique needs of Research Software Engineering (RSE) projects, confusing users, developers, funders, and stakeholders. | ||
A collaborative effort between software engineering researchers (SERs) and RSEs at a Dagstuhl seminar aimed to address this issue. The group found discrepancies in terminology and definitions, such as varying views on the stage of a software project. | ||
Through their work, they explored concepts like software maturity, intended audience, and future use. This poster presents a working categorization of research software types and an abstract software lifecycle model that can be customized for different projects. The goal is to guide decisions and development standards tailored to each stage and team. | ||
Community input is sought to improve these tools in future iterations. | ||
|
||
There was a lot of good discussion about the poster, and I captured the contributions of others as sticky notes, as seen below. The group of authors is now considering writing a paper based on this to a call open to deRSE25 attendees to expand their presentations into papers. | ||
{:style="display: block; margin: auto; max-width: 600px;" } | ||
|
||
In addition to presenting, I also enjoyed attending. I was also at deRSE last year, so I've gotten to know a number of people in the German RSE community, and it was nice to meet them again and to be able to find out about their recent work. | ||
|
||
A few other random thoughts: | ||
|
||
* I was surprised by the number of talks that had slides decorated with generative AI images. In some cases, the images were helpful in illustrating the ideas, but in many, they were just visual noise that, for me, took away from the actual content of the talk. | ||
* I felt like there were a lot of quite different views of what RSEs are, how they work, how they fit into an organization, and how they work with one or more projects. I guess this isn't much different than the US, though I did feel like there might have been some systematic difference between the experience of RSEs in the two countries, but not in a way I can easily describe. | ||
* Having the RSE and SE meetings co-located, with some common events and common breaks, was useful, and I am envious that this happens in Germany. I wonder if we could get a subset of the US SE community to work more closely with US-RSE, or at least to talk more together? | ||
|
||
Again, I really appreciate the support from US-RSE that enabled me to attend this meeting! | ||
|
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.