Update licenses_gov.qmd

content/licenses_gov.qmd

@@ -9,7 +9,7 @@ title: "Licenses for Government Work"
 Work produced by federal staff is required to be released under an open license.
 
 * Data, publications and content: Use the CC0 license
-* Code: Use an official Open Source license: GPL-3, Apache 2.0, or MIT plus the LICENSE addendum file and the disclaimer file
+* Code: Use an official open source license plus add the LICENSE addendum file and the disclaimer file
 * How? See details below.
 
 ### Background
@@ -18,7 +18,7 @@ Work of the United States government that is done by US federal employees as par
 
 ### Data, publications and content
 
-For data, publications and content Creative Commons license (CC0-1.0) is the recommended license. [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/) is a very broad declaration of public domain.
+For data, publications and content Creative Commons license (CC0-1.0) is the recommended license. [CC0-1.0](https://creativecommons.org/publicdomain/zero/1.0/) is a very broad declaration of public domain. See the 
 
 **How do you specify the license?**
 
@@ -32,7 +32,7 @@ It depends how you release the data. In many cases, a statement regarding that t
 
 There are some special considerations for licenses for open source software: Do not use CC0 for software even though you will see it commonly used on GitHub. Although NOAA has not yet issued its guidelines regarding what open source license to use, it will definitely not be CC0. The CC0 website [does not recommend the license for software](https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software), but instead recommends using an open source license designed for software. If you want to publish your tool in the [Journal of Open Source Software](https://joss.theoj.org/), for example, CC0 is not acceptable because it is not one of the [listed open source licenses](https://opensource.org/licenses/) on the Open Source Initiative. 
 
-The recommended open source licenses for government produced software are one of these: Apache 2.0 (not copyleft so can be used in proprietary software), MIT (not copyleft so can be used in proprietary software), or GPL-3 (strong copyleft so cannot be used in proprietary software).
+There are two general categories of open source licenses: permissive and restrictive. See [this](https://snyk.io/learn/open-source-licenses/) for a nice review of the two types. An example of a restrictive license is GPL-3 because it is strong copy-left; if you use the code in something else, the new code must also be licensed with GPL-3 and the derivative product must also be open source (so cannot be used in proprietary closed-source software). An example of permissive licenses are Apache 2.0 (commonly used by NASA for its open source software) and MIT. For these, the derivative product does not have to be open source so can be used in proprietary software. What license should you use? NOAA has not issued guidelines yet. NASA requires a permissive open source license and Apache 2.0 is commonly used for their code. Generally if you choose one of these, you should be good: Apache 2.0 (not copyleft so can be used in proprietary software), MIT (not copyleft so can be used in proprietary software), or GPL-3 (strong copyleft so cannot be used in proprietary software). But other permissive open source software licenses are probably fine too. 
 
 ***Additional License information**