2 ms·
The link provides the API on how to poll github repositories for license data, but is a far cry from being a reliable method in measuring usage. Lets suggest f
by belorn 10y ago
The link provides the API on how to poll github repositories for license data, but is a far cry from being a reliable method in measuring usage.
Lets suggest following criteria for a survey:
1#, no duplicates. A survey with duplicate has no meaning. Github data in the blog post do not exclude dubplicates.
2#, no empty projects. A project with no data in it is not actually a project. The Github data do not exclude such projects.
3#, only project with code in them. A lot of github projects is text collaboration, like party planning, discussion around the latests online drama, and so on. Github data do not exclude those.
4#, only project with running code that is useful for at least 1 person. Random data, incomplete or abandon attempts is not actually "a software project". Github data do not attempt to run projects, and very much do not limit its data storage to only code that works.
To my knowledge, only one license survey exist that passes those criteria, and that one was based on the curated repository of Debian. The study showed GPL to be heavily favored (80%), but the study concluded that more such studies (and discussion on research methodology) is highly needed.