browse.php

<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.96 -->
<!-- This page is derived from /server/standards/boilerplate.html -->
<!--#set var="TAGS" value="aboutfs" -->
<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
<title>Measures Governments Can Use to Promote Free Software
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/philosophy/po/government-free-software.translist" -->
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/philosophy/ph-breadcrumb.html" -->
<!--GNUN: OUT-OF-DATE NOTICE-->
<!--#include virtual="/server/top-addendum.html" -->
<div class="reduced-width">
<h2 style="margin-bottom: .2em">
Measures Governments Can Use to Promote Free Software</h2>
<h3 style="margin: 0 0 1.2em">
And why it is their duty to do so</h3>

<address class="byline">by <a href="https://www.stallman.org/">Richard
Stallman</a></address>

<div class="article">
<p>This article suggests policies for a strong and firm effort to promote
free software within the state, and to lead the rest of the country
towards software freedom.</p>

<p>The mission of the state is to organize society for the freedom and
well-being of the people.  One aspect of this mission, in the
computing field, is to encourage users to adopt free software:
<a href="/philosophy/free-sw.html">software that respects the users'
freedom</a>.  A proprietary (nonfree) program tramples the freedom of
those that use it; it is a social problem that the state should work
to eradicate.</p>

<p>The state needs to insist on free software in its own computing for
the sake of its computational sovereignty (the state's control over
its own computing).  All users deserve control over their computing,
but the state has a responsibility to the people to maintain control
over the computing it does on their behalf.  Most government
activities now depend on computing, and its control over those
activities depends on its control over that computing.  Losing this
control in an agency whose mission is critical undermines national
security.</p>

<p>Moving state agencies to free software can also provide secondary
benefits, such as saving money and encouraging local software support
businesses.</p>

<p>In this text, &ldquo;state entities&rdquo; refers to all levels of government, and
means public agencies including schools, public-private partnerships,
largely state-funded activities such as charter schools, and &ldquo;private&rdquo;
corporations controlled by the state or established with special
privileges or functions by the state.</p>

<h3>Education</h3>
<p>The most important policy concerns education, since that shapes
the future of the country:</p>

<ul>
<li><b>Teach only free software</b><br />
Educational activities, or at least those of state entities, must
teach only free software (thus, they should never lead students to use
a nonfree program), and should teach the civic reasons for insisting
on free software.  To teach a nonfree program is to teach dependence,
which is contrary to the mission of the school.</li>
</ul>

<h3>The State and the Public</h3>
<p>Also crucial are state policies that influence what software
individuals and organizations use:</p>

<ul>
<li><p><b>Never require nonfree programs</b><br />
Laws and public sector practices must be changed so that they never
require or pressure individuals or organizations to use a nonfree
program.  They should also discourage communication and publication
practices that imply such consequences (including
<a href="https://www.defectivebydesign.org/what_is_drm_digital_restrictions_management">Digital
Restrictions Management</a>).</p></li>

<li><p><b>Distribute only free software</b><br />
Whenever a state entity distributes software to the public,
including programs included in or specified by its web pages, it must
be distributed as free software, and must be capable of running on a
platform containing exclusively free software.</p></li>

<li><p><b>State web sites</b><br />
State entity web sites and network services must be designed so
that users can use them, without disadvantage, by means of free
software exclusively.</p></li>

<li><p><b>Free formats and protocols</b><br />
State entities must use only file formats and communication
protocols that are well supported by free software, preferably with
published specifications.  (We do not state this in terms of
&ldquo;standards&rdquo; because it should apply to nonstandardized interfaces as
well as standardized ones.)  For example, they must not distribute
audio or video recordings in formats that require Flash or nonfree
codecs, and public libraries must not distribute works with Digital
Restrictions Management.</p>

<p>To support the policy of distributing publications and works in
freedom-respecting formats, the state must insist that all reports
developed for it be delivered in freedom-respecting formats.</p></li>

<li><p><b>Untie computers from licenses</b><br />
Sale of computers must not require purchase of a proprietary
software license.  The seller should be required by law to offer the
purchaser the option of buying the computer without the proprietary
software and without paying the license fee.</p>
<p>The imposed payment is a secondary wrong, and should not distract
us from the essential injustice of proprietary software, the loss of
freedom which results from using it.  Nonetheless, the abuse of
forcing users to pay for it gives certain proprietary software
developers an additional unfair advantage, detrimental to users'
freedom.  It is proper for the state to prevent this abuse.</p>
</li>
</ul>

<h3>Computational Sovereignty</h3>
<p>Several policies affect the computational sovereignty of the state.
State entities must maintain control over their computing, not cede
control to private hands.  These points apply to all computers,
including smartphones.</p>

<ul>
<li><p><b>Migrate to free software</b><br />
State entities must migrate to free software, and must not install,
or continue using, any nonfree software except under a temporary
exception.  Only one agency should have the authority to grant these
temporary exceptions, and only when shown compelling reasons.  This
agency's goal should be to reduce the number of exceptions to zero.</p></li>

<li><p><b>Develop free IT solutions</b><br />
When a state entity pays for development of a computing solution, the
contract must require it be delivered as free software, and that it be
designed such that one can both run it and develop it on a 100%-free
environment.  All contracts must require this, so that if the
developer does not comply with these requirements, the work cannot be
paid for.</p></li>

<li><p><b>Choose computers for free software</b><br />
When a state entity buys or leases computers, it must choose among
the models that come closest, in their class, to being capable of
running without any proprietary software.  The state should maintain,
for each class of computers, a list of the models authorized based on
this criterion.  Models available to both the public and the state
should be preferred to models available only to the state.</p></li>

<li><p><b>Negotiate with manufacturers</b><br />
The state should negotiate actively with manufacturers to bring
about the availability in the market (to the state and the public) of
suitable hardware products, in all pertinent product areas, that
require no proprietary software.</p></li>

<li><p><b>Unite with other states</b><br />
The state should invite other states to negotiate collectively with
manufacturers about suitable hardware products.  Together they will
have more clout.</p></li>
</ul>

<h3>Computational Sovereignty II</h3>
<p>The computational sovereignty (and security) of the state includes
control over the computers that do the state's work.  This requires
avoiding <a href="/philosophy/who-does-that-server-really-serve.html">
Service as a Software Substitute</a>, unless the service is run by a state
agency under the same branch of government, as well as other practices
that diminish the state control over its computing.  Therefore,</p>

<ul>
<li><b>State must control its computers</b><br />
Every computer that the state uses must belong to or be leased by
the same branch of government that uses it, and that branch must not
cede to outsiders the right to decide who has physical access to the
computer, who can do maintenance (hardware or software) on it, or
what software should be installed in it.  If the computer is not
portable, then while in use it must be in a physical space of which
the state is the occupant (either as owner or as tenant).</li>
</ul>

<h3>Influence Development</h3>
<p>State policy affects free and nonfree software development:</p>

<ul>
<li><p><b>Encourage free</b><br />
The state should encourage developers to create or enhance free
software and make it available to the public, e.g. by tax breaks
and other financial incentive.  Contrariwise, no such incentives
should be granted for development, distribution or use of nonfree
software.</p></li>

<li><p><b>Don't encourage nonfree</b><br />
In particular, proprietary software developers should not be able to
&ldquo;donate&rdquo; copies to schools and claim a tax write-off for the nominal
value of the software.  Proprietary software is not legitimate in a
school.</p></li>
</ul>

<h3>E-waste</h3>
<p>Freedom should not imply e-waste:</p>

<ul>
<li><p><b>Replaceable software</b><br />
Many modern computers are designed to make it impossible to
replace their preloaded software with free software.  Thus, the only
way to free them is to junk them.  This practice is harmful to
society.</p>

<p>Therefore, it should be illegal, or at least substantially
discouraged through heavy taxation, to sell, import or distribute in
quantity a new computer (that is, not second-hand) or computer-based
product for which secrecy about hardware interfaces or intentional
restrictions prevent users from developing, installing and using
replacements for any and all of the installed software that the
manufacturer could upgrade.  This would apply, in particular, to any
device on which <a href="/proprietary/proprietary-jails.html">&ldquo;jailbreaking&rdquo;</a> is needed to install a
different operating system, or in which the interfaces for some
peripherals are secret.
</p></li>
</ul>

<h3>Technological neutrality</h3>

<p>With the measures in this article, the state can recover control
over its computing, and lead the country's citizens, businesses and
organizations towards control over their computing.  However, some
object on the grounds that this would violate the
&ldquo;principle&rdquo; of technological neutrality.</p>

