[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Cover Texts in the automake documentation
From: |
Ben Pfaff |
Subject: |
Re: Cover Texts in the automake documentation |
Date: |
Mon, 10 Apr 2006 10:15:42 -0700 |
User-agent: |
Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux) |
Eric Dorland <address@hidden> writes:
> * Alexandre Duret-Lutz (address@hidden) wrote:
>>
>> Eric:
>> | Is there any way you might consider dropping the
>> | Front and Back Cover Texts requirements from the manual?
>>
>> Sorry, this is the FSF policy. Not my call.
>
> Could you please point out where the FSF have made this policy?
http://www.gnu.org/prep/maintain/maintain.html#License-Notices
Documentation files should have license notices also. Manuals
should use the GNU Free Documentation License. Here is an example
of the license notice to use after the copyright notice. Please
adjust the list of invariant sections as appropriate for your
manual. (If there are none, then say with no invariant sections.)
See GNU Sample Texts, for a full example in a Texinfo manual.
Permission is granted to copy, distribute and/or modify this
document under the terms of the GNU Free Documentation
License, Version 1.2 or any later version published by the
Free Software Foundation; with the Invariant Sections being
"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".
(a) The FSF's Back-Cover Text is: ``You are free to copy
and modify this GNU Manual. Buying copies from GNU
Press supports the FSF in developing GNU and promoting
software freedom.''
If the FSF does not publish this manual on paper, then omit the
last sentence in (a) that talks about copies from GNU Press. If
the FSF is not the copyright holder, then replace FSF with the
appropriate name.
--
On Perl: "It's as if H.P. Lovecraft, returned from the dead and speaking by
seance to Larry Wall, designed a language both elegant and terrifying for his
Elder Things to write programs in, and forgot that the Shoggoths didn't turn
out quite so well in the long run." --Matt Olson