unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Carsten Dominik <dominik@uva.nl>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	emacs-devel Mailinglist <emacs-devel@gnu.org>
Subject: Re: Copyright question
Date: Fri, 13 Jun 2008 11:59:35 +0200	[thread overview]
Message-ID: <86r6b1irjs.fsf@lola.quinscape.zz> (raw)
In-Reply-To: <AF946339-A1D4-4C78-B186-56430EC5E0F1@uva.nl> (Carsten Dominik's message of "Fri, 13 Jun 2008 10:19:53 +0200")

Carsten Dominik <dominik@uva.nl> writes:

> On Jun 12, 2008, at 9:33 PM, Stefan Monnier wrote:
>
>>> I would like to switch the copyright of the Org-mode manual to GPL.
>>> Currently it is GFDL, with front/back cover texts, and I am told
>>> that the Debian cannot include this in their distribution - 
>>> therefore,
>>> the Org-mode package in Debian is currently without Manual.
>>
>> Actually, Debian can and does include such things in their
>> distribution,
>> but in the `non-free' section.  This is the case for the Emacs online
>> docs (in package emacs22-common-non-dfsg).
>>
>> Also, you do not need to abandon the GFDL to be allowed in the main
>> section of Debian.  You "only" need to use the GFDL without any
>> front&back matters (IIRC).
>
> Well, I am happy with this solution, so I am going to remove these
> parts from the copyright notice.  The copyright notice will now read:
>
> @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.
> @end quotation
>
> Any objections?

General GNU project policy is to distribute with certain front&back
matters.  So I'd ask Richard whether he is ok with it since he still is
pretty much the one setting the project licensing policies in Emacs.

Note that for the distribution as an integral part of Emacs, this is
sort of pointless, since the Emacs manuals are "Debian non-free" anyway
and so it is not particularly useful if org-mode is different here.

For the org-mode distributed separately by yourself, I believe it is
utlimately your own call to make, though it would be appropriate, if it
is registered as a GNU project, to apply the general guidelines to it.

-- 
David Kastrup




  reply	other threads:[~2008-06-13  9:59 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-12 14:43 Copyright question Carsten Dominik
2008-06-12 19:30 ` David Hansen
2008-06-12 19:33 ` Stefan Monnier
2008-06-13  8:19   ` Carsten Dominik
2008-06-13  9:59     ` David Kastrup [this message]
2008-06-13 22:48     ` Richard M Stallman
2008-06-14 13:15       ` Carsten Dominik
2008-06-14 20:11         ` Don Armstrong
2008-06-15 17:55         ` Richard M Stallman
2008-06-12 19:40 ` Glenn Morris
2008-06-12 20:47   ` Juanma Barranquero
2008-06-12 20:51     ` İsmail Dönmez
2008-06-12 23:31       ` Glenn Morris
2008-06-13  8:55         ` Andreas Röhler
2008-06-13  9:44           ` Alan Mackenzie
2008-06-13  9:36             ` Miles Bader
2008-06-13 13:35               ` Stefan Monnier
2008-06-13 10:35             ` Andreas Röhler
2008-06-13 11:00               ` David Kastrup
2008-06-12 21:08     ` David Kastrup
2008-06-12 21:31 ` Don Armstrong
2008-06-12 23:03   ` Bastien
2008-06-13  3:13     ` Alfred M. Szmidt
2008-06-13  4:06 ` Richard M Stallman
2008-06-13  7:58   ` Stephen J. Turnbull
2008-06-13  9:51   ` David Kastrup
2008-06-13  9:58   ` Alan Mackenzie
2008-06-13 22:48     ` Richard M Stallman
2008-06-14 12:03       ` Alan Mackenzie
2008-06-14 19:16         ` Glenn Morris
2008-06-14 19:28         ` Eli Zaretskii
2008-06-14 21:36         ` David Kastrup

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=86r6b1irjs.fsf@lola.quinscape.zz \
    --to=dak@gnu.org \
    --cc=dominik@uva.nl \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).