From: David Kastrup <dak@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Potential copyright problem in EIEIO improvement
Date: Wed, 06 Jan 2010 09:11:57 +0100 [thread overview]
Message-ID: <87aawrhctu.fsf@lola.goethe.zz> (raw)
In-Reply-To: E1NSGGz-0003zZ-Kp@fencepost.gnu.org
Richard Stallman <rms@gnu.org> writes:
> So in order to derive GPLed code from the GPLed Open Dylan code and
> assign the copyright of the new code to the FSF, the Open Dylan authors
> have to sign papers.
>
> Right. However, it would be obnoxious to ask them to assign their
> copyright to the FSF, because they didn't intend it as a contribution
> to GNU Emacs. Therefore, we must not ask. That puts us in a bit of a
> bind.
I think that in this case asking for a disclaimer should be more than
sufficient: after all, the code in question has been used as a template
but not used verbatim. So at most an original code citation in the
comment should not be covered by Emacs copyright, but the resulting
Elisp code should be sufficient original expression.
But since the original code has been released under the GPL (which
one?), a separate disclaimer should likely not even be necessary: the
GPL _is_ a license to "relicense" under the GPL.
> So I will ask our lawyers if it is ok if we use taht Dylan code
> without getting papers for it. Now I know all the facts I need to
> tell them.
Likely.
--
David Kastrup
next prev parent reply other threads:[~2010-01-06 8:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-30 2:49 Potential copyright problem in EIEIO improvement Jan Moringen
2009-12-30 5:42 ` Eli Zaretskii
2009-12-31 3:16 ` Jan Moringen
2009-12-31 1:45 ` Richard Stallman
2009-12-31 3:25 ` Jan Moringen
2010-01-01 2:55 ` Richard Stallman
2010-01-01 18:52 ` Jan Moringen
2010-01-02 15:45 ` Richard Stallman
2010-01-03 18:52 ` Jan Moringen
2010-01-04 4:09 ` Richard Stallman
2010-01-04 5:37 ` Jan Moringen
2010-01-04 16:23 ` Richard Stallman
2010-01-05 4:23 ` Jan Moringen
2010-01-05 20:45 ` Richard Stallman
2010-01-06 8:11 ` David Kastrup [this message]
2010-01-30 21:32 ` Richard Stallman
2010-02-01 3:02 ` Jan Moringen
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=87aawrhctu.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).