ISC-licensed repos
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
Comment only
 
 
ABC
1
Querying the GitHub tables in Google's BigQuery platform for the license data:
2
SELECT gh_licenses.repo_name, gh_since2015.num_stars
Open the link below, click the "query table" button, and paste the query there.
3
FROM [bigquery-public-data:github_repos.licenses] AS gh_licenses
The results can be directly exported to google sheets.
4
JOIN (
5
SELECT repo.name, COUNT(*) AS num_stars
6
FROM TABLE_DATE_RANGE([githubarchive:day.], TIMESTAMP('2015-01-01'), CURRENT_TIMESTAMP())
7
WHERE type = "WatchEvent"
8
GROUP BY repo.name
9
) AS gh_since2015
10
ON (gh_licenses.repo_name == gh_since2015.repo.name)
11
WHERE license="isc"
12
ORDER BY num_stars DESC
13
14
Documentation for the query-building process:
15
https://bigquery.cloud.google.com/table/githubarchive:day.20150101
One of the day-specific tables that I merge for my watch_event aggregating query
16
https://cloud.google.com/bigquery/query-reference
Documentation for writing the query
17
https://www.reddit.com/r/bigquery/comments/4qhlog/all_the_open_source_code_in_github_now_shared/
I documented some of my queries there, down to the one which produced the current table
18
https://github.com/github/choosealicense.com/pull/438#issuecomment-230150424
Final version of my query (same as the last one in the link above, only with different aliases)
19
20
Note: watch_count likely refers to stars:
21
https://developer.github.com/v3/activity/events/types/#watchevent
22
https://developer.github.com/changes/2012-09-05-watcher-api/
23
24
Possibly useful:
25
http://stackoverflow.com/questions/28013010/select-repository-url-from-github-timeline-group-pushes-and-downloads-by-repos
26
27
Repos not captured (no star events in the queried period, or some other reason):
28
https://github.com/isc-projects/mini-kea/pull/1
29
https://github.com/bundy-dns/bundy/blob/master/COPYING
30
https://github.com/mapbox/docbox/pull/19
31
https://github.com/martanne/vis/blob/master/LICENSE
32
https://github.com/jxcore/jxcore-cordova/pull/147
33
https://github.com/jperkin/node-openzwave/blob/master/LICENSE.md
34
https://github.com/minad/9mount/blob/master/COPYING
35
https://github.com/mirage/ocaml-ipaddr/pull/58
36
https://github.com/mapbox/cheap-ruler/pull/16
37
https://github.com/mapbox/vtinfo/pull/7
38
https://github.com/mapbox/retext-mapbox-standard/pull/14
39
40
Mistakenly captured (not ISC or not properly licensed):
41
https://github.com/Dean177/react-typescript-hotloading-boilerplate
Was MIT since the first commit, https://github.com/Dean177/react-typescript-hotloading-boilerplate/commit/aeafa94
42
43
Using the github API directly may be possible soon (GraphQL):
44
https://developer.github.com/early-access/graphql/explorer/
query { viewer { repositories (first:10) { edges { node { name license } } } } }
45
http://githubengineering.com/the-github-graphql-api/
https://gist.github.com/waldyrious/f564bc9e6b5f83c34f49cb92f7b89b53
46
https://developer.github.com/early-access/graphql/object/repository/
link above adapted from:
https://medium.com/@katopz/how-to-search-with-github-graphql-e6c142dc61ed
47
48
Using the github search interface
49
https://github.com/blog/2461-search-repositories-by-license
Announcement (3 Nov 2017)
50
https://github.com/search?type=Repositories&q=stars:>1000+license:isc
ISC repos with more than 1000 stars
51
52
more lists of ISC projects:TODO: process these
53
https://libraries.io/search?licenses=ISC&order=desc&sort=rank
(also sortable by other criteria)
54
google searchand-github LICENSE
55
google search-github COPYING
56
google search+github LICENSE
57
google search+github COPYING
58
google searchand/or-github LICENSE
59
google search-github COPYING
60
google search+github LICENSE
61
google search+github COPYING
62
https://github.com/github/choosealicense.com/issues/377
63
64
why add the title:
65
https://github.com/j256/ormlite-core/issues/82#issuecomment-228284752PR message:
66
"There are various reasons to add the title. One is to make it clearer what license is actually being used (e.g. to quickly verify whether a project's license is among those vetted by the relevant FOSS organizations). It also improves searching (especially since licenses often use very similar language). Additionally, this can serve as a fast early check for content-based license matchers. And I'm sure there are other reasons I'm missing."
as recommended in the template license text:
- https://choosealicense.com/licenses/isc/
- https://opensource.org/licenses/isc-license
- https://spdx.org/licenses/ISC.html#licenseText
67
https://github.com/ninenines/cowboy/pull/999#issuecomment-229811306
68
reading the license and understanding it is not enough: as most people lack the adequate legal background, they have to rely on trustworthy organizations to validate specific licenses (OSI, FSF) as compatible and not including (or lacking) small details they may overlook otherwise. And for this end, the only way to ensure a license is compliant is comparing it word by word with a few samples, which may be tedious if they don't already have a clear idea of what license (or even kind of license, e.g. permissive vs. copyleft) they must compare the text to. By providing a title you not only make this task hugely easier for humans, but also make this repo more discoverable and machine-processable by tools that can't afford to do full-text matching across thousands of repositories vs. dozens of possible licenses.
69
https://github.com/github/choosealicense.com/pull/9
70
"It's very helpful/timesaving to people considering making use of a project for the license text to have the title, so they don't have to do a search to confirm what the license is. "
71
https://github.com/github/choosealicense.com/pull/371
72
"This makes it immediately clear which license this is without reading and comparing the whole text."
73
https://github.com/debian-pi/raspbian-ua-netinst/pull/413
74
From what I've understood of it, you're supposed to use the (short) ID(entifier), not the name. See https://github.com/david-a-wheeler/spdx-tutorial/#spdx-license-expressions-in-source-code-files, http://wiki.spdx.org/view/Technical_Team/SPDX_Meta_Tags and https://events.linuxfoundation.org/sites/events/files/slides/DevelopersCare_JLovejoy_LinuxConEu_2015_final-static.pdf
75
https://events.linuxfoundation.org/sites/events/files/slides/DevelopersCare_JLovejoy_LinuxConEu_2015_final-static.pdf
76
"Focus on capturing facts; avoid interpretations" (p. 16)
77
"help reduce redundant work in determining software license information and facilitate compliance" (p. 16)
78
79
Instances of maintainers mistaking my PRs for spam / automated
80
https://github.com/silentbicycle/greatest/pull/53
81
https://github.com/rubblelabs/ripple/pull/25
82
(there's at least another one -- I thought I had noted these down...
83
84
ISC discussion links in license catalog projects
85
github/choosealicense.com#50: Adds ISC License
86
https://github.com/github/choosealicense.com/pull/50
87
github/choosealicense.com#377: Add list of projects using the ISC license
88
https://github.com/github/choosealicense.com/issues/377
89
gjtorikian/addalicense.com#21: Point BSD-2 license to ISC
90
https://github.com/gjtorikian/addalicense.com/pull/21
91
OpenSourceOrg/licenses: Add wikipedia page for the ISC license (and further discussion)
92
https://github.com/OpenSourceOrg/licenses/pull/41
93
choosealicense.com#371: Add name of license to ISC license text
94
https://github.com/github/choosealicense.com/pull/371
95
benbalter/licensee#139: Allow synonyms in the disclaimer section (AUTHOR vs. COPYRIGHT OWNER, etc)
96
https://github.com/benbalter/licensee/issues/139
97
spdx/license-list-XML#497: ISC title variations
98
https://github.com/spdx/license-list-XML/pull/497/files
99
100
ISC reference links
Loading...
 
 
 
Notes
All ISC-licensed repos
All ISC repos (30 Aug 2017)
>1000 stars (4 Nov 2017)
>1000 stars (21 Mar 2018)
 
 
Main menu