Skip to content

Commit 2e0a3a7

Browse files
authored
Initial commit
0 parents  commit 2e0a3a7

15 files changed

+787
-0
lines changed

.gitattributes

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Normal text let sit to auto
2+
*.htm text
3+
*.html text
4+
*.css text
5+
*.js text
6+
7+
## Declare files that will always have LF (aka \n aka 10 aka 0x0a) line endings on checkout.
8+
*.sh text eol=lf
9+
*.md text eol=lf
10+
*.json text eol=lf
11+
*.yml text eol=lf
12+
*.csv text eol=lf
13+

.github/ISSUE_TEMPLATE/bug_report.md

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what feature is not working.
12+
13+
**Impact**
14+
Please describe the impact this bug is causing to your program or organization.
15+
16+
**To Reproduce**
17+
Steps to reproduce the behavior:
18+
1. Go to '...'
19+
2. Click on '....'
20+
3. Scroll down to '....'
21+
4. See error
22+
23+
**Expected behavior**
24+
A clear and concise description of what you expected to happen.
25+
26+
**Screenshots**
27+
If applicable, add screenshots to help explain your problem.
28+
29+
**Logs**
30+
If applicable, please attach logs to help describe your problem.
31+
32+
**Desktop (please complete the following information):**
33+
- OS: [e.g. iOS]
34+
- Browser [e.g. chrome, safari]
35+
- Version [e.g. 22]
36+
37+
**Smartphone (please complete the following information):**
38+
- Device: [e.g. iPhone6]
39+
- OS: [e.g. iOS8.1]
40+
- Browser [e.g. stock browser, safari]
41+
- Version [e.g. 22]
42+
43+
**Additional context**
44+
Add any other context about the problem here.
+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you'd like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

.github/ISSUE_TEMPLATE/maintenance.md

+18
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: Maintenance
3+
about: Questions and requests related to organizational support and maintenance
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**What type of help do you need?**
11+
12+
* [ ] Question
13+
* [ ] New Repo
14+
* [ ] Delete Repo
15+
* [ ] User Membership (please make sure new members are familiar with the [CDC open practices](https://github.com/CDCgov/template/blob/master/open_practices.md#profile-setup) and set up their profile with name and org info to help people collaborate with them)
16+
* [ ] Other
17+
18+
**Please describe how you'd like us to help.**
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
---
8+
9+
**Please describe the bug this fixes or the feature this adds.**
10+
11+
**Please describe how you tested this change. Include unit tests whenever possible.**
12+
13+
**Did you create or modify any associated documentation with this change? If documentation is not included in PR, please link to related documentation.**
14+
15+
**If you added or modified HTML, did you check that it was 508 compliant?**
16+
17+
**Please tag any specific reviewers you would like to review this PR**
18+
19+
**Please include the following checks for open source contributing?**
20+
21+
* [ ] Did you check for sensitive data, and remove any?
22+
* [ ] Are additional approvals needed for this change?
23+
* [ ] Are there potential vulnerabilities or licensing issues with any new dependencies introduced?
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
name: Vulnerability Maintenance
3+
about: Routine updates to address vulnerabilities.
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**What vulnerabilities does this PR remove or update?**
11+
12+
**Have you tested to make sure these updates do not cause unintended consequences?**
13+
14+
**Are these patch updates? minor? major?**

.vscode/settings.json

+8
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"cSpell.words": [
3+
"ATSDR",
4+
"CFPB",
5+
"ISSO",
6+
"cybersecurity"
7+
]
8+
}

CONTRIBUTING.md

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
# Welcome!
2+
Thank you for contributing to CDC's Open Source projects! If you have any
3+
questions or doubts, don't be afraid to send them our way. We appreciate all
4+
contributions, and we are looking forward to fostering an open, transparent, and
5+
collaborative environment.
6+
7+
Before contributing, we encourage you to also read or [LICENSE](https://github.com/CDCgov/template/blob/master/LICENSE),
8+
[README](https://github.com/CDCgov/template/blob/master/README.md), and
9+
[code-of-conduct](https://github.com/CDCgov/template/blob/master/code-of-conduct.md)
10+
files, also found in this repository. If you have any inquiries or questions not
11+
answered by the content of this repository, feel free to [contact us](mailto:[email protected]).
12+
13+
## Public Domain
14+
This project is in the public domain within the United States, and copyright and
15+
related rights in the work worldwide are waived through the [CC0 1.0 Universal public domain dedication](https://creativecommons.org/publicdomain/zero/1.0/).
16+
All contributions to this project will be released under the CC0 dedication. By
17+
submitting a pull request you are agreeing to comply with this waiver of
18+
copyright interest.
19+
20+
## Requesting Changes
21+
Our pull request/merging process is designed to give the CDC Surveillance Team
22+
and other in our space an opportunity to consider and discuss any suggested
23+
changes. This policy affects all CDC spaces, both on-line and off, and all users
24+
are expected to abide by it.
25+
26+
### Open an issue in the repository
27+
If you don't have specific language to submit but would like to suggest a change
28+
or have something addressed, you can open an issue in this repository. Team
29+
members will respond to the issue as soon as possible.
30+
31+
### Submit a pull request
32+
If you would like to contribute, please submit a pull request. In order for us
33+
to merge a pull request, it must:
34+
* Be at least seven days old. Pull requests may be held longer if necessary
35+
to give people the opportunity to assess it.
36+
* Receive a +1 from a majority of team members associated with the request.
37+
If there is significant dissent between the team, a meeting will be held to
38+
discuss a plan of action for the pull request.

DISCLAIMER.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# DISCLAIMER
2+
Use of this service is limited only to **non-sensitive and publicly available
3+
data**. Users must not use, share, or store any kind of sensitive data like
4+
health status, provision or payment of healthcare, Personally Identifiable
5+
Information (PII) and/or Protected Health Information (PHI), etc. under **ANY**
6+
circumstance.
7+
8+
Administrators for this service reserve the right to moderate all information
9+
used, shared, or stored with this service at any time. Any user that cannot
10+
abide by this disclaimer and Code of Conduct may be subject to action, up to
11+
and including revoking access to services.
12+
13+
The material embodied in this software is provided to you "as-is" and without
14+
warranty of any kind, express, implied or otherwise, including without
15+
limitation, any warranty of fitness for a particular purpose. In no event shall
16+
the Centers for Disease Control and Prevention (CDC) or the United States (U.S.)
17+
government be liable to you or anyone else for any direct, special, incidental,
18+
indirect or consequential damages of any kind, or any damages whatsoever,
19+
including without limitation, loss of profit, loss of use, savings or revenue,
20+
or the claims of third parties, whether or not CDC or the U.S. government has
21+
been advised of the possibility of such loss, however caused and on any theory
22+
of liability, arising out of or in connection with the possession, use or
23+
performance of this software.

0 commit comments

Comments
 (0)