[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses why-affero-gpl.hr.html po/why-affe...
|
From: |
GNUN |
|
Subject: |
www/licenses why-affero-gpl.hr.html po/why-affe... |
|
Date: |
Sun, 19 Jan 2014 16:36:37 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 14/01/19 16:36:37
Modified files:
licenses : why-affero-gpl.hr.html
Added files:
licenses/po : why-affero-gpl.hr-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/why-affero-gpl.hr.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/why-affero-gpl.hr-diff.html?cvsroot=www&rev=1.1
Patches:
Index: why-affero-gpl.hr.html
===================================================================
RCS file: /web/www/www/licenses/why-affero-gpl.hr.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- why-affero-gpl.hr.html 23 Sep 2013 18:28:05 -0000 1.1
+++ why-affero-gpl.hr.html 19 Jan 2014 16:36:36 -0000 1.2
@@ -11,6 +11,13 @@
<!--#include virtual="/licenses/po/why-affero-gpl.translist" -->
<!--#include virtual="/server/banner.hr.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="http://www.gnu.org/licenses/po/why-affero-gpl.hr.po";>
+ http://www.gnu.org/licenses/po/why-affero-gpl.hr.po</a>' -->
+ <!--#set var="ORIGINAL_FILE" value="/licenses/why-affero-gpl.html" -->
+ <!--#set var="DIFF_FILE" value="/licenses/po/why-affero-gpl.hr-diff.html" -->
+ <!--#set var="OUTDATED_SINCE" value="2013-11-20" -->
+ <!--#include virtual="/server/outdated.hr.html" -->
<h2>ZaÅ¡to opÄa javna licenca Affero</h2>
<p>OpÄa javna licenca GNU Affero je izmijenjena verzija obiÄne opÄe javne
@@ -140,7 +147,7 @@
<p><!-- timestamp start -->
Vrijeme zadnje izmjene:
-$Date: 2013/09/23 18:28:05 $
+$Date: 2014/01/19 16:36:36 $
<!-- timestamp end -->
</p>
Index: po/why-affero-gpl.hr-diff.html
===================================================================
RCS file: po/why-affero-gpl.hr-diff.html
diff -N po/why-affero-gpl.hr-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/why-affero-gpl.hr-diff.html 19 Jan 2014 16:36:37 -0000 1.1
@@ -0,0 +1,160 @@
+<!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>/licenses/why-affero-gpl.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.75 -->
+<title>Why the GNU Affero GPL
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/why-affero-gpl.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Why the Affero GPL</h2>
+
+<p>The GNU Affero General Public License is a modified version of the
+ordinary GNU GPL version 3. It has one added requirement: if you run
+the program on a server and let other users communicate with it there,
+your server must also allow them to download the source code
+corresponding to the program that it's running. If what's running
+there is your modified version of the program, the server's users must
+get the source code as you modified it.</p>
+
+<p>The purpose of the GNU Affero GPL is to prevent a problem that
+affects developers of free programs that are often used on
+servers.</p>
+
+<p>Suppose you develop and release a free program under the ordinary
+GNU GPL. If developer D modifies the program and releases it, the GPL
+requires him to distribute his version under the GPL too. Thus, if
+you get a copy of his version, you are free to incorporate some or all
+of his changes into your own version.</p>
+
+<p>But suppose the program is mainly useful on servers. When D
+modifies the program, he might very likely run it on his own server
+and never release copies. Then you would never get a copy of the
+source code of his version, so you would never have the chance to
+include his changes in your version. You may not like that
+outcome.</p>
+
+<p>Using the GNU Affero GPL avoids that outcome. If D runs his
+version on a server that everyone can use, you too can use it.
+Assuming he has followed the license requirement to let the server's
+users download the source code of his version, you can do so, and then
+you can incorporate his changes into your version. (If he hasn't
+followed it, you have your lawyer complain to him.)</p>
+
+<p>Both the ordinary GNU GPL, version 3, and the GNU Affero GPL have
+text allowing you to link together modules under these two licenses in
+one program.</p>
+
+<span class="removed"><del><strong><!-- Added a link to rms' article here.
If it can be improved, please do it! -->
+<p>One problem which the</strong></del></span>
+
+<span class="inserted"><ins><em><p>The</em></ins></span> GNU Affero GPL
does not address <span class="removed"><del><strong>is</strong></del></span>
the problem
+of <span class="removed"><del><strong>Software as a</strong></del></span>
<span class="inserted"><ins><em><a
href="/philosophy/who-does-that-server-really-serve.html"></em></ins></span>
+Service <span class="removed"><del><strong>(SaaS). It is impossible, as
far</strong></del></span> as
+<span class="removed"><del><strong>we know, to address this problem
with</strong></del></span> a <span class="removed"><del><strong>software
+license. <a href="/philosophy/who-does-that-server-really-serve.html">
+[1] </a></p>
+
+<p>SaaS</strong></del></span> <span class="inserted"><ins><em>Software
Substitute (SaaSS)</a>.</p>
+
+<p>SaaSS</em></ins></span> means <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>that users</em></ins></span> use <span
class="removed"><del><strong>of someone's network server, by
others,</strong></del></span> <span class="inserted"><ins><em>someone else's
web server</em></ins></span> to do
+<span class="removed"><del><strong>work which is</strong></del></span> their
+own computing. <span class="removed"><del><strong>They
have</strong></del></span> <span class="inserted"><ins><em>This requires
them</em></ins></span> to send their data to the server,
+which does their computing for <span
class="removed"><del><strong>them,</strong></del></span> <span
class="inserted"><ins><em>them</em></ins></span> and sends the results back to
+them. <span class="removed"><del><strong>SaaS</strong></del></span> <span
class="inserted"><ins><em>SaaSS</em></ins></span> is <span
class="removed"><del><strong>a problem</strong></del></span> <span
class="inserted"><ins><em>an injustice</em></ins></span> because the users
cannot control <span class="removed"><del><strong>the</strong></del></span>
<span class="inserted"><ins><em>their</em></ins></span>
+computing <span class="removed"><del><strong>which the server does for
them.</p></strong></del></span> <span class="inserted"><ins><em>when it's
done that way.</p></em></ins></span>
+
+<p>If some program on this server is released under the GNU Affero
+GPL, <span class="removed"><del><strong>it requires that</strong></del></span>
the <span class="removed"><del><strong>users have a way</strong></del></span>
<span class="inserted"><ins><em>server is required</em></ins></span> to <span
class="removed"><del><strong>download</strong></del></span> <span
class="inserted"><ins><em>offer the users</em></ins></span> the corresponding
+source of that program. That is good, but having this source code
+does not give them control over the computing <span
class="removed"><del><strong>the server
+does for them.</strong></del></span> <span class="inserted"><ins><em>done on
that server.</em></ins></span> It
+also does not tell them what other software may be running on that
+server, examining or changing their data in other ways.</p>
+
+<span class="inserted"><ins><em><p>We don't see any sensible way to
address the SaaSS problem with
+license conditions on particular programs. Even to write a legal
+condition to distinguish between SaaSS use and non-SaaSS use would be
+a challenge, and if we had that, it is not clear what we would want to
+require in the SaaSS case. Thus, our solution to the problem of SaaSS
+is simple: refuse to use it.</p>
+
+<p>If a program is meant specifically and only for SaaSS, you
+shouldn't write it. But many programs are useful for a variety of
+kinds of services, including some that are SaaSS and some that are
+not. It's useful to write and release these programs so people can
+set up non-SaaSS services with them, and good to release them under
+the AGPL.</p></em></ins></span>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden"><address@hidden></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"><address@hidden></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">
+ <address@hidden></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>
+
+<!-- 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 3.0 US. 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. -->
+
+<p>Copyright © 2010, 2013 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2014/01/19 16:36:37 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/licenses why-affero-gpl.hr.html po/why-affe...,
GNUN <=