-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Inconsitency in file license-list-data/json/licenses.json #1676
Comments
Hi @goneall Could you please have a look at this issue? |
@vargenau The name is getting pulled from the license XML This is more of a policy question as to whether names should be the same or different and if there even needs to be a consistency on the names for deprecated license names. Once the policy is decided, the license XML's may need to be updated. Since the names are more informative and are not required to be unique, I think it would be OK to update the names for existing licenses. |
Thanks @vargenau - the license-list-data should update within an hour of those PR's being merged. |
Hi @goneall Could you please merge these pull requests? Thank you |
Thanks @vargenau for the attention to detail on these!
Based on that, I'm going to go ahead and close this issue after closing #1712 and #1713. Thanks all! |
In file
license-list-data/json/licenses.json
you have:In short, you have the same "name" for both the deprecated license and the replacement license.
This is true for:
But it is not the case for other deprecated licenses.
For example, you have:
and
Also:
and
I would expect that you have the same "name" for both the deprecated license and the replacement license.
The text was updated successfully, but these errors were encountered: