emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alan L Tyree <alantyree@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: GFDL
Date: Sun, 10 Mar 2013 11:43:40 +1100	[thread overview]
Message-ID: <513BD73C.3050704@gmail.com> (raw)
In-Reply-To: <6D1B3E63-A3F0-447E-A1F4-12F8B3156DB9@gmail.com>

On 10/03/13 02:11, Carsten Dominik wrote:
>
> On 9.3.2013, at 16:02, Achim Gratz <Stromeko@nexgo.de> wrote:
>
>> Carsten Dominik writes:
>>> I am wondering, are we required to include the full text of the GFDL
>>> in the manual?  I find it a big waste of space and feed that a link
>>> should do.  But I have not been able to find the rules that say what
>>> needs to be included in a document distributed under GFDL?
>>
>> http://www.gnu.org/licenses/fdl-howto
>> http://www.gnu.org/licenses/fdl-1.3.html
>>
>> "To use this License in a document you have written, include a copy of
>> the License in the document and put the following copyright and license
>> notices just after the title page:[…]"
>>
>> I read this: If there's just one document, it must contain the license
>> in full, if there are several that reference each other, it is enough to
>> include it in the top-level document.
>
> Yes it sounds like it.  Thank you for the link.
>
> I still think it is crazy to add these 8 pages to each time someone prints it....
>
> Regards
>
> - Carsten
>
I also think it is crazy, and I don't think it is necessary. Although 
the FSF might prefer you to include the whole licence, in my opinion 
there is no need to do so. The manual is released under the GFDL and so 
is subject to the terms of the license.

In my view, this statement from Creative Commons is accurate:

"How can I license my work?

There is no registration to use the Creative Commons licenses.

Licensing a work is as simple as selecting which of the six licenses 
best meets your goals, and then marking your work in some way so that 
others know that you have chosen to release the work under the terms of 
that license."

The important part here is that "others know", that is, it must be very 
clear that the manual is released subject to the GFDL. As a courtesy, a 
link to the GFDL or including a copy as part of the package might be nice.

Alan



-- 
Alan L Tyree                    http://www2.austlii.edu.au/~alan
Tel:  04 2748 6206		sip:172385@iptel.org

  parent reply	other threads:[~2013-03-10  0:43 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 14:30 GFDL Carsten Dominik
2013-03-09 15:02 ` GFDL Achim Gratz
2013-03-09 15:11   ` GFDL Carsten Dominik
2013-03-09 15:25     ` GFDL Achim Gratz
2013-03-09 16:13       ` GFDL Carsten Dominik
2013-03-10 10:07         ` GFDL Bastien
2013-03-10 12:31           ` GFDL Achim Gratz
2013-03-10 14:06             ` GFDL Bastien
2013-03-10  0:43     ` Alan L Tyree [this message]
2013-03-19  6:44       ` GFDL Carsten Dominik
2013-03-19 15:42         ` GFDL Bastien
2013-03-19 19:06         ` GFDL Marcin Borkowski
2013-03-19 21:35           ` GFDL Bastien
2013-03-20  2:56             ` GFDL Marcin Borkowski
2013-03-20  6:01               ` GFDL Marcin Borkowski
2013-03-20 14:00                 ` GFDL Bastien
2013-03-20 15:25                   ` GFDL Marcin Borkowski
2013-03-20 19:55                     ` GFDL Marcin Borkowski
2013-04-06  1:05                       ` GFDL Bastien
2013-05-21  1:02         ` GFDL Ben Finney
2013-05-21 10:27           ` GFDL Bastien
2013-05-21 12:56             ` GFDL Sebastien Vauban
2013-05-21 13:01               ` GFDL Bastien
2013-05-26  3:35                 ` GFDL Ben Finney
2013-05-27  7:12                   ` GFDL Bastien
2013-06-04  9:35                     ` GFDL Ben Finney
2013-05-21 13:34               ` GFDL François Pinard
2013-05-21 14:18                 ` GFDL Carsten Dominik
2013-05-21 15:03                   ` GFDL François Pinard
2013-05-22  4:43                     ` GFDL Carsten Dominik
2013-05-21 16:12               ` [OT] Contributors to org.texi (was: GFDL) Memnon Anon

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=513BD73C.3050704@gmail.com \
    --to=alantyree@gmail.com \
    --cc=emacs-orgmode@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/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).