unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: github.com@gnu.support
To: "syl20bnr/spacemacs"
	<reply+AF5M4K5FIIIIYDUQTGUROR56JQ25DEVBNHHDBSUAQA@reply.github.com>
Cc: emacs-tangents@gnu.org
Subject: Re: [syl20bnr/spacemacs] Proposal to improve GPL compliance (#14444)
Date: Thu, 4 Mar 2021 09:26:30 +0300	[thread overview]
Message-ID: <YEB9lqD82+i+TjYo@protected.rcdrun.com> (raw)
In-Reply-To: <syl20bnr/spacemacs/issues/14444/790262904@github.com>

* Sylvain Benner <notifications@github.com> [2021-03-04 06:33]:
> @gnusupport You are the expert here. I don't understand half of what you are saying and I'm not interested in understanding it. But I'm willing to improve Spacemacs compliance with GPLv3 if it is a reasonable proposal (i.e. I don't 3km long headers in each file).
> 
> You are asking about doing this:
> - [ ]  Full license text file is missing in the distribution.
> - [ ] 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.
> - [ ] Somewhere in the interactive interface you could add short
>    copyright notice, something like "Copying Conditions" in accordance
>    with the section 5.
> 
> Can you either:
> - open a PR with the correct missing info
> - or give concrete examples about what is needed
> 
> Thank you for your help, this is greatly appreciated.

Sorry I cannot open pull request as I do not use Github neither other
Git. I have opened this issue, and it should be clear what has to be
done, you confirmed it as well in this comment.

1. Placing COPYING file with the GPLv3 inside of the Spacemacs
   repository should be a minute of work. Plaint text format is here:
   https://www.gnu.org/licenses/gpl-3.0.txt

2. Source files can be distributed independently of the whole package,
   how the copyright notice each source file should look like one can
   see for example when you do M-x find-library RET async RET with the
   difference of author's names. Same information on "How to Apply
   These Terms to Your New Programs" is written in the license text of
   the GPL-3.0 above.

3. Read section from GPL-3.0:

   "An interactive user interface displays "Appropriate Legal Notices"
    to the extent that it includes a convenient and prominently
    visible feature that (1) displays an appropriate copyright notice,
    and (2) tells the user that there is no warranty for the work
    (except to the extent that warranties are provided), that
    licensees may convey the work under this License, and how to view
    a copy of this License.  If the interface presents a list of user
    commands or options, such as a menu, a prominent item in the list
    meets this criterion."

    As when one runs plain Emacs that is complied to, but when user
    runs Spacemacs there is no appropriate prominent item in the list
    to tell about licensing.





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

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=YEB9lqD82+i+TjYo@protected.rcdrun.com \
    --to=github.com@gnu.support \
    --cc=emacs-tangents@gnu.org \
    --cc=reply+AF5M4K5FIIIIYDUQTGUROR56JQ25DEVBNHHDBSUAQA@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).