OpenCores
URL https://opencores.org/ocsvn/openrisc/openrisc/trunk

Subversion Repositories openrisc

[/] [openrisc/] [trunk/] [gnu-stable/] [gcc-4.5.1/] [libstdc++-v3/] [doc/] [xml/] [manual/] [appendix_free.xml] - Blame information for rev 826

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 424 jeremybenn
2
3
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"
4
[ ]>
5
 
6
7
8
 
9
10
  
11
    
12
      ISO C++
13
    
14
    
15
      library
16
    
17
  
18
19
 
20
</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>21</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  Free Software Needs Free Documentation</code></pre></td>
      </tr>
      <tr valign="middle">
         <td>22</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  <indexterm></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>23</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>    <primary>Appendix</primary></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>24</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>    <secondary>Free Documentation</secondary></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>25</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>  </indexterm></code></pre></td>
      </tr>
      <tr valign="middle">
         <td>26</td>
         <td></td>
         <td></td>
         <td class="code"><pre><code>
27
 
28
29
The biggest deficiency in free operating systems is not in the
30
software--it is the lack of good free manuals that we can include in
31
these systems.  Many of our most important programs do not come with
32
full manuals.  Documentation is an essential part of any software
33
package; when an important free software package does not come with a
34
free manual, that is a major gap.  We have many such gaps today.
35
36
 
37
38
Once upon a time, many years ago, I thought I would learn Perl.  I got
39
a copy of a free manual, but I found it hard to read.  When I asked
40
Perl users about alternatives, they told me that there were better
41
introductory manuals--but those were not free.
42
43
 
44
45
Why was this?  The authors of the good manuals had written them for
46
O'Reilly Associates, which published them with restrictive terms--no
47
copying, no modification, source files not available--which exclude
48
them from the free software community.
49
50
 
51
52
That wasn't the first time this sort of thing has happened, and (to
53
our community's great loss) it was far from the last.  Proprietary
54
manual publishers have enticed a great many authors to restrict their
55
manuals since then.  Many times I have heard a GNU user eagerly tell
56
me about a manual that he is writing, with which he expects to help
57
the GNU project--and then had my hopes dashed, as he proceeded to
58
explain that he had signed a contract with a publisher that would
59
restrict it so that we cannot use it.
60
61
 
62
63
Given that writing good English is a rare skill among programmers, we
64
can ill afford to lose manuals this way.
65
66
 
67
68
  Free documentation, like free software, is a matter of freedom,
69
not price.  The problem with these manuals was not that O'Reilly
70
Associates charged a price for printed copies--that in itself is fine.
71
(The Free Software Foundation sells printed copies of
72
free GNU manuals, too.)  But GNU manuals are available in source code
73
form, while these manuals are available only on paper.  GNU manuals
74
come with permission to copy and modify; the Perl manuals do not.
75
These restrictions are the problems.
76
77
 
78
79
The criterion for a free manual is pretty much the same as for free
80
software: it is a matter of giving all users certain freedoms.
81
Redistribution (including commercial redistribution) must be
82
permitted, so that the manual can accompany every copy of the program,
83
on-line or on paper.  Permission for modification is crucial too.
84
85
 
86
87
As a general rule, I don't believe that it is essential for people to
88
have permission to modify all sorts of articles and books.  The issues
89
for writings are not necessarily the same as those for software.  For
90
example, I don't think you or I are obliged to give permission to
91
modify articles like this one, which describe our actions and our
92
views.
93
94
 
95
96
But there is a particular reason why the freedom to modify is crucial
97
for documentation for free software.  When people exercise their right
98
to modify the software, and add or change its features, if they are
99
conscientious they will change the manual too--so they can provide
100
accurate and usable documentation with the modified program.  A manual
101
which forbids programmers to be conscientious and finish the job, or
102
more precisely requires them to write a new manual from scratch if
103
they change the program, does not fill our community's needs.
104
105
 
106
107
While a blanket prohibition on modification is unacceptable, some
108
kinds of limits on the method of modification pose no problem.  For
109
example, requirements to preserve the original author's copyright
110
notice, the distribution terms, or the list of authors, are ok.  It is
111
also no problem to require modified versions to include notice that
112
they were modified, even to have entire sections that may not be
113
deleted or changed, as long as these sections deal with nontechnical
114
topics.  (Some GNU manuals have them.)
115
116
 
117
118
These kinds of restrictions are not a problem because, as a practical
119
matter, they don't stop the conscientious programmer from adapting the
120
manual to fit the modified program.  In other words, they don't block
121
the free software community from making full use of the manual.
122
123
 
124
125
However, it must be possible to modify all the technical
126
content of the manual, and then distribute the result in all the usual
127
media, through all the usual channels; otherwise, the restrictions do
128
block the community, the manual is not free, and so we need another
129
manual.
130
131
 
132
133
Unfortunately, it is often hard to find someone to write another
134
manual when a proprietary manual exists.  The obstacle is that many
135
users think that a proprietary manual is good enough--so they don't
136
see the need to write a free manual.  They do not see that the free
137
operating system has a gap that needs filling.
138
139
 
140
141
Why do users think that proprietary manuals are good enough?  Some
142
have not considered the issue.  I hope this article will do something
143
to change that.
144
145
 
146
147
Other users consider proprietary manuals acceptable for the same
148
reason so many people consider proprietary software acceptable: they
149
judge in purely practical terms, not using freedom as a criterion.
150
These people are entitled to their opinions, but since those opinions
151
spring from values which do not include freedom, they are no guide for
152
those of us who do value freedom.
153
154
 
155
156
Please spread the word about this issue.  We continue to lose manuals
157
to proprietary publishing.  If we spread the word that proprietary
158
manuals are not sufficient, perhaps the next person who wants to help
159
GNU by writing documentation will realize, before it is too late, that
160
he must above all make it free.
161
162
 
163
164
We can also encourage commercial publishers to sell free, copylefted
165
manuals instead of proprietary ones.  One way you can help this is to
166
check the distribution terms of a manual before you buy it, and
167
prefer copylefted manuals to non-copylefted ones.
168
169
170
[Note: We now maintain a web page
171
that lists free books available from other publishers].
172
173
 
174
Copyright © 2004, 2005, 2006, 2007 Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA
175
 
176
Verbatim copying and distribution of this entire article are
177
permitted worldwide, without royalty, in any medium, provided this
178
notice is preserved.
179
 
180
Report any problems or suggestions to webmaster@fsf.org.
181
 
182

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.