libstdc++-v3/doc/html/manual/appendix_free.html

   1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix C.  Free Software Needs Free Documentation</title><meta name="generator" content="DocBook XSL-NS Stylesheets V1.76.1"><meta name="keywords" content="
   2       ISO C++
   3     ,
   4       library
   5     "><meta name="keywords" content="
   6       ISO C++
   7     ,
   8       runtime
   9     ,
  10       library
  11     "><link rel="home" href="../index.html" title="The GNU C++ Library"><link rel="up" href="bk01pt04.html" title="Part IV.  Appendices"><link rel="prev" href="backwards.html" title="Backwards Compatibility"><link rel="next" href="appendix_gpl.html" title="Appendix D.  GNU General Public License version 3"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Appendix C.
  12   Free Software Needs Free Documentation
  13
  14 </th></tr><tr><td width="20%" align="left"><a accesskey="p" href="backwards.html">Prev</a> </td><th width="60%" align="center">Part IV.
  15   Appendices
  16 </th><td width="20%" align="right"> <a accesskey="n" href="appendix_gpl.html">Next</a></td></tr></table><hr></div><div class="appendix" title="Appendix C.  Free Software Needs Free Documentation"><div class="titlepage"><div><div><h1 class="title"><a name="appendix.free"></a>
  17   Free Software Needs Free Documentation
  18   <a class="indexterm" name="id688290"></a>
  19 </h1></div></div></div><p>
  20 The biggest deficiency in free operating systems is not in the
  21 software--it is the lack of good free manuals that we can include in
  22 these systems.  Many of our most important programs do not come with
  23 full manuals.  Documentation is an essential part of any software
  24 package; when an important free software package does not come with a
  25 free manual, that is a major gap.  We have many such gaps today.
  26 </p><p>
  27 Once upon a time, many years ago, I thought I would learn Perl.  I got
  28 a copy of a free manual, but I found it hard to read.  When I asked
  29 Perl users about alternatives, they told me that there were better
  30 introductory manuals--but those were not free.
  31 </p><p>
  32 Why was this?  The authors of the good manuals had written them for
  33 O'Reilly Associates, which published them with restrictive terms--no
  34 copying, no modification, source files not available--which exclude
  35 them from the free software community.
  36 </p><p>
  37 That wasn't the first time this sort of thing has happened, and (to
  38 our community's great loss) it was far from the last.  Proprietary
  39 manual publishers have enticed a great many authors to restrict their
  40 manuals since then.  Many times I have heard a GNU user eagerly tell
  41 me about a manual that he is writing, with which he expects to help
  42 the GNU project--and then had my hopes dashed, as he proceeded to
  43 explain that he had signed a contract with a publisher that would
  44 restrict it so that we cannot use it.
  45 </p><p>
  46 Given that writing good English is a rare skill among programmers, we
  47 can ill afford to lose manuals this way.
  48 </p><p>
  49   Free documentation, like free software, is a matter of freedom,
  50 not price.  The problem with these manuals was not that O'Reilly
  51 Associates charged a price for printed copies--that in itself is fine.
  52 (The Free Software Foundation <a class="link" href="http://www.gnu.org/doc/doc.html" target="_top">sells printed copies</a> of
  53 free GNU manuals, too.)  But GNU manuals are available in source code
  54 form, while these manuals are available only on paper.  GNU manuals
  55 come with permission to copy and modify; the Perl manuals do not.
  56 These restrictions are the problems.
  57 </p><p>
  58 The criterion for a free manual is pretty much the same as for free
  59 software: it is a matter of giving all users certain freedoms.
  60 Redistribution (including commercial redistribution) must be
  61 permitted, so that the manual can accompany every copy of the program,
  62 on-line or on paper.  Permission for modification is crucial too.
  63 </p><p>
  64 As a general rule, I don't believe that it is essential for people to
  65 have permission to modify all sorts of articles and books.  The issues
  66 for writings are not necessarily the same as those for software.  For
  67 example, I don't think you or I are obliged to give permission to
  68 modify articles like this one, which describe our actions and our
  69 views.
  70 </p><p>
  71 But there is a particular reason why the freedom to modify is crucial
  72 for documentation for free software.  When people exercise their right
  73 to modify the software, and add or change its features, if they are
  74 conscientious they will change the manual too--so they can provide
  75 accurate and usable documentation with the modified program.  A manual
  76 which forbids programmers to be conscientious and finish the job, or
  77 more precisely requires them to write a new manual from scratch if
  78 they change the program, does not fill our community's needs.
  79 </p><p>
  80 While a blanket prohibition on modification is unacceptable, some
  81 kinds of limits on the method of modification pose no problem.  For
  82 example, requirements to preserve the original author's copyright
  83 notice, the distribution terms, or the list of authors, are ok.  It is
  84 also no problem to require modified versions to include notice that
  85 they were modified, even to have entire sections that may not be
  86 deleted or changed, as long as these sections deal with nontechnical
  87 topics.  (Some GNU manuals have them.)
  88 </p><p>
  89 These kinds of restrictions are not a problem because, as a practical
  90 matter, they don't stop the conscientious programmer from adapting the
  91 manual to fit the modified program.  In other words, they don't block
  92 the free software community from making full use of the manual.
  93 </p><p>
  94 However, it must be possible to modify all the <span class="emphasis"><em>technical</em></span>
  95 content of the manual, and then distribute the result in all the usual
  96 media, through all the usual channels; otherwise, the restrictions do
  97 block the community, the manual is not free, and so we need another
  98 manual.
  99 </p><p>
 100 Unfortunately, it is often hard to find someone to write another
 101 manual when a proprietary manual exists.  The obstacle is that many
 102 users think that a proprietary manual is good enough--so they don't
 103 see the need to write a free manual.  They do not see that the free
 104 operating system has a gap that needs filling.
 105 </p><p>
 106 Why do users think that proprietary manuals are good enough?  Some
 107 have not considered the issue.  I hope this article will do something
 108 to change that.
 109 </p><p>
 110 Other users consider proprietary manuals acceptable for the same
 111 reason so many people consider proprietary software acceptable: they
 112 judge in purely practical terms, not using freedom as a criterion.
 113 These people are entitled to their opinions, but since those opinions
 114 spring from values which do not include freedom, they are no guide for
 115 those of us who do value freedom.
 116 </p><p>
 117 Please spread the word about this issue.  We continue to lose manuals
 118 to proprietary publishing.  If we spread the word that proprietary
 119 manuals are not sufficient, perhaps the next person who wants to help
 120 GNU by writing documentation will realize, before it is too late, that
 121 he must above all make it free.
 122 </p><p>
 123 We can also encourage commercial publishers to sell free, copylefted
 124 manuals instead of proprietary ones.  One way you can help this is to
 125 check the distribution terms of a manual before you buy it, and
 126 prefer copylefted manuals to non-copylefted ones.
 127 </p><p>
 128 [Note: We now maintain a <a class="link" href="http://www.fsf.org/licensing/doc/other-free-books.html" target="_top">web page
 129 that lists free books available from other publishers</a>].
 130 </p><p>Copyright © 2004, 2005, 2006, 2007 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA</p><p>Verbatim copying and distribution of this entire article are
 131 permitted worldwide, without royalty, in any medium, provided this
 132 notice is preserved.</p><p>Report any problems or suggestions to <code class="email">&lt;<a class="email" href="mailto:webmaster@fsf.org">webmaster@fsf.org</a>&gt;</code>.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="backwards.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="bk01pt04.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="appendix_gpl.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Backwards Compatibility </td><td width="20%" align="center"><a accesskey="h" href="../index.html">Home</a></td><td width="40%" align="right" valign="top"> Appendix D.
 133     <acronym class="acronym">GNU</acronym> General Public License version 3
 134   </td></tr></table></div></body></html>