You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When comparing the result we get from ClearlyDefined with our approved license list, our code chokes on OTHER for some packages because that's not a known SPDX license. Perhaps the intention is for tools to produce errors on that, but I wonder if it would better to at least produce a valid SPDX license so that people can make a decision about what to do with it without tools/libraries just erroring. It could be, for example, LicenseRef-clearlydefined-other.
When comparing the result we get from ClearlyDefined with our approved license list, our code chokes on
OTHER
for some packages because that's not a known SPDX license. Perhaps the intention is for tools to produce errors on that, but I wonder if it would better to at least produce a valid SPDX license so that people can make a decision about what to do with it without tools/libraries just erroring. It could be, for example,LicenseRef-clearlydefined-other
.OTHER was added in response to #522
Perhaps @royaljust has an opinion about this?
The text was updated successfully, but these errors were encountered: