Skip to content

Fix false positive for Apache-2.0 OR BSD-3-Clause and add Apache-2.0 … #4126

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

Open
wants to merge 5 commits into
base: develop
Choose a base branch
from

Conversation

TanayPawar
Copy link

…OR MIT rule

Fixes #4088

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 📁
  • Updated documentation pages (if applicable)
  • Updated CHANGELOG.rst (if applicable)

Copy link
Member

@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. You are missing a DCO signoff, and should start by adding a test. Do not update existing rules with different texts. Create new ones, and check https://aboutcode.readthedocs.io/en/latest/contributing/writing_good_commit_messages.html

@@ -1,11 +1,11 @@
---
license_expression: apache-2.0 OR bsd-new
is_license_notice: yes
relevance: 99
relevance: 100
Copy link
Member

Choose a reason for hiding this comment

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

Do not change this. How can you be 100% sure that LICENSE.BSD contains a bsd-new

found in {{LICENSE.APACHE}} or {{LICENSE.BSD}}. Both must be present for this rule to apply.
Copy link
Member

Choose a reason for hiding this comment

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

Do not change existing rules. Create new ones

This software is made available under the terms of *either* of the licenses
found in LICENSE.APACHE2 or LICENSE.MIT.
Copy link
Member

Choose a reason for hiding this comment

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

Do not change existing rules. Create new ones

ignorable_urls:
- http://opensource.org/licenses/MIT
- http://www.apache.org/licenses/LICENSE-2.0
- LICENSE.APACHE2
Copy link
Member

Choose a reason for hiding this comment

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

Is this a URL?

@TanayPawar
Copy link
Author

@pombredanne sir so shall I create a new rule with the respective changes?

@alok1304
Copy link
Contributor

alok1304 commented Mar 6, 2025

shall I create a new rule with the respective changes?

yes you should create new rule file.

TanayPawar and others added 4 commits March 11, 2025 21:45
@TanayPawar TanayPawar requested a review from pombredanne March 11, 2025 17:31
@TanayPawar
Copy link
Author

hey @pombredanne , @alok1304
I have created a new rule (apache-2.0_or_bsd-new_11.RULE) instead of modifying the existing one as per the review.
Can you please review on it.
Thank you.

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.

"Apache-2.0 OR MIT" includes wrong detection of BSD-3-Clause
3 participants