[Top][All Lists]

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

www/philosophy ucita.ja.html po/ucita.ja-diff.html

From: GNUN
Subject: www/philosophy ucita.ja.html po/ucita.ja-diff.html
Date: Wed, 31 May 2017 07:00:00 -0400 (EDT)

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     17/05/31 07:00:00

Modified files:
        philosophy     : ucita.ja.html 
Added files:
        philosophy/po  : ucita.ja-diff.html 

Log message:
        Automatic update by GNUnited Nations.


Index: ucita.ja.html
RCS file: /web/www/www/philosophy/ucita.ja.html,v
retrieving revision 1.32
retrieving revision 1.33
diff -u -b -r1.32 -r1.33
--- ucita.ja.html       18 Nov 2016 07:32:51 -0000      1.32
+++ ucita.ja.html       31 May 2017 10:59:59 -0000      1.33
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/philosophy/ucita.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/philosophy/po/ucita.ja.po">
+ https://www.gnu.org/philosophy/po/ucita.ja.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/philosophy/ucita.html"
+ --><!--#set var="DIFF_FILE" value="/philosophy/po/ucita.ja-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-04-01" --><!--#set 
var="ENGLISH_PAGE" value="/philosophy/ucita.en.html" -->
 <!--#include virtual="/server/header.ja.html" -->
 <!-- Parent-Version: 1.79 -->
@@ -8,6 +13,7 @@
 <!--#include virtual="/philosophy/po/ucita.translist" -->
 <!--#include virtual="/server/banner.ja.html" -->
+<!--#include virtual="/server/outdated.ja.html" -->
@@ -172,7 +178,7 @@
 <p class="unprintable"><!-- timestamp start -->
-$Date: 2016/11/18 07:32:51 $
+$Date: 2017/05/31 10:59:59 $
 <!-- timestamp end -->

