Photo by Nick Fewings on Unsplash.

Authors

  • Daniel S. Katz (co-founder, US-RSE and co-founder, International Council)
  • Simon Hettrick (co-founder UK RSE and Society of RSE)
  • Stephan Druskat (co-founder, de-RSE and co-founder, International Council)
  • Ian Cosden (co-founder, US-RSE and co-founder, International Council)
  • Anna-Lena Lamprecht (council member for NL-RSE and later de-RSE)

In the beginning, there was the Software Sustainability Institute (SSI), which encouraged and helped found the creation of the UK Research Software Engineers Association in 2013-2014, and later a grant for the RSE Network provided, amongst other things, the funding for an annual conference which began in 2016. International attendees at the conference and the later ones started their own RSE organizations, and the UK RSE Association became a Society.

In 2017-2018, the SSI began work to make RSE sustainable by ensuring that the RSE community could exist entirely independently of it. Up to 2020, new national RSE organisations were supported informally with the SSI acting as the repository of knowledge on how to set up and run a national organisation. In 2020, members of several national RSE associations and initiatives organized the 2nd International RSE Leaders Meeting. A breakout group at this meeting, led by Ian A. Cosden (then-Chair, US-RSE) and Paul Richmond (then-President, Society for RSE), began to discuss the need for a venue for RSE organizations to talk to each other 1) to avoid conflicts with dates, 2) to coordinate about joint activities, 3) support each other and fairly resolve conflicts, and 4) to encourage other RSE communities to form.

Together, the group drafted the first version of a charter for an International Council of RSE Associations, which was subsequently discussed and refined by meeting participants. See https://researchsoftware.org/2021/01/27/introducing-the-international-council-of-RSE-associations.html.

The council started in 2021 with two members from each organization (see https://github.com/rse-council/researchsoftware.org/commit/7116d29e5bf6d48e87e3cfc438b96ba0b626e67b for the original members), who have changed often, and a charter, which has been unchanged. As an example of cooperative, multinational RSE advocacy the council decided to declare the second Thursday in October each year as International RSE Day. The first International RSE Day was celebrated on 14 October 2021.

Initially, the council didn’t have any schedule of regular meetings or leader/chair. It used a rotating model, where in each meeting, a leader would be chosen for the next meeting who would be responsible for picking a date (often via a poll of other members), setting up a virtual meeting channel (e.g., zoom), determining an agenda, and then hosting the meeting.

This process worked for a while, but started to break down especially as founding members rotated off and new members rotated in, as it was dependent on the selected leader from each meeting ensuring that a new leader was selected for the next meeting, and that leader doing what they said they would do.

In 2024, The Research Software Alliance (ReSA) volunteered to act as the secretariat for the council, via an email from Michelle Barker, ReSA director, to Simon Hetrick, who also wanted to ensure that the council was working. Anna-Lena Lamprecht, who was a de-RSE delegate to the council, brought this to the council, and reported back to ReSA: “Not surprisingly, there was broad consensus for accepting the fantastic offer by ReSA!”

When ReSA offered to help the Council by providing the secretariat, members at the time wanted the meetings to continue to be informal, mostly ad-hoc chats, with the occasional talk from a member, so things have continued in this vein, as of late 2026.

As Secretariat, ReSA provides support to help the meetings happen, and the communications around that. In doing that, ReSA has at times filled some gaps to keep things moving, like accepting member suggestions on what to discuss at the next meeting (because there is no mechanism for a Council member/s to do this).

The Council remains responsible for its own agenda, decision making, coordination, etc. All leadership regarding the aims and scope of the Council, and content and format of the meetings, remains the responsibility of the Council.