all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: "Stephen J. Turnbull" <stephen@xemacs.org>,
	emacs-devel@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: Lawyer's evaluation
Date: Wed, 24 Sep 2003 19:58:42 +0900	[thread overview]
Message-ID: <877k3yxxjx.fsf@tleepslib.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <m3k77yo8kj.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "24 Sep 2003 11:10:52 +0200")

>>>>> "Kim" == Kim F Storm <storm@cua.dk> writes:

    Kim> What about combining things like this:

There are several good ideas here, but there are a couple of problems.

    Kim> "Free" means that all users have the freedom to study, share,
    Kim> change and improve Emacs.  In fact, you may freely use and
    Kim> modify Emacs for your own purposes without knowing any of the
    Kim> details of the GPL.

This is misleading; in order to modify Emacs you must accept the GPL.
Sure, you can accept it without knowing the details, but we don't want
to encourage that.

    Kim> However, once you distribute your changes to others, you
    Kim> should be aware that the conditions and rights in the GPL
    Kim> will extend to cover your changes as well, so before doing

In fact, it implies acceptance of the license.  That means we really
need to say that such distribution must follow the terms of the
license.  I don't see how that can happen if the user doesn't read it.

    Kim> so, you are strongly advised to read the license.

    Kim> Also, if you write and distribute an extension to Emacs in
    Kim> Emacs Lisp (the extension language used by Emacs), that
    Kim> extension will be covered by the GPL too, as running such an
    Kim> extension requires "linking" with Emacs.

This is true only if you put a strict interpretation on Emacs Lisp,
ie, those parts of Lisp that are unique to Emacs Lisp.  True, in
practice it's hard to imagine substantial Lisp applications that don't
do buffer I/O, etc, being written in Emacs Lisp, but it's possible.

I don't think it's a good idea to put debatable statements here, even
if they are pragmatically correct.

-- 
Institute of Policy and Planning Sciences     http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba                    Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
               Ask not how you can "do" free software business;
              ask what your business can "do for" free software.

  reply	other threads:[~2003-09-24 10:58 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-18 22:44 Lawyer's evaluation Richard Stallman
2003-09-18 23:16 ` Miles Bader
2003-09-19 13:56   ` Stephen J. Turnbull
2003-09-22  2:02     ` Miles Bader
2003-09-24  5:27       ` Stephen J. Turnbull
2003-09-25 12:05         ` Richard Stallman
2003-09-24  9:10       ` Kim F. Storm
2003-09-24 10:58         ` Stephen J. Turnbull [this message]
2003-09-24 12:19           ` Kim F. Storm
2003-09-24 14:41             ` Stephen J. Turnbull
2003-09-25 12:06           ` Richard Stallman
2003-09-25 12:06         ` Richard Stallman
2003-09-25 12:42           ` David Kastrup
2003-09-26  9:53             ` Richard Stallman

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=877k3yxxjx.fsf@tleepslib.sk.tsukuba.ac.jp \
    --to=stephen@xemacs.org \
    --cc=emacs-devel@gnu.org \
    --cc=miles@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.