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 VP18 our main topics are:
Reproducibility and Guix
Guix used in a computational center
Collaborative session notes: https://docs.google.com/document/d/1_R_ylzBI2ixC6YD_q35obiTAiaypeJ8DhT081UlCKZw/edit?usp=sharing
The agenda will be roughly as follow:
Short introduction to the Software Souorce Code Interest Group and its aims (5 minutes)
Updates from the community (10 minutes)
Reproducibility and Guix (45 minutes)
Activity - collecting tools and use cases (20 minutes)
Conclusion of group activity (10 minutes)
The target audience for this session comprises: repository managers, software project owners, software catalog maintainers, software source code researchers, software preservation and archival experts, and others with an interest in the discovery, description and preservation of software source code. This session will be particularly of interest to those who have implemented, or are thinking or implementing, techniques using package management systems, virtual environments or containers to facilitate reproducibility.
Participants should familiarise themselves with current efforts in preserving source code (such as Software Heritage), describing software (e.g. CodeMeta) and citing software (the FORCE11 Software Citation Principles). Participants may also wish to read the overview for GNU Guix, to get an idea of its features, but these will be described in the session.
Other optional reading material of potential interest:
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” .
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 the last plenary (VP17) we have presented the EOSC SIRS TF  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.
 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
 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
Ongoing Interest Group open to discussion about software source code in different domains and for different use cases.
- 680 reads