Create DISCLAIMER.md

[jlaura]

For a formal USGS software release, the code to be released must have an official disclaimer as approved by USGS. This PR adds this disclaimer.

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Documentation change (update to the documentation; no code change)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have read and agree to abide by the Code of Conduct
• I have read the CONTRIBUTING document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• I have added myself to the .zenodo.json document.
• I have added any user impacting changes to the CHANGELOG.md document.

Licensing

This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

• I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

[jlaura]

This can be reviewed and approved (assuming it looks good), but can not be merged until the approval process is completed. I am getting this staged for the release.

[rfergason]

This disclaimer is appropriate and correct for this particular software application, and is compliant with USGS Fundamental Science Practices.

[acpaquette]

@jlaura Can this be merged/ready for review?

[jlaura]

We are at SCD approval. Hopefully mergeable Monday. :) Thanks for staying on top of this!