<p>The idea of technological neutrality is that the state should not
impose arbitrary preferences on technical choices.  Whether that is a
valid principle is disputable, but it is limited in any case to issues
that are merely technical.  The measures advocated here address issues
of ethical, social and political importance, so they are
<a href="/philosophy/technological-neutrality.html">outside the scope
of <em>technological</em> neutrality</a>.  Only those who wish to
subjugate a country would suggest that its government be
&ldquo;neutral&rdquo; about its sovereignty or its citizens' freedom.</p>
</div>
</div>

</div><!-- for id="content", starts in the include above -->
<!--#include virtual="/server/footer.html" -->
<div id="footer" role="contentinfo">
<div class="unprintable">

<p>Please send general FSF &amp; GNU inquiries to <a
href="mailto:gnu@gnu.org">&lt;gnu@gnu.org&gt;</a>.  There are also <a
href="/contact/">other ways to contact</a> the FSF.  Broken links and other
corrections or suggestions can be sent to <a
href="mailto:webmasters@gnu.org">&lt;webmasters@gnu.org&gt;</a>.</p>

<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
        replace it with the translation of these two:

        We work hard and do our best to provide accurate, good quality
        translations.  However, we are not exempt from imperfection.
        Please send your comments and general suggestions in this regard
        to <a href="mailto:web-translators@gnu.org">
        &lt;web-translators@gnu.org&gt;</a>.</p>

        <p>For information on coordinating and contributing translations of
        our web pages, see <a
        href="/server/standards/README.translations.html">Translations
        README</a>. -->
Please see the <a
href="/server/standards/README.translations.html">Translations README</a> for
information on coordinating and contributing translations of this article.</p>
</div>

<p>Copyright &copy; Copyright &copy; 2011-2014, 2016, 2017 Free Software
Foundation, Inc.</p>

<p>This page is licensed under a <a rel="license"
href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
Commons Attribution-NoDerivatives 4.0 International License</a>.</p>

<!--#include virtual="/server/bottom-notes.html" -->

