www-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

www/philosophy po/government-free-software.zh-t...


From: GNUN
Subject: www/philosophy po/government-free-software.zh-t...
Date: Tue, 15 Jan 2019 02:28:56 -0500 (EST)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     19/01/15 02:28:56

Modified files:
        philosophy/po  : government-free-software.zh-tw.po 
Added files:
        philosophy     : government-free-software.zh-tw.html 
        philosophy/po  : government-free-software.zh-tw-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/government-free-software.zh-tw.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/government-free-software.zh-tw.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/po/government-free-software.zh-tw-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/government-free-software.zh-tw.po
===================================================================
RCS file: /web/www/www/philosophy/po/government-free-software.zh-tw.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2

Index: government-free-software.zh-tw.html
===================================================================
RCS file: government-free-software.zh-tw.html
diff -N government-free-software.zh-tw.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ government-free-software.zh-tw.html 15 Jan 2019 07:28:55 -0000      1.1
@@ -0,0 +1,187 @@
+<!--#set var="ENGLISH_PAGE" 
value="/philosophy/government-free-software.en.html" -->
+
+<!--#include virtual="/server/header.zh-tw.html" -->
+<!-- Parent-Version: 1.86 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>政府推動自由軟體的可行辦法 - GNU 專案 - 
自由軟體基金會</title>
+
+<!--#include virtual="/philosophy/po/government-free-software.translist" -->
+<!--#include virtual="/server/banner.zh-tw.html" -->
+<h2>政府推動自由軟體的可行辦法</h2>
+<h3>以及為什麼這是政府的責任</h3>
+
+<p>作者為 <a href="http://www.stallman.org/";><strong>Richard 
Stallman</strong></a></p>
+
+<p>本文倡議各州政府 <a href="#trans1">[按1]</a> 
應以強而有力的政策推動自由軟體,並引領國內å…
¶é¤˜è¡Œæ”¿å€æœè»Ÿé«”自由的目標前進。</p>
+
+<p>州政府的使命是讓社會得以實現人民的自由與福祉。落在電è
…¦é ˜åŸŸï¼Œé€™å€‹ä½¿å‘½å°±æ˜¯é¼“勵使用者採用自由軟體:<a
+href="/philosophy/free-sw.html">即尊重使用者
自由的軟體</a>。專有(非自由)軟體踐踏了使用者
的自由;這是政府應當努力根絕的社會問題。</p>
+
+<p>為了保有國家的運算主權(國家對於其電è…
¦é‹ç®—作業的自主控制權),州政府必須堅
持使用自由軟體作電腦運算。所有使用者都應得自主掌控電è…
¦é‹ç®—的權利,而政府有責任起身為人民守護這份運算自主權。現在大多數的政府活動都開始依賴電è
…¦ï¼Œè€Œæ”¿åºœå°é€™äº›æ´»å‹•çš„控制權則取決於對於電è…
¦é‹ç®—的控制權。在對政府運作而言相當重要的機關中,若失去這樣的控制權將危及國家安å
…¨ã€‚</p>
+
+<p>讓政府機關導入自由軟體還有å…
¶ä»–好處,例如省錢還有助於地方軟體支援產業的發展。</p>
+
+<p>在下文中,「政府機關」泛指各級政府,亦代表如學æ 
¡å–®ä½ã€å…¬ç§åˆç‡Ÿæ©Ÿé—œï¼Œç”±æ”¿åºœä¸»è¦è³‡åŠ©çš„事業如公立學æ 
¡ï¼Œä»¥åŠç”±æ”¿åºœæŽŒæŽ§æˆ–以特殊權利或功能設立的「私營」å…
¬å¸ç­‰ã€‚</p>
+
+<h3>教育</h3>
+<p>最重要的政策就是教育政策,因
為教育政策形塑了國家的未來:</p>
+
+<ul>
+<li><b>只教育自由軟體</b><br />
+教育事業,或至少是那些由政府機關主導的教育事業,必é 
ˆåªæ•™è‚²è‡ªç”±è»Ÿé«”(所以,他們絕對不應引導學生使用非自由軟體),而且應該教育學生å
 …持採用自由軟體的å…
