From: Mats Lidell <mats.lidell@cag.se>
To: Richard Stallman <rms@gnu.org>
Cc: jonas@bernoul.li, emacs-devel@gnu.org
Subject: Re: Some hard numbers on licenses used by elisp packages
Date: Tue, 01 Aug 2017 23:46:44 +0200 [thread overview]
Message-ID: <87fudbvu4b.fsf@ernst> (raw)
In-Reply-To: <E1dbyvM-0003Mv-9J@fencepost.gnu.org> (Richard Stallman's message of "Sun, 30 Jul 2017 20:51:08 -0400")
> Richard Stallman writes:
> How useful is that package?
[1]
Pragmatically I would say that small packages, like this, generally would not
be that useful. But again for a few users it could be a very useful
package. Who can tell or judge that?
> It may be possible to find the person's heirs. It would be some work,
> though. How much work would that package be worth?
In this case it might be possible to find the heirs but generally I suspect
that can be very difficult if not impossible. So for a small package I suspect
that it is easier to give it a new implementation. But theoretically that will
not solve the issue I guess since the new implementation would not really
replace the old one so that would still be around.
These are the tricky questions you wind up in when there is no license and I
don't know the proper way out of it if there is any. I suspect at some distant
time in the future an unmaintained package will break and will be removed for
that reason.
Yours Mats
Footnotes: [1] This is my investigation about the author. The package is
https://github.com/Raynes/refheap.el. When the authors email given at github
did not work I search the net to find this
article. https://www.facebook.com/lancepantz/posts/10104155686547809?pnref=story
Which links to the memory page of Anthony Grimes. The github profile picture
is there and the authors interest in clojure indicates a match.
next prev parent reply other threads:[~2017-08-01 21:46 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 [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fudbvu4b.fsf@ernst \
--to=mats.lidell@cag.se \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).