#3 Reproducing statistical results · injunctive
“Terms of use and licensing. Ideally code and data default to open; that is, they are published under a permissive reuse license” (p. 11); and “I suggest that scholarly objects be made openly available using the Reproducible Research Standard… which recommends attribution-only open licensing for code, data, and the research article” (p. 13)
#14 An empirical analysis of journal policy effectiveness for computational reproducibility · injunctive
“Any restrictions on the availability of data, codes, or materials, including fees and original data obtained from other sources… must be disclosed to the editors upon submission” (p.2584)
#19 The ReproRubric: evaluation criteria for the reproducibility of computational analyses · injunctive
Materials and/or code is licensed using an approved license
#20 Successes and struggles with computational reproducibility: lessons from the fragile families challenge · injunctive
“The code should be released under the MIT license, but we will consider other permissive licenses in special situations” (footnote 12, p.6)
#32 Beyond open data: a model for linking digital artifacts to enable reproducibility of scientific claims · injunctive
“The preceding discussion is predicated on the author having the ability and legal rights to share data and code associated with claims” (p. 11)
#34 Reproducibility and replicability in economics · injunctive
“Some widely used data sets are accessible by any researcher, but the license they are subject to prevents their redistribution and thus their inclusion as part of data deposits.” (p. 15)
#35 Trust, but verify: an investigation of methods of verification and dissemination of computational research artifacts for transparency and reproducibility · injunctive
“License and copyright information should be provided for all elements of the package. Although not strictly required for reproducibility assessment, license and copyright are important for future reusability” (p.170)
#38 Ten simple rules for writing dockerfiles for reproducible data science · injunctive
“Regarding licensing information, this should include the license of your own code and could point to a LICENSE file within the image” (p. 11-12)
#39 How to make a pie: reproducible research for empirical economics and econometrics · injunctive
“the choice of the versioning tool should satisfy the data terms of use” (p. 1147)
#45 Toward reusable science with readable code and reproducibility · injunctive
“Our form features both data and code license fields as different types of licenses apply to these resources. The absence of one of the two licenses in a replication package with data and code may create legal uncertainty. Though the licenses should be open to allow reuse, no license within the published material means that all copyright laws apply and that the author retains all rights to data or code. To create a platform that facilitates reusable research, licenses for both types of resources needed to be incorporated.” (p. 4)
Note: only check presence of the license file, not the content
#48 Challenges of curating for reproducible and FAIR research output · injunctive
“Inability to access data when conditions of use are unclear” (p.20) and “Unclear usage license” (p.21)
#51 A reproducible data analysis workflow with R Markdown, Git, Make, and Docker · injunctive
“to ensure that other users are legally able to benefit from the shared materials, authors must choose an appropriate license” (p.23)
#52 CODECHECK: an open science initiative for the independent execution of computations underlying research articles during peer review to improve reproducibility · injunctive
“Unless there are strong reasons to the contrary (e.g., sensitive data on human subjects), all code and data… will be made freely available when the certificate is published.” (Core Principle 5, p. 7)
#54 WORCS: a workflow for open reproducible code in science · injunctive
“we recommend users to specify an appropriate license for their projects… suggests a CC-BY 4.0 license by default” (p. 44)
#55 Computational reproducibility: a practical framework for data curators · injunctive
“It is important to specify how others are permitted to use, modify, and distribute your work” (p.8)
#56 Reproducibility badging and definitions · injunctive
“made available via standard open licenses that maximize artifact availability” (p.3)
#57 Principles for data analysis workflows · injunctive
an appropriate license should be assigned to the data set prior to publication (p.18); “appropriate licensing relevant to the Explore phase are also a necessity for open-source software” (p.21)
#59 Understanding experiments and research practices for reproducibility: an exploratory study · descriptive
“Survey participants rated software license as very important/absolutely essential (37%)” (p.13)
#62 Containerization for creating reusable model code · injunctive
“Before releasing or publishing a container, it is vital to confirm that it complies with the appropriate licenses and permissions” (~p.5)
#66 Reproducible research publication workflow: a canonical workflow framework and FAIR digital object approach to quality research output · tacit
Curator “Checks license” (Fig. 2, p.308–309)
#67 Tools and recommendations for reproducible teaching · injunctive
“It is essential that all work shared openly is released with a license that makes it clear how others can reproduce and reuse the material” (p. 253); “you should release your materials with a license” (p. 257)
#69 The interdependence of data producers and data users: how researchers’ behaviors can support or hinder each other · injunctive
“Specify appropriate uses of the data source (e.g., via a data license describing terms of use)… Provide a data use agreement (e.g., license) describing the data and its terms of use” (Table 2, p.23)
#70 The Stark realities of reproducible statistically orientated sociological research: Some newer rules of the sociological method · injunctive
“Stark states that your code should also state how it is licenced.” (p.211)
#77 Report of the AEA data editor · injunctive
“…documented permission to redistribute [publish] the data” (p.857) and “The default license for all repositories based at openICPSR is the Creative Commons Attribution (CC-BY)… All licenses are vetted by the data editor for compliance with the DCAP” (p.856)
#83 Reproducibility and transparency versus privacy and confidentiality: Reflections from a data editor · injunctive
“…access to the data and code is clearly and precisely documented and is non-exclusive to the authors.” (slide “Key elements”) and “An open license is required by the AEA, in order to allow others to re-use the data and code.” (slide “Tools and Guidance” — Depositing Data section)
#93 Unintended code errors and computational reproducibility · injunctive
“Information about license and rights to the files is present” (Appendix A, DOCUMENTATION, p.8)
#99 Introducing reproducible research standards at the world bank · injunctive
“a license file” (p.4); “Reproducibility packages are published under the MIT license or the 3-Clause BSD3 license, which were approved internally” (p.8
#108 Checklists for computational reproducibility in social sciences: insights from literature and survey evaluation · injunctive
“A license must be added to the repository. The commonly used open licenses on GitHub are MIT, Apache 2.0, and CC By 4.0” (Checklist 3)
#120 Reproducibility spectrum for applied social sciences: conceptual taxonomy and recommended tools · tacit
“Specify licensing (CC BY, CC0)” listed under Practices × Data
#139 PRIMAD-LID: a developed framework for computational reproducibility · injunctive
“Additional aspects, such as resource details, functionality, human roles, licensing, and metadata” (p. 14) and Akhlaghi et al.’s eight criteria for longevity include “free/open-source software (FOSS)” (p. 13)