## Expected Behavior Licenses that are the same should have the same name in the repo metadata. Came up in addressing https://github.com/GSA/code-gov-web/issues/543 ## Current Behavior License names aren't standardized. For example, the license could be `CC0` or `Creative Commons Zero (CC0)`. ## Possible Solution - Enforce License Standardization in code.json like what NPMJS does for their package.json - https://docs.npmjs.com/files/package.json#license - https://spdx.org/licenses/ - When harvesting, map possible license values in code.json to SPDX term ## Steps to Reproduce (for bugs) - https://beta.observablehq.com/@danieljdufour/licenses-of-projects-on-code-gov ## Context <!--- How has this issue affected you? What are you trying to accomplish? --> <!--- Providing context helps us come up with a solution that is most useful in the real world --> This makes it difficult for users to determine the distribution of licenses across code.gov ### Caveats - We have to balance the needs to standardize license names while allowing agencies flexibility to specify their license.
Expected Behavior
Licenses that are the same should have the same name in the repo metadata. Came up in addressing #543
Current Behavior
License names aren't standardized. For example, the license could be
CC0orCreative Commons Zero (CC0).Possible Solution
Steps to Reproduce (for bugs)
Context
This makes it difficult for users to determine the distribution of licenses across code.gov
Caveats