diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 2632c4cc..9298c81a 100644 --- a/CONTRIBUTING.md +++ b/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", ... ], ... } diff --git a/README.md b/README.md index 2c73de3b..b86f2325 100644 --- a/README.md +++ b/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. diff --git a/_config.yml b/_config.yml index 98336b00..60d6bf8e 100644 --- a/_config.yml +++ b/_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: code@dds.mil defaults: @@ -38,4 +38,4 @@ styles: - /assets/css/custom.css google_analytics_ua: G-1DDRY0RP72 -dap_agency: DOD +dap_agency: DOW diff --git a/src/_data/footer.yml b/src/_data/footer.yml index 7ca1fc9c..d66e963e 100644 --- a/src/_data/footer.yml +++ b/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 diff --git a/src/_data/press.yml b/src/_data/press.yml index 5d829cdd..df02bd7f 100644 --- a/src/_data/press.yml +++ b/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 diff --git a/src/_data/tree_nodes.yml b/src/_data/tree_nodes.yml index bd30b64c..f97a5f02 100644 --- a/src/_data/tree_nodes.yml +++ b/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. diff --git a/src/_plugins/code_gov_inventory_generator.rb b/src/_plugins/code_gov_inventory_generator.rb index 4e82446c..7c490522 100644 --- a/src/_plugins/code_gov_inventory_generator.rb +++ b/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' diff --git a/src/_releases/github.com/Code-dot-mil/code.mil.json b/src/_releases/github.com/Code-dot-mil/code.mil.json index f163503a..18558447 100644 --- a/src/_releases/github.com/Code-dot-mil/code.mil.json +++ b/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": "code@dds.mil", diff --git a/src/_releases/github.com/deptofdefense/covid19-calculator.json b/src/_releases/github.com/deptofdefense/covid19-calculator.json index 6b1c6589..411e0f6e 100644 --- a/src/_releases/github.com/deptofdefense/covid19-calculator.json +++ b/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": [ { diff --git a/src/frequently-asked-questions.md b/src/frequently-asked-questions.md index ab1e6f55..2c08f8bc 100644 --- a/src/frequently-asked-questions.md +++ b/src/frequently-asked-questions.md @@ -11,21 +11,21 @@ subnav: ## What is Code.mil? -Code.mil is an experiment in open source at the U.S. Department of Defense (DoD). The goal is to foster open collaboration with the developer community across the world on DoD open source projects. +Code.mil is an experiment in open source at the U.S. Department of War (DoW). The goal is to foster open collaboration with the developer community across the world on DoW open source projects. 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 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 DoW 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. 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 DoW 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. +We're now in a sustaining phase where we are expanding the effort to include projects from other DoW 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 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. +This initiative is not intended to set DoW policy, but rather is exploring alternate ways to join the open source and free software communities. ## Who is behind Code.mil? -The [Defense Digital Service](https://dds.mil) (DDS) launched Code.mil on February 22, 2017. Established on November 18, 2015 by the Secretary of Defense, DDS brings in the best private sector talent, technology, and processes to DoD. DDS functions like a SWAT team of nerds working on high impact challenges during one to two year tours of duty as federal employees. +The [Defense Digital Service](https://dds.mil) (DDS) launched Code.mil on February 22, 2017. Established on November 18, 2015 by the Secretary of Defense, DDS brings in the best private sector talent, technology, and processes to DoW. DDS functions like a SWAT team of nerds working on high impact challenges during one to two year tours of duty as federal employees. ## Who has been involved with Code.mil? @@ -33,19 +33,19 @@ DDS has collaborated extensively with organizations in the open source and free ## How does Code.mil relate to Code.gov? -We launched Code.mil to further the mission of [Code.gov](https://code.gov) within DoD. We are in close collaboration with the team at Code.gov to expand upon government reuse and public access to custom-developed Federal source code. Projects hosted on Code.mil will also be accessible through the Code.gov platform. +We launched Code.mil to further the mission of [Code.gov](https://code.gov) within DoW. We are in close collaboration with the team at Code.gov to expand upon government reuse and public access to custom-developed Federal source code. Projects hosted on Code.mil will also be accessible through the Code.gov platform. -## Why is DoD doing this? +## Why is DoW doing this? U.S. military members and their families make significant sacrifices to protect our country. Their lives should not be negatively impacted by outdated tools and software development practices that lag far behind private sector standards. -Modern software is open sourced software. The creative contribution of individual developers to help solve complex problems of impact is largely untapped by DoD. Through this experiment, we are trying to more actively participate in the open source and free software communities. We need your help to build better software products and services for our military members and citizens across the country. +Modern software is open sourced software. The creative contribution of individual developers to help solve complex problems of impact is largely untapped by DoW. Through this experiment, we are trying to more actively participate in the open source and free software communities. We need your help to build better software products and services for our military members and citizens across the country. -## What is the DoD policy on Open Source Software (OSS)? +## What is the DoW 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 War (DoW) 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 DoW policy as it impacts open source. We suggest you read that document along with their very helpful [DoW 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. -## Where can I find other DoD open source projects? +## Where can I find other DoW open source projects? There are many other projects that have already been open sourced. They are located in various places such as GitHub, code.gov, and numerous other web sites. We're working to inventory and catalog many of these, but you can find some of them using the [`code-mil` topic on GitHub](https://github.com/topics/code-mil) @@ -67,7 +67,7 @@ The updated strategy in [`INTENT.md`](https://github.com/Code-dot-mil/code.mil/b Good point! We definitely considered this. CC0 1.0 Universal seeks to dedicate copyrighted work to the public domain by waiving the author's rights to the work worldwide under copyright law. Using CC0 1.0 Universal is one possibility, but not the only one. There are many high quality and widely adopted open source and free software licenses, each with their own advantages and disadvantages. We are not intending to judge the merit of using CC0 1.0 Universal. Rather, we are positing that the project maintainer should have the freedom of choice when it comes to selecting the "best" license for that particular project. -Intelligent minds will differ on the "best" avenue for a U.S. Federal government agency to participate in open source. The reality is that every organization, and every project, has unique circumstances that affect which option might make the most sense. This initiative is not intended to set DoD policy, but rather is exploring alternate ways for joining the open source community. +Intelligent minds will differ on the "best" avenue for a U.S. Federal government agency to participate in open source. The reality is that every organization, and every project, has unique circumstances that affect which option might make the most sense. This initiative is not intended to set DoW policy, but rather is exploring alternate ways for joining the open source community. ## How are you handling code contributions? @@ -86,10 +86,10 @@ What you need to do if you fork the project depends on the status of the project - If the project includes no copyrighted code (so there have been no merged copyrighted contributions and your jurisdiction does not recognize copyright for U.S. Government-written work), then 'LICENSE.md' has not attached to the project. - If the project includes copyrighted code (so there are merged copyrighted contributions or your jurisdiction recognizes copyright for U.S. Government-written work), then `LICENSE.md` has attached to the project and you must comply with the terms of the license. The authors and contributors are listed in `CONTRIBUTORS.md` and, in some cases, the source file headers. -## Is DoD trying to do something funny here? +## Is DoW trying to do something funny here? No! -We mean to be totally transparent in our intent and purpose with Code.mil. We want to be really clear about what we’re doing and why we’re doing it so that you feel comfortable contributing to DoD projects. +We mean to be totally transparent in our intent and purpose with Code.mil. We want to be really clear about what we’re doing and why we’re doing it so that you feel comfortable contributing to DoW projects. **For more information or questions, please contact our team at [{{site.email}}](mailto:{{site.email}}). Happy coding!** diff --git a/src/how-to-open-source.md b/src/how-to-open-source.md index bba20c04..1c528685 100644 --- a/src/how-to-open-source.md +++ b/src/how-to-open-source.md @@ -80,7 +80,7 @@ If you aren't sure where to post the code, or you need help getting source contr ### Step 6: OMB Policy Tracking -The last piece of this process is adding your project to 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. +The last piece of this process is adding your project to 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 the [Code.mil project on GitHub](https://github.com/Code-dot-mil/code.mil). There are instructions for doing so in our code repository, but if you are not familiar with GitHub, you can also just [tell us about your project](/tell-us-about-your-code.html) and we can get the process started. diff --git a/src/index.md b/src/index.md index 3e0ba72f..64908c09 100644 --- a/src/index.md +++ b/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 @@ -27,20 +27,20 @@ graphics: description: We've drafted this documentation in partnership with the open source community. You can help improve our open source strategy by improving these documents! Open an issue or a pull request with your suggestions. intro: | - 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 does not have copyright protections under U.S. and some international laws. This can make it difficult to attach an open source license to our code. The [Defense Digital Service](https://dds.mil) (DDS) has been working with DoD and the open source community since early 2017 to develop a guideline for supporting open source software (OSS) within the Department. + The U.S. Department of War (DoW) faces unique challenges in open sourcing its code. Unlike most software projects, code written by U.S. Federal government employees typically does not have copyright protections under U.S. and some international laws. This can make it difficult to attach an open source license to our code. The [Defense Digital Service](https://dds.mil) (DDS) has been working with DoW and the open source community since early 2017 to develop a guideline for supporting open source software (OSS) within the Department. ---
## 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. 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 DoW website. -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. +At the moment we're getting our first open source projects published in the open. We are also calling on the entire DoW developer community to reach out to DDS to begin tracking all of the great OSS projects coming out. -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://code.gov/#/policy-guide/docs/overview/introduction) on the [Code.gov](https://code.gov) web site.
diff --git a/src/tell-us-about-your-code.html b/src/tell-us-about-your-code.html index 945775d1..13750ec8 100644 --- a/src/tell-us-about-your-code.html +++ b/src/tell-us-about-your-code.html @@ -5,7 +5,7 @@ ---

- The DoD is reforming our processes and adopting agile acquisition and software + The DoW is reforming our processes and adopting agile acquisition and software development practices so that we may more diligently contract for, license, mark, receive, and release our custom-developed source code. We’re doing this to create better technical outcomes for our users, improve our security diff --git a/src/thank-you.md b/src/thank-you.md index 46e641ab..82bbc8de 100644 --- a/src/thank-you.md +++ b/src/thank-you.md @@ -2,4 +2,4 @@ title: Thank you for your submission! --- -Thank you for submitting your custom software project! For information on Code.mil and open source software within the DoD, check out our [Why Open Source](/why-open-source.html) page. +Thank you for submitting your custom software project! For information on Code.mil and open source software within the DoW, check out our [Why Open Source](/why-open-source.html) page. diff --git a/src/why-open-source.md b/src/why-open-source.md index 34d416ad..8e6837c3 100644 --- a/src/why-open-source.md +++ b/src/why-open-source.md @@ -3,7 +3,7 @@ title: Why Open Source updated_at: 2024-07-07 --- -**Modern software is open sourced software (OSS)**. The creative contribution of individual developers to help solve complex problems of impact is largely untapped by DoD. We must more actively participate in the open source and free software communities if we are to truly reap the benefits of OSS. +**Modern software is open sourced software (OSS)**. The creative contribution of individual developers to help solve complex problems of impact is largely untapped by DoW. We must more actively participate in the open source and free software communities if we are to truly reap the benefits of OSS. There are some misconceptions, however: for example, that open source software is not secure. Without delving too deep into this topic (we're happy to discuss it in person), consider that the single most popular web server software is, and always has been, open source: [Apache](https://www.apache.org/). This code runs a vast swath of sites on the Internet. Do bugs come up? Of course! But they are often patched (fixed with a small amount of code) in mere hours after identification. @@ -11,13 +11,13 @@ In fact, nearly every popular software product relies heavily on open source sof A simple google search of "why OSS" will bring you to [a paper by David Wheeler](https://dwheeler.com/oss_fs_why.html) which goes into extensive detail on this subject. -You may have lots of questions about OSS and how a DoD project can be released publicly. **This is the goal of Code.mil!** We want to provide guidance on how you, a DoD project owner, can release your code as open source software and why it is in your best interest. +You may have lots of questions about OSS and how a DoW project can be released publicly. **This is the goal of Code.mil!** We want to provide guidance on how you, a DoW project owner, can release your code as open source software and why it is in your best interest. ### 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). -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..." +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 War shall initiate for the Department of War the open source software pilot program established by the Office of Management and Budget Memorandum M-16-21..."