├── .gitattributes ├── doc └── Screenshot.png ├── INSTALL.md ├── .github ├── ISSUE_TEMPLATE.md └── PULL_REQUEST_TEMPLATE.md ├── CHANGELOG.md ├── .gitignore ├── CONTRIBUTING.md ├── TERMS.md ├── SECURITY.md ├── README.md └── LICENSE /.gitattributes: -------------------------------------------------------------------------------- 1 | /CHANGELOG.md merge=union 2 | -------------------------------------------------------------------------------- /doc/Screenshot.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/NOAA-OWP/owp-open-source-project-template/HEAD/doc/Screenshot.png -------------------------------------------------------------------------------- /INSTALL.md: -------------------------------------------------------------------------------- 1 | # Installation instructions 2 | 3 | Detailed instructions on how to install, configure, and get the project running. 4 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | Short description explaining the high-level reason for the new issue. 2 | 3 | ## Current behavior 4 | 5 | 6 | ## Expected behavior 7 | 8 | 9 | ## Steps to replicate behavior (include URLs) 10 | 11 | 1. 12 | 13 | 14 | ## Screenshots 15 | 16 | 17 | 18 | -------------------------------------------------------------------------------- /CHANGELOG.md: -------------------------------------------------------------------------------- 1 | All notable changes to this project will be documented in this file. 2 | We follow the [Semantic Versioning 2.0.0](http://semver.org/) format. 3 | 4 | 5 | ## x.y.z - YYYY-MM-DD 6 | 7 | ### Added 8 | 9 | - Lorem ipsum dolor sit amet 10 | 11 | ### Deprecated 12 | 13 | - Nothing. 14 | 15 | ### Removed 16 | 17 | - Nothing. 18 | 19 | ### Fixed 20 | 21 | - Nothing. 22 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | # Compiled source # 2 | ################### 3 | *.com 4 | *.class 5 | *.dll 6 | *.exe 7 | *.o 8 | *.so 9 | _site/ 10 | 11 | # Packages # 12 | ############ 13 | # it's better to unpack these files and commit the raw source 14 | # git has its own built in compression methods 15 | *.7z 16 | *.dmg 17 | *.gz 18 | *.iso 19 | *.jar 20 | *.rar 21 | *.tar 22 | *.zip 23 | 24 | # Logs and databases # 25 | ###################### 26 | *.log 27 | *.sql 28 | *.sqlite 29 | 30 | # OS generated files # 31 | ###################### 32 | .DS_Store 33 | .DS_Store? 34 | .Spotlight-V100 35 | .Trashes 36 | Icon? 37 | ehthumbs.db 38 | Thumbs.db 39 | 40 | # Vim swap files # 41 | ################## 42 | *.swp 43 | 44 | # Python # 45 | ################# 46 | *.pyc 47 | *.egg-info/ 48 | __pycache__/ 49 | *.py[cod] 50 | .env 51 | .python-version 52 | 53 | # pyenv # 54 | ######### 55 | .python-version 56 | 57 | # Django # 58 | ################# 59 | *.egg-info 60 | .installed.cfg 61 | 62 | # Unit test / coverage reports 63 | ################# 64 | htmlcov/ 65 | .tox/ 66 | .coverage 67 | .cache 68 | nosetests.xml 69 | coverage.xml 70 | 71 | # Front-End # 72 | ############# 73 | node_modules/ 74 | bower_components/ 75 | .grunt/ 76 | src/vendor/ 77 | dist/ 78 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Guidance on how to contribute 2 | 3 | > All contributions to this project will be released to the public domain. 4 | > By submitting a pull request or filing a bug, issue, or 5 | > feature request, you are agreeing to comply with this waiver of copyright interest. 6 | > Details can be found in our [TERMS](TERMS.md) and [LICENSE](LICENSE). 7 | 8 | 9 | There are two primary ways to help: 10 | - Using the issue tracker, and 11 | - Changing the code-base. 12 | 13 | 14 | ## Using the issue tracker 15 | 16 | Use the issue tracker to suggest feature requests, report bugs, and ask questions. 17 | This is also a great way to connect with the developers of the project as well 18 | as others who are interested in this solution. 19 | 20 | Use the issue tracker to find ways to contribute. Find a bug or a feature, mention in 21 | the issue that you will take on that effort, then follow the _Changing the code-base_ 22 | guidance below. 23 | 24 | 25 | ## Changing the code-base 26 | 27 | Generally speaking, you should fork this repository, make changes in your 28 | own fork, and then submit a pull request. All new code should have associated 29 | unit tests that validate implemented features and the presence or lack of defects. 30 | Additionally, the code should follow any stylistic and architectural guidelines 31 | prescribed by the project. In the absence of such guidelines, mimic the styles 32 | and patterns in the existing code-base. 33 | -------------------------------------------------------------------------------- /TERMS.md: -------------------------------------------------------------------------------- 1 | ## Disclaimer 2 | 3 | This repository is a scientific product and is not official communication of the National Oceanic and Atmospheric Administration, or the United States Department of Commerce. All NOAA GitHub project code is provided on an 'as is' basis and the user assumes responsibility for its use. Any claims against the Department of Commerce or Department of Commerce bureaus stemming from the use of this GitHub project will be governed by all applicable Federal law. Any reference to specific commercial products, processes, or services by service mark, trademark, manufacturer, or otherwise, does not constitute or imply their endorsement, recommendation or favoring by the Department of Commerce. The Department of Commerce seal and logo, or the seal and logo of a DOC bureau, shall not be used in any manner to imply endorsement of any commercial product or activity by DOC or the United States Government. 4 | 5 | [NOAA GitHub Policy](https://github.com/NOAAGov/Information) 6 | 7 | ### Other Information 8 | 9 | Unless expressly stated otherwise, the person who associated a work with 10 | this deed makes no warranties about the work, and disclaims liability for 11 | all uses of the work, to the fullest extent permitted by applicable law. 12 | When using or citing the work, you should not imply endorsement by the 13 | author or the affirmer. 14 | 15 | ## Exceptions 16 | 17 | _Source code or other assets that are excluded from the TERMS should be listed 18 | here. These may include dependencies that may be licensed differently or are 19 | not in the public domain._ 20 | -------------------------------------------------------------------------------- /.github/PULL_REQUEST_TEMPLATE.md: -------------------------------------------------------------------------------- 1 | [Short description explaining the high-level reason for the pull request] 2 | 3 | ## Additions 4 | 5 | - 6 | 7 | ## Removals 8 | 9 | - 10 | 11 | ## Changes 12 | 13 | - 14 | 15 | ## Testing 16 | 17 | 1. 18 | 19 | ## Screenshots 20 | 21 | 22 | ## Notes 23 | 24 | - 25 | 26 | ## Todos 27 | 28 | - 29 | 30 | ## Checklist 31 | 32 | - [ ] PR has an informative and human-readable title 33 | - [ ] Changes are limited to a single goal (no scope creep) 34 | - [ ] Code can be automatically merged (no conflicts) 35 | - [ ] Code follows project standards (link if applicable) 36 | - [ ] Passes all existing automated tests 37 | - [ ] Any _change_ in functionality is tested 38 | - [ ] New functions are documented (with a description, list of inputs, and expected output) 39 | - [ ] Placeholder code is flagged / future todos are captured in comments 40 | - [ ] Visually tested in supported browsers and devices (see checklist below :point_down:) 41 | - [ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG) 42 | - [ ] Reviewers requested with the [Reviewers tool](https://help.github.com/articles/requesting-a-pull-request-review/) :arrow_right: 43 | 44 | ## Testing checklist 45 | 46 | ### Target Environment support 47 | 48 | - [ ] Windows 49 | - [ ] Linux 50 | - [ ] Browser 51 | 52 | ### Accessibility 53 | 54 | - [ ] Keyboard friendly 55 | - [ ] Screen reader friendly 56 | 57 | ### Other 58 | 59 | - [ ] Is useable without CSS 60 | - [ ] Is useable without JS 61 | - [ ] Flexible from small to large screens 62 | - [ ] No linting errors or warnings 63 | - [ ] JavaScript tests are passing 64 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | # Security Policy 2 | 3 | There MUST be no unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days. 4 | 5 | The vulnerability must be patched and released by the project itself (patches may be developed elsewhere). A vulnerability becomes publicly known (for this purpose) once it has a CVE with publicly released non-paywalled information (reported, for example, in the National Vulnerability Database) or when the project has been informed and the information has been released to the public (possibly by the project). A vulnerability is considered medium or higher severity if its Common Vulnerability Scoring System (CVSS) base qualitative score is medium or higher. In CVSS versions 2.0 through 3.1, this is equivalent to a CVSS score of 4.0 or higher. Projects may use the CVSS score as published in a widely-used vulnerability database (such as the National Vulnerability Database) using the most-recent version of CVSS reported in that database. Projects may instead calculate the severity themselves using the latest version of CVSS at the time of the vulnerability disclosure, if the calculation inputs are publicly revealed once the vulnerability is publicly known. Note: this means that users might be left vulnerable to all attackers worldwide for up to 60 days. This criterion is often much easier to meet than what Google recommends in Rebooting responsible disclosure, because Google recommends that the 60-day period start when the project is notified _even_ if the report is not public. Also note that this badge criterion, like other criteria, applies to the individual project. Some projects are part of larger umbrella organizations or larger projects, possibly in multiple layers, and many projects feed their results to other organizations and projects as part of a potentially-complex supply chain. An individual project often cannot control the rest, but an individual project can work to release a vulnerability patch in a timely way. Therefore, we focus solely on the individual project's response time. Once a patch is available from the individual project, others can determine how to deal with the patch (e.g., they can update to the newer version or they can apply just the patch as a cherry-picked solution). 6 | 7 | The public repositories MUST NOT leak any valid private credential (e.g., a working password or private key) that is intended to limit public access. 8 | 9 | ## Supported Versions 10 | 11 | Use this section to tell people about which versions of your project are 12 | currently being supported with security updates. 13 | 14 | | Version | Supported | 15 | | ------- | ------------------ | 16 | | 5.1.x | :white_check_mark: | 17 | | 5.0.x | :x: | 18 | | 4.0.x | :white_check_mark: | 19 | | < 4.0 | :x: | 20 | 21 | ## Reporting a Vulnerability 22 | 23 | Use this section to tell people how to report a vulnerability. 24 | 25 | Tell them where to go, how often they can expect to get an update on a 26 | reported vulnerability, what to expect if the vulnerability is accepted or 27 | declined, etc. 28 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | #### OWP Open Source Project Template Instructions 2 | 3 | 1. Create a new project. 4 | 2. [Copy these files into the new project](#installation) 5 | 3. Update the README, replacing the contents below as prescribed. 6 | 4. Add any libraries, assets, or hard dependencies whose source code will be included 7 | in the project's repository to the _Exceptions_ section in the [TERMS](TERMS.md). 8 | - If no exceptions are needed, remove that section from TERMS. 9 | 5. If working with an existing code base, answer the questions on the [open source checklist](opensource-checklist.md) 10 | 6. Delete these instructions and everything up to the _Project Title_ from the README. 11 | 7. Write some great software and tell people about it. 12 | 13 | > Keep the README fresh! It's the first thing people see and will make the initial impression. 14 | 15 | ## Installation 16 | 17 | To install all of the template files, run the following script from the root of your project's directory: 18 | 19 | ``` 20 | bash -c "$(curl -s https://raw.githubusercontent.com/NOAA-OWP/owp-open-source-project-template/open_source_template.sh)" 21 | ``` 22 | 23 | ---- 24 | 25 | # Project Title 26 | 27 | **Description**: Put a meaningful, short, plain-language description of what 28 | this project is trying to accomplish and why it matters. 29 | Describe the problem(s) this project solves. 30 | Describe how this software can improve the lives of its audience. 31 | 32 | Other things to include: 33 | 34 | - **Technology stack**: Indicate the technological nature of the software, including primary programming language(s) and whether the software is intended as standalone or as a module in a framework or other ecosystem. 35 | - **Status**: Alpha, Beta, 1.1, etc. It's OK to write a sentence, too. The goal is to let interested people know where this project is at. This is also a good place to link to the [CHANGELOG](CHANGELOG.md). 36 | - **Links to production or demo instances** 37 | - Describe what sets this apart from related-projects. Linking to another doc or page is OK if this can't be expressed in a sentence or two. 38 | 39 | 40 | **Screenshot**: If the software has visual components, place a screenshot after the description; e.g., 41 | 42 | ![](https://raw.githubusercontent.com/NOAA-OWP/owp-open-source-project-template/master/doc/Screenshot.png) 43 | 44 | 45 | ## Dependencies 46 | 47 | Describe any dependencies that must be installed for this software to work. 48 | This includes programming languages, databases or other storage mechanisms, build tools, frameworks, and so forth. 49 | If specific versions of other software are required, or known not to work, call that out. 50 | 51 | ## Installation 52 | 53 | Detailed instructions on how to install, configure, and get the project running. 54 | This should be frequently tested to ensure reliability. Alternatively, link to 55 | a separate [INSTALL](INSTALL.md) document. 56 | 57 | ## Configuration 58 | 59 | If the software is configurable, describe it in detail, either here or in other documentation to which you link. 60 | 61 | ## Usage 62 | 63 | Show users how to use the software. 64 | Be specific. 65 | Use appropriate formatting when showing code snippets. 66 | 67 | ## How to test the software 68 | 69 | If the software includes automated tests, detail how to run those tests. 70 | 71 | ## Known issues 72 | 73 | Document any known significant shortcomings with the software. 74 | 75 | ## Getting help 76 | 77 | Instruct users how to get help with this software; this might include links to an issue tracker, wiki, mailing list, etc. 78 | 79 | **Example** 80 | 81 | If you have questions, concerns, bug reports, etc, please file an issue in this repository's Issue Tracker. 82 | 83 | ## Getting involved 84 | 85 | This section should detail why people should get involved and describe key areas you are 86 | currently focusing on; e.g., trying to get feedback on features, fixing certain bugs, building 87 | important pieces, etc. 88 | 89 | General instructions on _how_ to contribute should be stated with a link to [CONTRIBUTING](CONTRIBUTING.md). 90 | 91 | 92 | ---- 93 | 94 | ## Open source licensing info 95 | 96 | These links must be included in the final version of your project README (keep this section, 97 | as is, but remove this sentence): 98 | 99 | 1. [TERMS](TERMS.md) 100 | 2. [LICENSE](LICENSE) 101 | 102 | 103 | ---- 104 | 105 | ## Credits and references 106 | 107 | 1. Projects that inspired you 108 | 2. Related projects 109 | 3. Books, papers, talks, or other sources that have meaningful impact or influence on this project 110 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | 2 | Apache License 3 | Version 2.0, January 2004 4 | http://www.apache.org/licenses/ 5 | 6 | TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 7 | 8 | 1. Definitions. 9 | 10 | "License" shall mean the terms and conditions for use, reproduction, 11 | and distribution as defined by Sections 1 through 9 of this document. 12 | 13 | "Licensor" shall mean the copyright owner or entity authorized by 14 | the copyright owner that is granting the License. 15 | 16 | "Legal Entity" shall mean the union of the acting entity and all 17 | other entities that control, are controlled by, or are under common 18 | control with that entity. For the purposes of this definition, 19 | "control" means (i) the power, direct or indirect, to cause the 20 | direction or management of such entity, whether by contract or 21 | otherwise, or (ii) ownership of fifty percent (50%) or more of the 22 | outstanding shares, or (iii) beneficial ownership of such entity. 23 | 24 | "You" (or "Your") shall mean an individual or Legal Entity 25 | exercising permissions granted by this License. 26 | 27 | "Source" form shall mean the preferred form for making modifications, 28 | including but not limited to software source code, documentation 29 | source, and configuration files. 30 | 31 | "Object" form shall mean any form resulting from mechanical 32 | transformation or translation of a Source form, including but 33 | not limited to compiled object code, generated documentation, 34 | and conversions to other media types. 35 | 36 | "Work" shall mean the work of authorship, whether in Source or 37 | Object form, made available under the License, as indicated by a 38 | copyright notice that is included in or attached to the work 39 | (an example is provided in the Appendix below). 40 | 41 | "Derivative Works" shall mean any work, whether in Source or Object 42 | form, that is based on (or derived from) the Work and for which the 43 | editorial revisions, annotations, elaborations, or other modifications 44 | represent, as a whole, an original work of authorship. For the purposes 45 | of this License, Derivative Works shall not include works that remain 46 | separable from, or merely link (or bind by name) to the interfaces of, 47 | the Work and Derivative Works thereof. 48 | 49 | "Contribution" shall mean any work of authorship, including 50 | the original version of the Work and any modifications or additions 51 | to that Work or Derivative Works thereof, that is intentionally 52 | submitted to Licensor for inclusion in the Work by the copyright owner 53 | or by an individual or Legal Entity authorized to submit on behalf of 54 | the copyright owner. For the purposes of this definition, "submitted" 55 | means any form of electronic, verbal, or written communication sent 56 | to the Licensor or its representatives, including but not limited to 57 | communication on electronic mailing lists, source code control systems, 58 | and issue tracking systems that are managed by, or on behalf of, the 59 | Licensor for the purpose of discussing and improving the Work, but 60 | excluding communication that is conspicuously marked or otherwise 61 | designated in writing by the copyright owner as "Not a Contribution." 62 | 63 | "Contributor" shall mean Licensor and any individual or Legal Entity 64 | on behalf of whom a Contribution has been received by Licensor and 65 | subsequently incorporated within the Work. 66 | 67 | 2. Grant of Copyright License. Subject to the terms and conditions of 68 | this License, each Contributor hereby grants to You a perpetual, 69 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 70 | copyright license to reproduce, prepare Derivative Works of, 71 | publicly display, publicly perform, sublicense, and distribute the 72 | Work and such Derivative Works in Source or Object form. 73 | 74 | 3. Grant of Patent License. Subject to the terms and conditions of 75 | this License, each Contributor hereby grants to You a perpetual, 76 | worldwide, non-exclusive, no-charge, royalty-free, irrevocable 77 | (except as stated in this section) patent license to make, have made, 78 | use, offer to sell, sell, import, and otherwise transfer the Work, 79 | where such license applies only to those patent claims licensable 80 | by such Contributor that are necessarily infringed by their 81 | Contribution(s) alone or by combination of their Contribution(s) 82 | with the Work to which such Contribution(s) was submitted. If You 83 | institute patent litigation against any entity (including a 84 | cross-claim or counterclaim in a lawsuit) alleging that the Work 85 | or a Contribution incorporated within the Work constitutes direct 86 | or contributory patent infringement, then any patent licenses 87 | granted to You under this License for that Work shall terminate 88 | as of the date such litigation is filed. 89 | 90 | 4. Redistribution. You may reproduce and distribute copies of the 91 | Work or Derivative Works thereof in any medium, with or without 92 | modifications, and in Source or Object form, provided that You 93 | meet the following conditions: 94 | 95 | (a) You must give any other recipients of the Work or 96 | Derivative Works a copy of this License; and 97 | 98 | (b) You must cause any modified files to carry prominent notices 99 | stating that You changed the files; and 100 | 101 | (c) You must retain, in the Source form of any Derivative Works 102 | that You distribute, all copyright, patent, trademark, and 103 | attribution notices from the Source form of the Work, 104 | excluding those notices that do not pertain to any part of 105 | the Derivative Works; and 106 | 107 | (d) If the Work includes a "NOTICE" text file as part of its 108 | distribution, then any Derivative Works that You distribute must 109 | include a readable copy of the attribution notices contained 110 | within such NOTICE file, excluding those notices that do not 111 | pertain to any part of the Derivative Works, in at least one 112 | of the following places: within a NOTICE text file distributed 113 | as part of the Derivative Works; within the Source form or 114 | documentation, if provided along with the Derivative Works; or, 115 | within a display generated by the Derivative Works, if and 116 | wherever such third-party notices normally appear. The contents 117 | of the NOTICE file are for informational purposes only and 118 | do not modify the License. You may add Your own attribution 119 | notices within Derivative Works that You distribute, alongside 120 | or as an addendum to the NOTICE text from the Work, provided 121 | that such additional attribution notices cannot be construed 122 | as modifying the License. 123 | 124 | You may add Your own copyright statement to Your modifications and 125 | may provide additional or different license terms and conditions 126 | for use, reproduction, or distribution of Your modifications, or 127 | for any such Derivative Works as a whole, provided Your use, 128 | reproduction, and distribution of the Work otherwise complies with 129 | the conditions stated in this License. 130 | 131 | 5. Submission of Contributions. Unless You explicitly state otherwise, 132 | any Contribution intentionally submitted for inclusion in the Work 133 | by You to the Licensor shall be under the terms and conditions of 134 | this License, without any additional terms or conditions. 135 | Notwithstanding the above, nothing herein shall supersede or modify 136 | the terms of any separate license agreement you may have executed 137 | with Licensor regarding such Contributions. 138 | 139 | 6. Trademarks. This License does not grant permission to use the trade 140 | names, trademarks, service marks, or product names of the Licensor, 141 | except as required for reasonable and customary use in describing the 142 | origin of the Work and reproducing the content of the NOTICE file. 143 | 144 | 7. Disclaimer of Warranty. Unless required by applicable law or 145 | agreed to in writing, Licensor provides the Work (and each 146 | Contributor provides its Contributions) on an "AS IS" BASIS, 147 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or 148 | implied, including, without limitation, any warranties or conditions 149 | of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A 150 | PARTICULAR PURPOSE. You are solely responsible for determining the 151 | appropriateness of using or redistributing the Work and assume any 152 | risks associated with Your exercise of permissions under this License. 153 | 154 | 8. Limitation of Liability. In no event and under no legal theory, 155 | whether in tort (including negligence), contract, or otherwise, 156 | unless required by applicable law (such as deliberate and grossly 157 | negligent acts) or agreed to in writing, shall any Contributor be 158 | liable to You for damages, including any direct, indirect, special, 159 | incidental, or consequential damages of any character arising as a 160 | result of this License or out of the use or inability to use the 161 | Work (including but not limited to damages for loss of goodwill, 162 | work stoppage, computer failure or malfunction, or any and all 163 | other commercial damages or losses), even if such Contributor 164 | has been advised of the possibility of such damages. 165 | 166 | 9. Accepting Warranty or Additional Liability. While redistributing 167 | the Work or Derivative Works thereof, You may choose to offer, 168 | and charge a fee for, acceptance of support, warranty, indemnity, 169 | or other liability obligations and/or rights consistent with this 170 | License. However, in accepting such obligations, You may act only 171 | on Your own behalf and on Your sole responsibility, not on behalf 172 | of any other Contributor, and only if You agree to indemnify, 173 | defend, and hold each Contributor harmless for any liability 174 | incurred by, or claims asserted against, such Contributor by reason 175 | of your accepting any such warranty or additional liability. 176 | 177 | END OF TERMS AND CONDITIONS 178 | 179 | APPENDIX: How to apply the Apache License to your work. 180 | 181 | To apply the Apache License to your work, attach the following 182 | boilerplate notice, with the fields enclosed by brackets "[]" 183 | replaced with your own identifying information. (Don't include 184 | the brackets!) The text should be enclosed in the appropriate 185 | comment syntax for the file format. We also recommend that a 186 | file or class name and description of purpose be included on the 187 | same "printed page" as the copyright notice for easier 188 | identification within third-party archives. 189 | 190 | Copyright [yyyy] [name of copyright owner] 191 | 192 | Licensed under the Apache License, Version 2.0 (the "License"); 193 | you may not use this file except in compliance with the License. 194 | You may obtain a copy of the License at 195 | 196 | http://www.apache.org/licenses/LICENSE-2.0 197 | 198 | Unless required by applicable law or agreed to in writing, software 199 | distributed under the License is distributed on an "AS IS" BASIS, 200 | WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 201 | See the License for the specific language governing permissions and 202 | limitations under the License. 203 | 204 | - - - - - - - - - - - - - - 205 | 206 | “Software code created by U.S. Government employees is not subject to copyright in the 207 | United States (17 U.S.C. §105). The United States/Department of Commerce reserves all 208 | rights to seek and obtain copyright protection in countries other than the United States 209 | for Software authored in its entirety by the Department of Commerce. To this end, the 210 | Department of Commerce hereby grants to Recipient a royalty-free, nonexclusive license 211 | to use, copy, and create derivative works of the Software outside of the United States.” 212 | --------------------------------------------------------------------------------