¬æ°‘原則。教育非自由軟體就是教育學生依賴特定廠
商,而這違背了學校的教育使命。</li>
+</ul>
+
+<h3>政府與民眾</h3>
+<p>那些會影響個人與組織單位如何使用軟體的政策也很重要:</p>
+
+<ul>
+<li><p><b>不應要求非自由軟體</b><br />
+法律與公部門行政時的施行辦法都必須修改,兩者永遠
都不可要求或迫使個人或組織單位使用某個非自由軟體。他們也應該勸阻å¿
…然導致這類結果的傳播與出版做法(其中包含<a
+href="http://www.defectivebydesign.org/what_is_drm";>數位限制管理,即 
DRM </a>技術)。</p></li>
+
+<li><p><b>僅只散布自由軟體</b><br />
+每當政府機關向民眾散布軟體時,包括機關網é 
ä¸­æ‰€å«æœ‰çš„或指定的程式,都必é 
ˆä»¥è‡ªç”±è»Ÿé«”授權散布,並且該軟體必é 
ˆå¯ä»¥åœ¨åªæ”¶éŒ„自由軟體的作業平臺上執行。</p></li>
+
+<li><p><b>政府網站</b><br />
+政府機關必須讓其網站與網路服務,在僅
只使用自由軟體的情況下,也可以完å…
¨æ­£å¸¸åŸ·è¡Œèˆ‡ä½¿ç”¨ã€‚</p></li>
+
+<li><p><b>自由格式與協定</b><br />
+政府機關必須只使用自由軟體可良好支援的檔案æ 
¼å¼æˆ–通訊協定,其中最好採取公開的規æ 
¼ã€‚(我們沒有使用「標準」一詞來描述,是因
為這應該要同時適用於未標準化介面與已標準化介面。)舉例來說,機關不能以需要有
+Flash 或非自由編解碼器才能播放的æ 
¼å¼æ•£å¸ƒéŸ³è¨Šæˆ–視訊,而公å…
±åœ–書館也不可散布以數位限制管理技術發行的作品。</p>
+
+<p>為了支持採用尊重自由的æ 
¼å¼æ•£å¸ƒå‡ºç‰ˆå“èˆ‡ä½œå“çš„政策,州政府必須堅
持所有與此政策相關的各類報告都以尊重自由的æ 
¼å¼æä¾›ã€‚</p></li>
+
+<li><p><b>解除電腦的授權綁縛</b><br />
+電è…
¦ä¹‹éŠ·å”®ï¼Œä¸å¾—要求一併購買專有軟體授權。法律應要求電è…
¦è³£æ–¹å‘買方提供無專有軟體且不必繳交授權費的選項。</p>
+<p>強加
買方購買金額是次要關心的問題,而這不應分散我們對專有軟體å
…
¶ä¸æ­£ç¾©æœ¬è³ªçš„注意,焦點在於使用專有軟體會導致失去自由。不過,濫用強迫使用è€
…付款的銷售手法,會為某些專有軟體開發商帶來額外的不å…
¬å¹³å„ªå‹¢ï¼Œé€™å°ä½¿ç”¨è€…
的自由極為不利。合理之道是政府應當防止這類濫用。</p>
+</li>
+</ul>
+
+<h3>電腦運算主權</h3>
+<p>許多政策都會影響國家的電腦運算主權。政府機關必é 
ˆä¿æŒå°å…¶é›»è…
¦é‹ç®—的控制權,而不是將控制權讓與私人之手。這點適用所有種類的電è
…¦ï¼ŒåŒ…含智慧型手機亦是如此。</p>
+
+<ul>
+<li><p><b>遷移至自由軟體</b><br />
+政府機關必é 
ˆé·ç§»è‡³è‡ªç”±è»Ÿé«”環境,而且不得安裝或繼續使用任何非自由軟體,除非是特殊的暫時例外æƒ
…
況。政府應設立單一機構有權授予這些暫時例外,而且只在有理由å
……足時才發予許可。這個機構的最終目標是將例外情
況減少至完全沒有。</p></li>
+
+<li><p><b>開發自由的 IT 解決方案</b><br />
+當政府機關為某個電腦運算解決方案支付開發費用時,必é 
ˆåœ¨å¥‘約中要求解決方案以自由軟體授權交付,而且其設計必
é 
ˆè¦è®“人可以在百分之百自由的環境中執行與開發。所有的契約都å¿
…須列入這項條件要求,所以如果開發者
無法遵守這些要求,就無法拿到成品費用。</p></li>
+
+<li><p><b>選擇適合自由軟體的電腦</b><br />
+當政府機關要購買或租賃電腦時,必須從同類型等級的電è…
¦ä¸­ï¼Œé¸æ“‡å‡ºæ²’有任何專有軟體的狀況下,最能夠
正常運行的電腦。政府機關應當針對各種類型的電è…
¦ï¼Œç¶­è­·ä¸€ä»½ä»¥æ­¤æ¨™æº–條件為基礎的機型列表。而民眾與政府都可獲取使用的機型,應該優å
…ˆåˆ—於僅政府可獲取使用的機型之前。</p></li>
+
+<li><p><b>與廠商談判</b><br />
+州政府應與製造商積極協商談判,以在所有相關產品é 
˜åŸŸçš„市å 
´ä¸Šï¼Œï¼ˆå‘政府與民眾)供應不需要專有軟體的合適硬體產品。</p></li>
+
+<li><p><b>與其他州政府合作</b><br />
+州政府應該邀請其他州政府一同與製造
商就合適的硬體進行協商談判。同心協力所發揮的影響力道就會更大。</p></li>
+</ul>
+
+<h3>電腦運算主權二</h3>
+<p>國家的電腦運算主權(與運算安全),包
含了要對執行政府作業內容的電è…
¦æœ‰å®Œæ•´æŽ§åˆ¶æ¬Šã€‚若要達成這項目標,就需要避免採用<a
+href="/philosophy/who-does-that-server-really-serve.html">服務替代軟體 
(SaSS)
+</a>架構(除非該服務是由同一政府機關下轄的單位營運),以及避å
…æŽ¡å–其他會促使政府降低電è…
¦é‹ç®—控制權的措施。所以,</p>
+
+<ul>
+<li><b>政府必須掌控其電腦</b><br />
+政府使用的每臺電腦,都必é 
ˆç”±ä½¿ç”¨å®ƒå€‘的政府機關擁有或是由å…
¶ç§Ÿè³ƒï¼›è€Œä¸”該分支機構不得有權決定誰可以將這些電è…
¦çš„實體存取權利、(軟體或硬體)維護權利、軟體安裝權利等,讓與外部人員。如果不是可攜式電è
…¦ï¼Œå‰‡é›»è…¦åœ¨ä½¿ç”¨æœŸé–“必須存放在政府機關佔用者
(無論身份為擁有者或租賃者)的實體空間中。</li>
+</ul>
+
+<h3>影響開發</h3>
+<p>以政策影響自由軟體與非自由軟體的開發:</p>
+
+<ul>
+<li><p><b>鼓勵自由軟體</b><br />
+政府應該鼓勵開發者製作或改善自由軟體,並將å…
¶æä¾›çµ¦æ°‘眾使用,例如:透過減稅或å…
¶ä»–經濟獎勵措施達成。反過來說,對於非自由軟體的開發、散布、使用等,就不應給予這類獎勵。</p></li>
+
+<li><p><b>不鼓勵非自由軟體</b><br />
+尤其,不應讓專有軟體開發者可「捐贈」其軟體副本給學æ 
¡ï¼Œä¸¦æ ¹æ“šè»Ÿé«”的名義價值取得稅額扣抵。專有軟體在學æ 
¡é«”系之中沒有合法正當性。</p></li>
+</ul>
+
+<h3>電子垃圾</h3>
+<p>自由不應造成電子垃圾:</p>
+
+<ul>
+<li><p><b>軟體可以取代</b><br />
+許多現代電腦的設計,使其無法以自由軟體取代電腦已é 
è¼‰çš„軟體。因此,解除這些電腦綁縛的唯一辦法,就是將å…
¶ä¸Ÿæ£„。而這種做法對社會有害。</p>
+
+<p>因此,對於採用硬體介面或其他蓄意限制,來防止使用者
進行開發、安裝、使用自由軟體,以取代一部份或全部é 
è¼‰è»Ÿé«”的新電腦(亦即非二手)或以電è…
¦ç‚ºåŸºç¤Žçš„產品,無論是銷售、進口、大量散布等做法,皆應視為違法行為,或至少以沉重的ç¨
…賦作為反制。這尤其更適用於想安裝不同作業系統得先<a
+href="/proprietary/proprietary-jails.html">「越獄」</a>的裝置,或是某些周邊設備介面屬於祕密的裝置。
+</p></li>
+</ul>
+
+<h3>技術中立</h3>
+
+<p>透過本文提出的辦法,政府可以重拾對其電è…
¦é‹ç®—的控制權,並引領國家的å…
¬æ°‘、企業、組織等,取回對其電è…
¦é‹ç®—的控制權。然而,有些人卻認為這會違反技術中立「原則」。</p>
+
+<p>技術中立的概念,是指政府不應恣意對某種技術有特別偏好。這個原則是否有意義仍å
……滿爭議,而在純技術議題中的任何情
況下,此原則影響也有限。本文倡議的辦法則指出道德、社會、政治等層面上應強調的重點,這些層面已<a
+href="/philosophy/technological-neutrality.html">遠超
出<em>技術</em>中立的範疇</a>。只有那些想要征服國家的人,才會建議政府對å
…¶ä¸»æ¬Šæˆ–其公民自由之議題應保持「中立」。</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<b>譯者註︰</b>
+<ol><li id="trans1">理查・史托曼先生 (Richard Stallman) 為美國å…
¬æ°‘,因此以美國觀點出發。美國全名為美利堅聯合眾國
+(United States of
+America),州並非國家下設的行政區,而是由等同於國的各州å…
±åŒçµ„成一個聯邦國家。若對應到現行臺灣行政體系,則約略可概說是「直轄市、縣市行政區」,但仍有所不同。</li>
+</ol></div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-tw.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>請來信到 <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> 
詢問有關自由軟體基金會(FSF)和
+GNU 的一般問題;或者<a href="/contact/">以å…
¶ä»–方式</a>聯絡自由軟體基金會。至於損毀的連結及å…
¶ä»–修正和建議,可以將之寄給 <a
+href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>
+
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting translations of
+        our web pages, see <a
+        href="/server/standards/README.translations.html">Translations
+        README</a>. -->
+我們努力盡所能提供貼切、品質良善的翻譯。然而,我們無法十å
…¨åç¾Žï¼Œé‚„請將你的意見評述與一般建議寄給 <a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。</p>
+<p>請參照 <a href="/server/standards/README.translations.html">翻譯讀我 
README</a>
+來瞭解協調和提交我們的網頁翻譯相關事宜。</p>
+</div>
+
+<p>Copyright &copy; 2011, 2015, 2016, 2017, 2018 Free Software Foundation, 
Inc.</p>
+
+<p>本頁面採用<a rel="license"
+href="https://creativecommons.org/licenses/by-nd/4.0/deed.zh_TW";>創用 CC
+姓名標示-禁止改作 4.0 國際</a>條款給予授權。</p>
+
+<!--#include virtual="/server/bottom-notes.zh-tw.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>翻譯</b>:黃柏諺 <a href="mailto:s8321414 (at) gmail (dot) 
com">&lt;s8321414
+(at) gmail (dot) com&gt;</a>, 2018.<br />
+<b>校對</b>:曾政嘉 <a href="mailto:zerngjia (at) gmail (dot) 
com">&lt;zerngjia
+(at) gmail (dot) com&gt;</a>, 2019.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+更新時間︰
+
+$Date: 2019/01/15 07:28:55 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+<!-- for class="inner", starts in the banner include -->
+</body>
+</html>

Index: po/government-free-software.zh-tw-en.html
===================================================================
RCS file: po/government-free-software.zh-tw-en.html
diff -N po/government-free-software.zh-tw-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/government-free-software.zh-tw-en.html   15 Jan 2019 07:28:55 -0000      
1.1
@@ -0,0 +1,275 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.86 -->
+<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" -->
+<h2>Measures Governments Can Use to Promote Free Software</h2>
+<h3>And why it is their duty to do so</h3>
+
+<p>by <a href="http://www.stallman.org/";><strong>Richard
+Stallman</strong></a></p>
+
+<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 (non-free) 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="http://www.defectivebydesign.org/what_is_drm";>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><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF &amp; GNU inquiries to <a
+href="mailto:address@hidden";>&lt;address@hidden&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:address@hidden";>&lt;address@hidden&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:address@hidden";>
+        &lt;address@hidden&gt;</a>.</p>
+
+        <p>For information on coordinating and submitting 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 submitting translations of this article.</p>
+</div>
+
+<p>Copyright &copy; 2011, 2015, 2016, 2017, 2018 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: 2019/01/15 07:28:55 $
+<!-- timestamp end -->
+</p>
+</div>
+</div><!-- for class="inner", starts in the banner include -->
+</body>
+</html>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]