Updates comment to point to new data source for the license list. The SPDX have recently made a GitHub repository available containing a JSON formatted license list for easier programmatic consumption.
The outdated list of licenses causes some users to experience lower scores on License checks, in addition including licenses that are not FSF/OSI-approved.
What is the new behavior (if this is a feature change)?**
The updated list of licenses should help prevent these issues.
[ ] Tests for the changes have been added (for bug fixes/features)
Which issue(s) this PR fixes
Fixes #4031
Special notes for your reviewer
For now, this just updates the list of licenses. A future enhancement can be added to programmatically fetch the licenses from the SPDX repo, and format the data in the way that fsfOsiApprovedLicenseMap expects.
Does this PR introduce a user-facing change?
Updates list of supported SDPX licenses to include latest data.
What kind of change does this PR introduce?
Updates the existing SPDX license list to include the latest data from SPDX.
Updates comment to point to new data source for the license list. The SPDX have recently made a GitHub repository available containing a JSON formatted license list for easier programmatic consumption.
[x] PR title follows the guidelines defined in our pull request documentation
What is the current behavior?
The outdated list of licenses causes some users to experience lower scores on License checks, in addition including licenses that are not FSF/OSI-approved.
What is the new behavior (if this is a feature change)?**
The updated list of licenses should help prevent these issues.
Which issue(s) this PR fixes
Fixes #4031
Special notes for your reviewer
For now, this just updates the list of licenses. A future enhancement can be added to programmatically fetch the licenses from the SPDX repo, and format the data in the way that
fsfOsiApprovedLicenseMapexpects.Does this PR introduce a user-facing change?