taler-merchant-demos

Python-based Frontends for the Demonstration Web site
Log | Files | Refs | Submodules | README | LICENSE

using-gfdl.html (6259B)


      1 <!--#include virtual="/server/header.html" -->
      2 <!-- Parent-Version: 1.96 -->
      3 <!-- This page is derived from /server/standards/boilerplate.html -->
      4 <!--#set var="TAGS" value="essays licensing copyleft" -->
      5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
      6 <title>Using GNU FDL
      7 - GNU Project - Free Software Foundation</title>
      8 <!--#include virtual="/philosophy/po/using-gfdl.translist" -->
      9 <!--#include virtual="/server/banner.html" -->
     10 <!--#include virtual="/philosophy/ph-breadcrumb.html" -->
     11 <!--GNUN: OUT-OF-DATE NOTICE-->
     12 <!--#include virtual="/server/top-addendum.html" -->
     13 <div class="article reduced-width">
     14 <h2>Using GNU FDL</h2>
     15 
     16 <address class="byline">by <a href="https://www.stallman.org/">Richard
     17 Stallman</a></address>
     18 
     19 <p>If you know someone who is writing a manual about free software,
     20 and looking towards commercial publication, you have a chance to help
     21 the Free Software Movement a great deal with a small amount of work:
     22 by suggesting the idea of publishing the manual under
     23 the <a href="/licenses/fdl.html">GNU Free Documentation
     24 License</a>.</p>
     25 
     26 <p>Until recently, commercial book publication almost always implied a
     27 nonfree book.  But just as free commercial software has been
     28 increasing for a while, now free commercial documentation is starting
     29 to take off as well.  Some of the major commercial publishers of
     30 documentation about the <a href= "/gnu/linux-and-gnu.html">GNU/Linux
     31 system</a>, and about free software in general, are now willing to
     32 publish books under the GNU FDL, and pay the authors in the usual
     33 way&mdash;IF the authors are firm about this.</p>
     34 
     35 <p>But publishers are likely to first propose an ordinary proprietary
     36 book. And if the authors agree, that's what it will be.  So it is
     37 essential for authors to take the lead; to say, &ldquo;We want to use
     38 the GNU FDL for this book.&rdquo;  So when your friend mentions
     39 writing a manual, you can influence the course of events simply by
     40 pointing out this possibility.</p>
     41 
     42 <p>If a publisher rejects the request at first, the GNU Project may be
     43 able to help the authors prevail.  They can contact us
     44 at <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.</p>
     45 
     46 <p>There
     47 are <a href="/licenses/license-list.html#DocumentationLicenses">
     48 other</a> legitimate free documentation licenses, but sometimes using
     49 them requires care. For example, one license is equipped with two
     50 optional clauses that can be enabled; the license is free if neither
     51 optional clause is used, but enabling either of them makes the book
     52 nonfree.  (See <a href="/licenses/license-list.html">
     53 gnu.org/licenses/license-list.html</a>.) Authors that want
     54 to publish free documentation, but using a license other than the GNU
     55 FDL, can contact us so we can check that the license really qualifies
     56 for free documentation.</p>
     57 
     58 <p>When a commercial manual is free and relates to the GNU system, the
     59 GNU Project can recommend it to the public.  So if the authors or
     60 publisher set up a web page to describe it and/or sell copies, we can
     61 make a link to that page from <a
     62 href="/doc/other-free-books.html">www.gnu.org/doc/other-free-books.html</a>,
     63 provided the page meets our usual criteria (for instance, it should
     64 not link to other pages about nonfree software or documentation, and
     65 should not be obnoxious about trying to persuade people to buy).
     66 Please inform <a href="mailto:webmasters@gnu.org">
     67 &lt;webmasters@gnu.org&gt;</a> about such pages.</p>
     68 <hr class="column-limit" />
     69 
     70 <p>See also <a href="/philosophy/free-doc.html">Free Software and Free
     71 Manuals</a>.</p>
     72 </div>
     73 
     74 </div><!-- for id="content", starts in the include above -->
     75 <!--#include virtual="/server/footer.html" -->
     76 <div id="footer" role="contentinfo">
     77 <div class="unprintable">
     78 
     79 <p>Please send general FSF &amp; GNU inquiries to
     80 <a href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.
     81 There are also <a href="/contact/">other ways to contact</a>
     82 the FSF.  Broken links and other corrections or suggestions can be sent
     83 to <a href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>
     84 
     85 <p><!-- TRANSLATORS: Ignore the original text in this paragraph,
     86         replace it with the translation of these two:
     87 
     88         We work hard and do our best to provide accurate, good quality
     89         translations.  However, we are not exempt from imperfection.
     90         Please send your comments and general suggestions in this regard
     91         to <a href="mailto:web-translators@gnu.org">
     92         &lt;web-translators@gnu.org&gt;</a>.</p>
     93 
     94         <p>For information on coordinating and contributing translations of
     95         our web pages, see <a
     96         href="/server/standards/README.translations.html">Translations
     97         README</a>. -->
     98 Please see the <a
     99 href="/server/standards/README.translations.html">Translations
    100 README</a> for information on coordinating and contributing translations
    101 of this article.</p>
    102 </div>
    103 
    104 <!-- Regarding copyright, in general, standalone pages (as opposed to
    105      files generated as part of manuals) on the GNU web server should
    106      be under CC BY-ND 4.0.  Please do NOT change or remove this
    107      without talking with the webmasters or licensing team first.
    108      Please make sure the copyright date is consistent with the
    109      document.  For web pages, it is ok to list just the latest year the
    110      document was modified, or published.
    111      
    112      If you wish to list earlier years, that is ok too.
    113      Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
    114      years, as long as each year in the range is in fact a copyrightable
    115      year, i.e., a year in which the document was published (including
    116      being publicly visible on the web or in a revision control system).
    117      
    118      There is more detail about copyright years in the GNU Maintainers
    119      Information document, www.gnu.org/prep/maintain. -->
    120 
    121 <p>Copyright &copy; 1999, 2021 Richard M. Stallman</p>
    122 
    123 <p>This page is licensed under a <a rel="license"
    124 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
    125 Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
    126 
    127 <!--#include virtual="/server/bottom-notes.html" -->
    128 
    129 <p class="unprintable">Updated:
    130 <!-- timestamp start -->
    131 $Date: 2021/09/10 10:58:36 $
    132 <!-- timestamp end -->
    133 </p>
    134 </div>
    135 </div><!-- for class="inner", starts in the banner include -->
    136 </body>
    137 </html>