Built site for gh-pages

.nojekyll

@@ -1 +1 @@
-f51a171d
+b360137f

content/licenses_gov.html

@@ -299,7 +299,7 @@ <h1 class="title">Licenses for Government Work</h1>
 <section id="licenses" class="level2">
 <h2 class="anchored" data-anchor-id="licenses">Licenses</h2>
 <p>Work of the United States government that is done by US federal employees as part of their official duties is generally <a href="https://fairuse.stanford.edu/overview/public-domain/welcome/#us_government_works">in the public domain</a> within the United States of America. That means it cannot be copyrighted. (The relevant law is <a href="https://www.law.cornell.edu/uscode/text/17/105">here</a> Code (or anything else) developed by US federal employees should have a notice that the work is in the public domain. It is common to waive copyright and related rights in the work worldwide through the CC0 1.0 Universal public domain dedication.</p>
-<p>Government agencies will use some kind of public domain license, but which one used varies. There are two main licenses used for products by federal agencies (or their employees) on GitHub: Creative Commons license (CC0-1.0) and the GNU General Public License v3. <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0-1.0 is a very broad declaration of public domain</a> while <a href="https://www.gnu.org/licenses/gpl-3.0.en.html">GPL-3 is explicit about derivative works and how those works must retain an open source license</a>.</p>
+<p>Products by federal agencies (or their employees) on GitHub will use some kind of public domain license, but which one used varies. For data, publications and content Creative Commons license (CC0-1.0) is the recommended license. <a href="https://creativecommons.org/publicdomain/zero/1.0/">CC0-1.0</a> is a very broad declaration of public domain. For software, there are a variety of public domain licenses used:</p>
 <ul>
 <li>Other <a href="https://github.com/NOAAGov/NOAA-Affiliated-Projects">NOAA Affiliated GitHub organizations</a> use a mix of GPL-3 and CC0-1.0.</li>
 <li>USGS uses <a href="https://github.com/usgs/best-practices/blob/master/LICENSE.md">CC0-1.0 License + additional info</a></li>
@@ -309,7 +309,7 @@ <h2 class="anchored" data-anchor-id="licenses">Licenses</h2>
 <li>NASA uses <a href="https://github.com/nasa/astrobee/blob/master/LICENSE">Apache 2.0</a> mostly</li>
 <li>GSA uses <a href="https://github.com/18F/fedramp-data#public-domain">CC0-1.0 License</a></li>
 </ul>
-<p>There are some special considerations for licenses for open source software. The CC0 website <a href="https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software">does not recommend the license for software</a>, but instead recommends using an open source license designed for software. If you want to publish your tool in the <a href="https://joss.theoj.org/">Journal of Open Source Software</a>, for example, CC0 is not acceptable because it is not one of the <a href="https://opensource.org/licenses/">listed open source licenses</a> on the Open Source Initiative.</p>
+<p>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 re what open source license to use, it will definitely not be CC0. The CC0 website <a href="https://creativecommons.org/faq/#can-i-apply-a-creative-commons-license-to-software">does not recommend the license for software</a>, but instead recommends using an open source license designed for software. If you want to publish your tool in the <a href="https://joss.theoj.org/">Journal of Open Source Software</a>, for example, CC0 is not acceptable because it is not one of the <a href="https://opensource.org/licenses/">listed open source licenses</a> on the Open Source Initiative. The recommended open source licenses for government produced software are 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 and cannot be used in proprietary software).</p>
 </section>
 <section id="additional-license-information" class="level2">
 <h2 class="anchored" data-anchor-id="additional-license-information">Additional License information</h2>