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

Github API and search by license: consider this for improved detection #1283

Open
Tracked by #1825
pombredanne opened this issue Nov 13, 2018 · 3 comments
Open
Tracked by #1825

Comments

@pombredanne
Copy link
Member

See "Searching GitHub by license type" https://help.github.com/articles/licensing-a-repository/

These may be material for new license rules?

You can filter repositories based on their license or license family using the license qualifier and the exact license keyword:

License License keyword
Academic Free License v3.0 afl-3.0
Apache license 2.0 apache-2.0
Artistic license 2.0 artistic-2.0
Boost Software License 1.0 bs1-1.0
BSD 2-clause "Simplified" license bsd-2-clause
BSD 3-clause "New" or "Revised" license bsd-3-clause
BSD 3-clause Clear license bsd-3-clause-clear
Creative Commons license family cc
Creative Commons Zero v1.0 Universal cc0-1.0
Creative Commons Attribution 4.0 cc-by-4.0
Creative Commons Attribution Share Alike 4.0 cc-by-sa-4.0
Do What The F*ck You Want To Public License wtfpl
Educational Community License v2.0 ecl-2.0
Eclipse Public License 1.0 epl-1.0
European Union Public License 1.1 eupl-1.1
GNU Affero General Public License v3.0 agpl-3.0
GNU General Public License family gpl
GNU General Public License v2.0 gpl-2.0
GNU General Public License v3.0 gpl-3.0
GNU Lesser General Public License family lgpl
GNU Lesser General Public License v2.1 lgpl-2.1
GNU Lesser General Public License v3.0 lgpl-3.0
ISC isc
LaTeX Project Public License v1.3c lppl-1.3c
Microsoft Public License ms-pl
MIT mit
Mozilla Public License 2.0 mpl-2.0
Open Software License 3.0 osl-3.0
PostgreSQL License postgresql
SIL Open Font License 1.1 ofl-1.1
University of Illinois/NCSA Open Source License ncsa
The Unlicense unlicense
zLib License zlib
@sbs2001
Copy link
Contributor

sbs2001 commented Oct 17, 2019

I would like to work on this. Can you provide some additional details about, what exactly needs to be done?

@pombredanne
Copy link
Member Author

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

pombredanne pushed a commit to sbs2001/scancode-toolkit that referenced this issue Oct 27, 2019
Signed-off-by: sbs2001 <shivam.sandbhor@gmail.com>
pombredanne added a commit to sbs2001/scancode-toolkit that referenced this issue Oct 27, 2019
The original Github keys are not proper ScanCode license keys

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit to sbs2001/scancode-toolkit that referenced this issue Oct 27, 2019
These are too short to be valid tests alone

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit to sbs2001/scancode-toolkit that referenced this issue Oct 27, 2019
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
pombredanne added a commit that referenced this issue Oct 28, 2019
Add Github key's test file pairs #1283
viragumathe5 pushed a commit to viragumathe5/scancode-toolkit that referenced this issue Mar 13, 2020
Signed-off-by: sbs2001 <shivam.sandbhor@gmail.com>
viragumathe5 pushed a commit to viragumathe5/scancode-toolkit that referenced this issue Mar 13, 2020
The original Github keys are not proper ScanCode license keys

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
viragumathe5 pushed a commit to viragumathe5/scancode-toolkit that referenced this issue Mar 13, 2020
These are too short to be valid tests alone

Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
viragumathe5 pushed a commit to viragumathe5/scancode-toolkit that referenced this issue Mar 13, 2020
Signed-off-by: Philippe Ombredanne <pombredanne@nexb.com>
@saif007s
Copy link

I am beginner in the issue can you please suggest me how to get started

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants