Thank you for contributing to CDC's Open Source projects! If you have any questions or doubts, don't be afraid to send them our way. We appreciate all contributions, and we are looking forward to fostering an open, transparent, and collaborative environment.

Before contributing, we encourage you to also read or LICENSE, README, and code-of-conduct files, also found in this repository. If you have any inquiries or questions not answered by the content of this repository, feel free to contact us.

This project is in the public domain within the United States, and copyright and related rights in the work worldwide are waived through the CC0 1.0 Universal public domain dedication. All contributions to this project will be released under the CC0 dedication. By submitting a pull request you are agreeing to comply with this waiver of copyright interest.

Our pull request/merging process is designed to give the CDC DHQP Team and others in our space an opportunity to consider and discuss any suggested changes. This policy affects all CDC spaces, both on-line and off, and all users are expected to abide by it.

If you don't have specific language (code) to submit, but would like to suggest a change or have something addressed, you can open an issue in this repository. Team members will respond to the issue as soon as possible.

When submitting an issue please provide a reproducible example that will allow someone else to recreate your problem.

There are four things you need to include to make your example reproducible:

1. What environment you are running Quaisar (i.e. HPC, local, cloud etc) in
2. What version you are using
3. The command that was run to cause the error
4. The text of the error itself
5. Include the files that caused the error (if the files contain sensitive information email HAISeq@cdc.gov with the title QH ISSUE #).

If you would like to contribute, please submit a pull request. In order for us to merge a pull request, it must:

• Be at least seven days old. Pull requests may be held longer if necessary to give people the opportunity to assess it.
• Receive a +1 from a majority of team members associated with the request. If there is significant dissent between the team, a meeting will be held to discuss a plan of action for the pull request.

For further information or help, don't hesitate to get in touch on the Slack #quaisar-h-dev channel.