From: Chong Yidong <cyd@stupidchicken.com>
To: Dave Love <fx@gnu.org>
Cc: Glenn Morris <rgm@gnu.org>, emacs-devel@gnu.org
Subject: Re: legal status of progmodes/sym-comp.el
Date: Thu, 21 Feb 2008 14:02:38 -0500 [thread overview]
Message-ID: <8763wiw2sx.fsf@stupidchicken.com> (raw)
In-Reply-To: <3h7igyw31a.fsf@fencepost.gnu.org> (Glenn Morris's message of "Thu\, 21 Feb 2008 13\:57\:37 -0500")
Glenn Morris <rgm@gnu.org> writes:
> It's can of worms time again...
>
> Dave Love's latest version of python.el requires his sym-comp library.
> This is now installed as lisp/progmodes/sym-comp.el.
> It is "Copyright (C) 2004 Dave Love".
>
> As far as I know, he has expressed no interest in contributing this to
> Emacs, so I don't see that we can just take it and make it copyright FSF.
>
> I mean, I have a blanket past and future Emacs copyright assignment,
> but that doesn't mean you can take any elisp code I happen to put on a
> website and make it copyright FSF - only those things I explicitly
> contribute.
>
> (We seem to be interpreting the lawyer's statement:
>
> http://lists.gnu.org/archive/html/emacs-devel/2007-05/msg00466.html
> From: Richard Stallman
> Subject: We can use python.el
> Date: Sat, 12 May 2007 12:47:54 -0400
>
> Our lawyer says we can use python.el, including the more recent changes.
>
> to mean that any changes Dave makes to python.el on his website can be
> incorporated into Emacs for the rest of time, even if he doesn't
> explicitly say so. That seems odd to me as well.)
Thanks for the catch. I'm forwarding this to Dave Love as well.
next prev parent reply other threads:[~2008-02-21 19:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-21 18:57 legal status of progmodes/sym-comp.el Glenn Morris
2008-02-21 19:02 ` Chong Yidong [this message]
2008-02-22 19:48 ` Dave Love
2008-02-22 20:26 ` Chong Yidong
2008-02-27 0:36 ` Dave Love
2008-02-22 20:37 ` Glenn Morris
2008-02-29 0:14 ` Dave Love
2008-02-29 2:00 ` Stefan Monnier
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=8763wiw2sx.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=fx@gnu.org \
--cc=rgm@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.