From: David Kastrup <dak@gnu.org>
Subject: Re: beamer, pdflatex and auctex
Date: Thu, 19 Oct 2006 03:27:41 +0200 [thread overview]
Message-ID: <853b9lxfg2.fsf@lola.goethe.zz> (raw)
In-Reply-To: mailman.81.1161219122.2130.help-gnu-emacs@gnu.org
Dieter Wilhelm <dieter@duenenhof-wilhelm.de> writes:
> David Kastrup <dak@gnu.org> writes:
>
>> Dieter Wilhelm <dieter@duenenhof-wilhelm.de> writes:
>>
>>> Why is this not sufficient for including their work in the
>>> official Emacs installation, why must they even give up their
>>> copyright? They already stated that their code can be reused by
>>> everyone, couldn't it?
>>
>> They made no legally binding statement whatsoever.
>
> From a legal point of view clearly problematic, with common sense
> it's another story. When I give something to a "charity" I'm not
> eligible to claim later on "interest".
But if there is no proof that you have given anything, that does not
help.
>> Emacs is too important for the FSF to risk that.
>
> <off_topic>
> I'm curious whether the usage of Emacs and TeX is still growing or has
> reached some saturation / decline in this age of graphical IDEs.
> </off_topic>
My guess is that percentages decrease and absolute numbers increase.
> Furthermore I'm interested whether the guys in the snippet below
> have signed legal papers for the FSF (as is claimed in a certain
> lisp file), I'm using and reworking their code. Do you know how I
> could get this piece of information in an unbureaucratic way?
>
> ;; This file containes code from ansys-mod.el.
> ;; Copyright (C) 1997 Free Software Foundation, Inc.
> ;; Author: Tim Read <Tim.Read@fp.co.nz> (Author does not respond)
> ;; Author: Geoff Foster <fosterg@fp.co.nz> (Address unreachable,
> ;; Dieter Wilhelm 2006-03-08)
I don't see an assignment from either person in the copyright
assignment file accessible by GNU maintainers.
Where did you get the claim?
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-10-19 1:27 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7941.1160431815.9609.help-gnu-emacs@gnu.org>
2006-10-09 22:22 ` beamer, pdflatex and auctex David Kastrup
2006-10-09 23:00 ` Xavier Maillard
[not found] ` <mailman.7943.1160434867.9609.help-gnu-emacs@gnu.org>
2006-10-09 23:26 ` David Kastrup
2006-10-14 15:20 ` Dieter Wilhelm
[not found] ` <mailman.8143.1160840051.9609.help-gnu-emacs@gnu.org>
2006-10-15 22:17 ` David Kastrup
2006-10-16 1:02 ` Dieter Wilhelm
[not found] ` <mailman.8198.1160960624.9609.help-gnu-emacs@gnu.org>
2006-10-16 7:41 ` David Kastrup
2006-10-16 21:26 ` Dieter Wilhelm
[not found] ` <mailman.5.1161034016.2130.help-gnu-emacs@gnu.org>
2006-10-16 21:51 ` David Kastrup
2006-10-19 0:51 ` Dieter Wilhelm
[not found] ` <mailman.81.1161219122.2130.help-gnu-emacs@gnu.org>
2006-10-19 1:27 ` David Kastrup [this message]
2006-10-19 6:55 ` Dieter Wilhelm
[not found] ` <mailman.88.1161240959.2130.help-gnu-emacs@gnu.org>
2006-10-19 7:31 ` David Kastrup
2006-10-20 0:01 ` Dieter Wilhelm
[not found] ` <mailman.13.1161359797.27805.help-gnu-emacs@gnu.org>
2006-10-20 20:48 ` David Kastrup
2006-10-21 8:50 ` Dieter Wilhelm
2006-10-21 11:59 ` David Kastrup
2006-10-21 19:28 ` Dieter Wilhelm
2006-10-09 22:10 Xavier Maillard
2006-10-09 22:29 ` Peter Dyballa
2006-10-09 23:00 ` Xavier Maillard
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=853b9lxfg2.fsf@lola.goethe.zz \
--to=dak@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.
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).