chore: rename from DoD to Dow

CONTRIBUTING.md

@@ -153,7 +153,7 @@ You should also run the testing script against your local build. This script wil
 
 ## Submitting Your Open Source Project
 
-If you have a project that you have open sourced, then you need to add (or update) your project in the [code inventory](https://code.mil/code.json) file that the DoD uses to comply with [OMB Policy (M-16-21)](https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2016/m_16_21.pdf). You can read more about the format of the [code inventory format](https://code.gov/about/compliance/inventory-code) on the Code.gov website.
+If you have a project that you have open sourced, then you need to add (or update) your project in the [code inventory](https://code.mil/code.json) file that the DoW uses to comply with [OMB Policy (M-16-21)](https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2016/m_16_21.pdf). You can read more about the format of the [code inventory format](https://code.gov/about/compliance/inventory-code) on the Code.gov website.
 
 To add your project you will need to submit a Pull Request to this project on GitHub. You can follow the instructions here for doing so, but if you are not familiar with GitHub, you can also just [tell us about your project](https://code.mil/tell-us-about-your-code.html) and we can get the process started.
 
@@ -168,8 +168,8 @@ Start by [forking our repository](https://help.github.com/en/github/getting-star
 ```
 {
   "name": "FooBar",
-  "organization": "DoD FooBar",
-  "description": "A project to track all the foobars in the DoD.",
+  "organization": "DoW FooBar",
+  "description": "A project to track all the foobars in the DoW.",
   "tags": [ "foo", "bar", ... ],
   ...
 }

README.md

@@ -2,15 +2,15 @@
 
 ![Build Status](https://github.com/Code-dot-mil/code.mil/actions/workflows/jekyll.yml/badge.svg)
 
-An experiment in open source at the Department of Defense.
+An experiment in open source at the Department of War.
 
-The U.S. Department of Defense (DoD) faces unique challenges in open sourcing its code. Unlike most software projects, code written by U.S. Federal government employees typically doesn't have copyright protections under U.S. and some international laws. This can make it hard to attach an open source license to our code, and our team here at Defense Digital Service wants to find a solution. [Read about our journey so far on Medium](https://medium.com/@DefenseDigitalService/code-mil-an-open-source-initiative-at-the-pentagon-5ae4986b79bc#.i78how76u).
+The U.S. Department of Defense (DoW) faces unique challenges in open sourcing its code. Unlike most software projects, code written by U.S. Federal government employees typically doesn't have copyright protections under U.S. and some international laws. This can make it hard to attach an open source license to our code, and our team here at Defense Digital Service wants to find a solution. [Read about our journey so far on Medium](https://medium.com/@DefenseDigitalService/code-mil-an-open-source-initiative-at-the-pentagon-5ae4986b79bc#.i78how76u).
 
 This repository is the open source home for the public-facing web site [Code.mil](https://code.mil).
 
 ## Build with us.
 
-The DoD is charged with protecting our citizens and national security. We have an incredibly diverse portfolio spanning from communications, logistics, education, healthcare, and even the next generation of GPS (yes, _the_ GPS!) that supports billions of people across the globe.
+The DoW is charged with protecting our citizens and national security. We have an incredibly diverse portfolio spanning from communications, logistics, education, healthcare, and even the next generation of GPS (yes, _the_ GPS!) that supports billions of people across the globe.
 
 We need your help in contributing to our projects to build better products and services for the American people. You can contribute by [finding a project](https://github.com/topics/code-mil), reviewing its contributor guidelines, and submitting an issue or Pull Request!
 
@@ -21,6 +21,6 @@ We need your help in contributing to our projects to build better products and s
 
 ## Make us better.
 
-We've drafted documentation on [implementing OSS within the DoD](https://code.mil/getting-started.html) and a guideline for [accepting contributions to DoD OSS projects](https://code.mil/how-to-open-source.html#step-4-contributions) so the DoD can participate in the open source and free software communities, even where we may not have copyright. This lets us harness the depth and breadth of talent in the open source and free software communities to improve our software and make our code available for public use.
+We've drafted documentation on [implementing OSS within the DoW](https://code.mil/getting-started.html) and a guideline for [accepting contributions to DoW OSS projects](https://code.mil/how-to-open-source.html#step-4-contributions) so the DoW can participate in the open source and free software communities, even where we may not have copyright. This lets us harness the depth and breadth of talent in the open source and free software communities to improve our software and make our code available for public use.
 
 We want your help to continue making our open source strategy better. Our philosophy is continuous iteration. We encourage everybody to [open an issue](https://github.com/Code-dot-mil/code.mil/issues/new) (or a pull request!) with your suggestions on how to continue improving.

_config.yml

@@ -8,7 +8,7 @@ include:
 host: 0.0.0.0
 
 title: Code.mil
-description: An experiment in open source within the Department of Defense.
+description: An experiment in open source within the Department of War.
 email: [email protected]
 
 defaults:
@@ -38,4 +38,4 @@ styles:
   - /assets/css/custom.css
 
 google_analytics_ua: G-1DDRY0RP72
-dap_agency: DOD
+dap_agency: DOW

src/_data/footer.yml

@@ -32,7 +32,7 @@ heading: Code.mil
 # If the logo is external add external: true
 logos:
   - src: /assets/images/dod_seal.svg
-    alt: DoD
+    alt: DoW
     external: false
   - src: /assets/images/dds-logo-desktop-full.png
     alt: DDS

src/_data/press.yml

@@ -2,7 +2,7 @@
    press_url: https://www.fedscoop.com/defense-digital-service-revamps-code-mil-clearer-accessible-guidance/
    author: FedScoop
 
- - title: Amid congressional mandate to open source DoD’s software code, Code.mil serves as guidepost
+ - title: Amid congressional mandate to open source DoW’s software code, Code.mil serves as guidepost
    press_url: https://federalnewsnetwork.com/on-dod/2018/03/amid-congressional-mandate-to-open-source-dods-software-code-code-mil-serves-as-guidepost/
    author: Federal News Radio
 

src/_data/tree_nodes.yml

@@ -79,7 +79,7 @@
 - title: Gov Only
   id: gov-only
   content: |
-    Awesome! We're really happy to hear about all the great things that the DoD is doing on a regular basis. You may not be aware, but most code produced by a U.S. federal employee within the scope of their employment does not have copyright protections in the U.S. and certain foreign jurisdictions. In the U.S., creative works (like code) without copyright protections are sometimes referred to as "public domain." Not all countries recognize the concept of public domain, and many countries actually recognize copyright protections for code written by U.S. federal employees.
+    Awesome! We're really happy to hear about all the great things that the DoW is doing on a regular basis. You may not be aware, but most code produced by a U.S. federal employee within the scope of their employment does not have copyright protections in the U.S. and certain foreign jurisdictions. In the U.S., creative works (like code) without copyright protections are sometimes referred to as "public domain." Not all countries recognize the concept of public domain, and many countries actually recognize copyright protections for code written by U.S. federal employees.
 
     However, other countries can enforce our open source licenses, even for code in the public domain. Additionally, it can be good guidance for public contributors to identify what open source license and contribution policy govern a project. The Code.mil team recommends attaching an open source license along with an "intent" document that clearly indicates how the government intends the code to be released, even if in the United States the law says it is public domain.
 
@@ -92,7 +92,7 @@
 - title: Gov and Contractor
   id: mixed-code
   content: |
-    Great! We understand that partnering with the private sector is how most project development happens in the DoD. You may still be able to open source the resulting code for the project depending on the U.S. federal government's data rights in the contract! The key is to **identify any pieces of the code that are proprietary to the contractor or otherwise restricted from public disclosure**. If there are such pieces then you may need to segment those so that you don't violate the license terms in the contract. That said, if you have Unlimited Rights in segregable portions of the code, you should be able to follow the Code.mil guideline for open sourcing that code!
+    Great! We understand that partnering with the private sector is how most project development happens in the DoW. You may still be able to open source the resulting code for the project depending on the U.S. federal government's data rights in the contract! The key is to **identify any pieces of the code that are proprietary to the contractor or otherwise restricted from public disclosure**. If there are such pieces then you may need to segment those so that you don't violate the license terms in the contract. That said, if you have Unlimited Rights in segregable portions of the code, you should be able to follow the Code.mil guideline for open sourcing that code!
 
     You will need to attach an appropriate license to the project, and because it was developed in part by the U.S. Federal Government you will need to specify the "intent" of the licensing (we have recommended language in the "How to" section). This  language is recommended because most code produced by a U.S. federal employee within the scope of their employment does not have copyright protections in the U.S. and certain foreign jurisdictions. This matters because  it affects the enforceability of your chosen license depending on the jurisdiction and who wrote the code. But no worries! You can still attach an open source license to your project and govern your project per that license.
 

src/_plugins/code_gov_inventory_generator.rb

@@ -25,7 +25,7 @@ def file_paths
 
       def page_content
         output = {
-          agency: 'DOD',
+          agency: 'DOW',
           version: '2.0.0',
           measurementType: {
             method: 'projects'

src/_releases/github.com/Code-dot-mil/code.mil.json

@@ -1,7 +1,7 @@
 {
   "organization": "DDS",
   "name": "Code.mil",
-  "description": "An experiment in open source at the Department of Defense. The goal is to foster open collaboration with the developer community around the world on DoD open source projects.",
+  "description": "An experiment in open source at the Department of War. The goal is to foster open collaboration with the developer community around the world on DoW open source projects.",
   "tags": [],
   "contact": {
     "email": "[email protected]",

src/_releases/github.com/deptofdefense/covid19-calculator.json

@@ -2,7 +2,7 @@
   "name": "covid19-calculator",
   "version": "1.4.0",
   "repositoryURL": "https://github.com/deptofdefense/covid19-calculator",
-  "description": "Provides a set of scoring algorithms for evaluating COVID-19 symptoms implemented in TypeScript. The algorithms and associated inputs in this model are based on United States Department of Defense medical opinion and are actively used in MySymptoms.mil.",
+  "description": "Provides a set of scoring algorithms for evaluating COVID-19 symptoms implemented in TypeScript. The algorithms and associated inputs in this model are based on United States Department of War medical opinion and are actively used in MySymptoms.mil.",
   "permissions": {
     "licenses": [
       {