Update to "Dow"; fix github actions and update to newer Ruby.

Author: risacher

.ruby-version

@@ -1 +1 @@
-3.0.5
+3.2.3

Gemfile

@@ -1,4 +1,4 @@
-ruby '3.0.5'
+ruby '3.2.3'
 
 source 'https://rubygems.org'
 

scripts/test

@@ -2,5 +2,5 @@
 set -e # halt script on error
 
 bundle exec jekyll build
-# I do not know why those URLs fail the proofer, they do exist. :/
-bundle exec htmlproofer ./public --timeframe 6w --url-ignore "/^mailto:/,/code.gov\/about\/open-source\/introduction/,/code.gov\/about\/compliance\/inventory-code/,/twitter.com\/DefenseDigital/"
+# Government and some other sites block automated requests with 403; ignore them.
+bundle exec htmlproofer ./public --timeframe 6w --url-ignore "/^mailto:/,/code.gov\/about\/open-source\/introduction/,/code.gov\/about\/compliance\/inventory-code/,/twitter.com\/DefenseDigital/,/dodcio\.defense\.gov/,/www\.defense\.gov/"

src/_data/footer.yml

@@ -32,26 +32,17 @@ heading: Code.mil
 # If the logo is external add external: true
 logos:
   - src: /assets/images/dod_seal.svg
-    alt: DoD
-    external: false
-  - src: /assets/images/dds-logo-desktop-full.png
-    alt: DDS
+    alt: DoW
     external: false
 
 # Configuration for footer contact links
 contact:
 # Configuration for social media links
 # Comment out links you don't want to use (RSS is an example)
   social_links:
-    - text: <span class="usa-link-twitter usa-social_link" title="Twitter"><span>Twitter</span></span>
-      href: https://twitter.com/DefenseDigital
-      external: true
     - text: <span class="usa-link-github usa-social_link" title="GitHub"><span>GitHub</span></span>
       href: https://github.com/Code-dot-mil/code.mil
       external: true
-    - text: <span class="usa-link-medium usa-social_link" title="Medium"><span>Medium</span></span>
-      href: https://medium.com/defense-digital-service
-      external: true
   heading: Contact Us
 # Configuration for contact links for email, phone, etc...
   contact_links:

src/frequently-asked-questions.md

