Some journals offer to publish your article under a Creative Commons license, but still demand an exclusive publishing and distribution license or a copyright assignment from you. This would give them more rights than the readers of the article have through the respective Creative Commons license (Rumsey & Labastida, 2022) and exceeds by far what is necessary to make publication possible (Suber, 2022). Consequently, authors should oppose this practice and grant publishers the same rights that every other reader of the article has. If your chosen publisher insists on an exclusive license, you may at least retain the copyright for your figures – follow the guide “Retaining copyright for figures in academic publications to allow easy citation and reuse” by Elson (2016) to learn how to do that.
-If you have published a closed-access paper before, you can consult ShareYourPaper for legal options to still make it available free of charge to readers.
+Some journals offer to publish your article under a Creative Commons license, but still demand an exclusive publishing and distribution license or a copyright assignment from you. This would give them more rights than the readers of the article have through the respective Creative Commons license (Rumsey & Labastida, 2022) and exceeds by far what is necessary to make publication possible (Suber, 2022). Consequently, authors should oppose this practice and grant publishers the same rights that every other reader of the article has. To facilitate self-archiving, one can also modify the contract with publishers via a rights retention statement (UK Reproducibility Network & Eglen, 2023) / author’s addendum (SPARC, 2006). If you have published a closed-access paper before, you can consult ShareYourPaper for legal options to still make it available free of charge to readers.
+If your chosen publisher insists on an exclusive license, you may at least retain the copyright for your figures – follow the guide “Retaining copyright for figures in academic publications to allow easy citation and reuse” by Elson (2016) to learn how to do that.
The licenses we discuss here mostly regard copyright. Therefore, recipients may lack other rights such as publicity, privacy, moral, patent,2 or trademark rights. For example, sharing photos that depict people is not only a matter of copyright, but also of privacy rights. Conversely, the licenses do not apply if recipients are allowed to use the works for other reasons such as fair use, the right to quote, or because they made a different arrangement with the author.
@@ -556,7 +556,7 @@You may have noticed that we mostly refer to licenses using a name and a version number. This is because the organizations that created the licenses sometimes publish updated versions to accommodate for developments in copyright law and the communities that use the licenses. For example, the Creative Commons licenses (that start with CC) were first published in 2002. Since then, the possibility to relicense under later (v2.0) and compatible licenses (v3.0) has been added, a 30-day window to correct license violations has been established to combat copyleft trolls, and sui generis database rights are covered explicitly (v4.0). There are many more subtle differences between license versions, therefore it is important to indicate which license version exactly one is referring to, as the license of a work does not “update” automatically.
You may have noticed that we mostly refer to licenses using a name and a version number. This is because the organizations that created the licenses sometimes publish updated versions to accommodate for developments in copyright law and the communities that use the licenses. For example, the Creative Commons licenses (that start with CC) were first published in 2002. Since then, the possibility to relicense under later (v2.0, 2004) and compatible licenses (v3.0, 2007) has been added, a 30-day window to correct license violations has been established to combat copyleft trolls, and sui generis database rights are covered explicitly (v4.0, 2013). There are many more subtle differences between license versions, therefore it is important to indicate which license version exactly one is referring to, as the license of a work does not “update” automatically. CC0, officially introduced in 2009, is still at version 1.0.
For the AGPLv3 it is even recommended to state whether a work is licensed under exactly the indicated version of the license or, alternatively, also under newer versions of the license (Stallman, 2022a).
Suppose you are reading an article about a new imaging method to turn seismological data into subsurface images. The article describes the ideas that went into developing this method and presents a few examples to illustrate its superiority over previous approaches. You got interested and would like to apply this method to your own data. However, with only the article available, it could take months to come up with a working solution, if possible at all. This situation has been put aptly by Buckheit & Donoho (1995, p. 59), distilling an idea by the geophysicist Jon Claerbout:
-“An article about computational science in a scientific publication is not the scholarship itself, it is merely advertising of the scholarship. The actual scholarship is the complete software development environment and the complete set of instructions which generated the figures.”
+“An article about computational science in a scientific publication is not the scholarship itself, it is merely advertising of the scholarship. The actual scholarship is the complete software development environment and the complete set of instructions which generated the figures.”
Even when researchers merely apply existing methods (rather than report on a new method), sharing the source code and being transparent about the computational environment is imperative to making their results reproducible (Ince et al., 2012). By reproducibility, we mean “obtaining consistent results using the same input data; computational steps, methods, and code; and conditions of analysis” (National Academies of Sciences, Engineering, and Medicine, 2019, p. 46).
diff --git a/search.json b/search.json index c339a69..33eded9 100644 --- a/search.json +++ b/search.json @@ -136,14 +136,14 @@ "href": "about.html", "title": "About", "section": "", - "text": "This work was completed with the following R packages: datawizard v. 0.12.3 (Patil et al., 2022), grateful v. 0.2.4 (Francisco Rodriguez-Sanchez & Connor P. Jackson, 2023), knitr v. 1.48 (Xie, 2014, 2015, 2024), palmerpenguins v. 0.1.1 (Horst et al., 2020), quarto v. 1.4.4 (Allaire & Dervieux, 2024), renv v. 1.0.7 (Ushey & Wickham, 2024), report v. 0.5.9 (Makowski et al., 2023), rmarkdown v. 2.28 (Allaire et al., 2024; Xie et al., 2018, 2020), sessioninfo v. 1.2.2 (Wickham et al., 2021), tidyverse v. 2.0.0 (Wickham et al., 2019), tinylabels v. 0.2.4 (Barth, 2023), tinytable v. 0.4.0 (Arel-Bundock, 2024), withr v. 3.0.1 (Hester et al., 2024).\n\n\nQuarto: 1.6.39\n\nsessioninfo::session_info()\n\n─ Session info ───────────────────────────────────────────────────────────────\n setting value\n version R version 4.4.2 (2024-10-31)\n os Ubuntu 22.04.5 LTS\n system x86_64, linux-gnu\n ui X11\n language (EN)\n collate C.UTF-8\n ctype C.UTF-8\n tz UTC\n date 2024-12-07\n pandoc 3.4 @ /opt/quarto/bin/tools/ (via rmarkdown)\n\n─ Packages ───────────────────────────────────────────────────────────────────\n ! package * version date (UTC) lib source\n P cli 3.6.3 2024-06-21 [?] RSPM (R 4.4.0)\n P digest 0.6.37 2024-08-19 [?] RSPM (R 4.4.0)\n P evaluate 0.24.0 2024-06-10 [?] RSPM (R 4.4.0)\n P fastmap 1.2.0 2024-05-15 [?] RSPM (R 4.4.0)\n P grateful 0.2.4 2023-10-22 [?] RSPM (R 4.4.0)\n P htmltools 0.5.8.1 2024-04-04 [?] RSPM (R 4.4.0)\n P jsonlite 1.8.8 2023-12-04 [?] RSPM (R 4.4.0)\n P knitr 1.48 2024-07-07 [?] RSPM (R 4.4.0)\n P later 1.3.2 2023-12-06 [?] RSPM (R 4.4.0)\n P processx 3.8.4 2024-03-16 [?] RSPM (R 4.4.0)\n P ps 1.7.7 2024-07-02 [?] RSPM (R 4.4.0)\n P quarto 1.4.4 2024-07-20 [?] RSPM (R 4.4.0)\n P Rcpp 1.0.13 2024-07-17 [?] RSPM (R 4.4.0)\n renv 1.0.7 2024-04-11 [1] RSPM (R 4.4.2)\n P rlang 1.1.4 2024-06-04 [?] RSPM (R 4.4.0)\n P rmarkdown 2.28 2024-08-17 [?] RSPM (R 4.4.0)\n P rstudioapi 0.16.0 2024-03-24 [?] RSPM (R 4.4.0)\n P sessioninfo 1.2.2 2021-12-06 [?] RSPM (R 4.4.0)\n P withr 3.0.1 2024-07-31 [?] RSPM (R 4.4.0)\n P xfun 0.47 2024-08-17 [?] RSPM (R 4.4.0)\n P yaml 2.3.10 2024-07-26 [?] RSPM (R 4.4.0)\n\n [1] /home/runner/work/code-publishing/code-publishing/renv/library/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu\n [2] /home/runner/.cache/R/renv/sandbox/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu/db5e602d\n\n P ── Loaded and on-disk path mismatch.\n\n──────────────────────────────────────────────────────────────────────────────" + "text": "This work was completed with the following R packages: datawizard v. 0.12.3 (Patil et al., 2022), grateful v. 0.2.4 (Francisco Rodriguez-Sanchez & Connor P. Jackson, 2023), knitr v. 1.48 (Xie, 2014, 2015, 2024), palmerpenguins v. 0.1.1 (Horst et al., 2020), quarto v. 1.4.4 (Allaire & Dervieux, 2024), renv v. 1.0.7 (Ushey & Wickham, 2024), report v. 0.5.9 (Makowski et al., 2023), rmarkdown v. 2.28 (Allaire et al., 2024; Xie et al., 2018, 2020), sessioninfo v. 1.2.2 (Wickham et al., 2021), tidyverse v. 2.0.0 (Wickham et al., 2019), tinylabels v. 0.2.4 (Barth, 2023), tinytable v. 0.4.0 (Arel-Bundock, 2024), withr v. 3.0.1 (Hester et al., 2024).\n\n\nQuarto: 1.6.39\n\nsessioninfo::session_info()\n\n─ Session info ───────────────────────────────────────────────────────────────\n setting value\n version R version 4.4.2 (2024-10-31)\n os Ubuntu 22.04.5 LTS\n system x86_64, linux-gnu\n ui X11\n language (EN)\n collate C.UTF-8\n ctype C.UTF-8\n tz UTC\n date 2024-12-10\n pandoc 3.4 @ /opt/quarto/bin/tools/ (via rmarkdown)\n\n─ Packages ───────────────────────────────────────────────────────────────────\n ! package * version date (UTC) lib source\n P cli 3.6.3 2024-06-21 [?] RSPM (R 4.4.0)\n P digest 0.6.37 2024-08-19 [?] RSPM (R 4.4.0)\n P evaluate 0.24.0 2024-06-10 [?] RSPM (R 4.4.0)\n P fastmap 1.2.0 2024-05-15 [?] RSPM (R 4.4.0)\n P grateful 0.2.4 2023-10-22 [?] RSPM (R 4.4.0)\n P htmltools 0.5.8.1 2024-04-04 [?] RSPM (R 4.4.0)\n P jsonlite 1.8.8 2023-12-04 [?] RSPM (R 4.4.0)\n P knitr 1.48 2024-07-07 [?] RSPM (R 4.4.0)\n P later 1.3.2 2023-12-06 [?] RSPM (R 4.4.0)\n P processx 3.8.4 2024-03-16 [?] RSPM (R 4.4.0)\n P ps 1.7.7 2024-07-02 [?] RSPM (R 4.4.0)\n P quarto 1.4.4 2024-07-20 [?] RSPM (R 4.4.0)\n P Rcpp 1.0.13 2024-07-17 [?] RSPM (R 4.4.0)\n renv 1.0.7 2024-04-11 [1] RSPM (R 4.4.2)\n P rlang 1.1.4 2024-06-04 [?] RSPM (R 4.4.0)\n P rmarkdown 2.28 2024-08-17 [?] RSPM (R 4.4.0)\n P rstudioapi 0.16.0 2024-03-24 [?] RSPM (R 4.4.0)\n P sessioninfo 1.2.2 2021-12-06 [?] RSPM (R 4.4.0)\n P withr 3.0.1 2024-07-31 [?] RSPM (R 4.4.0)\n P xfun 0.47 2024-08-17 [?] RSPM (R 4.4.0)\n P yaml 2.3.10 2024-07-26 [?] RSPM (R 4.4.0)\n\n [1] /home/runner/work/code-publishing/code-publishing/renv/library/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu\n [2] /home/runner/.cache/R/renv/sandbox/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu/db5e602d\n\n P ── Loaded and on-disk path mismatch.\n\n──────────────────────────────────────────────────────────────────────────────" }, { "objectID": "about.html#utilized-software", "href": "about.html#utilized-software", "title": "About", "section": "", - "text": "This work was completed with the following R packages: datawizard v. 0.12.3 (Patil et al., 2022), grateful v. 0.2.4 (Francisco Rodriguez-Sanchez & Connor P. Jackson, 2023), knitr v. 1.48 (Xie, 2014, 2015, 2024), palmerpenguins v. 0.1.1 (Horst et al., 2020), quarto v. 1.4.4 (Allaire & Dervieux, 2024), renv v. 1.0.7 (Ushey & Wickham, 2024), report v. 0.5.9 (Makowski et al., 2023), rmarkdown v. 2.28 (Allaire et al., 2024; Xie et al., 2018, 2020), sessioninfo v. 1.2.2 (Wickham et al., 2021), tidyverse v. 2.0.0 (Wickham et al., 2019), tinylabels v. 0.2.4 (Barth, 2023), tinytable v. 0.4.0 (Arel-Bundock, 2024), withr v. 3.0.1 (Hester et al., 2024).\n\n\nQuarto: 1.6.39\n\nsessioninfo::session_info()\n\n─ Session info ───────────────────────────────────────────────────────────────\n setting value\n version R version 4.4.2 (2024-10-31)\n os Ubuntu 22.04.5 LTS\n system x86_64, linux-gnu\n ui X11\n language (EN)\n collate C.UTF-8\n ctype C.UTF-8\n tz UTC\n date 2024-12-07\n pandoc 3.4 @ /opt/quarto/bin/tools/ (via rmarkdown)\n\n─ Packages ───────────────────────────────────────────────────────────────────\n ! package * version date (UTC) lib source\n P cli 3.6.3 2024-06-21 [?] RSPM (R 4.4.0)\n P digest 0.6.37 2024-08-19 [?] RSPM (R 4.4.0)\n P evaluate 0.24.0 2024-06-10 [?] RSPM (R 4.4.0)\n P fastmap 1.2.0 2024-05-15 [?] RSPM (R 4.4.0)\n P grateful 0.2.4 2023-10-22 [?] RSPM (R 4.4.0)\n P htmltools 0.5.8.1 2024-04-04 [?] RSPM (R 4.4.0)\n P jsonlite 1.8.8 2023-12-04 [?] RSPM (R 4.4.0)\n P knitr 1.48 2024-07-07 [?] RSPM (R 4.4.0)\n P later 1.3.2 2023-12-06 [?] RSPM (R 4.4.0)\n P processx 3.8.4 2024-03-16 [?] RSPM (R 4.4.0)\n P ps 1.7.7 2024-07-02 [?] RSPM (R 4.4.0)\n P quarto 1.4.4 2024-07-20 [?] RSPM (R 4.4.0)\n P Rcpp 1.0.13 2024-07-17 [?] RSPM (R 4.4.0)\n renv 1.0.7 2024-04-11 [1] RSPM (R 4.4.2)\n P rlang 1.1.4 2024-06-04 [?] RSPM (R 4.4.0)\n P rmarkdown 2.28 2024-08-17 [?] RSPM (R 4.4.0)\n P rstudioapi 0.16.0 2024-03-24 [?] RSPM (R 4.4.0)\n P sessioninfo 1.2.2 2021-12-06 [?] RSPM (R 4.4.0)\n P withr 3.0.1 2024-07-31 [?] RSPM (R 4.4.0)\n P xfun 0.47 2024-08-17 [?] RSPM (R 4.4.0)\n P yaml 2.3.10 2024-07-26 [?] RSPM (R 4.4.0)\n\n [1] /home/runner/work/code-publishing/code-publishing/renv/library/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu\n [2] /home/runner/.cache/R/renv/sandbox/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu/db5e602d\n\n P ── Loaded and on-disk path mismatch.\n\n──────────────────────────────────────────────────────────────────────────────" + "text": "This work was completed with the following R packages: datawizard v. 0.12.3 (Patil et al., 2022), grateful v. 0.2.4 (Francisco Rodriguez-Sanchez & Connor P. Jackson, 2023), knitr v. 1.48 (Xie, 2014, 2015, 2024), palmerpenguins v. 0.1.1 (Horst et al., 2020), quarto v. 1.4.4 (Allaire & Dervieux, 2024), renv v. 1.0.7 (Ushey & Wickham, 2024), report v. 0.5.9 (Makowski et al., 2023), rmarkdown v. 2.28 (Allaire et al., 2024; Xie et al., 2018, 2020), sessioninfo v. 1.2.2 (Wickham et al., 2021), tidyverse v. 2.0.0 (Wickham et al., 2019), tinylabels v. 0.2.4 (Barth, 2023), tinytable v. 0.4.0 (Arel-Bundock, 2024), withr v. 3.0.1 (Hester et al., 2024).\n\n\nQuarto: 1.6.39\n\nsessioninfo::session_info()\n\n─ Session info ───────────────────────────────────────────────────────────────\n setting value\n version R version 4.4.2 (2024-10-31)\n os Ubuntu 22.04.5 LTS\n system x86_64, linux-gnu\n ui X11\n language (EN)\n collate C.UTF-8\n ctype C.UTF-8\n tz UTC\n date 2024-12-10\n pandoc 3.4 @ /opt/quarto/bin/tools/ (via rmarkdown)\n\n─ Packages ───────────────────────────────────────────────────────────────────\n ! package * version date (UTC) lib source\n P cli 3.6.3 2024-06-21 [?] RSPM (R 4.4.0)\n P digest 0.6.37 2024-08-19 [?] RSPM (R 4.4.0)\n P evaluate 0.24.0 2024-06-10 [?] RSPM (R 4.4.0)\n P fastmap 1.2.0 2024-05-15 [?] RSPM (R 4.4.0)\n P grateful 0.2.4 2023-10-22 [?] RSPM (R 4.4.0)\n P htmltools 0.5.8.1 2024-04-04 [?] RSPM (R 4.4.0)\n P jsonlite 1.8.8 2023-12-04 [?] RSPM (R 4.4.0)\n P knitr 1.48 2024-07-07 [?] RSPM (R 4.4.0)\n P later 1.3.2 2023-12-06 [?] RSPM (R 4.4.0)\n P processx 3.8.4 2024-03-16 [?] RSPM (R 4.4.0)\n P ps 1.7.7 2024-07-02 [?] RSPM (R 4.4.0)\n P quarto 1.4.4 2024-07-20 [?] RSPM (R 4.4.0)\n P Rcpp 1.0.13 2024-07-17 [?] RSPM (R 4.4.0)\n renv 1.0.7 2024-04-11 [1] RSPM (R 4.4.2)\n P rlang 1.1.4 2024-06-04 [?] RSPM (R 4.4.0)\n P rmarkdown 2.28 2024-08-17 [?] RSPM (R 4.4.0)\n P rstudioapi 0.16.0 2024-03-24 [?] RSPM (R 4.4.0)\n P sessioninfo 1.2.2 2021-12-06 [?] RSPM (R 4.4.0)\n P withr 3.0.1 2024-07-31 [?] RSPM (R 4.4.0)\n P xfun 0.47 2024-08-17 [?] RSPM (R 4.4.0)\n P yaml 2.3.10 2024-07-26 [?] RSPM (R 4.4.0)\n\n [1] /home/runner/work/code-publishing/code-publishing/renv/library/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu\n [2] /home/runner/.cache/R/renv/sandbox/linux-ubuntu-jammy/R-4.4/x86_64-pc-linux-gnu/db5e602d\n\n P ── Loaded and on-disk path mismatch.\n\n──────────────────────────────────────────────────────────────────────────────" }, { "objectID": "about.html#license-and-disclaimer", @@ -296,7 +296,7 @@ "href": "choose_license.html#a-primer-on-licenses", "title": "Choose a License", "section": "A Primer on Licenses", - "text": "A Primer on Licenses\nWhenever you create a literary or artistic work (such as a text, image, video, or software), the copyright law in most countries limits other people from copying, modifying, and sharing it without your express permission. This even applies if you make it available to others (e.g., on your website): First and foremost they are not allowed to copy, modify, or share it. This legal default of “all rights reserved” was created to benefit publishers, not authors (Fogel, 2006), and runs counter to many cultural and scientific processes. Copyright licenses enable authors to free up their works for reuse by others.If the work was created as part of your job, it might be your employer who holds the copyright to the work, depending on the country and contract.\nA license is a legal document that regulates what others are allowed to do with a copyright-protected work – the licenses we discuss are non-exclusive licenses and do not limit the author or copyright holder in their rights. And while you could write your own license, there are already many pre-formulated licenses available to choose from and to apply to your work.1\n\n\nFor the purpose of this tutorial, by license we mean copyright license.\n\n\n\n\n\n\nWarning 1: Giving Publishers Exclusive Rights\n\n\n\nSome journals offer to publish your article under a Creative Commons license, but still demand an exclusive publishing and distribution license or a copyright assignment from you. This would give them more rights than the readers of the article have through the respective Creative Commons license (Rumsey & Labastida, 2022) and exceeds by far what is necessary to make publication possible (Suber, 2022). Consequently, authors should oppose this practice and grant publishers the same rights that every other reader of the article has. If your chosen publisher insists on an exclusive license, you may at least retain the copyright for your figures – follow the guide “Retaining copyright for figures in academic publications to allow easy citation and reuse” by Elson (2016) to learn how to do that.\nIf you have published a closed-access paper before, you can consult ShareYourPaper for legal options to still make it available free of charge to readers.\n\n\nThe licenses we discuss here mostly regard copyright. Therefore, recipients may lack other rights such as publicity, privacy, moral, patent,2 or trademark rights. For example, sharing photos that depict people is not only a matter of copyright, but also of privacy rights. Conversely, the licenses do not apply if recipients are allowed to use the works for other reasons such as fair use, the right to quote, or because they made a different arrangement with the author.", + "text": "A Primer on Licenses\nWhenever you create a literary or artistic work (such as a text, image, video, or software), the copyright law in most countries limits other people from copying, modifying, and sharing it without your express permission. This even applies if you make it available to others (e.g., on your website): First and foremost they are not allowed to copy, modify, or share it. This legal default of “all rights reserved” was created to benefit publishers, not authors (Fogel, 2006), and runs counter to many cultural and scientific processes. Copyright licenses enable authors to free up their works for reuse by others.If the work was created as part of your job, it might be your employer who holds the copyright to the work, depending on the country and contract.\nA license is a legal document that regulates what others are allowed to do with a copyright-protected work – the licenses we discuss are non-exclusive licenses and do not limit the author or copyright holder in their rights. And while you could write your own license, there are already many pre-formulated licenses available to choose from and to apply to your work.1\n\n\nFor the purpose of this tutorial, by license we mean copyright license.\n\n\n\n\n\n\nWarning 1: Giving Publishers Exclusive Rights\n\n\n\nSome journals offer to publish your article under a Creative Commons license, but still demand an exclusive publishing and distribution license or a copyright assignment from you. This would give them more rights than the readers of the article have through the respective Creative Commons license (Rumsey & Labastida, 2022) and exceeds by far what is necessary to make publication possible (Suber, 2022). Consequently, authors should oppose this practice and grant publishers the same rights that every other reader of the article has. To facilitate self-archiving, one can also modify the contract with publishers via a rights retention statement (UK Reproducibility Network & Eglen, 2023) / author’s addendum (SPARC, 2006). If you have published a closed-access paper before, you can consult ShareYourPaper for legal options to still make it available free of charge to readers.\nIf your chosen publisher insists on an exclusive license, you may at least retain the copyright for your figures – follow the guide “Retaining copyright for figures in academic publications to allow easy citation and reuse” by Elson (2016) to learn how to do that.\n\n\nThe licenses we discuss here mostly regard copyright. Therefore, recipients may lack other rights such as publicity, privacy, moral, patent,2 or trademark rights. For example, sharing photos that depict people is not only a matter of copyright, but also of privacy rights. Conversely, the licenses do not apply if recipients are allowed to use the works for other reasons such as fair use, the right to quote, or because they made a different arrangement with the author.", "crumbs": [ "Home", "Choose a License" @@ -329,7 +329,7 @@ "href": "choose_license.html#applying-the-license", "title": "Choose a License", "section": "Applying the License", - "text": "Applying the License\nHaving selected the licenses of your choice – again, you might need multiple ones depending on the types of works your project contains –, we encourage you to read through the full license text (or at least a legal summary) to understand their effect. Then, you can record the license of existing content and apply the licenses of your own contributions. Mostly, this just means indicating which file or folder is covered by which license, usually in the project’s README (among other places), whose creation will be discussed later. Notably, no sort of registration is required.\n\n\n\n\n\n\nCaution 1: License Versions Are Important\n\n\n\nYou may have noticed that we mostly refer to licenses using a name and a version number. This is because the organizations that created the licenses sometimes publish updated versions to accommodate for developments in copyright law and the communities that use the licenses. For example, the Creative Commons licenses (that start with CC) were first published in 2002. Since then, the possibility to relicense under later (v2.0) and compatible licenses (v3.0) has been added, a 30-day window to correct license violations has been established to combat copyleft trolls, and sui generis database rights are covered explicitly (v4.0). There are many more subtle differences between license versions, therefore it is important to indicate which license version exactly one is referring to, as the license of a work does not “update” automatically.\nFor the AGPLv3 it is even recommended to state whether a work is licensed under exactly the indicated version of the license or, alternatively, also under newer versions of the license (Stallman, 2022a).\n\n\nFor example, the apaquarto extension that you included in your project is a work by others.11 You need to indicate its license so that others know what they are allowed to do – and, of course, you need to comply with any terms yourself, such as retaining the copyright notice.12 In contrast, if it were not for this tutorial, the manuscript would contain your own work and you would need to indicate under which license you provide it to others.\n\n\n\n\n\n\nTip 3: Follow the Help Provided by the License Authors\n\n\n\nFor all the licenses recommended in this tutorial, the organizations that created these licenses provide more information on how to apply them to your work:\n\n\n\n\n\n\n\nApache 2.0\nMPL 2.0\nAGPLv3\n\n\n\n\nCC licenses\nODbL 1.0\n\n\n\n\nCreative Commons even provides a range of considerations for licensors and licensees (Creative Commons, 2013) and an interactive chooser which you can use to create text snippet that you can copy and paste to the desired location.\n\n\nWhile it is common to state the chosen license(s) in the README, usually one of the following actions is taken in addition:\nIn the simplest case, one just creates a file called LICENSE.txt where the full text of the license is copied verbatim. This is a practice propagated by GitHub, which provides instructions for and comparisons of many licenses via ChooseALicense.com. However, if the project is not completely covered by one single license, this practice may become unwieldy. For example, if a project contains different types of works by different authors, the LICENSE.txt needs to detail which file is covered by which license(s), along with any copyright notices.\nIndividual programming languages also have their own way of stating which license a package is distributed under. For R packages, this is usually set by the field License in the file DESCRIPTION (Wickham & Bryan, 2023).\nFinally, Note 4 explains how to use the REUSE specification to make the choice of license machine-readable. This is the approach we recommend taking.\n\n\n\n\n\n\nNote 4: Using REUSE to Record Licenses\n\n\n\n\n\nEvery major free/open license has a unique SPDX identifier which allows communicating the license choice unequivocally. We will be using that to indicate the license for every file in your project, along with the year of publication and the copyright holder. To do this, we add a comment to the beginning of every file and include the two tags SPDX-FileCopyrightText and SPDX-License-Identifier. How this works depends on the file type, as the syntax for a comment varies.\nFor example, if you previously created the file create_data_dictionary.R, you can now add the following comment to the beginning of the file, replacing <YEAR> and <NAME> with the current year and your name – of course, you can also choose a different license:\n\n\ncreate_data_dictionary.R\n\n# SPDX-FileCopyrightText: <YEAR> <NAME>\n#\n# SPDX-License-Identifier: CC0-1.0\n\nYou need to use # to start the comment because this is the symbol that starts comment lines in R scripts. Alternatively, you can use the reuse tool to add these information for you. After installing it with…\n\n\nTerminal\n\npipx install reuse\n\n…you can add the copyright information using the following command – the current year will be added automatically:\n\n\nTerminal\n\nreuse annotate --copyright=\"<NAME>\" --license=\"CC0-1.0\" create_data_dictionary.R\n\nIn many cases, the reuse tool will figure out the appropriate comment style for you. If this is not the case, as currently with Quarto files, you can tell it directly which comment style to use (html in this case):\n\n\nTerminal\n\nreuse annotate --copyright=\"Josephine Zerna <josephine.zerna@tu-dresden.de>\" --copyright=\"Christoph Scheffel <christoph_scheffel@tu-dresden.de>\" --copyright=\"Florian Kohrt\" --license=\"CC-BY-4.0\" --style=html Manuscript.qmd\n\nThis adds the following header to Manuscript.qmd:\n\n\nManuscript.qmd\n\n<!--\nSPDX-FileCopyrightText: 2024 Christoph Scheffel <christoph_scheffel@tu-dresden.de>\nSPDX-FileCopyrightText: 2024 Florian Kohrt\nSPDX-FileCopyrightText: 2024 Josephine Zerna <josephine.zerna@tu-dresden.de>\n\nSPDX-License-Identifier: CC-BY-4.0\n-->\n\nNote that Manuscript.qmd was provided to you under CC BY 4.0, which is what you indicate with the previous comment. If you edited the file, you may also add yourself.13\nSometimes, there are file types which do not allow for adding the license information inside them, such as PDF and CSV files. For these, a corresponding .license file can be created. Try the following command which indicates that the data were published under CC0 1.0:\n\n\nTerminal\n\nreuse annotate --copyright=\"Kristen Gorman\" --license=\"CC0-1.0\" Data.csv\n\nYou will notice that this creates another file called Data.csv.license containing the relevant information:\n\n\nData.csv.license\n\nSPDX-FileCopyrightText: 2024 Kristen Gorman\n\nSPDX-License-Identifier: CC0-1.0\n\nIf you want to indicate the license for all files in a particular folder, you can create a file called REUSE.toml and add an [[annotations]] table for them:\n\n\nREUSE.toml\n\nversion = 1\n\n# apaquarto extension from https://github.com/wjschne/apaquarto\n[[annotations]]\npath = \"_extensions/wjschne/apaquarto/*\"\nSPDX-FileCopyrightText = \"2024 William Joel Schneider <w.joel.schneider@gmail.com>\"\nSPDX-License-Identifier = \"CC0-1.0\"\n\nFinally, there may be some minor files which are build artifacts. You can either add them to your .gitignore file or use the CC0 1.0 license/waiver with a copyright tag such as SPDX-FileCopyrightText: NONE to assert that there is no copyright holder. For more information, also discussing other corner cases, you can read their Frequently Asked Questions.\nOnce you are done, you can download the texts of all indicated licenses using…\n\n\nTerminal\n\nreuse download --all\n\n…and verify that you did not miss a file by running…\n\n\nTerminal\n\nreuse lint\n\n\n\n\nRegardless of how exactly the licenses are added to the project, this is a good opportunity to verify one last time that all third party content is provided to you under a free/open license and that you comply with it. Please add a license to your project now, either creating a file LICENSE.txt or following the REUSE standard.", + "text": "Applying the License\nHaving selected the licenses of your choice – again, you might need multiple ones depending on the types of works your project contains –, we encourage you to read through the full license text (or at least a legal summary) to understand their effect. Then, you can record the license of existing content and apply the licenses of your own contributions. Mostly, this just means indicating which file or folder is covered by which license, usually in the project’s README (among other places), whose creation will be discussed later. Notably, no sort of registration is required.\n\n\n\n\n\n\nCaution 1: License Versions Are Important\n\n\n\nYou may have noticed that we mostly refer to licenses using a name and a version number. This is because the organizations that created the licenses sometimes publish updated versions to accommodate for developments in copyright law and the communities that use the licenses. For example, the Creative Commons licenses (that start with CC) were first published in 2002. Since then, the possibility to relicense under later (v2.0, 2004) and compatible licenses (v3.0, 2007) has been added, a 30-day window to correct license violations has been established to combat copyleft trolls, and sui generis database rights are covered explicitly (v4.0, 2013). There are many more subtle differences between license versions, therefore it is important to indicate which license version exactly one is referring to, as the license of a work does not “update” automatically. CC0, officially introduced in 2009, is still at version 1.0.\nFor the AGPLv3 it is even recommended to state whether a work is licensed under exactly the indicated version of the license or, alternatively, also under newer versions of the license (Stallman, 2022a).\n\n\nFor example, the apaquarto extension that you included in your project is a work by others.11 You need to indicate its license so that others know what they are allowed to do – and, of course, you need to comply with any terms yourself, such as retaining the copyright notice.12 In contrast, if it were not for this tutorial, the manuscript would contain your own work and you would need to indicate under which license you provide it to others.\n\n\n\n\n\n\nTip 3: Follow the Help Provided by the License Authors\n\n\n\nFor all the licenses recommended in this tutorial, the organizations that created these licenses provide more information on how to apply them to your work:\n\n\n\n\n\n\n\nApache 2.0\nMPL 2.0\nAGPLv3\n\n\n\n\nCC licenses\nODbL 1.0\n\n\n\n\nCreative Commons even provides a range of considerations for licensors and licensees (Creative Commons, 2013) and an interactive chooser which you can use to create text snippet that you can copy and paste to the desired location.\n\n\nWhile it is common to state the chosen license(s) in the README, usually one of the following actions is taken in addition:\nIn the simplest case, one just creates a file called LICENSE.txt where the full text of the license is copied verbatim. This is a practice propagated by GitHub, which provides instructions for and comparisons of many licenses via ChooseALicense.com. However, if the project is not completely covered by one single license, this practice may become unwieldy. For example, if a project contains different types of works by different authors, the LICENSE.txt needs to detail which file is covered by which license(s), along with any copyright notices.\nIndividual programming languages also have their own way of stating which license a package is distributed under. For R packages, this is usually set by the field License in the file DESCRIPTION (Wickham & Bryan, 2023).\nFinally, Note 4 explains how to use the REUSE specification to make the choice of license machine-readable. This is the approach we recommend taking.\n\n\n\n\n\n\nNote 4: Using REUSE to Record Licenses\n\n\n\n\n\nEvery major free/open license has a unique SPDX identifier which allows communicating the license choice unequivocally. We will be using that to indicate the license for every file in your project, along with the year of publication and the copyright holder. To do this, we add a comment to the beginning of every file and include the two tags SPDX-FileCopyrightText and SPDX-License-Identifier. How this works depends on the file type, as the syntax for a comment varies.\nFor example, if you previously created the file create_data_dictionary.R, you can now add the following comment to the beginning of the file, replacing <YEAR> and <NAME> with the current year and your name – of course, you can also choose a different license:\n\n\ncreate_data_dictionary.R\n\n# SPDX-FileCopyrightText: <YEAR> <NAME>\n#\n# SPDX-License-Identifier: CC0-1.0\n\nYou need to use # to start the comment because this is the symbol that starts comment lines in R scripts. Alternatively, you can use the reuse tool to add these information for you. After installing it with…\n\n\nTerminal\n\npipx install reuse\n\n…you can add the copyright information using the following command – the current year will be added automatically:\n\n\nTerminal\n\nreuse annotate --copyright=\"<NAME>\" --license=\"CC0-1.0\" create_data_dictionary.R\n\nIn many cases, the reuse tool will figure out the appropriate comment style for you. If this is not the case, as currently with Quarto files, you can tell it directly which comment style to use (html in this case):\n\n\nTerminal\n\nreuse annotate --copyright=\"Josephine Zerna <josephine.zerna@tu-dresden.de>\" --copyright=\"Christoph Scheffel <christoph_scheffel@tu-dresden.de>\" --copyright=\"Florian Kohrt\" --license=\"CC-BY-4.0\" --style=html Manuscript.qmd\n\nThis adds the following header to Manuscript.qmd:\n\n\nManuscript.qmd\n\n<!--\nSPDX-FileCopyrightText: 2024 Christoph Scheffel <christoph_scheffel@tu-dresden.de>\nSPDX-FileCopyrightText: 2024 Florian Kohrt\nSPDX-FileCopyrightText: 2024 Josephine Zerna <josephine.zerna@tu-dresden.de>\n\nSPDX-License-Identifier: CC-BY-4.0\n-->\n\nNote that Manuscript.qmd was provided to you under CC BY 4.0, which is what you indicate with the previous comment. If you edited the file, you may also add yourself.13\nSometimes, there are file types which do not allow for adding the license information inside them, such as PDF and CSV files. For these, a corresponding .license file can be created. Try the following command which indicates that the data were published under CC0 1.0:\n\n\nTerminal\n\nreuse annotate --copyright=\"Kristen Gorman\" --license=\"CC0-1.0\" Data.csv\n\nYou will notice that this creates another file called Data.csv.license containing the relevant information:\n\n\nData.csv.license\n\nSPDX-FileCopyrightText: 2024 Kristen Gorman\n\nSPDX-License-Identifier: CC0-1.0\n\nIf you want to indicate the license for all files in a particular folder, you can create a file called REUSE.toml and add an [[annotations]] table for them:\n\n\nREUSE.toml\n\nversion = 1\n\n# apaquarto extension from https://github.com/wjschne/apaquarto\n[[annotations]]\npath = \"_extensions/wjschne/apaquarto/*\"\nSPDX-FileCopyrightText = \"2024 William Joel Schneider <w.joel.schneider@gmail.com>\"\nSPDX-License-Identifier = \"CC0-1.0\"\n\nFinally, there may be some minor files which are build artifacts. You can either add them to your .gitignore file or use the CC0 1.0 license/waiver with a copyright tag such as SPDX-FileCopyrightText: NONE to assert that there is no copyright holder. For more information, also discussing other corner cases, you can read their Frequently Asked Questions.\nOnce you are done, you can download the texts of all indicated licenses using…\n\n\nTerminal\n\nreuse download --all\n\n…and verify that you did not miss a file by running…\n\n\nTerminal\n\nreuse lint\n\n\n\n\nRegardless of how exactly the licenses are added to the project, this is a good opportunity to verify one last time that all third party content is provided to you under a free/open license and that you comply with it. Please add a license to your project now, either creating a file LICENSE.txt or following the REUSE standard.", "crumbs": [ "Home", "Choose a License" @@ -351,7 +351,7 @@ "href": "choose_license.html#additional-figures", "title": "Choose a License", "section": "Additional Figures", - "text": "Additional Figures\n\n\n\n\n\n\n\n\n\nflowchart TB\n start(\"We want to choose a<br>license for software,<br>writing, image, audio,<br>or video.\") --\"We adapted a work by<br>others shared under a<br>free/open license.\"--> use_existing_license[\"<em>Use its license</em>\"]\n start --\"We created the work<br>entirely by ourselves.\"--> regulation(\"Other regulation<br>(by community or funder)<br>concerning license?\")\n \n regulation --\"Exists\"--> follow_existing_norms[\"<em>Follow that</em>\"]\n regulation --\"Does not<br>exist\"--> type(\"Work type?\")\n \n type --\"Software\"--> code_sa(\"Attribution?<br>State changes?<br>Copyleft?\")\n type --\"Writing, image, audio, video\"--> nocode_cc(\"Attribution?<br>State changes?<br>Anti-DRM?<br>Copyleft?\")\n \n code_sa --\"Attribution &<br>State changes\"--> apache[\"Apache 2.0\"]\n code_sa --\"Attribution &<br>Weak copyleft\"--> mpl[\"MPL 2.0\"]\n code_sa --\"Attribution &<br>State changes &<br>Strong copyleft\"--> agpl[\"AGPLv3\"]\n \n nocode_cc --\"Neither\"--> cc0[\"CC0 1.0\"]\n nocode_cc --\"Attribution &<br>State changes &<br>Anti-DRM\"--> cc_by[\"CC BY 4.0\"]\n nocode_cc --\"Attribution &<br>State changes &<br>Anti-DRM &<br>Copyleft\"--> cc_by_sa[\"CC BY-SA 4.0\"]\n \n click apache href \"https://choosealicense.com/licenses/apache-2.0/\"\n click mpl href \"https://choosealicense.com/licenses/mpl-2.0/\"\n click agpl href \"https://choosealicense.com/licenses/agpl-3.0/\"\n click cc0 href \"https://creativecommons.org/publicdomain/zero/1.0/\"\n click cc_by href \"https://creativecommons.org/licenses/by/4.0/\"\n click cc_by_sa href \"https://creativecommons.org/licenses/by-sa/4.0/\"\n\n\n\n\n\n\nNote. DRM = digital rights management\n\n\nFigure 2: Advanced License Flowchart for Software, Writing, Images, Audio, and Video\n\n\n\n\n\n\n\n\n\n\n\nflowchart TB\n start(\"We want to choose a<br>license for data.\") --\"We adapted a database by<br>others shared under a<br>free/open license.\"--> use_existing_license_db[\"<em>Use its license(s)<br>for content and database</em>\"]\n start --\"We created a database<br>entirely by ourselves.\"--> regulation(\"Other regulation<br>(by community or funder)<br>concerning license?\")\n \n regulation --\"Exists\"--> follow_existing_norms[\"<em>Follow that</em>\"]\n regulation --\"Does not<br>exist\"--> existing_license_content(\"Adapting content<br> by others?\")\n \n subgraph \"License for individual data entries (content)\"\n existing_license_content --\"No, we created the content<br>entirely by ourselves.\"--> facts(\"Entries are facts<br>(like measurements<br>or metadata)?\")\n existing_license_content --\"Yes, it was<br>shared under a<br>free/open license.\"--> use_existing_license_content[\"<em>Use that license</em>\"]\n facts --\"Yes\"--> cc0_content_metadata[\"CC0 1.0\"]\n facts --\"No\"--> choose_license[\"<em>Consult flowchart for<br>software, writing,<br>image, audio, and video</em>\"]\n end\n \n subgraph \"License for combination of data (database)\"\n choose_license --> switch_license[\"<em>Depending on<br>content license</em>\"]\n use_existing_license_content --> switch_license\n \n cc0_content_metadata --> cc0_db[\"CC0 1.0\"]\n switch_license --\"CC0 or<br>non-CC license\"--> sa(\"Attribution?<br>Anti-DRM?<br>Copyleft?\")\n switch_license --\"CC BY or<br>CC BY-SA\"--> same[\"<em>Same license for DB</em>\"]\n \n sa --\"Neither\"--> cc0_db\n sa --\"Attribution &<br>Anti-DRM &<br>Copyleft\"--> odbl[\"ODbL 1.0\"]\n \n %% the following link is only added to have terminal nodes on the same level\n sa ~~~ same\n end\n \n click cc0_content_metadata href \"https://creativecommons.org/publicdomain/zero/1.0/\"\n click cc0_db href \"https://creativecommons.org/publicdomain/zero/1.0/\"\n click odbl href \"https://opendatacommons.org/licenses/odbl/summary/\"\n\n\n\n\n\n\n\n\nFigure 3: Advanced License Flowchart for Data(base)", + "text": "Additional Figures\n\n\n\n\n\n\n\n\n\nflowchart TB\n start(\"We want to choose a<br>license for software,<br>writing, image, audio,<br>or video.\") --\"We adapted a work by<br>others shared under a<br>free/open license.\"--> use_existing_license[\"<em>Use its license</em>\"]\n start --\"We created the work<br>entirely by ourselves.\"--> regulation(\"Other regulation<br>(by community or funder)<br>concerning license?\")\n \n regulation --\"Exists\"--> follow_existing_norms[\"<em>Follow that</em>\"]\n regulation --\"Does not<br>exist\"--> type(\"Work type?\")\n \n type --\"Software\"--> code_sa(\"Attribution?<br>State changes?<br>Copyleft?\")\n type --\"Writing, image, audio, video\"--> nocode_cc(\"Attribution?<br>State changes?<br>Anti-DRM?<br>Copyleft?\")\n \n code_sa --\"Attribution &<br>State changes\"--> apache[\"Apache 2.0\"]\n code_sa --\"Attribution &<br>Weak copyleft\"--> mpl[\"MPL 2.0\"]\n code_sa --\"Attribution &<br>State changes &<br>Strong copyleft\"--> agpl[\"AGPLv3\"]\n \n nocode_cc --\"Neither\"--> cc0[\"CC0 1.0\"]\n nocode_cc --\"Attribution &<br>State changes &<br>Anti-DRM\"--> cc_by[\"CC BY 4.0\"]\n nocode_cc --\"Attribution &<br>State changes &<br>Anti-DRM &<br>Copyleft\"--> cc_by_sa[\"CC BY-SA 4.0\"]\n \n click apache href \"https://choosealicense.com/licenses/apache-2.0/\"\n click mpl href \"https://choosealicense.com/licenses/mpl-2.0/\"\n click agpl href \"https://choosealicense.com/licenses/agpl-3.0/\"\n click cc0 href \"https://creativecommons.org/publicdomain/zero/1.0/\"\n click cc_by href \"https://creativecommons.org/licenses/by/4.0/\"\n click cc_by_sa href \"https://creativecommons.org/licenses/by-sa/4.0/\"\n\n\n\n\n\n\nNote. DRM = digital rights management\n\n\nFigure 2: Advanced License Flowchart for Software, Writing, Images, Audio, and Video\n\n\n\n\n\n\n\n\n\n\n\nflowchart TB\n start(\"We want to choose a<br>license for data.\") --\"We adapted a database by<br>others shared under a<br>free/open license.\"--> use_existing_license_db[\"<em>Use its license(s)<br>for content and database</em>\"]\n start --\"We created a database<br>entirely by ourselves.\"--> regulation(\"Other regulation<br>(by community or funder)<br>concerning license?\")\n \n regulation --\"Exists\"--> follow_existing_norms[\"<em>Follow that</em>\"]\n regulation --\"Does not<br>exist\"--> existing_license_content(\"Adapting content<br> by others?\")\n \n subgraph content[\"<strong>License for content</strong>\"]\n existing_license_content --\"No, we created the content<br>entirely by ourselves.\"--> facts(\"Entries are facts<br>(like measurements<br>or metadata)?\")\n existing_license_content --\"Yes, it was<br>shared under a<br>free/open license.\"--> use_existing_license_content[\"<em>Use that license</em>\"]\n facts --\"Yes\"--> cc0_content_metadata[\"CC0 1.0\"]\n facts --\"No\"--> choose_license[\"<em>Consult flowchart for<br>software, writing,<br>image, audio, and video</em>\"]\n end\n \n subgraph database[\"<strong>License for database</strong>\"]\n choose_license --> switch_license[\"<em>Depending on<br>content license</em>\"]\n use_existing_license_content --> switch_license\n \n cc0_content_metadata --> cc0_db[\"CC0 1.0\"]\n switch_license --\"CC0 or<br>non-CC license\"--> sa(\"Attribution?<br>Anti-DRM?<br>Copyleft?\")\n switch_license --\"CC BY or<br>CC BY-SA\"--> same[\"<em>Same license for DB</em>\"]\n \n sa --\"Neither\"--> cc0_db\n sa --\"Attribution &<br>Anti-DRM &<br>Copyleft\"--> odbl[\"ODbL 1.0\"]\n \n %% the following link is only added to have terminal nodes on the same level\n sa ~~~ same\n end\n \n click cc0_content_metadata href \"https://creativecommons.org/publicdomain/zero/1.0/\"\n click cc0_db href \"https://creativecommons.org/publicdomain/zero/1.0/\"\n click odbl href \"https://opendatacommons.org/licenses/odbl/summary/\"\n\n\n\n\n\n\n\n\nFigure 3: Advanced License Flowchart for Data(base)", "crumbs": [ "Home", "Choose a License" diff --git a/setup.html b/setup.html index e422084..9066a00 100644 --- a/setup.html +++ b/setup.html @@ -544,12 +544,12 @@