unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: What license to use for Emacs libraries?
Date: Tue, 18 Aug 2015 21:11:45 -0400	[thread overview]
Message-ID: <jwvd1ykozpr.fsf-monnier+gnu.emacs.help@gnu.org> (raw)
In-Reply-To: mailman.8593.1439940074.904.help-gnu-emacs@gnu.org

> OK, thanks for the clarification.  As I said a moment ago, the
> distinction between GPLvn and GPLvn+ escaped me.  That explains a lot.
> (Still, all this licensing stuff feels much like craziness to me.)

Yes, I think most people agree it's crazy.  So the sane thing to do is
to go with the standard (which in this case is GPLv3+ or GPLv2+) and
move on.

> Still, it is kind of funny: it is not enough to look into the
> file named LICENSE to learn what license the code is under.

The standard COPYING file just contains the definition of the GPLvN
license, but doesn't say which files it applies to.

Instead, each file says individually under which license it is
distributed (referring back to the COPYING file, basically).

To a large extent the COPYING file is redundant, since the definition of
the GPLvN is something you can find easily even if the COPYING file
is missing.

>>> Does that mean that GitHub is a part of a sinister software-patent
>>> conspiracy or something?
>> That wouldn't be a surprise, now, would it?
> Now that Phillip warned me (implicitly) about GitHub police visiting me
> at 5am with handcuffs I'm afraid to say anything more on this topic. ;-)

I don't think they'd bother with handcuffs,


        Stefan


  parent reply	other threads:[~2015-08-19  1:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 21:06 What license to use for Emacs libraries? Marcin Borkowski
2015-08-18 21:48 ` Phillip Lord
2015-08-18 22:01   ` Stefan Monnier
2015-08-18 22:15     ` Phillip Lord
2015-08-18 23:46       ` Robert Thorpe
2015-08-19 14:12         ` Phillip Lord
2015-08-20  7:05         ` Steinar Bang
2015-08-18 23:16   ` Marcin Borkowski
2015-08-19 14:36     ` Tassilo Horn
2015-08-19 21:46       ` Robert Thorpe
2015-08-20  4:44         ` Tassilo Horn
2015-08-19 16:00     ` Phillip Lord
2015-08-18 21:53 ` Stefan Monnier
2015-08-18 23:21   ` Marcin Borkowski
     [not found]   ` <mailman.8593.1439940074.904.help-gnu-emacs@gnu.org>
2015-08-19  1:11     ` Stefan Monnier [this message]
2015-08-19 16:02       ` Phillip Lord

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=jwvd1ykozpr.fsf-monnier+gnu.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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).