From: Jan Moringen <jan.moringen@uni-bielefeld.de>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Potential copyright problem in EIEIO improvement
Date: Tue, 05 Jan 2010 05:23:19 +0100 [thread overview]
Message-ID: <10232_1262665401_ZZg0O2_6YeI6u.00_1262665399.3761.1675.camel@localhost.localdomain> (raw)
In-Reply-To: <E1NRpii-0004qB-TF@fencepost.gnu.org>
On Mon, 2010-01-04 at 11:23 -0500, Richard Stallman wrote:
> I think, the most important part is the code in Appendix B since
> code
> very similar to Appendix A is available in Open Dylan (I included
> both
> in my last email). My code could have been derived from the Open
> Dylan
> code except for the improvement presented in Appendix B.
>
> I'm talking about the code from Open Dylan. That is 50 lines, and
> normally we would not install 50 lines without getting papers for
> them. I will ask whether we can make an exception, once I have enough
> info.
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. I wasn't aware of that. Thanks for pointing it out.
> Dual-license: GNU Lesser General Public License
>
> Does it say what version?
I found a license file in the Open Dylan project root directory which
says:
GNU LESSER GENERAL PUBLIC LICENSE
Version 2.1, February 1999
Kind regards,
Jan
next prev parent reply other threads:[~2010-01-05 4:23 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 [this message]
2010-01-05 20:45 ` Richard Stallman
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
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=10232_1262665401_ZZg0O2_6YeI6u.00_1262665399.3761.1675.camel@localhost.localdomain \
--to=jan.moringen@uni-bielefeld.de \
--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 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).