[Michelle Barker]

The Policies in Research Organisations for Research Software (PRO4RS) Working Group (WG) is establishing a project to collate resources on how to support policy change in research institutions in practice. Everyone is welcome to get involved.
 
We seek contributions from organisations and individuals around the world who are experienced in implementing policy changes in research culture, and/or an interest in learning about this area. We will establish a knowledge base for organisations seeking to implement similar changes. The leads for this project are Jeremy Cohen (Imperial College London), Dan Rudmann (Leiden University), and Michelle Barker (Research Software Alliance).
 
There are two ways to contribute to this project:
 
1. Contribute materials to the project’s list of resources (e.g. papers, workshops, case studies, talks etc) by 29 Feb 2024, and be acknowledged in the project output for your contribution. Examples of the types of materials that this project will collect include:

How to Introduce and Implement Policy in Your Institution and Still Have Friends After, a FORCE11 2020 Scholarly Communication Institute course by Danny Kingsley and Sarah Shreeves

Want to speed up scientific progress? First understand how science policy works by Matt Clancy, Dan Correa, Jordan Dworkin, Paul Niehaus, Caleb Watney & Heidi Williams, a Nature commentary

Recommendations for the Implementation of Guidelines and Policies on Research Software Management by Helmholtz Open Science Office

2. Join the project group who will curate the materials by emailing Michelle Barker at info@researchsoft.org by 29 Feb 2024. The project will aim to curate resources throughout March, and write-up the outcomes in April. The benefits of involvement in this activity include an opportunity to share expertise and/or learn about best practices internationally. Members of the group will be able to choose how much time to commit to this, ranging from a few hours to give inputs into group discussions, or 10-15  hours curating resources and writing up the final output. All members will be acknowledged in the final project output.

 

Discussion