diff --git a/python/ngen_config_gen/CONTRIBUTING.md b/python/ngen_config_gen/CONTRIBUTING.md deleted file mode 100644 index 0f109b26..00000000 --- a/python/ngen_config_gen/CONTRIBUTING.md +++ /dev/null @@ -1,32 +0,0 @@ -# Guidance on how to contribute - -> All contributions to this project will be released to the public domain. -> By submitting a pull request or filing a bug, issue, or -> feature request, you are agreeing to comply with this waiver of copyright interest. -> Details can be found in our [TERMS](TERMS.md) and [LICENSE](LICENSE). - - -There are two primary ways to help: - - Using the issue tracker, and - - Changing the code-base. - - -## Using the issue tracker - -Use the issue tracker to suggest feature requests, report bugs, and ask questions. -This is also a great way to connect with the developers of the project as well -as others who are interested in this solution. - -Use the issue tracker to find ways to contribute. Find a bug or a feature, mention in -the issue that you will take on that effort, then follow the _Changing the code-base_ -guidance below. - - -## Changing the code-base - -Generally speaking, you should fork this repository, make changes in your -own fork, and then submit a pull request. All new code should have associated -unit tests that validate implemented features and the presence or lack of defects. -Additionally, the code should follow any stylistic and architectural guidelines -prescribed by the project. In the absence of such guidelines, mimic the styles -and patterns in the existing code-base. diff --git a/python/ngen_config_gen/CONTRIBUTING.md b/python/ngen_config_gen/CONTRIBUTING.md new file mode 120000 index 00000000..f939e75f --- /dev/null +++ b/python/ngen_config_gen/CONTRIBUTING.md @@ -0,0 +1 @@ +../../CONTRIBUTING.md \ No newline at end of file diff --git a/python/ngen_config_gen/LICENSE b/python/ngen_config_gen/LICENSE deleted file mode 100644 index a0230332..00000000 --- a/python/ngen_config_gen/LICENSE +++ /dev/null @@ -1,7 +0,0 @@ -“Software code created by U.S. Government employees is not subject to copyright -in the United States (17 U.S.C. §105). The United States/Department of Commerce -reserve all rights to seek and obtain copyright protection in countries other -than the United States for Software authored in its entirety by the Department -of Commerce. To this end, the Department of Commerce hereby grants to Recipient -a royalty-free, nonexclusive license to use, copy, and create derivative works -of the Software outside of the United States.” diff --git a/python/ngen_config_gen/LICENSE b/python/ngen_config_gen/LICENSE new file mode 120000 index 00000000..30cff740 --- /dev/null +++ b/python/ngen_config_gen/LICENSE @@ -0,0 +1 @@ +../../LICENSE \ No newline at end of file diff --git a/python/ngen_config_gen/SECURITY.md b/python/ngen_config_gen/SECURITY.md deleted file mode 100644 index 0cdd1d99..00000000 --- a/python/ngen_config_gen/SECURITY.md +++ /dev/null @@ -1,27 +0,0 @@ -# Security Policy - -There MUST be no unpatched vulnerabilities of medium or higher severity that have been publicly known for more than 60 days. - -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). - -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. - -## Supported Versions - -Use this section to tell people about which versions of your project are -currently being supported with security updates. - -| Version | Supported | -| ------- | ------------------ | -| 5.1.x | :white_check_mark: | -| 5.0.x | :x: | -| 4.0.x | :white_check_mark: | -| < 4.0 | :x: | - -## Reporting a Vulnerability - -Use this section to tell people how to report a vulnerability. - -Tell them where to go, how often they can expect to get an update on a -reported vulnerability, what to expect if the vulnerability is accepted or -declined, etc. diff --git a/python/ngen_config_gen/SECURITY.md b/python/ngen_config_gen/SECURITY.md new file mode 120000 index 00000000..42cce94f --- /dev/null +++ b/python/ngen_config_gen/SECURITY.md @@ -0,0 +1 @@ +../../SECURITY.md \ No newline at end of file diff --git a/python/ngen_config_gen/TERMS.md b/python/ngen_config_gen/TERMS.md deleted file mode 100644 index b49b176b..00000000 --- a/python/ngen_config_gen/TERMS.md +++ /dev/null @@ -1,19 +0,0 @@ -## Disclaimer - -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. - -[NOAA GitHub Policy](https://github.com/NOAAGov/Information) - -### Other Information - -Unless expressly stated otherwise, the person who associated a work with -this deed makes no warranties about the work, and disclaims liability for -all uses of the work, to the fullest extent permitted by applicable law. -When using or citing the work, you should not imply endorsement by the -author or the affirmer. - -## Exceptions - -_Source code or other assets that are excluded from the TERMS should be listed -here. These may include dependencies that may be licensed differently or are -not in the public domain._ diff --git a/python/ngen_config_gen/TERMS.md b/python/ngen_config_gen/TERMS.md new file mode 120000 index 00000000..873e35b9 --- /dev/null +++ b/python/ngen_config_gen/TERMS.md @@ -0,0 +1 @@ +../../TERMS.md \ No newline at end of file