[Morane Gruenpeter]

Dear FAIR4RS WG,
A few weeks ago I have shared subgroup3 summary report for feedback, during
the WG review we have decided to capture the controversy about defining
Research Software without actually defining it, since it seemed impossible.
With some reflection and discussions in the subgroup3 gitter channel, we
have agreed on the following text for the Research Software definition:
*”Research Software includes source code files, algorithms, scripts,
computational workflows and executables that were created during the
research process or for a research purpose. Software components (e.g.,
operating systems, libraries, dependencies, packages, scripts, etc.) that
are used for research but were not created during or specifically for
research should be considered software in research and not Research
Software. This differentiation may vary between disciplines. The minimal
requirement for achieving computational reproducibility is that all the
computational components (Research Software, software used in research, and
hardware) used during the research are identified, described, and made
accessible to the extent that is possible.”*
Please let us know in this mail thread or on the summary report document if
you have comments or improvements suggestions.
The definition in the document is version 4 on page 17 in the last section:
https://docs.google.com/document/d/139vi8KCz2h0KyYfhN46SR7bEuJ3nggYgb1ka…
Kind regards,
—
Morane Ottilia GRUENPETER
Software engineer and metadata specialist
Software Heritage http://www.softwareheritage.org
@INRIA Paris
personal website: http://moranegg.github.io/

Discussion