-
Notifications
You must be signed in to change notification settings - Fork 2
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
[rl-reuse_tool-4] Violation against OSS Rules of Play #22
Comments
hi @dellagustin-sap ! |
Hello @TeresaCerdeiraSAP , the documentation about those is internal, I'll send you a link. |
Hello @TeresaCerdeiraSAP , I have checked this finding with the reuse command line using the docker (run It seems to be false positive, as the result is positive, so it seems to be a false positive:
We will need to check it, I'll follow up internally. |
The reuse badge is not displayed in readme, That is why this issue is created - #25 should fix this. |
@ajinkyapatil8190 thank you for jumping in and sending the PR, I was about to write you 😄 . |
Thank you both @dellagustin-sap @ajinkyapatil8190 ! |
@TeresaCerdeiraSAP , heads up, there are some warnings on the REUSE compliance, you may want to take a look with low priority: At https://api.reuse.software/info/github.com/SAP/sap-customer-data-cloud-toolkit
They were all similar, I picked an excerpt so that it does not flood this issue. |
Thanks for the heads up @dellagustin-sap. I will align with the team |
Hi @dellagustin-sap , I was discussing the issue with the team. |
Hello @TeresaCerdeiraSAP , there is no immediate action necessary, we don't need, or even can suppress this warnings as the information is coming from a 3rd party service. |
Ok, we will have it in mind for the future 🙂Thanks @dellagustin-sap |
A violation against the OSS Rules of Play has been detected.
Rule ID: rl-reuse_tool-4
Explanation: Is it compliant with REUSE rules? No
Find more information at: https://sap.github.io/fosstars-rating-core/oss_rules_of_play_rating.html
The text was updated successfully, but these errors were encountered: