Merge pull request #1 from gw-ospo/review

Review

lessons/_config.yml

@@ -33,7 +33,7 @@ html:
   use_repository_button: true
   extra_footer: |
     <p>
-    (c) 2024 -- This work is licensed under Creative Commons Attribution 4.0 International (CC-BY-4.0) <br>
+    &copy; 2024 -- This work is licensed under Creative Commons Attribution 4.0 International (CC-BY-4.0) <br>
     </p>
 sphinx:
   config:
@@ -43,4 +43,4 @@ parse:
     # don't forget to list any other extensions you want enabled,
     # including those that are enabled by default!
     - deflist
-    - colon_fence
+    - colon_fence

lessons/intro.md

@@ -1,6 +1,6 @@
 # OSS Licensing for Research and Education
 
-This is a a short course that introduces researchers (doctoral students, postdocs, staff researchers and PIs) to the essentials of open-source software (OSS) licensing for research and educational purposes. The course duration should be about 3 hours when taught live, and we will also produce an online version for self-study. 
+This is a a short course that introduces researchers (doctoral students, postdocs, staff researchers and PIs) to the essentials of open-source software (OSS) licensing for research and educational purposes. The course duration should be about 3 hours when taught live, and we will also produce an online version for self-study.
 
 The course covers the key topics related to using, licensing, and collaborating with open source software, data, and content in a research and education context. Each section includes relevant subtopics and practical concerns, focusing on key licensing concepts, choosing appropriate licenses, navigating institutional processes, and fostering open source collaboration in research teams.
 
@@ -22,7 +22,7 @@ Samantha feels overwhelmed by the licensing complexities and is unsure about the
 As researchers increasingly rely on open source tools and collaborate across institutions, understanding software licensing has become crucial. Making the wrong choices could lead to legal troubles, restrict future opportunities, or inadvertently limit the impact of one's work.
 `````
 
-The dilemma presented in the vignette above is an example of how you might first encounter open-source software: someone on the internet posted their code on a website... _Can you use it? Can you incorporate it into your own code? Can you modify it? Can you redistribute it? Should you credit the author?_ 
+The dilemma presented in the vignette above is an example of how you might first encounter open-source software: someone on the internet posted their code on a website... _Can you use it? Can you incorporate it into your own code? Can you modify it? Can you redistribute it? Should you credit the author?_
 
 Once you have experienced the joy of reusing someone else's open-source software, and it has benefitted your research or educational endeavors, you may ask: _how do I share my own code with the world?_ After all, we seek to have impact through our work, and you now see clearly that sharing can have impact! What do you need to know to license your own code, data, or other works?
 
@@ -38,7 +38,7 @@ The vignettes in this course are all fictional, except this one!
 `````{admonition} Vignette: Why open source?
 :class: tip
 ```{image} ../assets/2015_blog.png
-:alt: old blog 
+:alt: old blog
 :width: 400px
 :align: center
 ```
@@ -57,4 +57,4 @@ In an October 2015 [interview](https://web.archive.org/web/20180514095134/http:/
 
 ```{bibliography}
 :style: alpha
-```
+```

lessons/license_collaborative_work.md

@@ -164,7 +164,7 @@ As graduates of Sunnyvale University moved on to other institutions and industri
 Looking back on the success of "Open Source for All," Dr. Hernandez couldn't help but feel proud. What had started as a small initiative had grown into a movement that was changing the face of research and education at Sunnyvale University and beyond. She knew that the impact of embracing open-source licensing would continue to ripple outwards, driving progress and innovation for years to come.
 ```
 
-This vignette illustrates the powerful potential of open-source licensing to transform an academic community. By embracing the principles of sharing, collaboration, and transparency, researchers and educators can create a virtuous cycle of innovation and discovery that benefits everyone.
+This vignette illustrates the powerful potential of open-source licensing to transform an academic community. By embracing the principles of sharing, collaboration, and transparency, researchers and educators can create a **virtuous cycle of innovation and discovery that benefits everyone**.
 
 As you complete this course and begin to apply what you've learned to your own work, remember that you too have the power to drive change in your community. By choosing to license your projects openly and contributing to the open-source ecosystem, you become part of a global movement that is shaping the future of research and education.
-So go forth, share your work, and collaborate with others. **Together, we can build a more open, equitable, and innovative world.**
+So go forth, share your work, and collaborate with others. **Together, we can build a more open, equitable, and innovative world.**

lessons/license_your_own_work.md

@@ -1,4 +1,4 @@
-# Lesson 2: Licensing Your Own Software and Other Works 
+# Lesson 2: Licensing Your Own Software and Other Works
 
 ````{admonition} Vignette: So Much to Share
 :class: tip
@@ -43,7 +43,7 @@ Moreover, many funding agencies and journals now require or strongly encourage r
 
 One of the most powerful aspects of openly licensing your research outputs is that it facilitates (and even invites) others to collaborate with you and build upon your work. By pre-emptively granting permissions for others to use, modify, and share your code, data, and materials, you open up new opportunities for collaboration and innovation.
 
-Imagine a scenario where another researcher comes across your openly licensed software and realizes that it could be adapted to solve a problem they've been working on. By building upon your work, they are able to make new discoveries and advance their own research. In turn, they may contribute back to your project, leading to a virtuous cycle of collaboration and mutual benefit.
+Imagine a scenario where another researcher comes across your openly licensed software and realizes that it could be adapted to solve a problem they've been working on. By building upon your work, they are able to make new discoveries and advance their own research. In turn, they may contribute back to your project, leading to a **virtuous cycle of collaboration and mutual benefit**.
 
 Or perhaps a teacher discovers your openly licensed dataset and incorporates it into a lesson plan, exposing a new generation of students to your work and inspiring them to pursue careers in your field.
 
@@ -96,7 +96,7 @@ The [CC-BY license](https://choosealicense.com/licenses/cc-by-4.0/) is the most
 
 When choosing a CC license, consider your goals and the potential impact you want your work to have. In general, we recommend using the most permissive license that still aligns with your needs and values.
 
-```{warning} 
+```{warning}
 It's important to note that *CC licenses are not appropriate for software*, as they do not address important issues like source code distribution, patent rights, and warranty disclaimers. Stick to OSI-approved licenses for software, and use CC licenses for other types of content.
 ```
 
@@ -148,7 +148,7 @@ Now that you realize the importance of licensing your work and the different typ
 
 ### Picking a license when creating a code repository on GitHub
 
-When [creating a new repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-new-repository) on GitHub, you can easily add a license to your project. After entering your repository name and description, look for the "Choose a license" dropdown menu. 
+When [creating a new repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/creating-a-new-repository) on GitHub, you can easily add a license to your project. After entering your repository name and description, look for the "Choose a license" dropdown menu.
 
 ```{image} ../assets/repository-license-picker.png
 :alt: screen capture github license picker
@@ -191,7 +191,7 @@ A typical copyright notice and license summary might look like this:
 Copyright (c) [Year] [Your Name]
 
 This project is licensed under the terms of the [License Name] license.
-You are free to use, modify, and distribute this work, subject to the 
+You are free to use, modify, and distribute this work, subject to the
 conditions specified in the LICENSE file.
 ```
 
@@ -200,9 +200,9 @@ For example:
 ```
 Copyright (c) 2023 Jane Doe
 
-This dataset is licensed under the terms of the Creative Commons 
-Attribution 4.0 International (CC BY 4.0) license. You are free to 
-share and adapt this dataset, as long as you give appropriate credit 
+This dataset is licensed under the terms of the Creative Commons
+Attribution 4.0 International (CC BY 4.0) license. You are free to
+share and adapt this dataset, as long as you give appropriate credit
 and indicate if changes were made. See the LICENSE file for details.
 ```
 
@@ -217,21 +217,21 @@ As a researcher, you don't operate in a vacuum. Your work is supported by and co
 ### Familiarizing yourself with your institution's IP policies
 
 ::::{margin}
-:::{seealso} 
+:::{seealso}
 The American Association of University Professors, AAUP, has issued a [Statement on Intellectual Property](https://www.aaup.org/report/statement-intellectual-property) that puts in place expectations for universities in the U.S.
 ::::
 
 At many colleges and universities in the United States, the principles of academic freedom dictate that faculty, students, and some staff (librarians, for example) own the rights to their research and scholarly creations. This means that, as an author, you traditionally retain the copyright to your work and have the authority to decide how it is disseminated, including the choice of license.
 
-However, it's essential to familiarize yourself with your institution's specific IP policies, as they may have some variations or exceptions. For example, some institutions may claim ownership of certain types of work, such as software developed using significant university resources or projects funded by specific sources. 
+However, it's essential to familiarize yourself with your institution's specific IP policies, as they may have some variations or exceptions. For example, some institutions may claim ownership of certain types of work, such as software developed using significant university resources or projects funded by specific sources.
 
 To understand your rights and responsibilities, consult your institution's IP policy documents, faculty handbook, or research administration office. If you have questions or concerns, don't hesitate to reach out to your department chair, librarian, or legal counsel for guidance.
 
 ```{admonition} GW Copyright Policies
 :class: tip
 The [GW Copyright Policy](https://compliance.gwu.edu/copyright) says that faculty, librarians, and students retain the copyright of any works done:
 > ...in pursuit of their normal scholarly, professional, or academic responsibilities, including normal use of the university's physical facilities, by their own initiative...
-> Sponsored Research, without a specific agreement for copyright, shall be considered scholarly work and the copyright in such works shall belong to the author(s), not to the university. 
+> Sponsored Research, without a specific agreement for copyright, shall be considered scholarly work and the copyright in such works shall belong to the author(s), not to the university.
 
 This means that scholarly works---including software, documentation, and educational content---belong to the author, who is thus free to choose to share the works under any license.
 ```
@@ -270,4 +270,4 @@ Additionally, consider engaging with your institution's faculty governance bodie
 
 Navigating institutional policies and processes related to open licensing can seem daunting, but remember that you are not alone. By familiarizing yourself with your institution's IP policies, leveraging the resources and expertise of your OSPO, and actively advocating for open-licensing practices, you can ensure that your research outputs are widely shared and have the greatest possible impact.
 
-As you work to openly license your own research, you are advancing your own career and reputation while also contributing to a larger movement towards open and equitable access to knowledge. _Your efforts, combined with those of your colleagues and institution, can help shape a future where the fruits of academic research are freely and openly available to all._
+As you work to openly license your own research, you are advancing your own career and reputation while also contributing to a larger movement towards open and equitable access to knowledge. _Your efforts, combined with those of your colleagues and institution, can help shape a future where the fruits of academic research are freely and openly available to all._

lessons/use_licensed_works.md

@@ -25,13 +25,13 @@ In the world of research and education, open licensing has become increasingly i
 In essence, open licensing refers to a set of principles and legal frameworks that grant permissions for others to freely access, use, modify, and share creative works or products. This concept applies to various types of outputs, including software, research data, scholarly publications, and educational materials.
 
 ```{image} ../assets/licensing_orgs.png
-:alt: logos of licensing orgs 
+:alt: logos of licensing orgs
 :width: 500px
 :align: center
 ```
 
 ````{margin}
-```{note} The [Open Source Initiative](https://opensource.org) (OSI), founded in 1998, is the stewardship organization of the "open-source" label and [OSS licenses](https://opensource.org/license). It drafted the famous [Open Source Definition](https://opensource.org/osd) that defines ten criteria that must be met for a software license to be considered open source. 
+```{note} The [Open Source Initiative](https://opensource.org) (OSI), founded in 1998, is the stewardship organization of the "open-source" label and [OSS licenses](https://opensource.org/license). It drafted the famous [Open Source Definition](https://opensource.org/osd) that defines ten criteria that must be met for a software license to be considered open source.
  ```
 ````
 
@@ -53,7 +53,7 @@ Open licensing is not just a technological or legal construct; it represents a _
 ```{important}
 Open licensing gives us _freedom_---contrary to intellectual-property instruments that want to control how creative works are used.
 
-Freedom is power. In this case, the power of open-source software comes not just from being able to read the source code, but from being able to contribute to and build from it. 
+Freedom is power. In this case, the power of open-source software comes not just from being able to read the source code, but from being able to contribute to and build from it.
 
 For this power to be realized, it's not sufficient to make the source public to read. We must attach a license that allows others to modify and distribute the code.
 
@@ -89,7 +89,7 @@ As a researcher or educator you'll likely find yourself wanting to use code, dat
 
 ### What is license compatibility?
 
-Some licenses play nicely with others, while others have strict requirements that can limit their compatibility. When combining pieces of code together, you will want to check whether the terms of their different licenses allow them to be used together in the same project. 
+Some licenses play nicely with others, while others have strict requirements that can limit their compatibility. When combining pieces of code together, you will want to check whether the terms of their different licenses allow them to be used together in the same project.
 
 For example, let's say you want to use a Python library licensed under the permissive MIT license in your research project. You also want to include a dataset licensed under the Creative Commons Attribution (CC BY) license. In this case, you're in luck! The MIT and CC BY licenses are generally compatible, meaning you can use them together without any legal hiccups.
 
@@ -201,7 +201,7 @@ By engaging in this activity, you'll gain practical experience in navigating the
 
 ````{admonition} Vignette: The Tale of Dr. Flack's Data Visualization Journey
 :class: tip
-Dr. Roberta Flack, a climate scientist, needs to create interactive visualizations of global temperature data. 
+Dr. Roberta Flack, a climate scientist, needs to create interactive visualizations of global temperature data.
 After some searching, she finds a JavaScript library called "ClimateViz" that seems perfect for her needs. The library is hosted on GitHub and is released under the MIT license. She also discovers a dataset of global temperature anomalies from the National Oceanic and Atmospheric Administration (NOAA), which is available under the Creative Commons Attribution (CC-BY) license.
 
 **Identifying and Complying with License Terms**---
@@ -222,4 +222,4 @@ By taking the time to understand and comply with the license terms, attribution
 
 ## Sources
 
-Portions of this lesson are based on materials from the presentation by {cite:t}`barba2017-licensing`, which drew from {cite:t}`morin2012quick`.
+Portions of this lesson are based on materials from the presentation by {cite:t}`barba2017-licensing`, which drew from {cite:t}`morin2012quick`.