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

* Eli-Zaretskii <notifications@github.com> [2021-03-03 10:47]:
> So if Spacemacs adds a `COPYING` file which is GPLv3, and adds the
> missing copyright notices to the files it provides, the problem is
> solved, right?

License in the distribution should be there, of course.

But each source file has to have copyright notice as how it is
explained in the license as that will give clear information to people
that software is free software and that there is no warranties.

Stating only "GPLv3" means nothing in itself, and implies that
receiver is supposed to know what it the license. It is unclear for
the end receiver of the software.




  parent reply	other threads:[~2021-03-03 10:08 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
     [not found] ` <syl20bnr/spacemacs/issues/14444/789512582@github.com>
2021-03-03 10:08   ` github.com [this message]
     [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=YD9gNyBPd84Xn6Ms@protected.rcdrun.com \
    --to=github.com@gnu.support \
    --cc=emacs-tangents@gnu.org \
    --cc=reply+AF5M4K2JW7XPGMGWYLT3YAV6JMQAHEVBNHHDBSUAQA@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).