Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Documentation licenses
Date: Tue, 18 May 2004 15:58:53 +0200	[thread overview]
Message-ID: <v9oeolltuq.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3wu3cynbu.fsf@quimbies.gnus.org>

On Mon, May 17 2004, Lars Magne Ingebrigtsen wrote:

> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>
>> Maybe we can't do this for pgg.texi, sasl.texi and possibly other
>> manuals distributed with Gnus.
>
> And the copyright is assigned to the FSF, so perhaps the easiest
> thing to do would be for me to ask Richard if it'd be OK to
> dual-licence the manuals? 

Hm, the Emacs manual is also licensed under GFDL:

,----[ man/emacs.texi ]
| @quotation
| Permission is granted to copy, distribute and/or modify this document
| under the terms of the GNU Free Documentation License, Version 1.1 or
| any later version published by the Free Software Foundation; with the
| Invariant Sections being ``The GNU Manifesto'', ``Distribution'' and
| ``GNU GENERAL PUBLIC LICENSE'', with the Front-Cover texts being ``A GNU
| Manual,'' and with the Back-Cover Texts as in (a) below.  A copy of the
| license is included in the section entitled ``GNU Free Documentation
| License.''
| [...]
`----

So it would probably make more sense if the debian-legal people find
some agreement with the Emacs maintainers.  (Will Debian also remove
GNU Emacs or move if to "non-free" otherwise?)

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2004-05-18 13:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28 17:39 Manoj Srivastava
2004-05-16 11:59 ` Lars Magne Ingebrigtsen
2004-05-16 17:09   ` Reiner Steib
2004-05-16 23:16     ` Lars Magne Ingebrigtsen
2004-05-18 13:58       ` Reiner Steib [this message]
2004-05-18 14:17         ` Lars Magne Ingebrigtsen
2004-05-19 15:13           ` Manoj Srivastava
2004-05-19 15:46             ` Lars Magne Ingebrigtsen

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=v9oeolltuq.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.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.
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 NNTP newsgroup(s).