all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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, 14 Jul 2017 21:44:41 +0200	[thread overview]
Message-ID: <877ezaajme.fsf@bernoul.li> (raw)
In-Reply-To: <E1dVd9a-00051z-A8@fencepost.gnu.org>


Richard Stallman <rms@gnu.org> writes:
>   > > This may be because the
>   > > library lacks a permission statement altogether (possibly because an
>   > > accompanying ~LICENSE~ file is considered sufficient by the upstream),
>
>   > > but it may also be because ~elx-license~ does not attempt to detect the
>   > > used non-standard and/or non-fsf permission statement, or because of
>   > > typos in the statement, or for a number of other reasons.
>
> We need to get a handle on what is really going on for these cases.
> A typo in a license notice, or an unusual license, might not be a real
> problem.  The lack of a clearly stated free license is a real problem,
> and the mere possibility that someone stated a license for it
> in some other site is not enough to make the problem go away.
>
> We need to find out what is going on in those 500 packages.
>
> One useful way to investigate would be to pick 10 of those packages,
> and see what is the situation with each of them.
>
> Would someone please volunteer to do this?

Once you have found someone to do this, s/he should contact me and I
will provide the necessary data and/or help that person get started
using my tools themselve.  Using those tools instead of just relying
on a data dump would actually make the process easier.  But currently
the usage instructions are spread across multiple manual, blog posts,
and repositories, so some guidance by me might be necessary to get
started.

The process could then be something like
1. emacs ~/code/epkg-stats/licenses-extras.org
2. emacs ~/code/emacsmirror/mirror/<package>/<package>.el
3. emacs ~/.emacs.d/lib/elx/elx.el # refine and add regexps
4. M-: (elx-license)               # in <package>.el
   unless satisfied, goto 3
5. M-x emir-recreate-packages      # *
6. C-c C-v C-b                     # in licenses-extras.org
7. M-x magit-diff-unstaged
8. goto 1

* Doesn't actually exist right now, you need to use
  emir-update-packages, with the irrelevant parts
  commented out.  Even then, this takes a few minutes.

  Jonas



  reply	other threads:[~2017-07-14 19:44 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 [this message]
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
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=877ezaajme.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.