unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: github.com@gnu.support
To: "syl20bnr/spacemacs"
	<reply+AF5M4KZWZJE25GW53D7XOR56JMFTPEVBNHHDBSUAQA@reply.github.com>
Cc: emacs-tangents@gnu.org, Richard Stallman <rms@gnu.org>
Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444)
Date: Wed, 3 Mar 2021 10:21:30 +0300	[thread overview]
Message-ID: <YD84+pxva5AaYPHZ@protected.rcdrun.com> (raw)
In-Reply-To: <syl20bnr/spacemacs/issues/14444/789468543@github.com>

* Lucius Hu <notifications@github.com> [2021-03-03 09:19]:
> > Emacs Lisp code is modifying the original Emacs.
> 
> So if one writes shell script is he modifying the shell? Or when I
> program on my proprietary programmable calculator, am I modifying
> the calculator and therefore violated the copyright of its
> manufacture?

Spacemacs is not shell script that does something separate for itself
separate from Emacs as editor and environment.

If one writes a shell script that modifies the behavior of Bash shell,
and distributes such in public, then such shell script becomes new
combined work that modified Bash and is modified work.

When you program on your proprietary programmable calculator, that
issue is not related to free software, especially not because you have
not say that you are distributing it.

> > 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.
> 
> No. I don't like stupid people. Stop your balderdash and get off this repository.

That is unfortunate to see such statement.



  parent reply	other threads:[~2021-03-03  7:21 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
     [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 [this message]
     [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=YD84+pxva5AaYPHZ@protected.rcdrun.com \
    --to=github.com@gnu.support \
    --cc=emacs-tangents@gnu.org \
    --cc=reply+AF5M4KZWZJE25GW53D7XOR56JMFTPEVBNHHDBSUAQA@reply.github.com \
    --cc=rms@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).