Add license according to new NOAA Administrative Order on NOAA developed software and code #36
Description
Follow best practices in the NAO-201-118 by adding licenses to our repository. More specifically, add LICENSE and INTENT files with an Apache 2.0 license.
Eli shared in a few google spaces on Nov. 22:
FYI , today the new NOAA Administrative Order (NAO) on NOAA developed software and code was released: https://www.noaa.gov/administration/nao-201-118-software-governance-and-public-release-policy
Key points: Code should be Open Source to the extent possible, use version-control and shared repos (standard norms for code development), and apply open licenses to code. I added some info on this NAO to https://nmfs-opensci.github.io/GitHub-Guide/#noaa-and-open-source-software
In a follow up conversation thread in 2024-NMFS-Champions space, she clarified:
The new NOAA policy for Open Source software recommends Apache 2.0 for software and CC0 for data/content.
The NMFS open science website includes templates for exactly what those files should look like. I would say we go with Apache 2.0 for VMS-Pipeline, since this repository is code rather than figures. If we fork it for a publication and add figures or data, then I think that repository should have a Creative Commons CC0 license instead, since that's the recommendation for data and content.