https://github.com/18F/bpa-fs-epermit-intake : 003QASP.md
18F intends that any data or deliverable created as a result of the work performed under the call order be committed to the public domain.
Further, 18F intends to commit the following items, to the public domain, at a minimum:
- All data, documents, graphics and code created under this call order including but not limited to, plans, reports, schedules, schemas, metadata, architecture designs, and the like;
- Any and all new open source software created by the contractor and forks or branches of current open source software where the contractor has made a modification; and,
- Any and all new tooling, scripting configuration management, infrastructure as code, or any other final changes or edits to successfully deploy or operate the software.
The contractor shall use open source technologies wherever possible, in support of the 18F Source Code Policy. All licenses must be expressly listed in the deliverable. Regardless of license(s) used (e.g., MIT, GPL, Creative Commons 0) the license(s) shall be clearly listed in the documentation.
If the contractor needs to use work that does not have an open source license, the contractor is required to request permission from 18F, in writing, before utilizing that work in any way in connection with the order. If approved, all licenses shall be clearly set forth in a conspicuous place when work is delivered to 18F.
If an open source license provides implementation guidance, the contractor shall ensure compliance with that guidance. If implementation guidance is not available, the contractor shall attach or include the license within the work itself. Examples of this include code comments at the beginning of a file or contained in a license file within a software repository.