unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: github.com@gnu.support
To: "syl20bnr/spacemacs"
	<reply+AF5M4K7MWFTOGOXMNMW3NXF6JI3F3EVBNHHDBSUAQA@reply.github.com>
Cc: emacs-tangents@gnu.org
Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444)
Date: Wed, 3 Mar 2021 10:17:18 +0300	[thread overview]
Message-ID: <YD83/odKI61V8m+G@protected.rcdrun.com> (raw)
In-Reply-To: <syl20bnr/spacemacs/issues/14444/788977796@github.com>

* Lucius Hu <notifications@github.com> [2021-03-02 18:10]:
> Why would the user don't know?
> Or is there any description of Spacemacs says it's not a configuration but a modified version of Emacs?

Descriptions are in terms of copyright not really relevant.

Classification like naming such as "configuration" is also not
relevant.

Question is if it represents combined work and thus modified version
of Emacs as visually and practically it represents modified version of
Emacs. It is not relevant that code was added to it, and that some
sources were not "changed" directly. The modification of software is
taking place in adding that new code. 

IMHO it represents combined work, new modified work thus the section
"5. Conveying Modified Source Versions." applies:

1. TODO Full license text file is missing in the distribution.

2. TODO Source files do not have proper license notices. "GPLv3" is
   not enough. This is not even related to the section 5 but to
   general application of GNU GPLv3 license, and Spacemacs authors
   with to license it as GPLv3 but just need to place proper notices
   in each source files.

3. TODO Somewhere in the interactive interface you could add short
   copyright notice, something like "Copying Conditions" in accordance
   with the section 5.



  parent reply	other threads:[~2021-03-03  7:17 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
     [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 [this message]
     [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

  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=YD83/odKI61V8m+G@protected.rcdrun.com \
    --to=github.com@gnu.support \
    --cc=emacs-tangents@gnu.org \
    --cc=reply+AF5M4K7MWFTOGOXMNMW3NXF6JI3F3EVBNHHDBSUAQA@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.
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).