Skip to content
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

License check separation and severity #762

Open
ernilambar opened this issue Oct 30, 2024 · 3 comments
Open

License check separation and severity #762

ernilambar opened this issue Oct 30, 2024 · 3 comments
Labels
[Team] Plugin Review Issues owned by Plugin Review Team [Type] Enhancement A suggestion for improvement of an existing feature

Comments

@ernilambar
Copy link
Member

Proposal 1:
Change error type

Code Current Type Proposed Type
invalid_license WARNING ERROR
license_mismatch WARNING ERROR

Proposal 2:
Currently same error code no_license is used for missing license in readme and plugin header which is confusing. Similar for invalid_license.

My proposal is keeping same error code for readme and add introduce separate error code for plugin header license check:

  • plugin_header_no_license
  • plugin_header_invalid_license

Proposal 3:
Regarding license check:

  • Check one - Check if License is valid SPDX identifier (We could use error code like invalid_license_identifier and plugin_header_invalid_license_identifier)
  • Check two - Check if License is GPL compatible (Use existing error code for this - invalid_license)
@ernilambar ernilambar added [Team] Plugin Review Issues owned by Plugin Review Team [Type] Enhancement A suggestion for improvement of an existing feature labels Oct 30, 2024
@ernilambar
Copy link
Member Author

CC @frantorres @davidperezgar

@davidperezgar
Copy link
Member

I see that separate checks could benefit to be more clear in the report. Ok for that.
Are your proposal separate? or making all of them? If it's the first thing, I'd vote for proposal 2, that is clear for the user.

@ernilambar
Copy link
Member Author

All three would be good improvement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Team] Plugin Review Issues owned by Plugin Review Team [Type] Enhancement A suggestion for improvement of an existing feature
Projects
None yet
Development

No branches or pull requests

2 participants