This repo contains the policies and discussions for the USACE organization. The Github org USACE is unofficially associated with the USACE enterprise and is managed by a group of volunteers.
General disclaimer This organization was created for use by USACE programs to collaborate on projects in support of the USACE mission. GitHub is not hosted by USACE, but is a third party website used by USACE and its partners to share information and collaborate on software. USACE use of GitHub does not imply an endorsement of any one particular service, product, or enterprise.
There are few requirements for participating in the USACE organization, and some recommendations below:
In order to access non-public resources on the USACE organization, you will need to set up a GitHub account. Each member of the organization must have an individual account, sharing account credentials violates the GitHub terms of service, your cyber security training, and common sense.
We understand there are reasons for maintaining a pseudonymous profile on Github, we do requre that the profile you use as a member of this organization be set up so that we can collaborate more effectively, as of 6-Oct-2023 we will be requiring all member profiles to include:
- Name: Your first and last name.
- Company: Your government agency or contracting company. (If you also use GitHub for personal projects, consider specifying “USACE (work) + personal projects” to make it clear that some of your GitHub projects may be personal in nature.)
- Location: Your primary work location (city, state).
- Photo: A headshot photo, or an appropriate image that is unique to you.
Note that if you do not want to mix your work and personal profile, we recommend you create a separate account tied to your work e-mail address and use that for USACE projects.
You must have 2-Factor authentication turned on for your account, this is just a good idea in general.
We don't have a very formal process right now, reach out to Will Breitkreutz, Lyle Seethaler or Randy Goss (find e-mails in outlook, not going to put them here) via USACE e-mail to request access or new repositories.
We aren't going to be enforcing these, but as a general rule, it's a good idea to set up your project with the following notices and license. Feel free to use another license, the Apache 2 license lines up pretty well with the overall regulations, MIT is another good option.
This repository constitutes a work of the United States Government and is not subject to domestic copyright protection under 17 USC § 105. This repository 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 repository will be released under the CC0 dedication. By submitting a pull request you are agreeing to comply with this waiver of copyright interest.
The repository utilizes code licensed under the terms of the Apache Software License and therefore is licensed under ASL v2 or later.
This source code in this repository is free: you can redistribute it and/or modify it under the terms of the Apache Software License version 2, or (at your option) any later version.
This source code in this repository is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the Apache Software License for more details.
You should have received a copy of the Apache Software License along with this program. If not, see http://www.apache.org/licenses/LICENSE-2.0.html
The source code forked from other open source projects will inherit its license.
This repository contains only non-sensitive, publicly available data and information.