From: github.com@gnu.support
To: "syl20bnr/spacemacs"
<reply+AF5M4KY6RPTAGS63NFX7IG56JGG3NEVBNHHDBSUAQA@reply.github.com>
Cc: emacs-tangents@gnu.org
Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444)
Date: Wed, 3 Mar 2021 10:06:25 +0300 [thread overview]
Message-ID: <YD81cZSAGcUYfCR7@protected.rcdrun.com> (raw)
In-Reply-To: <syl20bnr/spacemacs/issues/14444/788544413@github.com>
* Ilya Grigoriev <notifications@github.com> [2021-03-02 06:11]:
> I think @gnusupport is under the impression that the Spacemacs
> distribution includes GNU Emacs. This was not my experience -- to
> run Spacemacs, I had to obtain GNU emacs separately. I don't
> believe there is any of the releases in
> https://github.com/syl20bnr/spacemacs/releases contain any portion
> of GNU Emacs (or, at least, they shouldn't), and there's no way for
> a user to run Spacemacs using those files without obtaining GNU
> emacs separately.
> However, if there is a Spacemacs distribution on the website or
> elsewhere that DOES include GNU Emacs, @gnusupport may have a point.
For copyright law it does not matter where are other parts of the
combined work located. You said it well, Spacemacs depends on
Emacs. Thus Spacemacs together with Emacs creates combined work.
Please read the GNU GPLv3:
https://www.gnu.org/licenses/
Spacemacs is not mere an aggregate:
" A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate."
- Spacemacs is extension to Emacs
- Spacemacs is combined with Emacs to form larger program
Thus Spacemacs is not merely an aggregate. I have given already
references to it in previous comments.
It really does not matter how other parts of the combined work are
pulled, fetched, from where, packaged, or not packaged together. They
can be apart. There is so much other software that is fetching from
other places other parts of software.
That fact of fetching other software does not exclude it from placing
proper licensing notices or complying to GPLv3.
next prev parent reply other threads:[~2021-03-03 7:06 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
[not found] ` <syl20bnr/spacemacs/issues/14444/788544413@github.com>
2021-03-03 7:06 ` github.com [this message]
[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=YD81cZSAGcUYfCR7@protected.rcdrun.com \
--to=github.com@gnu.support \
--cc=emacs-tangents@gnu.org \
--cc=reply+AF5M4KY6RPTAGS63NFX7IG56JGG3NEVBNHHDBSUAQA@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.