all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Jan Moringen <jan.moringen@uni-bielefeld.de>
Cc: emacs-devel@gnu.org
Subject: Re: Potential copyright problem in EIEIO improvement
Date: Tue, 05 Jan 2010 15:45:01 -0500	[thread overview]
Message-ID: <E1NSGGz-0003zZ-Kp@fencepost.gnu.org> (raw)
In-Reply-To: <10232_1262665401_ZZg0O2_6YeI6u.00_1262665399.3761.1675.camel@localhost.localdomain> (message from Jan Moringen on Tue, 05 Jan 2010 05:23:19 +0100)

    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.

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.

Thanks.




  reply	other threads:[~2010-01-05 20:45 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 [this message]
2010-01-06  8:11                       ` David Kastrup
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=E1NSGGz-0003zZ-Kp@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.moringen@uni-bielefeld.de \
    /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.