From: Jonas Bernoulli <jonas@bernoul.li>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Some hard numbers on licenses used by elisp packages
Date: Fri, 28 Jul 2017 13:17:46 +0200 [thread overview]
Message-ID: <87379gbyjp.fsf@bernoul.li> (raw)
In-Reply-To: <E1dX4ga-000892-Lf@fencepost.gnu.org>
> > I have looked at some files and made some improvements. We are now down
> > to roughly 200 packages that still need to be checked.
>
> That's much better than it previously appeared.
And it is getting better. Patience seems like the best strategy right
now.
* I have improved the heuristics etc. More licenses and permission
statements are now being detected and identified. I also make an
effort to differentiate between variations of a license. This
obviously can still be improved, but that isn't urgent.
* I have looked at nearly every package with an "unknown" license, and
have split that set into two new sets: "none" and "failure".
- failure: The licensing terms are specified somehow. But my tools
cannot detect that. In some cases that is a failure of my tools,
in other cases it is a failure to specify the terms in a way that
could possibly be detected automatically.
I don't think it is important to get this number down at this point.
Doing so is certainly possible, but teaching the tools to match more
also comes at the risk of false-positives.
- none: Looking at the package for half a minute did not reveal any
license of permission statement. Like my tools, I myself can make
mistakes, so this is an upper bound. A small number of these
packages (let's guess ten) probably do actually feature some kind of
permission statement, which I failed to see.
* I have contacted nearly all of the authors of packages that appear to
not specify a license. These packages are being identified below by
the pseudo license "pending".
Responses - all positive - have started to dribble in. Several dozen
packages now have proper licensing terms thanks to these efforts. But
most of the authors I did not contact until last night, so a few dozen
additional quick responses are to be expected within a week or so.
What is needed now is patience. As I have said elsewhere in this
thread I have years of experience contacting authors of elisp packages
to ask them to fix something that they might consider to be a very
minor issue. Usually a small number of authors (up to 10%) respond
and acts very quickly, within hours or days. A large number of
authors (up to 60%) respond within one to three months without
requiring any reminders. The rest requires reminders. However these
reminders should not be send out until a few months later. In my
experience, sending out reminders too early, reduces the likelihood of
something being done.
The newest statistics:
| License | Count | Percent |
|---------------+-------+---------|
| GPL-3+ | 2295 | 62 |
| GPL-2+ | 617 | 17 |
| ((pending)) | 128 | 3 |
| MIT (x11) | 117 | 3 |
| MIT | 102 | 3 |
| GPL-3 | 98 | 3 |
| ((failure)) | 66 | 2 |
| BSD-2-clause | 65 | 2 |
| GPL-2 | 40 | 1 |
| unlicense | 30 | 1 |
| Apache-2.0 | 26 | 1 |
| BSD-3-clause | 26 | 1 |
| public-domain | 23 | 1 |
| ((none)) | 16 | 0 |
| as-is | 15 | 0 |
| WTFPL | 11 | 0 |
| GPL-1+ | 4 | 0 |
| ISC (and) | 3 | 0 |
| Artistic-2.0 | 2 | 0 |
| CC-BY-3.0 | 2 | 0 |
| GPL | 2 | 0 |
| ISC | 2 | 0 |
| LGPL | 2 | 0 |
| AGPL-3 | 1 | 0 |
| AGPL-3+ | 1 | 0 |
| BSD | 1 | 0 |
| BSD-3 | 1 | 0 |
| EPL | 1 | 0 |
| EPL-1.0 | 1 | 0 |
| ISC (and/or) | 1 | 0 |
| LGPL-3 | 1 | 0 |
| LGPL-3+ | 1 | 0 |
| LGPL-3.0 | 1 | 0 |
| MPL-2 | 1 | 0 |
|---------------+-------+---------|
| total GNU | 3063 | 83 |
|---------------+-------+---------|
| total | 3703 | 100 |
Best regards,
Jonas
next prev parent reply other threads:[~2017-07-28 11:17 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 14:29 Some hard numbers on licenses used by elisp packages Jonas Bernoulli
2017-07-12 12:49 ` Jonas Bernoulli
2017-07-13 12:23 ` Richard Stallman
2017-07-14 19:44 ` Jonas Bernoulli
2017-07-15 19:38 ` Mats Lidell
2017-07-16 1:55 ` Richard Stallman
2017-07-16 2:20 ` Jean-Christophe Helary
2017-07-16 15:41 ` Jonas Bernoulli
2017-07-16 17:37 ` Mats Lidell
2017-07-16 22:17 ` Mats Lidell
2017-07-17 12:00 ` Richard Stallman
2017-07-17 12:00 ` Richard Stallman
2017-07-17 12:00 ` Richard Stallman
2017-07-17 21:23 ` Mats Lidell
2017-07-18 14:16 ` Richard Stallman
2017-07-23 22:14 ` Mats Lidell
2017-07-27 22:50 ` Mats Lidell
2017-07-28 17:16 ` Richard Stallman
2017-07-29 12:19 ` Mats Lidell
2017-07-29 19:09 ` Richard Stallman
2017-07-29 19:54 ` Mats Lidell
2017-07-29 22:49 ` Ivan Andrus
2017-07-31 0:46 ` Richard Stallman
2017-07-31 17:48 ` Achim Gratz
2017-08-08 1:02 ` Ivan Andrus
2017-07-31 0:51 ` Richard Stallman
2017-08-01 21:46 ` Mats Lidell
2017-08-02 1:54 ` Stefan Monnier
2017-08-03 19:42 ` Richard Stallman
2017-08-03 19:58 ` Stefan Monnier
2017-07-28 10:52 ` Jonas Bernoulli
2017-07-28 17:16 ` Richard Stallman
2017-07-28 17:47 ` Jonas Bernoulli
2017-07-28 17:16 ` Richard Stallman
2017-07-29 13:48 ` Jonas Bernoulli
2017-07-29 19:10 ` Richard Stallman
2017-07-29 19:10 ` Richard Stallman
2017-07-28 20:36 ` Karl Fogel
2017-07-29 19:07 ` Richard Stallman
2017-07-31 0:49 ` Richard Stallman
2017-07-17 11:59 ` Richard Stallman
2017-07-28 11:17 ` Jonas Bernoulli [this message]
2017-07-29 14:54 ` Mats Lidell
2017-07-29 19:09 ` Richard Stallman
2017-07-29 19:06 ` Richard Stallman
2017-07-29 19:06 ` Richard Stallman
2017-07-29 20:07 ` Mats Lidell
2017-07-30 6:28 ` Jean-Christophe Helary
2017-07-31 16:03 ` Jonas Bernoulli
2017-07-31 17:03 ` Jonas Bernoulli
2017-08-03 9:35 ` Mats Lidell
2017-08-03 19:50 ` Richard Stallman
2017-07-13 12:23 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87379gbyjp.fsf@bernoul.li \
--to=jonas@bernoul.li \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.