[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy government-free-software.html
From: |
Dora Scilipoti |
Subject: |
www/philosophy government-free-software.html |
Date: |
Wed, 28 Dec 2011 10:30:59 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Dora Scilipoti <dora> 11/12/28 10:30:59
Modified files:
philosophy : government-free-software.html
Log message:
Capitalize title. <li> elements are paragraphs. Link to article on
SaaS. RMS approved.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/government-free-software.html?cvsroot=www&r1=1.15&r2=1.16
Patches:
Index: government-free-software.html
===================================================================
RCS file: /web/www/www/philosophy/government-free-software.html,v
retrieving revision 1.15
retrieving revision 1.16
diff -u -b -r1.15 -r1.16
--- government-free-software.html 27 Dec 2011 15:59:21 -0000 1.15
+++ government-free-software.html 28 Dec 2011 10:30:56 -0000 1.16
@@ -1,10 +1,10 @@
<!--#include virtual="/server/header.html" -->
<!-- Parent-Version: 1.63 -->
-<title>Measures governments can use to promote free software
+<title>Measures Governments Can Use to Promote Free Software
- GNU Project - Free Software Foundation</title>
<!--#include virtual="/server/banner.html" -->
<!--#include virtual="/philosophy/po/government-free-software.translist" -->
-<h2>Measures governments can use to promote free software</h2>
+<h2>Measures Governments Can Use to Promote Free Software</h2>
<p>by <a href="http://www.stallman.org/"><strong>Richard
Stallman</strong></a></p>
@@ -52,29 +52,29 @@
individuals and organizations use:</p>
<ul>
-<li>Laws and public sector practices must be changed so that they never
+<li><p>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="http://www.defectivebydesign.org/what_is_drm">Digital
-Restrictions Management</a>).</li>
+Restrictions Management</a>).</p></li>
-<li>Whenever a state entity distributes software to the public,
+<li><p>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
-100% free environment.</li>
+100% free environment.</p></li>
-<li>State entity web sites and servers must be designed to function fully
-with 100% free environments on the user's computer.</li>
+<li><p>State entity web sites and servers must be designed to function fully
+with 100% free environments on the user's computer.</p></li>
-<li>State entities must use only file formats and communication
+<li><p>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
“standards” 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.</li>
+Restrictions Management.</p></li>
</ul>
<p>Several policies affect the computational sovereignty of the state.
@@ -83,38 +83,39 @@
including smartphones.</p>
<ul>
-<li>State entities must migrate to free software, and must not install,
+<li><p>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.</li>
+agency's goal should be to reduce the number of exceptions to zero.</p></li>
-<li>When a state entity pays for development of a computing solution,
+<li><p>When a state entity pays for development of a computing solution,
the contract must require it be delivered as free software and be
capable of running on a 100% free environment. All contracts must
require this, so that if the developer does not comply with this
-requirement, the work cannot be paid for.</li>
+requirement, the work cannot be paid for.</p></li>
-<li>When a state entity buys or leases computers, it must choose among
+<li><p>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.</li>
+should be preferred to models available only to the state.</p></li>
-<li>The state should negotiate actively with manufacturers to bring
+<li><p>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.</li>
+require no proprietary software.</p></li>
-<li>The state should invite other states to negotiate collectively with
+<li><p>The state should invite other states to negotiate collectively with
manufacturers about suitable hardware products. Together they will
-have more clout.</li>
+have more clout.</p></li>
</ul>
<p>The computational sovereignty (and security) of the state includes
control over the computers that do the state's work. This requires
-avoiding Software as a Service, unless the service is run by a state
+avoiding <a href="/philosophy/who-does-that-server-really-serve.html">
+Software as a Service</a>, unless the service is run by a state
agency under the same branch of government, as well as other practices
that deminish the state control over its computing. Therefore,</p>
@@ -131,16 +132,16 @@
<p>One other policy affects free and nonfree software development:</p>
<ul>
-<li>The state should encourage developers to create or enhance free
+<li><p>The state should encourage developers to create or enhance free
software and who 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.</li>
+software.</p></li>
-<li>In particular, proprietary software developers should not be able to
+<li><p>In particular, proprietary software developers should not be able to
“donate” copies to schools and claim a tax write-off for the
nominal
value of the software. Proprietary software is not legitimate in a
-school.</li>
+school.</p></li>
</ul>
<p>With these measures, the state can recover control over its computing,
@@ -179,7 +180,7 @@
<p>
Updated:
<!-- timestamp start -->
-$Date: 2011/12/27 15:59:21 $
+$Date: 2011/12/28 10:30:56 $
<!-- timestamp end -->
</p>
</div>
- www/philosophy government-free-software.html, (continued)
- www/philosophy government-free-software.html, Jason Self, 2011/12/19
- www/philosophy government-free-software.html, Richard M. Stallman, 2011/12/20
- www/philosophy government-free-software.html, Richard M. Stallman, 2011/12/20
- www/philosophy government-free-software.html, James Turner, 2011/12/20
- www/philosophy government-free-software.html, Richard M. Stallman, 2011/12/22
- www/philosophy government-free-software.html, Dora Scilipoti, 2011/12/23
- www/philosophy government-free-software.html, Pavel Kharitonov, 2011/12/26
- www/philosophy government-free-software.html, Pavel Kharitonov, 2011/12/26
- www/philosophy government-free-software.html, Pavel Kharitonov, 2011/12/26
- www/philosophy government-free-software.html, Richard M. Stallman, 2011/12/27
- www/philosophy government-free-software.html,
Dora Scilipoti <=
- www/philosophy government-free-software.html, James Turner, 2011/12/31