From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Bad choice of license in BzrForEmacsDevs
Date: Thu, 26 Nov 2009 09:05:41 +0900 [thread overview]
Message-ID: <87iqcy8816.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <E1NDOzf-00032S-SV@fencepost.gnu.org>
Richard Stallman writes:
> allowing GPLv2 and not GPLv3 is a very bad example. We should not
> set a bad licensing example.
Please get your lawyer to look at it. It was the need of XEmacs for a
license compatible with the unnamed, unversioned documentation license
we inherited from Lucid (which presumably inherited it from Emacs 18
and Emacs 19) that inspired the multiple licensing. Alex wanted to
generalize it, so the *intent* is that any license that grants the
listed rights and requires that they be granted to those "downstream"
of the licensee may be used. GPLv3 clearly qualifies by the intent.
I am fairly sure that Alex would be happy to modify the permission
notice based on a lawyer's advice on how to accomplish his intention.
> In addition, I wonder about the other pages in that wiki have a
> similar license.
All pages in the wiki are licensed that way.
I spot-checked one of the major programs distributed on the wiki, Drew
Adams's "icicles". The pages describing the program say it is "GPL v2
or later" although the pages have the standard permission notice for
the wiki. The libraries themselves contain the standard permission
notice, for "GPL v2 or later".
So I don't think there is a general problem with programs; anything
large enough to have a separate file probably has the standard
notice. Snippets of code included directly in a page will have the
page's license, of course, but AFAIK nobody using the wiki believes
that the GPL is only permitted as version 2. (I understand that what
a court says may vary; please help Alex get the legal advice he needs
to accomplish his intention.)
next prev parent reply other threads:[~2009-11-26 0:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-23 2:29 Bad choice of license in BzrForEmacsDevs Richard Stallman
2009-11-23 3:30 ` Karl Fogel
2009-11-23 20:37 ` Richard Stallman
2009-11-23 21:12 ` Lennart Borgman
2009-11-24 22:47 ` Richard Stallman
2009-11-24 22:57 ` Jay Belanger
2009-11-24 23:06 ` Les Harris
2009-11-25 2:38 ` Stefan Monnier
2009-11-23 21:32 ` Jay Belanger
2009-11-25 21:01 ` Richard Stallman
2009-11-25 21:19 ` Karl Fogel
2009-11-26 6:22 ` Richard Stallman
2009-11-25 21:32 ` Stefan Monnier
2009-11-25 21:52 ` Lennart Borgman
2009-11-25 21:52 ` Lennart Borgman
2009-11-25 22:02 ` Lennart Borgman
2009-11-26 6:23 ` Richard Stallman
2009-11-26 15:47 ` Jonas Bernoulli
2009-11-26 8:52 ` David Kastrup
2009-11-26 16:34 ` Stefan Monnier
2009-11-26 17:41 ` Lennart Borgman
2009-11-27 2:12 ` Stefan Monnier
2009-11-27 6:35 ` Richard Stallman
2009-11-26 0:05 ` Stephen J. Turnbull [this message]
2009-11-26 0:02 ` Lennart Borgman
2009-11-25 18:44 ` Giorgos Keramidas
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87iqcy8816.fsf@uwakimon.sk.tsukuba.ac.jp \
--to=stephen@xemacs.org \
--cc=emacs-devel@gnu.org \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.