-
-
Notifications
You must be signed in to change notification settings - Fork 562
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
Github API and search by license: consider this for improved detection #1283
Comments
I would like to work on this. Can you provide some additional details about, what exactly needs to be done? |
repaste from the giiter chat at: https://gitter.im/aboutcode-org/discuss?at=5da81c05809de9699f5148a9 the first thing is to understand how license detection works. You can browse the code under src/licensedcode or more simply check some doc https://github.com/nexB/scancode-toolkit/wiki/How-to:-Add-new-license-rules-for-enhanced-detection and examples of what we call license detection rules under src/licensedcode/data/rules I think the first approach would be to craft tests for each of the license names and codes in #1283 .... and determine for each what is the scancode license key |
Signed-off-by: sbs2001 <shivam.sandbhor@gmail.com>
The original Github keys are not proper ScanCode license keys Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
These are too short to be valid tests alone Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Add Github key's test file pairs #1283
Signed-off-by: sbs2001 <shivam.sandbhor@gmail.com>
The original Github keys are not proper ScanCode license keys Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
These are too short to be valid tests alone Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
I am beginner in the issue can you please suggest me how to get started |
See "Searching GitHub by license type" https://help.github.com/articles/licensing-a-repository/
These may be material for new license rules?
The text was updated successfully, but these errors were encountered: