-
Notifications
You must be signed in to change notification settings - Fork 47
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
Licenses for EESSI #457
base: 2023.06-software.eessi.io
Are you sure you want to change the base?
Licenses for EESSI #457
Conversation
Instance
|
Now the add_license_info.py script can process pypi, github and manual license addition to licenses.json file. There is also included work for other license fonts (libraries.io, repology and CRAN). This is fully functional, ready for review. |
Updates by the bot instance
|
Waiting for review/approval |
Updates by the bot instance
|
As suggested in 02/04/2023 meeting. Previously, spdx argument has been used to manually feeded licenses.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if we shouldn't break this off into it's own repository and create a GitHub Action for it? If we do it like then it can be easily used by others, and in other repositories for EasyStack files.
print('project in licenses.json') | ||
else: | ||
print('we do not have the license, adding into licenses.json') | ||
licenses[project]=dict(info) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From what I can see, this doesn't store information for the case of a licence change or multiple licences (academic versus commercial).
else: | ||
print('we do not have the license, adding into licenses.json') | ||
licenses[project]=dict(info) | ||
licJson=json.dumps(licenses, indent=4) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we should give 2 options here. There's kind of an assumption that this will make a change but if this is called within a GitHub Action the update to the licences file will be lost (without giving the Action permissions to write to the PR). It would be good to allow the display of the information in patch format so that it can be copied from the GitHub Actions and applied (or even posted as a review).
WIP