From: github.com@gnu.support
To: "syl20bnr/spacemacs"
<reply+AF5M4K67QTFSSIFY3FDE7WF6JERGVEVBNHHDBSUAQA@reply.github.com>
Cc: emacs-tangents@gnu.org
Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444)
Date: Wed, 3 Mar 2021 08:44:33 +0300 [thread overview]
Message-ID: <YD8iQWp/Nq9zLZNy@protected.rcdrun.com> (raw)
In-Reply-To: <syl20bnr/spacemacs/issues/14444/788212009@github.com>
* Lucius Hu <notifications@github.com> [2021-03-01 22:33]:
> > So the programs contained in Spacemacs package create modified
> work. Maybe you think with "not modifying Emacs on the fly" that it
> does not modify the OS executable on the fly. Your software is
> written in Emacs Lisp (how I see it) and is modified work of
> original.
>
> Point to a source file of emacs that is modified.
>
> > Compiling or not compiling is not essential. It is Emacs Lisp. No need
> to compile
>
> This is hilarious. Anyone with elementary knowledge of how
> interpreter works knows that the program needs to be compiled.
We speak of the work in copyright terms.
It does not matter how you call it, you can call it framework,
configuration, etc. It does not matter because I have not spoken of
technicalities or classification of type of software.
What matters is that it is new package, new work, new software.
It really does not matter if you modify C sources or you add Emacs
Lisp, you have made the work. It is nice work. It is combination of
various other works and Spacemacs programs.
Thus it is new work in copyright terms.
> > As it directly uses mainstream Emacs to
> provide new Emacs version
>
> What are you talking about? Where is the new emacs?
Emacs Lisp code is modifying the original Emacs.
Emacs Lisp code in original Emacs is part of Emacs.
Look inside of Emacs Lisp code distributed with Emacs to understand.
> > It is also visibly not the same appearance so that demonstrates
> the modification.
>
> Following your definition, if you change the wallpaper, colortheme,
> etc of an operating system, you are considered to modify the
> OS. This is just nonsense.
I have not been speaking of the OS and I do not know how is this
relevant, but here are my comments for you.
If user changes a wallpaper, user did not write software and did not
distribute software. It is not relevant to copyright.
If a color theme is changed and it is not software, that is user's
option to change it.
If however a color theme is software and user decides to publish it,
and that software runs with GNU Emacs, then such should be published
with the appropriate license compatible with GNU GPLv3. The copyright
notice must be placed properly in the file of the color theme.
Spacemacs files do not have proper copyright notices, could you please
look into that issue as that is one practical thing you can improve,
it impacts users of Spacemacs and helps them understand the licensing.
next prev parent reply other threads:[~2021-03-03 5:44 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 [this message]
[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
[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=YD8iQWp/Nq9zLZNy@protected.rcdrun.com \
--to=github.com@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=reply+AF5M4K67QTFSSIFY3FDE7WF6JERGVEVBNHHDBSUAQA@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.