Index: po/ucita.ja-diff.html
RCS file: po/ucita.ja-diff.html
diff -N po/ucita.ja-diff.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/ucita.ja-diff.html       31 May 2017 10:59:59 -0000      1.1
@@ -0,0 +1,261 @@
+<!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">
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<style type="text/css">
+span.removed { background-color: #f22; color: #000; }
+span.inserted { background-color: #2f2; color: #000; }
+&lt;!--#include virtual="/server/header.html" --&gt;
+&lt;!-- Parent-Version: 1.79 --&gt;
+&lt;title&gt;Why We Must Fight UCITA - GNU Project
+- Free Software Foundation&lt;/title&gt;
+&lt;!--#include virtual="/philosophy/po/ucita.translist" --&gt;
+&lt;!--#include virtual="/server/banner.html" --&gt;
+&lt;h2&gt;Why We Must Fight UCITA&lt;/h2&gt;
+UCITA is a proposed law, designed by the proprietary software
+developers, who are now asking all 50 states of the US to adopt it.
+If UCITA is adopted, it will threaten the free software community
+&lt;a href="#Note1"&gt;(1)&lt;/a&gt; with disaster.  To understand why, please
+read on.&lt;/p&gt;
+We generally believe that big companies ought to be held to a strict
+standard of liability to their customers, because they can afford it
+and because it will keep them honest.  On the other hand, individuals,
+amateurs, and good samaritans should be treated more favorably.&lt;/p&gt;
+UCITA does exactly the opposite.  It makes individuals, amateurs, and
+good samaritans liable, but not big companies.&lt;/p&gt;
+You see, UCITA says that by default a software developer or
+distributor is completely liable for flaws in a program; but it also
+allows a shrink-wrap license to override the default.  Sophisticated
+software companies that make proprietary software will use shrink-wrap
+licenses to avoid liability entirely.  But amateurs, and self-employed
+contractors who develop software for others, will often be shafted
+because they didn't know about this problem.  And we free software
+developers won't have any reliable way to avoid the problem.&lt;/p&gt;
+What could we do about this?  We could try to change our licenses to
+avoid it.  But since we don't use shrink-wrap licenses, we cannot
+override the UCITA default.  Perhaps we can prohibit distribution in
+the states that adopt UCITA.  That might solve the problem&mdash;for
+the software we release in the future.  But we can't do this
+retroactively for software we have already released.  Those versions
+are already available, people are already licensed to distribute them
+in these states&mdash;and when they do so, under UCITA, they would
+make us liable.  We are powerless to change this situation by changing
+our licenses now; we will have to make complex legal arguments that
+may or may not work.&lt;/p&gt;
+UCITA has another indirect consequence that would hamstring free
+software development in the long term&mdash;it gives proprietary
+software developers the power to prohibit reverse engineering.  This
+would make it easy for them to establish secret file formats and
+protocols, which there would be no lawful way for us to figure
+That could be a disastrous obstacle for development of free software
+that can serve users' practical needs, because communicating with
+users of non-free software is one of those needs.  Many users today
+feel that they must run Windows, simply so they can read and write
+files in Word format.  Microsoft's &ldquo;Halloween documents&rdquo;
+announced a plan to use secret formats and protocols as a weapon to
+obstruct the development of the GNU/Linux system
+&lt;a href="#Note2"&gt;(2)&lt;/a&gt;.&lt;/p&gt;
+Precisely this kind of restriction is now being used in Norway to
+prosecute 16-year-old Jon Johansen, who figured out the format of DVDs
+to make it possible to write free software to play them on free
+operating systems.  (The Electronic Frontier Foundation is helping
+with his defense; see &lt;a 
+for further information.)&lt;/p&gt;
+Some friends of free software have argued that UCITA would benefit our
+community, by making non-free software intolerably restrictive, and
+thus driving users to us.  Realistically speaking, this is unlikely,
+because it assumes that proprietary software developers will act
+against their own interests.  They may be greedy and ruthless, but
+they are not stupid.&lt;/p&gt;
+Proprietary software developers intend to use the additional power
+UCITA would give them to increase their profits.  Rather than using
+this power at full throttle all the time, they will make an effort to
+find the most profitable way to use it.  Those applications of UCITA
+power that make users stop buying will be abandoned; those that most
+users tolerate will become the norm.  UCITA will not help us.&lt;/p&gt;
+UCITA does not apply only to software.  It applies to any sort of
+computer-readable information.  Even if you use only free software,
+you are likely to read articles on your computer, and access data
+bases.  UCITA will allow the publishers to impose the most outrageous
+restrictions on you.  They could change the license retroactively at
+any time, and force you to delete the material if you don't accept the
+change.  They could even prohibit you from describing what you see as
+flaws in the material.&lt;/p&gt;
+This is too outrageous an injustice to wish on anyone, even if it
+would indirectly benefit a good cause.  As ethical beings, we must not
+favor the infliction of hardship and injustice on others on the
+grounds that it will drive them to join our cause.  We must not be
+Machiavellian.  The point of free software is concern for each other.&lt;/p&gt;
+Our only smart plan, our only ethical plan, is&hellip;to defeat 
+If you want to help the fight against UCITA, by meeting with state
+legislators in your state, send mail to Skip Lockwood
+&lt;a href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.  He 
can tell you how to
+contribute effectively.&lt;/p&gt;
+Volunteers are needed most urgently in Virginia and
+Maryland &lt;a href="#Note3"&gt;(3)&lt;/a&gt;, but California and Oklahoma are
+coming soon.  There will probably be a battle in every state sooner or
+For more information about UCITA, see
+[Archived Page]&lt;/a&gt; or read the UCITA page on
+Wikipedia: &lt;a 
+&lt;!-- Link broken as of 21 Oct 2012 
+InfoWorld magazine is also helping to fight
+against UCITA; see
+&lt;li id="Note1"&gt;Other people have been using the term &ldquo;open
+source&rdquo; to describe a similar category of software.  I use the
+term &ldquo;free software&rdquo; to show that the Free Software
+Movement still exists&mdash;that the Open Source Movement has not
+replaced or absorbed us.
+If you value your freedom as well as your convenience, I suggest you
+use the term &ldquo;free software&rdquo;, not &ldquo;open
+source&rdquo;, to describe your own work, so as to stand up clearly
+for your values.&lt;/p&gt;
+If you value accuracy, please use the term &ldquo;free
+software&rdquo;, not &ldquo;open source&rdquo;, to describe the work
+of the Free Software Movement.  The GNU operating system, its
+GNU/Linux variant, the many GNU software packages, and the GNU GPL,
+are all primarily the work of the Free Software Movement.  The
+supporters of the Open Source Movement have the right to promote their
+views, but they should not do so on the basis of our achievements.&lt;/p&gt;
+See &lt;a href="/philosophy/open-source-misses-the-point.html"&gt;
+http://www.gnu.org/philosophy/open-source-misses-the-point.html&lt;/a&gt; for
+more explanation.&lt;/p&gt;&lt;/li&gt;
+&lt;li id="Note2"&gt;The system is often called &ldquo;Linux&rdquo;, but
+properly speaking Linux is actually the kernel, one major component of
+the system (see
+&lt;li id="Note3"&gt;The Maryland lower house has approved UCITA; there is a
+push to get the state senate to approve it before the end of the
+legislative session, on April 10.
+To rush the consideration of this bill is even more obviously foolish
+than the bill itself.  So if you live in Maryland, please phone or
+write to your state senator, saying the senate should at least defer
+UCITA for summer study, if it is not rejected outright.&lt;/p&gt;
+If you know anyone in Maryland who works with computers, please
+forward this message to that person and ask for per 
+&lt;hr /&gt;
+&lt;p style="text-align:center"&gt;
+If you support the anti UCITA campaign, &lt;em&gt;please make prominent links 
+ this page, http://www.4cite.org [closed].&lt;/em&gt;
+&lt;hr /&gt;
+&lt;h4&gt;Links to other articles&lt;/h4&gt;
+ &lt;li&gt;&lt;a <span 
+  supports the movement to oppose <span 
<span class="inserted"><ins><em>UCITA [Archived 
+ &lt;li&gt;&lt;a 
+ join fight to kill UCITA&lt;/a&gt;&lt;/li&gt;
+ &lt;li&gt;&lt;a 
+UCITA, and other interesting links maintained by Citizens on the Web
+[Archived Page]&lt;/a&gt;
+&lt;/div&gt;&lt;!-- for id="content", starts in the include above --&gt;
+&lt;!--#include virtual="/server/footer.html" --&gt;
+&lt;div id="footer"&gt;
+&lt;div class="unprintable"&gt;
+&lt;p&gt;Please send general FSF &amp; GNU inquiries to
+&lt;a href="mailto:address@hidden"&gt;&lt;address@hidden&gt;&lt;/a&gt;.
+There are also &lt;a href="/contact/"&gt;other ways to contact&lt;/a&gt;
+the FSF.  Broken links and other corrections or suggestions can be sent
+to &lt;a 
+&lt;p&gt;&lt;!-- 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 &lt;a href="mailto:address@hidden"&gt;
+        &lt;address@hidden&gt;&lt;/a&gt;.&lt;/p&gt;
+        &lt;p&gt;For information on coordinating and submitting translations of
+        our web pages, see &lt;a
+        href="/server/standards/README.translations.html"&gt;Translations
+        README&lt;/a&gt;. --&gt;
+Please see the &lt;a
+README&lt;/a&gt; for information on coordinating and submitting translations
+of this article.&lt;/p&gt;
+&lt;!-- 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. --&gt;
+&lt;p&gt;Copyright &copy; 2000, 2008, 2013, <span 
class="removed"><del><strong>2016</strong></del></span> <span 
class="inserted"><ins><em>2016, 2017</em></ins></span> Free Software 
Foundation, Inc.&lt;/p&gt;
+&lt;p&gt;This page is licensed under a &lt;a rel="license"
+Commons Attribution-NoDerivatives 4.0 International 
+&lt;!--#include virtual="/server/bottom-notes.html" --&gt;
+&lt;p class="unprintable"&gt;Updated:
+&lt;!-- timestamp start --&gt;
+$Date: 2017/05/31 10:59:59 $
+&lt;!-- timestamp end --&gt;

reply via email to

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