emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <C.Dominik@uva.nl>
To: Seb <seb@untangle.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Re: GFDL with cover texts
Date: Thu, 12 Jun 2008 07:51:15 +0200	[thread overview]
Message-ID: <98F264E2-8247-431F-896C-0F6945E33016@uva.nl> (raw)
In-Reply-To: <slrng505m7.fca.seb@mephisto.metaloft.com>

Hi Sebastian,

On Jun 11, 2008, at 8:17 PM, Seb wrote:

> On 2008-06-10, Dominik, C. <C.Dominik@uva.nl> wrote:
>> I would be happy to dual-license the manual.  Does anyone know what
>> piece of text I would have to put there?  Does anyone know if the
>> GFDL prohbits me, the author, to add GPL as a second free license?
>> I sure hope not.
>> [...]
>> To be honest, I have absolutely no clue what it means, and it was
>> not my intention to restrict use of the manual in any way when I put
>> it under the GFDL.  Back then I must have thought that this simply
>> it the proper thing to use for documentation.
>
> The GFDL itself is fine, it's the use of Invariant Sections, Cover
> Texts, etc that make it not-free as far as Debian is concerned.
>
> But anyway, if you're the sole author, you can definitely move to a
> GPL+GFDL dual-license when you so please, but I guess I still need to
> add that IANAL...

I don't know what this last sentence means.

ALso, can you point me to an example of the text that I would have to  
insert to make you and Debian happy?

Thanks.

- Carsten

  reply	other threads:[~2008-06-12  6:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-06 21:07 GFDL with cover texts Seb
2008-06-06 21:19 ` Seb
2008-06-08 16:31   ` Seb
2008-06-09  2:00     ` Sebastian Rose
2008-06-11 16:43       ` Seb
2008-06-10  6:32     ` Dominik, C.
2008-06-11 18:17       ` Seb
2008-06-12  5:51         ` Carsten Dominik [this message]
2008-06-12 15:07           ` Seb

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.orgmode.org/

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

  git send-email \
    --in-reply-to=98F264E2-8247-431F-896C-0F6945E33016@uva.nl \
    --to=c.dominik@uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --cc=seb@untangle.com \
    /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/org-mode.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).