SPDX IDs #25
Merged
SPDX IDs #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Newer named files are added. No removals in this commit. Signed-off-by: enyst <engel.nyst@gmail.com>
This commit is separate to revert easily, if js callbacks are necessary and redirections are not desired. Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Case of IDs, spaces consistency in json, order of attributes, fix bsl. Signed-off-by: enyst <engel.nyst@gmail.com>
(scrape.py and app.js) Also remove 'historical', it's not a category in OSI lists. Signed-off-by: enyst <engel.nyst@gmail.com>
Signed-off-by: enyst <engel.nyst@gmail.com>
Regenerate files included. Signed-off-by: enyst <engel.nyst@gmail.com>
|
I'd be fine with using SPDX case conventions throughout, including filenames. That's what I'd prefer, unless anyone objects, which is unlikely. |
|
(Though I admit all lowercase looks pretty. I guess this is an admission that I have even less of an opinion than stated above.) |
|
Well, all lowercase seemed very readable to me when working directly with the files. (Could it be because usual programming styles don't endorse much unrelated-to-words FiLENAminG? 😸. Even acronyms seem more predictable, or they're not often used.) An example for the opposite choice, this is how it looks with almost-spdx names, respecting case. I like it too. Though there are currently fewer and well-known licenses in the list (so the comparison may not be entirely clear). |
mlinksva
added a commit
that referenced
this pull request
Jan 15, 2018
except where: 1. rename is changing capitalization only, or 2. previous name was ambiguous (eg "apache" for "Apache-1.0") might make sense to handle these cases a different way, if at all
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switched to SPDX IDs for OSI approved licenses. File names also changed where necessary, however kept them all lowercase, to minimize changes this round.
Fixed a few other related bugs (Eiffel license, I believe, was duplicate, the BSD case had to be split). Added newer approved OSI licenses (last year or so), and updated data and scripts for consistency.
Removed the older named files and records about them.
I think the remaining question is:
Notes:
Should fix issue #24, locally tested. If redirections are necessary, and on github.io I guess it's not possible, we could re-add files with older names...