Software Source Code – policy and incentives
-
Discussion
-
Collaborative session notes: https://docs.google.com/document/d/1hMjbd_FLbs_7Gz_hTZJEjsgzZTCutBk4KQ9g…Short introduction to the group and its aims
Update on FAIR4RS current status
Update Publisher Code Availability Policy group
Software in the Second French Plan for Open Science
National Agenda for Research Software at the ARDC
Software policy landscape
Group activity – incentives
Conclusions and next steps
Additional links to informative material
For further information, see:
Software Source Code Interest Group Charter
Software Source Code IG Wiki
Avoid conflict with the following group (1)
FAIR for Virtual Research Environments WGBrief introduction describing the activities and scope of the group
The Software Source Code IG was founded in 2017, after a BoF session at the 9th Plenary. It aims to discuss issues on identification, management, sharing, discovery, archival and provenance of software source code, review and revise metadata for describing and discovering source code, develop guidelines for managing, describing and publishing software source code, collect and publish use cases of current examples and practices, and contribute software related expertise to other groups in the RDA which have a software aspect.
During the P12 SSC IG session, a discussion to create a Working Group dedicated to software source code identification led to the creation of the Software Source Code Identification Working Group [SCID WG] which is a joint RDA and FORCE11 WG. This working group has completed its life-cycle with the supporting output:
“Use cases and identifiers schemes for software source code identification” [1].
At RDA plenary (VP15) we discussed the FAIR principles and started the process of creating a new working group, which was launched at the end of June 2020, the FAIR for research software working group [FAIR4RS WG]. The FAIR4RS WG is a joint initiative with ReSA and FORCE11.
At VP16 we have presented the SCID WG output and other outputs and activities from different RDA and FORCE11 working groups that discuss software. We have also collected software practices in the academic community.
At VP17 we have presented the EOSC SIRS TF [2] and other outputs and activities from different RDA and FORCE11 working groups that discuss software. We have also conducted a mini-workshop about software quality.
At VP18 we had a session about reproducibility, GUIX and the usage of GUIX in a computational center (GRICAD).
References
[1] Research Data Alliance/FORCE11 Software Source Code Identification WG, Allen, A., Bandrowski, A., Chan, P., Di Cosmo, R., Fenner, M., Garcia, L., Gruenpeter, M., Jones, C. M., Katz, D. S., Kunze, J., Schubotz, M. & Todorov, I. T. (2020). Use cases and identifier schemes for persistent software source code identification (V1.1). Research Data Alliance. https://doi.org/10.15497/RDA00053
[2] European Commission. Directorate General for Research and Innovation. (2020). Scholarly infrastructures for research software: report from the EOSC Executive Board Working Group (WG) Architecture Task Force (TF) SIRS. Publications Office. https://doi.org/10.2777/28598
[3] Second National Plan for Open Science. (2021). Ministry of Research, Higher Education and Innovation, France. Official version in french and english.Group chair serving as contact person
Morane GruenpeterMeeting objectives
This meeting is an opportunity for RDA members, who are interested in software and in particular in software source code, to discuss different aspects of software in the research lifecycle and in particular the importance of making software reproducible. At P20 our main topics are:International and national policies regarding software source code.
Initiatives supporting research software policies
Funders policies
Privacy Policy
1
Log in to reply.