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

Improve license clarity scoring #2875

Merged
merged 11 commits into from
Mar 9, 2022
Merged

Conversation

pombredanne
Copy link
Member

@pombredanne pombredanne commented Feb 24, 2022

This PR improves license clarity scoring as designed by @DennisClark in #2861

Tasks

  • Reviewed contribution guidelines
  • PR is descriptively titled 📑 and links the original issue above 🔗
  • Tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR
    Run tests locally to check for errors.
  • Commits are in uniquely-named feature branch and has no merge conflicts 📁

Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
    * Show boolean flags in scoring_elements to show what license judgement criteria was used

Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
Signed-off-by: Jono Yang <jyang@nexb.com>
    * If a package has conflicting or ambigous licenses and the score is already zero, do not subtract from the score

Signed-off-by: Jono Yang <jyang@nexb.com>
    * The classify plugin was determining the types of key files by checking the start or end of file names to see if they are a special type of file. However, the code checked the full filename with extension. This would cause us to not classify certain key files properly.

Signed-off-by: Jono Yang <jyang@nexb.com>
    * Fix logic in check_for_license_ambiguity
    * Removed unused test file

Signed-off-by: Jono Yang <jyang@nexb.com>
   * Add test for license ambiguity
   * Remove previous license clarity scoring plugin

Signed-off-by: Jono Yang <jyang@nexb.com>
@JonoYang JonoYang force-pushed the 2861-license-clarity-update branch from c9b366c to f998e21 Compare March 4, 2022 17:56
Copy link
Member Author

@pombredanne pombredanne left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! ... merging.

@pombredanne pombredanne merged commit 86c7db5 into develop Mar 9, 2022
@pombredanne pombredanne deleted the 2861-license-clarity-update branch March 9, 2022 09:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants