all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Etienne Prud’homme" <e.e.f.prudhomme@gmail.com>
To: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: comparing code on different branches
Date: Thu, 13 Jul 2017 17:48:17 -0400	[thread overview]
Message-ID: <871spkatzy.fsf@x230.lts> (raw)
In-Reply-To: <E1dT9B3-0004Pp-0H@fencepost.gnu.org> (Richard Stallman's message of "Thu, 06 Jul 2017 11:58:49 -0400")

Sorry, I just saw your replay.

Richard Stallman <rms@gnu.org> writes:

> I am not sure what those words mean, so this may (or may not) be an
> important problem.  Could you please describe more concretely a few of
> cases?

I don’t really want to point people.  My understanding is that any
package using Emacs components are subject to the GPL license as it
would fall (in my understanding) as a derivative work.

Some people are not happy with the GPL and remove the copyleft by using
licenses such as MIT, Simplified BSD and WTFPL[1].  Some people go even
further by publishing it in the public domain (unlicense).

I wouldn’t say those licenses are GPL incompatible, but they do not
abide to the GPL (still in my understanding).  GPL incompatibility can
mean a project with licence A can safely become a GPL project.  While
non GPL abiding would mean a project with a GPL license cannot become a
project with license A.

> is there any package in MELPA with a license that is nonfree?

I’ve not seen packages with proprietary licenses (that is software with
license incompatible with the GPL in the sense I said above).

> Is there any package in MELPA with no license?
> (A program with no license is automatically nonfree.)

I’ve seen packages with no license in the past.  It might not be the
case anymore, but I would need to check again.

I think most people using a non GPL abiding license simply don’t know
that their derivative projects is still subject to the GPL license.

A few of them simply don’t care or dislike the GPL license.  They are
aware of the GPL conditions, but don’t consider packages using language
standards (like common lisp) to be subject to the GPL.

That’s a tricky point since Emacs has both an interpreter and its own
functionality.  Having code being interpreted by Emacs doesn’t
necessarily make it GPL.  Someone could use Common Lisp procedures with
Emacs’ interpreter.

Also some Emacs code is in the Public Domain.  From my understanding of
the law it’s illegal to copyright things in the public domain and that
might be the reason why this is so.

I’m not a lawyer, I may be totally wrong on that.

[1] One example is El-get found at https://github.com/dimitri/el-get.
Worth noting it was discussed with
“Please change license from WTFPL (e.g. to GPL)”:
https://github.com/dimitri/el-get/issues/474 and the maintainer rejected
it.

--
Etienne



  reply	other threads:[~2017-07-13 21:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-04  0:53 comparing code on different branches Jean-Christophe Helary
2017-07-04  0:57 ` John Wiegley
2017-07-04  1:14   ` Jean-Christophe Helary
2017-07-04  5:17   ` Tino Calancha
2017-07-04  5:53   ` Marcin Borkowski
2017-07-04  9:30     ` Yuri Khan
2017-07-04 23:05       ` Richard Stallman
2017-07-04 23:48         ` Jean-Christophe Helary
2017-07-05 22:59           ` Richard Stallman
2017-07-05  5:54         ` Etienne Prud’homme
2017-07-05 15:55           ` Yann Hodique
2017-07-05 16:07             ` Kaushal Modi
2017-07-05 19:56             ` Etienne Prud'homme
2017-07-06 15:58               ` Richard Stallman
2017-07-13 21:48                 ` Etienne Prud’homme [this message]
2017-07-04 17:51 ` Stephen Leake

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=871spkatzy.fsf@x230.lts \
    --to=e.e.f.prudhomme@gmail.com \
    --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.