@@ -17,7 +17,7 @@ The Code.mil initiative will iterate in phases.
 
 During the first phase, which launched on February 22, 2017, we called upon the developer community to help finalize our open source strategy for code written by DoD employees. You can read the official [press release here](https://www.defense.gov/Newsroom/Releases/Release/Article/1092364/dod-announces-the-launch-of-codemil-an-experiment-in-open-source/).
 
-During the second phase, we finalized the strategy and launched our first open source projects on March 13, 2017. You can read about it [here](https://medium.com/@DefenseDigitalService/code-mil-an-open-source-initiative-at-the-pentagon-5ae4986b79bc#.tphs4mxqp). We also issued a call to the DoD developer community to contact us with projects that may be hosted on Code.mil.
+During the second phase, we finalized the strategy and launched our first open source projects on March 13, 2017. We also issued a call to the DoD developer community to contact us with projects that may be hosted on Code.mil.
 
 We're now in a sustaining phase where we are expanding the effort to include projects from other DoD offices, tackling procured source code, and addressing how this strategy might facilitate technology transfer. The hope is that Code.mil will encourage conversation around these topics and allow anyone around the world to contribute knowledge and code for DoD projects.
 
@@ -43,7 +43,7 @@ Modern software is open sourced software. The creative contribution of individua
 
 ## What is the DoD policy on Open Source Software (OSS)?
 
-The Department of Defense (DoD) Chief Information Officer in a 2022 memorandum ["Software Development and Open Source Software"](https://dodcio.defense.gov/Portals/0/Documents/Library/SoftwareDev-OpenSource.pdf) recognizes that "OSS forms the bedrock of the software-defined world and is critical in delivering software faster" and summarizes various aspects of the DoD policy as it impacts open source. We suggest you read that document along with their very helpful [DoD Open Source Software FAQ](https://dodcio.defense.gov/open-source-software-faq/) (Frequently Asked Questions) to gain a better understanding of the Departments perspectives on open source.
+The Department of Defense (DoD) Chief Information Officer in a 2022 memorandum ["Software Development and Open Source Software"](https://dodcio.defense.gov/portals/0/documents/library/softwaredev-opensource.pdf) recognizes that "OSS forms the bedrock of the software-defined world and is critical in delivering software faster" and summarizes various aspects of the DoD policy as it impacts open source.
 
 ## Where can I find other DoD open source projects?
 

src/getting-started.md

@@ -3,7 +3,7 @@ title: Getting Started
 updated_at: 2018-04-03
 ---
 
-This page will help you understand how to participate in Code.mil and comply with [OMB policy (M-16-21)](https://code.gov/#/policy-guide/docs/overview/introduction) for [open source code](https://code.gov/#/policy-guide/policy/open-source). Get started by answering a few questions, and then we can direct you to the right information or start a more in depth conversation.
+This page will help you understand how to participate in Code.mil and comply with [OMB policy (M-16-21)](https://digital.gov/resources/requirements-for-achieving-efficiency-transparency-and-innovation-through-reusable-and-open-source-software/) for [open source code](https://digital.gov/resources/requirements-for-achieving-efficiency-transparency-and-innovation-through-reusable-and-open-source-software/). Get started by answering a few questions, and then we can direct you to the right information or start a more in depth conversation.
 
 <section class="decision-tree">
   {%- for node in site.data.tree_nodes -%}

src/index.md

@@ -3,13 +3,13 @@ layout: home
 
 class: page-home
 
-tagline: Open Source at DoD
+tagline: Open Source at DoW
 
 hero:
   image: /assets/images/hero.jpg
   callout:
-    alt: "DoD Project Owners:"
-    text: Learn more about open source at DoD
+    alt: "DoW Project Owners:"
+    text: Learn more about open source at DoW
   button:
     text: Get Started
     href: /getting-started.html
@@ -34,13 +34,13 @@ intro: |
 
 ## What is Code.mil?
 
-Code.mil is an experiment in open source at the U.S. Department of Defense. The goal is to foster open collaboration with the developer community around the world on DoD open source projects. During the first phase, which launched in early 2017, we wrote a strategy for open sourcing code written by DoD employees, and then we called upon the OSS developer community to help us finalize that plan. You can read the official [press release](https://www.defense.gov/News/News-Releases/News-Release-View/Article/1092364/dod-announces-the-launch-of-codemil-an-experiment-in-open-source/) on the DoD website.
+Code.mil is an experiment in open source at the U.S. Department of War. The goal is to foster open collaboration with the developer community around the world on DoW open source projects. During the first phase, which launched in early 2017, we wrote a strategy for open sourcing code written by DoW employees, and then we called upon the OSS developer community to help us finalize that plan.
 
-At the moment we're getting our first open source projects published in the open. We are also calling on the entire DoD developer community to reach out to DDS to begin tracking all of the great OSS projects coming out.
+We are calling on the entire DoW developer community to reach out to the DoW CIO to begin tracking open source projects coming out of the Department.
 
-In the future we will tackle issues around procuring source code and addressing how this strategy might facilitate technology transfer. The hope is that Code.mil will encourage conversation around these topics and allow anyone around the world to contribute knowledge and code for DoD projects.
+In the future we will tackle issues around procuring source code and addressing how this strategy might facilitate technology transfer. The hope is that Code.mil will encourage conversation around these topics and allow anyone around the world to contribute knowledge and code for DoW projects.
 
-This initiative is not intended to set DoD policy, but rather is exploring alternate ways to join the open source and free software communities. You can read more about the [U.S. Federal Source Code Policy](https://code.gov/#/policy-guide/docs/overview/introduction) on the [Code.gov](https://code.gov) web site.
+This initiative is not intended to set DoW policy, but rather is exploring alternate ways to join the open source and free software communities. You can read more about the [U.S. Federal Source Code Policy](https://digital.gov/resources/requirements-for-achieving-efficiency-transparency-and-innovation-through-reusable-and-open-source-software/) on the [Digital.gov](https://digital.gov) web site.
 
 </div>
 <div class="usa-width-one-third" markdown="1">

src/why-open-source.md

@@ -15,7 +15,7 @@ You may have lots of questions about OSS and how a DoD project can be released p
 
 ### OMB Policy
 
-Aside from the technical benefits mentioned above, the [Federal Source Code Policy (M-16-21)](https://www.whitehouse.gov/wp-content/uploads/legacy_drupal_files/omb/memoranda/2016/m_16_21.pdf) from the US CTO includes a section initiating an [open source pilot](https://code.gov/about/open-source/introduction) which mandates that each government agency **release as OSS at least 20% of its new custom developed code** for the term of the program (and we recommend continuing that beyond the pilot).
+Aside from the technical benefits mentioned above, the [Federal Source Code Policy (M-16-21)](https://obamawhitehouse.archives.gov/sites/default/files/omb/memoranda/2016/m_16_21.pdf) from the US CTO includes a section initiating an [open source pilot](https://code.gov/about/open-source/introduction) which mandates that each government agency **release as OSS at least 20% of its new custom developed code** for the term of the program (and we recommend continuing that beyond the pilot).
 
 Going beyond the OMB policy itself, the [2018 NDAA](https://www.govinfo.gov/app/details/PLAW-115publ91) states in section 875 that "...the Secretary of Defense shall initiate for the Department of Defense the open source software pilot program established by the Office of Management and Budget Memorandum M-16-21..."