From: Jean-Christophe Helary <jean.christophe.helary@gmail.com>
To: rms@gnu.org
Cc: Jonas Bernoulli <jonas@bernoul.li>, emacs-devel@gnu.org
Subject: Re: Some hard numbers on licenses used by elisp packages
Date: Sun, 16 Jul 2017 11:20:07 +0900 [thread overview]
Message-ID: <6766A79E-D393-441F-9918-31AEA8C894FC@gmail.com> (raw)
In-Reply-To: <E1dWYmU-0007Gi-2Q@fencepost.gnu.org>
> On Jul 16, 2017, at 10:55, Richard Stallman <rms@gnu.org> wrote:
>
> [[[ To any NSA and FBI agents reading my email: please consider ]]]
> [[[ whether defending the US Constitution against all enemies, ]]]
> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>
> 500 (roughly) packages is a lot of packages, and checking them by hand
> would be a fair amount of work. The only way to check so many packages
> efficiently is with tools.
>
> But we don't need to study 500 packages to understand the _general
> causes_ for which packages show up as "unlicensed".
>
> I propose that people pick 10 of these packages, perhaps randomly, and
> study each of the 10 by hand. Does it have any license that the
> existing tools did not notice? If so, is there a way to fix them to
> notice that license? Was it a typo in the licence notice?
>
> Or was that package simply published with no license?
>
> 10 packages is a much smaller task. Small enough, I think, that there
> is no need to worry about making any special tools. It's enough to
> look at the source files.
>
> Once we understand what KINDS of problems appear among these
> "unlicensed" packages, I expect it will be clear what questions to
> pose for the other 500 or so "unlicensed" packages, and easy enough to
> write automatic tools to characterize almost all of them.
>
> Wha do you think of this approach?
That's an easy and useful task that can be handled by beginning contributors. Could experienced people provide the list of packages 500+ that we need to pick 10 from ?
Jean-Christophe
next prev parent reply other threads:[~2017-07-16 2:20 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 [this message]
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
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=6766A79E-D393-441F-9918-31AEA8C894FC@gmail.com \
--to=jean.christophe.helary@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jonas@bernoul.li \
--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.