From: github.com@gnu.support
To: "syl20bnr/spacemacs"
<reply+AF5M4KYPGRLRETVKOVNYOGF6JE3XDEVBNHHDBSUAQA@reply.github.com>
Cc: emacs-tangents@gnu.org
Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444)
Date: Wed, 3 Mar 2021 09:59:50 +0300 [thread overview]
Message-ID: <YD8z5gg7IDfa03PW@protected.rcdrun.com> (raw)
In-Reply-To: <syl20bnr/spacemacs/issues/14444/788279842@github.com>
* Dmitry Gutov <notifications@github.com> [2021-03-02 00:03]:
> The report might still have merit, but I kind of doubt it. Otherwise
> we venture into "cannot distribute my own user configuration
> publicly" territory.
That is definitely interesting observation.
It is related to copyrights, not quite technicalities.
init.el files run with Emacs, so when distributed IMHO such files
represent combined work in terms of copyrights. init.el is not just
single file that runs in itself alone. Thus it has to carry proper
copyright license as it is combined and dependent of Emacs.
How you call it, be it "init" or something else, it is your
classification of software.
We do not speak of how software is classified, we speak of copyrights.
You can distribute your program without copyright notice, but that
does not make it free software. It may also collide with the GNU GPLv3
because if program is dependent of Emacs and modifies Emacs than it is
not in compliance with the license.
If your program runs let us say some processing that do not modify
Emacs, then I guess it could be proprietary as well. For example if
your program processes some data, like making websites in a batch
mode, I guess it could be proprietary.
If it however opens up the interactive user interface and provides M-x
commands that modifies Emacs and the license shall be GNU GPLv3 (or
maybe compatible one).
next prev parent reply other threads:[~2021-03-03 6:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <syl20bnr/spacemacs/issues/14444@github.com>
[not found] ` <syl20bnr/spacemacs/issues/14444/788139959@github.com>
2021-03-01 18:54 ` [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444) github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788212009@github.com>
2021-03-03 5:44 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788214244@github.com>
2021-03-03 6:32 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788279842@github.com>
2021-03-03 6:59 ` github.com [this message]
[not found] ` <syl20bnr/spacemacs/issues/14444/788544413@github.com>
2021-03-03 7:06 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789479245@github.com>
2021-03-03 7:10 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/788977796@github.com>
2021-03-03 7:17 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789126947@github.com>
2021-03-03 7:18 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789468543@github.com>
2021-03-03 7:21 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789512582@github.com>
2021-03-03 10:08 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789893593@github.com>
2021-03-03 19:50 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/789995307@github.com>
2021-03-03 20:02 ` github.com
[not found] ` <syl20bnr/spacemacs/issues/14444/790262904@github.com>
2021-03-04 6:26 ` github.com
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=YD8z5gg7IDfa03PW@protected.rcdrun.com \
--to=github.com@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=reply+AF5M4KYPGRLRETVKOVNYOGF6JE3XDEVBNHHDBSUAQA@reply.github.com \
/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.