<p class="unprintable">Updated:
<!-- timestamp start -->
$Date: 2021/07/16 16:31:58 $
<!-- timestamp end -->
</p>
</div>
</div><!-- for class="inner", starts in the banner include -->
</body>
</html>
1	jturner	1.8	<!--#include virtual="/server/header.html" -->
2	th_g	1.54	<!-- Parent-Version: 1.96 -->
3			<!-- This page is derived from /server/standards/boilerplate.html -->
4			<!--#set var="TAGS" value="aboutfs" -->
5			<!--#set var="DISABLE_TOP_ADDENDUM" value="yes" -->
6	dora	1.16	<title>Measures Governments Can Use to Promote Free Software
7	ineiev	1.12	- GNU Project - Free Software Foundation</title>
8	ineiev	1.27	<!--#include virtual="/philosophy/po/government-free-software.translist" -->
9	ifarouk	1.1	<!--#include virtual="/server/banner.html" -->
10	th_g	1.54	<!--#include virtual="/philosophy/ph-breadcrumb.html" -->
11			<!--GNUN: OUT-OF-DATE NOTICE-->
12			<!--#include virtual="/server/top-addendum.html" -->
13			<div class="reduced-width">
14			<h2 style="margin-bottom: .2em">
15			Measures Governments Can Use to Promote Free Software</h2>
16			<h3 style="margin: 0 0 1.2em">
17			And why it is their duty to do so</h3>
18	ifarouk	1.1
19	th_g	1.54	<address class="byline">by <a href="https://www.stallman.org/">Richard
20			Stallman</a></address>
21	ifarouk	1.1
22	th_g	1.55	<div class="article">
23	ifarouk	1.1	<p>This article suggests policies for a strong and firm effort to promote
24			free software within the state, and to lead the rest of the country
25	jxself	1.3	towards software freedom.</p>
26	ifarouk	1.1
27			<p>The mission of the state is to organize society for the freedom and
28	jxself	1.3	well-being of the people. One aspect of this mission, in the
29	rms	1.30	computing field, is to encourage users to adopt free software:
30			<a href="/philosophy/free-sw.html">software that respects the users'
31	th_g	1.54	freedom</a>. A proprietary (nonfree) program tramples the freedom of
32	rms	1.30	those that use it; it is a social problem that the state should work
33			to eradicate.</p>
34	ifarouk	1.1
35			<p>The state needs to insist on free software in its own computing for
36			the sake of its computational sovereignty (the state's control over
37	jxself	1.3	its own computing). All users deserve control over their computing,
38	ifarouk	1.1	but the state has a responsibility to the people to maintain control
39	jxself	1.3	over the computing it does on their behalf. Most government
40	ifarouk	1.1	activities now depend on computing, and its control over those
41	jxself	1.3	activities depends on its control over that computing. Losing this
42	ifarouk	1.1	control in an agency whose mission is critical undermines national
43	jxself	1.3	security.</p>
44	ifarouk	1.1
45			<p>Moving state agencies to free software can also provide secondary
46			benefits, such as saving money and encouraging local software support
47	jxself	1.3	businesses.</p>
48	ifarouk	1.1
49	ineiev	1.12	<p>In this text, “state entities” refers to all levels of government, and
50	jxself	1.3	means public agencies including schools, public-private partnerships,
51	ineiev	1.12	largely state-funded activities such as charter schools, and “private”
52	jxself	1.3	corporations controlled by the state or established with special
53			privileges or functions by the state.</p>
54	ifarouk	1.1
55	rms	1.32	<h3>Education</h3>
56	ifarouk	1.1	<p>The most important policy concerns education, since that shapes
57	jxself	1.3	the future of the country:</p>
58	ifarouk	1.1
59			<ul>
60	rms	1.32	<li><b>Teach only free software</b><br />
61			Educational activities, or at least those of state entities, must
62	ifarouk	1.1	teach only free software (thus, they should never lead students to use
63			a nonfree program), and should teach the civic reasons for insisting
64	jxself	1.3	on free software. To teach a nonfree program is to teach dependence,
65			which is contrary to the mission of the school.</li>
66	ifarouk	1.1	</ul>
67
68	rms	1.32	<h3>The State and the Public</h3>
69	ifarouk	1.1	<p>Also crucial are state policies that influence what software
70	jxself	1.3	individuals and organizations use:</p>
71	ifarouk	1.1
72			<ul>
73	rms	1.32	<li><p><b>Never require nonfree programs</b><br />
74			Laws and public sector practices must be changed so that they never
75	ifarouk	1.1	require or pressure individuals or organizations to use a nonfree
76	jxself	1.3	program. They should also discourage communication and publication
77	rms	1.15	practices that imply such consequences (including
78	arh	1.52	<a href="https://www.defectivebydesign.org/what_is_drm_digital_restrictions_management">Digital
79	dora	1.16	Restrictions Management</a>).</p></li>
80	ifarouk	1.1
81	rms	1.32	<li><p><b>Distribute only free software</b><br />
82			Whenever a state entity distributes software to the public,
83	ifarouk	1.1	including programs included in or specified by its web pages, it must
84			be distributed as free software, and must be capable of running on a
85	rms	1.21	platform containing exclusively free software.</p></li>
86	ifarouk	1.1
87	rms	1.32	<li><p><b>State web sites</b><br />
88			State entity web sites and network services must be designed so
89	rms	1.21	that users can use them, without disadvantage, by means of free
90			software exclusively.</p></li>
91	ifarouk	1.1
92	rms	1.32	<li><p><b>Free formats and protocols</b><br />
93			State entities must use only file formats and communication
94	ifarouk	1.1	protocols that are well supported by free software, preferably with
95	jxself	1.3	published specifications. (We do not state this in terms of
96	ineiev	1.12	“standards” because it should apply to nonstandardized interfaces as
97	jxself	1.3	well as standardized ones.) For example, they must not distribute
98	ifarouk	1.1	audio or video recordings in formats that require Flash or nonfree
99			codecs, and public libraries must not distribute works with Digital
100	rms	1.44	Restrictions Management.</p>
101
102			<p>To support the policy of distributing publications and works in
103			freedom-respecting formats, the state must insist that all reports
104			developed for it be delivered in freedom-respecting formats.</p></li>
105	rms	1.31
106	rms	1.32	<li><p><b>Untie computers from licenses</b><br />
107			Sale of computers must not require purchase of a proprietary
108	rms	1.31	software license. The seller should be required by law to offer the
109			purchaser the option of buying the computer without the proprietary
110			software and without paying the license fee.</p>
111			<p>The imposed payment is a secondary wrong, and should not distract
112			us from the essential injustice of proprietary software, the loss of
113			freedom which results from using it. Nonetheless, the abuse of
114			forcing users to pay for it gives certain proprietary software
115			developers an additional unfair advantage, detrimental to users'
116			freedom. It is proper for the state to prevent this abuse.</p>
117			</li>
118	ifarouk	1.1	</ul>
119
120	rms	1.32	<h3>Computational Sovereignty</h3>
121	ifarouk	1.1	<p>Several policies affect the computational sovereignty of the state.
122			State entities must maintain control over their computing, not cede
123	jxself	1.3	control to private hands. These points apply to all computers,
124			including smartphones.</p>
125	ifarouk	1.1
126			<ul>
127	rms	1.32	<li><p><b>Migrate to free software</b><br />
128			State entities must migrate to free software, and must not install,
129	ifarouk	1.1	or continue using, any nonfree software except under a temporary
130	jxself	1.3	exception. Only one agency should have the authority to grant these
131			temporary exceptions, and only when shown compelling reasons. This
132	dora	1.16	agency's goal should be to reduce the number of exceptions to zero.</p></li>
133	ifarouk	1.1
134	rms	1.32	<li><p><b>Develop free IT solutions</b><br />
135	rms	1.33	When a state entity pays for development of a computing solution, the
136			contract must require it be delivered as free software, and that it be
137			designed such that one can both run it and develop it on a 100%-free
138			environment. All contracts must require this, so that if the
139	rms	1.34	developer does not comply with these requirements, the work cannot be
140	rms	1.33	paid for.</p></li>
141	ifarouk	1.1
142	rms	1.32	<li><p><b>Choose computers for free software</b><br />
143			When a state entity buys or leases computers, it must choose among
144	ifarouk	1.1	the models that come closest, in their class, to being capable of
145	jxself	1.3	running without any proprietary software. The state should maintain,
146	ifarouk	1.1	for each class of computers, a list of the models authorized based on
147	jxself	1.3	this criterion. Models available to both the public and the state
148	dora	1.16	should be preferred to models available only to the state.</p></li>
149	ifarouk	1.1
150	rms	1.32	<li><p><b>Negotiate with manufacturers</b><br />
151			The state should negotiate actively with manufacturers to bring
152	ifarouk	1.1	about the availability in the market (to the state and the public) of
153			suitable hardware products, in all pertinent product areas, that
154	dora	1.16	require no proprietary software.</p></li>
155	ifarouk	1.1
156	rms	1.32	<li><p><b>Unite with other states</b><br />
157			The state should invite other states to negotiate collectively with
158	jxself	1.3	manufacturers about suitable hardware products. Together they will
159	dora	1.16	have more clout.</p></li>
160	ifarouk	1.1	</ul>
161
162	rms	1.32	<h3>Computational Sovereignty II</h3>
163	ifarouk	1.1	<p>The computational sovereignty (and security) of the state includes
164	jxself	1.3	control over the computers that do the state's work. This requires
165	dora	1.16	avoiding <a href="/philosophy/who-does-that-server-really-serve.html">
166	jrasata	1.41	Service as a Software Substitute</a>, unless the service is run by a state
167	ifarouk	1.1	agency under the same branch of government, as well as other practices
168	jturner	1.17	that diminish the state control over its computing. Therefore,</p>
169	ifarouk	1.1
170			<ul>
171	rms	1.32	<li><b>State must control its computers</b><br />
172			Every computer that the state uses must belong to or be leased by
173	rms	1.10	the same branch of government that uses it, and that branch must not
174			cede to outsiders the right to decide who has physical access to the
175			computer, who can do maintenance (hardware or software) on it, or
176			what software should be installed in it. If the computer is not
177			portable, then while in use it must be in a physical space of which
178			the state is the occupant (either as owner or as tenant).</li>
179	ifarouk	1.1	</ul>
180
181	rms	1.32	<h3>Influence Development</h3>
182			<p>State policy affects free and nonfree software development:</p>
183	ifarouk	1.1
184			<ul>
185	rms	1.32	<li><p><b>Encourage free</b><br />
186			The state should encourage developers to create or enhance free
187	rms	1.37	software and make it available to the public, e.g. by tax breaks
188	jxself	1.3	and other financial incentive. Contrariwise, no such incentives
189	ineiev	1.13	should be granted for development, distribution or use of nonfree
190	dora	1.16	software.</p></li>
191	ifarouk	1.1
192	rms	1.32	<li><p><b>Don't encourage nonfree</b><br />
193			In particular, proprietary software developers should not be able to
194	ineiev	1.12	“donate” copies to schools and claim a tax write-off for the nominal
195	jxself	1.3	value of the software. Proprietary software is not legitimate in a
196	dora	1.16	school.</p></li>
197	jxself	1.4	</ul>
198	ifarouk	1.1
199	rms	1.32	<h3>E-waste</h3>
200	rms	1.22	<p>Freedom should not imply e-waste:</p>
201
202			<ul>
203	rms	1.32	<li><p><b>Replaceable software</b><br />
204			Many modern computers are designed to make it impossible to
205	rms	1.22	replace their preloaded software with free software. Thus, the only
206			way to free them is to junk them. This practice is harmful to
207			society.</p>
208
209			<p>Therefore, it should be illegal, or at least substantially
210			discouraged through heavy taxation, to sell, import or distribute in
211			quantity a new computer (that is, not second-hand) or computer-based
212			product for which secrecy about hardware interfaces or intentional
213	rsd	1.28	restrictions prevent users from developing, installing and using
214	rms	1.22	replacements for any and all of the installed software that the
215			manufacturer could upgrade. This would apply, in particular, to any
216	rms	1.44	device on which <a href="/proprietary/proprietary-jails.html">“jailbreaking”</a> is needed to install a
217	rms	1.22	different operating system, or in which the interfaces for some
218			peripherals are secret.
219			</p></li>
220	ineiev	1.23	</ul>
221	rms	1.22
222	rms	1.38	<h3>Technological neutrality</h3>
223
224			<p>With the measures in this article, the state can recover control
225			over its computing, and lead the country's citizens, businesses and
226			organizations towards control over their computing. However, some
227			object on the grounds that this would violate the
228			“principle” of technological neutrality.</p>
229
230			<p>The idea of technological neutrality is that the state should not
231			impose arbitrary preferences on technical choices. Whether that is a
232			valid principle is disputable, but it is limited in any case to issues
233			that are merely technical. The measures advocated here address issues
234			of ethical, social and political importance, so they are
235			<a href="/philosophy/technological-neutrality.html">outside the scope
236			of <em>technological</em> neutrality</a>. Only those who wish to
237	joeko	1.40	subjugate a country would suggest that its government be
238	th_g	1.39	“neutral” about its sovereignty or its citizens' freedom.</p>
239	th_g	1.54	</div>
240	th_g	1.55	</div>
241	ifarouk	1.1
242			</div><!-- for id="content", starts in the include above -->
243			<!--#include virtual="/server/footer.html" -->
244	th_g	1.54	<div id="footer" role="contentinfo">
245	ineiev	1.35	<div class="unprintable">
246	ifarouk	1.1
247	joeko	1.24	<p>Please send general FSF & GNU inquiries to <a
248			href="mailto:gnu@gnu.org"><gnu@gnu.org></a>. There are also <a
249			href="/contact/">other ways to contact</a> the FSF. Broken links and other
250			corrections or suggestions can be sent to <a
251			href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p>
252
253			<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
254			replace it with the translation of these two:
255
256			We work hard and do our best to provide accurate, good quality
257			translations. However, we are not exempt from imperfection.
258			Please send your comments and general suggestions in this regard
259			to <a href="mailto:web-translators@gnu.org">
260			<web-translators@gnu.org></a>.</p>
261
262	th_g	1.54	<p>For information on coordinating and contributing translations of
263	joeko	1.24	our web pages, see <a
264			href="/server/standards/README.translations.html">Translations
265			README</a>. -->
266			Please see the <a
267			href="/server/standards/README.translations.html">Translations README</a> for
268	th_g	1.54	information on coordinating and contributing translations of this article.</p>
269	ineiev	1.35	</div>
270	ifarouk	1.1
271	th_g	1.54	<p>Copyright © Copyright © 2011-2014, 2016, 2017 Free Software
272			Foundation, Inc.</p>
273	ifarouk	1.1
274			<p>This page is licensed under a <a rel="license"
275	gnun	1.42	href="http://creativecommons.org/licenses/by-nd/4.0/">Creative
276			Commons Attribution-NoDerivatives 4.0 International License</a>.</p>
277	ifarouk	1.1
278	ineiev	1.25	<!--#include virtual="/server/bottom-notes.html" -->
279
280	ineiev	1.36	<p class="unprintable">Updated:
281	ifarouk	1.1	<!-- timestamp start -->
282	th_g	1.55	$Date: 2021/07/16 16:31:58 $
283	ifarouk	1.1	<!-- timestamp end -->
284			</p>
285			</div>
286	ineiev	1.51	</div><!-- for class="inner", starts in the banner include -->
287	ifarouk	1.1	</body>
288			</html>
savannah-hackers-public@gnu.org	ViewVC Help
Powered by ViewVC 1.1.26