From: "Pascal J. Bourguignon" <pjb@informatimago.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Packages, release notes, etc
Date: Fri, 11 Sep 2015 04:15:36 +0200 [thread overview]
Message-ID: <87y4gd7lbr.fsf@kuiper.lan.informatimago.com> (raw)
In-Reply-To: slrnmv47bn.5pk.joost.m.kremers@j.kremers4.news.arnhem.chello.nl
Joost Kremers <joost.m.kremers@gmail.com> writes:
> Tassilo Horn wrote:
>> But what's the purpose of the copyleft when I can release a derived work
>> basing on GPL code under a GPL-compatible license which has no copyleft
>> anymore, e.g., Apache License, Version 2.0?
>
> But what's a derived work? IANAL but according to Wikipedia a derivative
> wokr includes (a significant portion of) the original work. In that
> view, Emacs plugins, are not derivative works.
>
> IIUC the FSF argues that using a library in your program makes your
> program a derivative work of that library. (It's why there's also an
> LGPL.) In that view, something could be said for the argument that
> plugins are derivative works, even though Emacs is strictly speaking
> not a library.
>
> If you say that Emacs is essentially a virtual machine, then plugins
> written by third parties are not derivative works, I think. I mean,
> Oracles JVM is GPL, but I doubt that means that every program running on
> it must also be GPL. OTOH most Emacs plugins aren't just programs that
> happen to run on the Emacs VM, they're extensions modifying or extending
> the functionality of Emacs itself. (There are a few packages that I
> would consider actual programs running on top of Emacs, such as Gnus,
> mu4e, magit, etc. To me, those are intuitively different from a package
> such as e.g., markdown-mode or hydra, but the line is difficult to draw.
> I'm myself not sure on what side of the line I'd put org-mode, for
> example.)
>
> Anyway, what I'm trying to say is that it's not at all clear what the
> legal status of Emacs packages is, and I'm pretty sure that if someone
> were to publish a proprietary Emacs extension and the FSF would sue,
> it'd be far from an open and shut case...
Indeed, and given that the legal analysis of the existing cases,
demonstrate that it all reduces to whether the judge considers to be in
presence of a derived work or not (nonwithstanding any technicalities
like linking, as I mentionned previously, a mere translation (in
literature) is considered derived work, I'm sure you could make the case
for source code too).
--
__Pascal Bourguignon__ http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk
next prev parent reply other threads:[~2015-09-11 2:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <vto7ccx8r5.ln2@news.c0t0d0s0.de>
2015-09-10 9:22 ` Packages, release notes, etc Tassilo Horn
2015-09-10 17:36 ` Stefan Monnier
2015-09-10 20:09 ` Tassilo Horn
2015-09-10 23:20 ` Stefan Monnier
[not found] ` <mailman.878.1441927224.19560.help-gnu-emacs@gnu.org>
2015-09-11 2:12 ` Pascal J. Bourguignon
2015-09-11 9:25 ` Alan Schmitt
2015-09-11 5:26 ` tomas
[not found] ` <mailman.874.1441915758.19560.help-gnu-emacs@gnu.org>
2015-09-11 0:16 ` Joost Kremers
2015-09-11 2:15 ` Pascal J. Bourguignon [this message]
[not found] ` <mailman.808.1441876951.19560.help-gnu-emacs@gnu.org>
[not found] ` <ni18ccxbua.ln2@news.c0t0d0s0.de>
2015-09-10 10:31 ` tomas
2015-09-10 11:00 ` Tassilo Horn
2015-09-10 11:38 ` tomas
2015-09-10 11:40 Alexis
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=87y4gd7lbr.fsf@kuiper.lan.informatimago.com \
--to=pjb@informatimago.com \
--cc=help-gnu-emacs@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.
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).