[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/philosophy government-free-software.pt-br.h...
|
From: |
GNUN |
|
Subject: |
www/philosophy government-free-software.pt-br.h... |
|
Date: |
Mon, 22 Nov 2021 05:35:36 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 21/11/22 05:35:36
Modified files:
philosophy : government-free-software.pt-br.html
Added files:
philosophy/po : government-free-software.pt-br-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/government-free-software.pt-br.html?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/government-free-software.pt-br-diff.html?cvsroot=www&rev=1.1
Patches:
Index: government-free-software.pt-br.html
===================================================================
RCS file: /web/www/www/philosophy/government-free-software.pt-br.html,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- government-free-software.pt-br.html 5 Sep 2021 10:06:05 -0000 1.7
+++ government-free-software.pt-br.html 22 Nov 2021 10:35:33 -0000 1.8
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/philosophy/government-free-software.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/government-free-software.pt-br.po">
+ https://www.gnu.org/philosophy/po/government-free-software.pt-br.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/philosophy/government-free-software.html"
+ --><!--#set var="DIFF_FILE"
value="/philosophy/po/government-free-software.pt-br-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2021-09-23" --><!--#set
var="ENGLISH_PAGE" value="/philosophy/government-free-software.en.html" -->
<!--#include virtual="/server/header.pt-br.html" -->
<!-- Parent-Version: 1.96 -->
@@ -14,6 +19,7 @@
<!--#include virtual="/server/banner.pt-br.html" -->
<!--#include virtual="/philosophy/ph-breadcrumb.pt-br.html" -->
<!--GNUN: OUT-OF-DATE NOTICE-->
+<!--#include virtual="/server/outdated.pt-br.html" -->
<!--#include virtual="/server/top-addendum.pt-br.html" -->
<div class="article reduced-width">
<h2 style="margin-bottom: .2em">
@@ -308,7 +314,7 @@
<p class="unprintable"><!-- timestamp start -->
Ãltima atualização:
-$Date: 2021/09/05 10:06:05 $
+$Date: 2021/11/22 10:35:33 $
<!-- timestamp end -->
</p>
Index: po/government-free-software.pt-br-diff.html
===================================================================
RCS file: po/government-free-software.pt-br-diff.html
diff -N po/government-free-software.pt-br-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/government-free-software.pt-br-diff.html 22 Nov 2021 10:35:36 -0000
1.1
@@ -0,0 +1,318 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/philosophy/government-free-software.html-diff</title>
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+</style></head>
+<body><pre>
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.96 -->
+<!-- This page is derived from /server/standards/boilerplate.html -->
+<!--#set var="TAGS" value="essays upholding need" -->
+<!--#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="article 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="introduction">
+<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>
+</div>
+
+<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, “state entities” refers to all levels of
government, and
+means public agencies including schools, public-private partnerships,
+largely state-funded activities such as charter schools, and
“private”
+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
+“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.</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
+“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.</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">“jailbreaking”</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
+“principle” 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
+“neutral” about its sovereignty or its citizens' freedom.</p>
+</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 & GNU inquiries to <a
+href="mailto:gnu@gnu.org"><gnu@gnu.org></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"><webmasters@gnu.org></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">
+ <web-translators@gnu.org></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>
+
+<span class="inserted"><ins><em><!-- Regarding copyright, in general,
standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND 4.0. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. --></em></ins></span>
+
+<p>Copyright © <span class="removed"><del><strong>Copyright
©</strong></del></span> 2011-2014, 2016, <span
class="removed"><del><strong>2017</strong></del></span> <span
class="inserted"><ins><em>2017, 2021</em></ins></span> 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/11/22 10:35:36 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/philosophy government-free-software.pt-br.h...,
GNUN <=