[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www distros/distros.it.html distros/distros.ja....
|
From: |
GNUN |
|
Subject: |
www distros/distros.it.html distros/distros.ja.... |
|
Date: |
Fri, 15 Dec 2017 13:59:40 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 17/12/15 13:59:40
Modified files:
distros : distros.it.html distros.ja.html distros.lt.html
distros.pl.html
free-system-distribution-guidelines.ar.html
free-system-distribution-guidelines.it.html
free-system-distribution-guidelines.ja.html
free-system-distribution-guidelines.lt.html
free-system-distribution-guidelines.pl.html
distros/po : distros.lt-diff.html
free-system-distribution-guidelines.ar-diff.html
free-system-distribution-guidelines.ja-diff.html
licenses : gpl-faq.it.html
licenses/po : gpl-faq.it-diff.html
Added files:
distros/po : distros.it-diff.html distros.ja-diff.html
distros.pl-diff.html
free-system-distribution-guidelines.it-diff.html
free-system-distribution-guidelines.lt-diff.html
free-system-distribution-guidelines.pl-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/distros.it.html?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/distros.ja.html?cvsroot=www&r1=1.35&r2=1.36
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/distros.lt.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/distros.pl.html?cvsroot=www&r1=1.40&r2=1.41
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/free-system-distribution-guidelines.ar.html?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/free-system-distribution-guidelines.it.html?cvsroot=www&r1=1.47&r2=1.48
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/free-system-distribution-guidelines.ja.html?cvsroot=www&r1=1.42&r2=1.43
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/free-system-distribution-guidelines.lt.html?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/free-system-distribution-guidelines.pl.html?cvsroot=www&r1=1.48&r2=1.49
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/distros.lt-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.ar-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.ja-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/distros.it-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/distros.ja-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/distros.pl-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.it-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.lt-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/distros/po/free-system-distribution-guidelines.pl-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/gpl-faq.it.html?cvsroot=www&r1=1.23&r2=1.24
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/gpl-faq.it-diff.html?cvsroot=www&r1=1.1&r2=1.2
Patches:
Index: distros/distros.it.html
===================================================================
RCS file: /web/www/www/distros/distros.it.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- distros/distros.it.html 15 Apr 2015 08:28:43 -0000 1.35
+++ distros/distros.it.html 15 Dec 2017 18:59:37 -0000 1.36
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/distros/distros.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/distros.it.po">
+ https://www.gnu.org/distros/po/distros.it.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/distros/distros.html"
+ --><!--#set var="DIFF_FILE" value="/distros/po/distros.it-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/distros.en.html" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.77 -->
@@ -11,6 +16,7 @@
<!--#include virtual="/distros/po/distros.translist" -->
<!--#include virtual="/server/banner.it.html" -->
+<!--#include virtual="/server/outdated.it.html" -->
<h2>Distribuzioni GNU/Linux</h2>
<p>
@@ -195,7 +201,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2015/04/15 08:28:43 $
+$Date: 2017/12/15 18:59:37 $
<!-- timestamp end -->
</p>
Index: distros/distros.ja.html
===================================================================
RCS file: /web/www/www/distros/distros.ja.html,v
retrieving revision 1.35
retrieving revision 1.36
diff -u -b -r1.35 -r1.36
--- distros/distros.ja.html 3 Feb 2016 09:11:59 -0000 1.35
+++ distros/distros.ja.html 15 Dec 2017 18:59:37 -0000 1.36
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/distros/distros.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/distros.ja.po">
+ https://www.gnu.org/distros/po/distros.ja.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/distros/distros.html"
+ --><!--#set var="DIFF_FILE" value="/distros/po/distros.ja-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/distros.en.html" -->
<!--#include virtual="/server/header.ja.html" -->
<!-- Parent-Version: 1.77 -->
@@ -11,6 +16,7 @@
<!--#include virtual="/distros/po/distros.translist" -->
<!--#include virtual="/server/banner.ja.html" -->
+<!--#include virtual="/server/outdated.ja.html" -->
<h2>GNU/Linux ãã£ã¹ãã</h2>
<p>
@@ -148,7 +154,7 @@
<p class="unprintable"><!-- timestamp start -->
æçµæ´æ°:
-$Date: 2016/02/03 09:11:59 $
+$Date: 2017/12/15 18:59:37 $
<!-- timestamp end -->
</p>
Index: distros/distros.lt.html
===================================================================
RCS file: /web/www/www/distros/distros.lt.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- distros/distros.lt.html 28 Aug 2015 07:02:22 -0000 1.5
+++ distros/distros.lt.html 15 Dec 2017 18:59:37 -0000 1.6
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/distros/distros.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/distros.lt.po">
+ https://www.gnu.org/distros/po/distros.lt.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/distros/distros.html"
+ --><!--#set var="DIFF_FILE" value="/distros/po/distros.lt-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/distros.en.html" -->
<!--#include virtual="/server/header.lt.html" -->
<!-- Parent-Version: 1.77 -->
@@ -11,6 +16,7 @@
<!--#include virtual="/distros/po/distros.translist" -->
<!--#include virtual="/server/banner.lt.html" -->
+<!--#include virtual="/server/outdated.lt.html" -->
<h2>GNU/Linux distribucijos</h2>
<p>
@@ -199,7 +205,7 @@
<p class="unprintable"><!-- timestamp start -->
Atnaujinta:
-$Date: 2015/08/28 07:02:22 $
+$Date: 2017/12/15 18:59:37 $
<!-- timestamp end -->
</p>
Index: distros/distros.pl.html
===================================================================
RCS file: /web/www/www/distros/distros.pl.html,v
retrieving revision 1.40
retrieving revision 1.41
diff -u -b -r1.40 -r1.41
--- distros/distros.pl.html 16 Jan 2016 00:04:43 -0000 1.40
+++ distros/distros.pl.html 15 Dec 2017 18:59:37 -0000 1.41
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/distros/distros.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/distros.pl.po">
+ https://www.gnu.org/distros/po/distros.pl.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/distros/distros.html"
+ --><!--#set var="DIFF_FILE" value="/distros/po/distros.pl-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/distros.en.html" -->
<!--#include virtual="/server/header.pl.html" -->
<!-- Parent-Version: 1.77 -->
@@ -11,6 +16,7 @@
<!--#include virtual="/distros/po/distros.translist" -->
<!--#include virtual="/server/banner.pl.html" -->
+<!--#include virtual="/server/outdated.pl.html" -->
<h2>Dystrubucje GNU/Linuksa</h2>
<p>
@@ -194,7 +200,7 @@
<p class="unprintable"><!-- timestamp start -->
Aktualizowane:
-$Date: 2016/01/16 00:04:43 $
+$Date: 2017/12/15 18:59:37 $
<!-- timestamp end -->
</p>
Index: distros/free-system-distribution-guidelines.ar.html
===================================================================
RCS file: /web/www/www/distros/free-system-distribution-guidelines.ar.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- distros/free-system-distribution-guidelines.ar.html 28 Mar 2017 10:28:49
-0000 1.3
+++ distros/free-system-distribution-guidelines.ar.html 15 Dec 2017 18:59:37
-0000 1.4
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/distros/free-system-distribution-guidelines.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/free-system-distribution-guidelines.ar.po">
+ https://www.gnu.org/distros/po/free-system-distribution-guidelines.ar.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/distros/free-system-distribution-guidelines.html"
+ --><!--#set var="DIFF_FILE"
value="/distros/po/free-system-distribution-guidelines.ar-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/free-system-distribution-guidelines.en.html"
-->
<!--#include virtual="/server/header.ar.html" -->
<!-- Parent-Version: 1.77 -->
@@ -12,6 +17,7 @@
<!--#include
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
<!--#include virtual="/server/banner.ar.html" -->
+<!--#include virtual="/server/outdated.ar.html" -->
<h2>اÙتÙجÙÙات اÙخاصة بتÙزÙعات اﻷÙظÙ
Ø© اÙØرة
(GNU FSDG)</h2>
<!--#include virtual="/licenses/fsf-licensing.ar.html" -->
@@ -338,7 +344,7 @@
<p class="unprintable"><!-- timestamp start -->
تØدÙØ«:
-$Date: 2017/03/28 10:28:49 $
+$Date: 2017/12/15 18:59:37 $
<!-- timestamp end -->
</p>
Index: distros/free-system-distribution-guidelines.it.html
===================================================================
RCS file: /web/www/www/distros/free-system-distribution-guidelines.it.html,v
retrieving revision 1.47
retrieving revision 1.48
diff -u -b -r1.47 -r1.48
--- distros/free-system-distribution-guidelines.it.html 27 Jun 2015 15:00:39
-0000 1.47
+++ distros/free-system-distribution-guidelines.it.html 15 Dec 2017 18:59:37
-0000 1.48
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/distros/free-system-distribution-guidelines.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/free-system-distribution-guidelines.it.po">
+ https://www.gnu.org/distros/po/free-system-distribution-guidelines.it.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/distros/free-system-distribution-guidelines.html"
+ --><!--#set var="DIFF_FILE"
value="/distros/po/free-system-distribution-guidelines.it-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/free-system-distribution-guidelines.en.html"
-->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.77 -->
@@ -12,6 +17,7 @@
<!--#include
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
<!--#include virtual="/server/banner.it.html" -->
+<!--#include virtual="/server/outdated.it.html" -->
<h2>Linee guida per distribuzioni di sistema libere (GNU FSDG)</h2>
<!--#include virtual="/licenses/fsf-licensing.it.html" -->
@@ -373,7 +379,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2015/06/27 15:00:39 $
+$Date: 2017/12/15 18:59:37 $
<!-- timestamp end -->
</p>
Index: distros/free-system-distribution-guidelines.ja.html
===================================================================
RCS file: /web/www/www/distros/free-system-distribution-guidelines.ja.html,v
retrieving revision 1.42
retrieving revision 1.43
diff -u -b -r1.42 -r1.43
--- distros/free-system-distribution-guidelines.ja.html 3 Feb 2016 09:12:01
-0000 1.42
+++ distros/free-system-distribution-guidelines.ja.html 15 Dec 2017 18:59:38
-0000 1.43
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/distros/free-system-distribution-guidelines.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/free-system-distribution-guidelines.ja.po">
+ https://www.gnu.org/distros/po/free-system-distribution-guidelines.ja.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/distros/free-system-distribution-guidelines.html"
+ --><!--#set var="DIFF_FILE"
value="/distros/po/free-system-distribution-guidelines.ja-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/free-system-distribution-guidelines.en.html"
-->
<!--#include virtual="/server/header.ja.html" -->
<!-- Parent-Version: 1.77 -->
@@ -11,6 +16,7 @@
<!--#include
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
<!--#include virtual="/server/banner.ja.html" -->
+<!--#include virtual="/server/outdated.ja.html" -->
<h2>èªç±ãªã·ã¹ãã
ã»ãã£ã¹ããªãã¥ã¼ã·ã§ã³ã®ã¬ã¤ãã©ã¤ã³ (GNU FSDG)</h2>
<!--#include virtual="/licenses/fsf-licensing.ja.html" -->
@@ -215,7 +221,7 @@
<p class="unprintable"><!-- timestamp start -->
æçµæ´æ°:
-$Date: 2016/02/03 09:12:01 $
+$Date: 2017/12/15 18:59:38 $
<!-- timestamp end -->
</p>
Index: distros/free-system-distribution-guidelines.lt.html
===================================================================
RCS file: /web/www/www/distros/free-system-distribution-guidelines.lt.html,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- distros/free-system-distribution-guidelines.lt.html 19 Jan 2016 07:08:02
-0000 1.2
+++ distros/free-system-distribution-guidelines.lt.html 15 Dec 2017 18:59:38
-0000 1.3
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/distros/free-system-distribution-guidelines.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/free-system-distribution-guidelines.lt.po">
+ https://www.gnu.org/distros/po/free-system-distribution-guidelines.lt.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/distros/free-system-distribution-guidelines.html"
+ --><!--#set var="DIFF_FILE"
value="/distros/po/free-system-distribution-guidelines.lt-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/free-system-distribution-guidelines.en.html"
-->
<!--#include virtual="/server/header.lt.html" -->
<!-- Parent-Version: 1.77 -->
@@ -12,6 +17,7 @@
<!--#include
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
<!--#include virtual="/server/banner.lt.html" -->
+<!--#include virtual="/server/outdated.lt.html" -->
<h2>Laisvos sistemos distribucijos gairÄs (GNU FSDG<sup><a
href="#TransNote1">1</a></sup>)</h2>
@@ -373,7 +379,7 @@
<p class="unprintable"><!-- timestamp start -->
Atnaujinta:
-$Date: 2016/01/19 07:08:02 $
+$Date: 2017/12/15 18:59:38 $
<!-- timestamp end -->
</p>
Index: distros/free-system-distribution-guidelines.pl.html
===================================================================
RCS file: /web/www/www/distros/free-system-distribution-guidelines.pl.html,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -b -r1.48 -r1.49
--- distros/free-system-distribution-guidelines.pl.html 16 Jan 2016 00:04:43
-0000 1.48
+++ distros/free-system-distribution-guidelines.pl.html 15 Dec 2017 18:59:38
-0000 1.49
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE"
value="/distros/free-system-distribution-guidelines.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/distros/po/free-system-distribution-guidelines.pl.po">
+ https://www.gnu.org/distros/po/free-system-distribution-guidelines.pl.po</a>'
+ --><!--#set var="ORIGINAL_FILE"
value="/distros/free-system-distribution-guidelines.html"
+ --><!--#set var="DIFF_FILE"
value="/distros/po/free-system-distribution-guidelines.pl-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/distros/free-system-distribution-guidelines.en.html"
-->
<!--#include virtual="/server/header.pl.html" -->
<!-- Parent-Version: 1.77 -->
@@ -12,6 +17,7 @@
<!--#include
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
<!--#include virtual="/server/banner.pl.html" -->
+<!--#include virtual="/server/outdated.pl.html" -->
<h2>Wytyczne dla wolnych systemów dystrybucji [<em>Free System Distribution
Guidelines (GNU FSDG)</em>]</h2>
@@ -394,7 +400,7 @@
<p class="unprintable"><!-- timestamp start -->
Aktualizowane:
-$Date: 2016/01/16 00:04:43 $
+$Date: 2017/12/15 18:59:38 $
<!-- timestamp end -->
</p>
Index: distros/po/distros.lt-diff.html
===================================================================
RCS file: /web/www/www/distros/po/distros.lt-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- distros/po/distros.lt-diff.html 12 Jun 2015 09:58:14 -0000 1.1
+++ distros/po/distros.lt-diff.html 15 Dec 2017 18:59:39 -0000 1.2
@@ -22,7 +22,8 @@
<h2>GNU/Linux Distros</h2>
<p>
-Free GNU/Linux system distributions (or “distros”) only
+Free <span class="removed"><del><strong>GNU/Linux system</strong></del></span>
distributions (or “distros”) <span class="inserted"><ins><em>of
+the <a href="/gnu/linux-and-gnu.html">GNU/Linux
system</a></em></ins></span> only
include and only propose free software. They reject non-free
applications, non-free programming platforms, non-free drivers,
non-free firmware “blobs”, and any other non-free software
@@ -45,7 +46,7 @@
free distro rather that starting a new free distro.
</p>
-<h3 <span class="inserted"><ins><em>id="freeNonDistros">Free Non-GNU
Distros</h3>
+<h3 id="freeNonDistros">Free Non-GNU Distros</h3>
<p>
These system distributions are free but quite different from GNU.
Using them is not similar to using GNU/Linux. However, they satisfy
@@ -60,7 +61,7 @@
starting a new free distro.
</p>
-<h3</em></ins></span> id="distroGuidelines">Free Distro
Guidelines</h3>
+<h3 id="distroGuidelines">Free Distro Guidelines</h3>
<p>
Here is the list of problems that can prevent a distro from being
considered entirely free:<br />
@@ -157,7 +158,7 @@
<!-- 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
+ be under CC BY-ND <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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
@@ -172,17 +173,18 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © <span
class="removed"><del><strong>2014</strong></del></span> <span
class="inserted"><ins><em>2014, 2015</em></ins></span> Free Software
Foundation, Inc.</p>
+<p>Copyright © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</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/3.0/us/">Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
<!--#include virtual="/server/bottom-notes.html" -->
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2015/06/12 09:58:14 $
+$Date: 2017/12/15 18:59:39 $
<!-- timestamp end -->
</p>
</div>
Index: distros/po/free-system-distribution-guidelines.ar-diff.html
===================================================================
RCS file:
/web/www/www/distros/po/free-system-distribution-guidelines.ar-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- distros/po/free-system-distribution-guidelines.ar-diff.html 24 Aug 2015
16:59:35 -0000 1.1
+++ distros/po/free-system-distribution-guidelines.ar-diff.html 15 Dec 2017
18:59:39 -0000 1.2
@@ -24,7 +24,7 @@
<h3 id="introduction">Introduction</h3>
<p>The purpose of these guidelines is to explain what it means for an
-installable system distribution (such as a GNU/Linux distribution) to
+installable system distribution (such as a <span
class="removed"><del><strong>GNU/Linux</strong></del></span> <span
class="inserted"><ins><em><a
href="/gnu/linux-and-gnu.html">GNU/Linux</a></em></ins></span>
distribution) to
qualify as <a href="/philosophy/free-sw.html">free</a> (libre), and
help distribution developers make their distributions qualify.</p>
@@ -88,6 +88,10 @@
should not suggest installing nonfree plugins, documentation, and so
on.</p>
+<span class="inserted"><ins><em><p>For instance, a free system
distribution must not contain browsers
+that implement EME, the browser functionality designed to load DRM
+modules.</p></em></ins></span>
+
<p>A free system distribution should be self-hosting. This means that
you must be able to develop and build the system with tools that the
system provides you. As a result, a free system distribution cannot
@@ -292,8 +296,7 @@
GNU system distributions</a> we know about. If you know about a free
distribution that isn't listed there, please ask its developers write
to <<a class="reference"
-<span
class="removed"><del><strong>href="mailto:address@hidden">address@hidden</a>></strong></del></span>
-<span
class="inserted"><ins><em>href="mailto:address@hidden">address@hidden</a>></em></ins></span>
with a description of
+href="mailto:address@hidden">address@hidden</a>> with a
description of
their system and a link to their web page.</p>
<p>We also list <a href="/distros/free-non-gnu-distros.html">free
@@ -301,8 +304,7 @@
<p>If you have questions or comments about these guidelines
themselves, feel free to send those to <<a class="reference"
-<span
class="removed"><del><strong>href="mailto:address@hidden">address@hidden</a>>.</strong></del></span>
-<span
class="inserted"><ins><em>href="mailto:address@hidden">address@hidden</a>>.</em></ins></span>
We hope
+href="mailto:address@hidden">address@hidden</a>>. We hope
that they help everyone better understand the issues that are important
for free system distributions, and we look forward to promoting more
of them in the future.</p>
@@ -339,7 +341,7 @@
<!-- 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 <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> Please do NOT change or
remove this
+ 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
@@ -354,18 +356,17 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2014, 2015 Free Software Foundation, Inc.</p>
+<p>Copyright © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</em></ins></span> Free Software
Foundation, Inc.</p>
<p>This page is licensed under a <a rel="license"
-<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
-<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
-Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+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: 2015/08/24 16:59:35 $
+$Date: 2017/12/15 18:59:39 $
<!-- timestamp end -->
</p>
</div>
Index: distros/po/free-system-distribution-guidelines.ja-diff.html
===================================================================
RCS file:
/web/www/www/distros/po/free-system-distribution-guidelines.ja-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- distros/po/free-system-distribution-guidelines.ja-diff.html 21 Oct 2014
16:00:13 -0000 1.1
+++ distros/po/free-system-distribution-guidelines.ja-diff.html 15 Dec 2017
18:59:39 -0000 1.2
@@ -24,7 +24,7 @@
<h3 id="introduction">Introduction</h3>
<p>The purpose of these guidelines is to explain what it means for an
-installable system distribution (such as a GNU/Linux distribution) to
+installable system distribution (such as a <span
class="removed"><del><strong>GNU/Linux</strong></del></span> <span
class="inserted"><ins><em><a
href="/gnu/linux-and-gnu.html">GNU/Linux</a></em></ins></span>
distribution) to
qualify as <a href="/philosophy/free-sw.html">free</a> (libre), and
help distribution developers make their distributions qualify.</p>
@@ -88,6 +88,10 @@
should not suggest installing nonfree plugins, documentation, and so
on.</p>
+<span class="inserted"><ins><em><p>For instance, a free system
distribution must not contain browsers
+that implement EME, the browser functionality designed to load DRM
+modules.</p></em></ins></span>
+
<p>A free system distribution should be self-hosting. This means that
you must be able to develop and build the system with tools that the
system provides you. As a result, a free system distribution cannot
@@ -241,6 +245,23 @@
Foobar Light. This is because we expect that the distinction between
the two would be lost in the process of communicating the message.</p>
+<p>In particular, the principal name of the free distribution
+(“Foobar”, in this example) should not be part of the name
+of any nonfree distribution.</p>
+
+<p>Some people have thought of adding the name “GNU” to a
+free distro name to distinguish it from a nonfree one. This has two
+problems. First, the two names would not be sufficiently different,
+since the principal word in both names would be the same.</p>
+
+<p>Second, this would promote a misunderstanding of what
+“GNU” means. <a href="/gnu/linux-and-gnu.html">GNU is an
+operating system</a>, typically used with Linux as the kernel, and
+essentially all so-called “Linux” distributions are really
+GNU/Linux distributions. In this scenario,
+<em>both</em> versions are GNU/Linux, and it would be misleading to
+omit “GNU” from the name of one of them.</p>
+
<h3 id="upstream">Contacting Upstream If You're Downstream</h3>
<p>For distro developers (or anyone else) who have sent an important bug
@@ -272,23 +293,18 @@
<h3 id="final-notes">Final Notes</h3>
<p>We maintain a list of the <a
href="/distros/free-distros.html">free
-<span class="inserted"><ins><em>GNU</em></ins></span> system
distributions</a> we know about. If you know about a free
+GNU system distributions</a> we know about. If you know about a free
distribution that isn't listed there, please ask its developers write
to <<a class="reference"
-href="mailto:address@hidden">address@hidden</a>> with a
description of
+href="mailto:address@hidden">address@hidden</a>> with a
description of
their system and a link to their web page.</p>
-<span class="removed"><del><strong><p>Our</strong></del></span>
-
-<span class="inserted"><ins><em><p>We also</em></ins></span> list <span
class="removed"><del><strong>consists of systems based on GNU which acknowledge
that
-they are based</strong></del></span> <span class="inserted"><ins><em><a
href="/distros/free-non-gnu-distros.html">free
-non-GNU system distributions</a></em></ins></span> on <span
class="removed"><del><strong>GNU. At present, we know of no other systems
-that would qualify. If someday there is one, we will list it,
-but not necessarily in</strong></del></span> <span
class="inserted"><ins><em>the</em></ins></span> same <span
class="removed"><del><strong>way.</p></strong></del></span> <span
class="inserted"><ins><em>ethical conditions.</p></em></ins></span>
+<p>We also list <a href="/distros/free-non-gnu-distros.html">free
+non-GNU system distributions</a> on the same ethical
conditions.</p>
<p>If you have questions or comments about these guidelines
themselves, feel free to send those to <<a class="reference"
-href="mailto:address@hidden">address@hidden</a>>. We hope
+href="mailto:address@hidden">address@hidden</a>>. We hope
that they help everyone better understand the issues that are important
for free system distributions, and we look forward to promoting more
of them in the future.</p>
@@ -325,7 +341,7 @@
<!-- 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
+ 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
@@ -340,17 +356,17 @@
There is more detail about copyright years in the GNU Maintainers
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2014 Free Software Foundation, Inc.</p>
+<p>Copyright © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</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/3.0/us/">Creative
-Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+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: 2014/10/21 16:00:13 $
+$Date: 2017/12/15 18:59:39 $
<!-- timestamp end -->
</p>
</div>
Index: licenses/gpl-faq.it.html
===================================================================
RCS file: /web/www/www/licenses/gpl-faq.it.html,v
retrieving revision 1.23
retrieving revision 1.24
diff -u -b -r1.23 -r1.24
--- licenses/gpl-faq.it.html 30 Sep 2017 21:00:08 -0000 1.23
+++ licenses/gpl-faq.it.html 15 Dec 2017 18:59:40 -0000 1.24
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/gpl-faq.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/gpl-faq.it.po">
+ https://www.gnu.org/licenses/po/gpl-faq.it.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/gpl-faq.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/gpl-faq.it-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/licenses/gpl-faq.en.html" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.79 -->
@@ -47,6 +52,7 @@
<!--#include virtual="/licenses/po/gpl-faq.translist" -->
<!--#include virtual="/server/banner.it.html" -->
+<!--#include virtual="/server/outdated.it.html" -->
<h2>Domande ricorrenti sulle licenze GNU</h2>
<!--#include virtual="/licenses/fsf-licensing.it.html" -->
@@ -3880,7 +3886,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2017/09/30 21:00:08 $
+$Date: 2017/12/15 18:59:40 $
<!-- timestamp end -->
</p>
Index: licenses/po/gpl-faq.it-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/gpl-faq.it-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- licenses/po/gpl-faq.it-diff.html 25 Jul 2016 15:28:11 -0000 1.1
+++ licenses/po/gpl-faq.it-diff.html 15 Dec 2017 18:59:40 -0000 1.2
@@ -11,7 +11,7 @@
</style></head>
<body><pre>
<!--#include virtual="/server/header.html" -->
-<!-- Parent-Version: 1.77 -->
+<!-- Parent-Version: 1.79 -->
<title>Frequently Asked Questions about the GNU Licenses
- GNU Project - Free Software Foundation</title>
<style type="text/css" media="screen">
@@ -113,10 +113,10 @@
public?</a></li>
<li><a href="#GPLAndNonfreeOnSameMachine">Can I have a
GPL-covered
- program and an unrelated non-free program on the same
computer?</a></li>
+ program and an unrelated nonfree program on the same
computer?</a></li>
<li><a href="#CanIDemandACopy">If I know someone has a copy of
a
- GPL-covered program, can I demand <span
class="removed"><del><strong>he</strong></del></span> <span
class="inserted"><ins><em>they</em></ins></span> give me a
copy?</a></li>
+ GPL-covered program, can I demand they give me a copy?</a></li>
<li><a href="#WhatDoesWrittenOfferValid">What does
“written offer
valid for any third party” mean in GPLv2? Does that mean everyone
@@ -316,7 +316,7 @@
<li><a href="#ReleaseUnderGPLAndNF">I would like to release a
program I wrote under the GNU GPL, but I would like to use the same
- code in non-free programs.</a></li>
+ code in nonfree programs.</a></li>
<li><a href="#CanDeveloperThirdParty">Can the developer of a
program
who distributed it under the GPL later license it to another party
@@ -351,7 +351,7 @@
system templates?</a></li>
<li><a href="#NonFreeTools">Can I release a program under the
GPL
- which I developed using non-free tools?</a></li>
+ which I developed using nonfree tools?</a></li>
<li><a href="#GiveUpKeys">I use public key cryptography to
sign my
code to assure its authenticity. Is it true that GPLv3 forces me to
@@ -475,7 +475,7 @@
<li><a href="#v3CoworkerConveying">If I give a copy of a
GPLv3-covered program to a coworker at my company, have I
- “conveyed” the copy to <span
class="removed"><del><strong>him?</a></li></strong></del></span>
<span class="inserted"><ins><em>that
coworker?</a></li></em></ins></span>
+ “conveyed” the copy to that coworker?</a></li>
<li><a href="#SourceInCVS">Am I complying with GPLv3 if I offer
binaries on an FTP server and sources by way of a link to a source
@@ -500,11 +500,11 @@
<ul>
<li><a href="#GPLAndNonfreeOnSameMachine">Can I have a
GPL-covered
- program and an unrelated non-free program on the same
+ program and an unrelated nonfree program on the same
computer?</a></li>
<li><a href="#CanIUseGPLToolsForNF">Can I use GPL-covered
editors
- such as GNU Emacs to develop non-free programs? Can I use
+ such as GNU Emacs to develop nonfree programs? Can I use
GPL-covered tools such as GCC to compile them?</a></li>
<li><a href="#GPLOutput">Is there some way that I can GPL the
output
@@ -515,7 +515,7 @@
<li><a href="#WhatCaseIsOutputGPL">In what cases is the output
of a
GPL program covered by the GPL too?</a></li>
- <li><a href="#PortProgramToGL">If I port my program to
GNU/Linux,
+ <li><a href="#PortProgramToGPL">If I port my program to
GNU/Linux,
does that mean I have to release it as free software under the GPL
or some other free software license?</a></li>
@@ -545,6 +545,9 @@
<li><a href="#v2v3Compatibility">Is GPLv3 compatible with
GPLv2?</a></li>
+ <li><a href="#InstInfo">Does GPLv2 have a requirement about
+ delivering installation information?</a></li>
+
<li><a href="#AllCompatibility">How are the various GNU
licenses
compatible with each other?</a></li>
@@ -596,14 +599,17 @@
program, do I have to use the GPL as the license for my
module?</a></li>
+ <li><a href="#GPLPlugins">When is a program and its plug-ins
+ considered a single combined program?</a></li>
+
<li><a href="#GPLAndPlugins">If I write a plug-in to use with
a GPL-covered program, what requirements does that impose
on the licenses I can use for distributing my plug-in?</a></li>
<li><a href="#GPLPluginsInNF">Can I apply the GPL when writing
a
- plug-in for a non-free program?</a></li>
+ plug-in for a nonfree program?</a></li>
- <li><a href="#NFUseGPLPlugins">Can I release a non-free program
+ <li><a href="#NFUseGPLPlugins">Can I release a nonfree program
that's designed to load a GPL-covered plug-in?</a></li>
<li><a href="#GPLInProprietarySystem">I'd like to incorporate
@@ -618,7 +624,7 @@
and the proprietary part?</a></li>
<li><a href="#FSWithNFLibs">Can I write free software that uses
- non-free libraries?</a></li>
+ nonfree libraries?</a></li>
<li><a href="#SystemLibraryException">Can I link a GPL program
with
a proprietary system library?</a></li>
@@ -839,22 +845,21 @@
<dt id="GPLAndNonfreeOnSameMachine">Can I have a GPL-covered
- program and an unrelated non-free program on the same computer?
+ program and an unrelated nonfree program on the same computer?
<span class="anchor-reference-id">(<a
href="#GPLAndNonfreeOnSameMachine"
>#GPLAndNonfreeOnSameMachine</a>)</span></dt>
<dd><p>Yes.</p></dd>
<dt id="CanIDemandACopy">If I know someone has a copy of a GPL-covered
- program, can I demand <span
class="removed"><del><strong>he</strong></del></span> <span
class="inserted"><ins><em>they</em></ins></span> give me a copy?
+ program, can I demand they give me a copy?
<span class="anchor-reference-id">(<a href="#CanIDemandACopy"
>#CanIDemandACopy</a>)</span></dt>
<dd><p>
-No. The GPL gives <span
class="removed"><del><strong>him</strong></del></span> <span
class="inserted"><ins><em>a person</em></ins></span> permission to make and
redistribute copies
-of the program <em>if and when <span
class="removed"><del><strong>he</strong></del></span> <span
class="inserted"><ins><em>that person</em></ins></span> chooses to do
so</em>. <span class="removed"><del><strong>He</strong></del></span>
-<span class="inserted"><ins><em>That person</em></ins></span> also has the
right not to <span class="inserted"><ins><em>choose to</em></ins></span>
redistribute the <span class="removed"><del><strong>program, when that is what
he
-chooses.</p></dd></strong></del></span>
-<span class="inserted"><ins><em>program.</p></dd></em></ins></span>
+No. The GPL gives a person permission to make and redistribute copies
+of the program <em>if and when that person chooses to do so</em>.
+That person also has the right not to choose to redistribute the
+program.</p></dd>
<dt id="WhatDoesWrittenOfferValid">What does “written offer
@@ -944,7 +949,9 @@
binary-only release.)</p></dd>
<dt id="DoesTheGPLAllowDownloadFee">Does the GPL allow me to charge a
- fee for downloading the program from my distribution site?</dt>
+ fee for downloading the program from my distribution site?
+ <span class="anchor-reference-id">(<a
href="#DoesTheGPLAllowDownloadFee"
+ >#DoesTheGPLAllowDownloadFee</a>)</span></dt>
<dd><p>
Yes. You can charge any fee you wish for distributing a copy of the
program. If you distribute binaries by download, you must provide
@@ -959,7 +966,7 @@
<span class="anchor-reference-id">(<a
href="#DoesTheGPLAllowRequireFee"
>#DoesTheGPLAllowRequireFee</a>)</span></dt>
<dd><p>
-No. In fact, a requirement like that would make the program non-free.
+No. In fact, a requirement like that would make the program nonfree.
If people have to pay when they get a copy of a program, or if they
have to notify anyone in particular, then the program is not free.
See the <a href="/philosophy/free-sw.html">
@@ -1074,7 +1081,7 @@
>#WhyMustIInclude</a>)</span></dt>
<dd><p>
Including a copy of the license with the work is vital so that
-everyone who gets a copy of the program can know what <span
class="removed"><del><strong>his</strong></del></span> <span
class="inserted"><ins><em>their</em></ins></span> rights are.</p>
+everyone who gets a copy of the program can know what their rights
are.</p>
<p>It might be tempting to include a URL that refers to the license,
instead of the license itself. But you cannot be sure that the URL
@@ -1209,29 +1216,29 @@
<dt id="FSWithNFLibs">Can I write
- free software that uses non-free libraries?
+ free software that uses nonfree libraries?
<span class="anchor-reference-id">(<a href="#FSWithNFLibs"
>#FSWithNFLibs</a>)</span></dt>
<dd><p>
If you do this, your program won't be fully usable in a free
-environment. If your program depends on a non-free library to do a
+environment. If your program depends on a nonfree library to do a
certain job, it cannot do that job in the Free World. If it depends on a
-non-free library to run at all, it cannot be part of a free operating
+nonfree library to run at all, it cannot be part of a free operating
system such as GNU; it is entirely off limits to the Free World.</p>
<p>So please consider: can you find a way to get the job done without
using
this library? Can you write a free replacement for that library?</p>
-<p>If the program is already written using the non-free library, perhaps
it
+<p>If the program is already written using the nonfree library, perhaps
it
is too late to change the decision. You may as well release the program
as it stands, rather than not release it. But please mention in the
-README that the need for the non-free library is a drawback, and suggest
+README that the need for the nonfree library is a drawback, and suggest
the task of changing the program so that it does the same job without
-the non-free library. Please suggest that anyone who thinks of doing
+the nonfree library. Please suggest that anyone who thinks of doing
substantial further work on the program first free it from dependence
-on the non-free library.</p>
+on the nonfree library.</p>
-<p>Note that there may also be legal issues with combining certain
non-free
+<p>Note that there may also be legal issues with combining certain
nonfree
libraries with GPL-covered free software. Please see <a
href="#GPLIncompatibleLibs">the question on GPL software with
GPL-incompatible libraries</a> for more information.</p></dd>
@@ -1277,9 +1284,9 @@
<p>When other people modify the program, they do not have to make the
same
exception for their code—it is their choice whether to do so.</p>
-<p>If the libraries you intend to link with are non-free, please also see
+<p>If the libraries you intend to link with are nonfree, please also see
<a href="#FSWithNFLibs">the section on writing Free Software which uses
-non-free libraries</a>.</p>
+nonfree libraries</a>.</p>
<p>If you're using GPLv3, you can accomplish this goal by granting an
additional permission under section 7. The following license notice will
@@ -1445,11 +1452,11 @@
<dt id="ReleaseUnderGPLAndNF">I would like to release a program I wrote
under the GNU GPL, but I would
- like to use the same code in non-free programs.
+ like to use the same code in nonfree programs.
<span class="anchor-reference-id">(<a href="#ReleaseUnderGPLAndNF"
>#ReleaseUnderGPLAndNF</a>)</span></dt>
<dd><p>
-To release a non-free program is always ethically tainted, but
+To release a nonfree program is always ethically tainted, but
legally there is no obstacle to your doing this. If you are the copyright
holder for the code, you can release it under various different
non-exclusive licenses at various times.</p></dd>
@@ -1481,7 +1488,7 @@
<dt id="CanIUseGPLToolsForNF">Can I use GPL-covered editors such as
- GNU Emacs to develop non-free programs? Can I use GPL-covered tools
+ GNU Emacs to develop nonfree programs? Can I use GPL-covered tools
such as GCC to compile them?
<span class="anchor-reference-id">(<a href="#CanIUseGPLToolsForNF"
>#CanIUseGPLToolsForNF</a>)</span></dt>
@@ -1497,11 +1504,11 @@
part of the output which is derived from the program's input inherits
the copyright status of the input.</p>
-<p>As it happens, Bison can also be used to develop non-free programs.
+<p>As it happens, Bison can also be used to develop nonfree programs.
This is because we decided to explicitly permit the use of the Bison
standard parser program in Bison output files without restriction. We
made the decision because there were other tools comparable to Bison
-which already permitted use for non-free programs.</p></dd>
+which already permitted use for nonfree programs.</p></dd>
<dt id="GPLFairUse">Do I have “fair use”
@@ -1595,8 +1602,8 @@
<dd><p>
In general this is legally impossible; copyright law does not give you
any say in the use of the output people make from their data using
-your program. If the user uses your program to enter or convert <span
class="removed"><del><strong>his</strong></del></span> <span
class="inserted"><ins><em>her</em></ins></span>
-own data, the copyright on the output belongs to <span
class="removed"><del><strong>him,</strong></del></span> <span
class="inserted"><ins><em>her,</em></ins></span> not you. More
+your program. If the user uses your program to enter or convert her
+own data, the copyright on the output belongs to her, not you. More
generally, when a program translates its input into some other form,
the copyright status of the output inherits that of the input it was
generated from.</p>
@@ -1652,7 +1659,7 @@
GPL.</p>
<p>But you can give additional permission for the use of your code. You
-can, if you wish, release your program under a license which is more lax
+can, if you wish, release your module under a license which is more lax
than the GPL but compatible with the GPL. The
<a href="/licenses/license-list.html">license list page</a> gives
a partial
list of GPL-compatible licenses. </p></dd>
@@ -1664,8 +1671,13 @@
<span class="anchor-reference-id">(<a href="#IfLibraryIsGPL"
>#IfLibraryIsGPL</a>)</span></dt>
<dd><p>
-Yes, because the software as it is actually run includes the
-library.</p></dd>
+Yes, because the program actually links to the library. As such,
+the terms of the GPL apply to the entire combination. The software modules
+that link with the library may be under various GPL compatible licenses, but
the
+work as a whole must be licensed under the GPL. See also:
+<a href="#WhatDoesCompatMean">What does it mean to say a license is
+“compatible with the GPL”?</a>
+</p></dd>
<dt id="IfInterpreterIsGPL">If a programming language interpreter
@@ -1756,82 +1768,87 @@
eliminates the problem.</p></dd>
+<dt id="GPLPlugins">When is a program and its plug-ins considered a
single combined program?
+ <span class="anchor-reference-id">(<a href="#GPLPlugins"
+ >#GPLPlugins</a>)</span></dt>
+<dd><p>
+ It depends on how the main program invokes its plug-ins. If the
+main program uses fork and exec to invoke plug-ins, and they establish
+intimate communication by sharing complex data structures, or shipping
+complex data structures back and forth, that can make them one single
+combined program. A main program that uses simple fork and exec to
+invoke plug-ins and does not establish intimate communication between
+them results in the plug-ins being a separate program.</p>
+
+<p> If the main program dynamically links plug-ins, and they make
+function calls to each other and share data structures, we believe
+they form a single combined program, which must be treated as an
+extension of both the main program and the plug-ins. If the main
+program dynamically links plug-ins, but the communication between them
+is limited to invoking the ‘main’ function of the plug-in
+with some options and waiting for it to return, that is a borderline
+case.</p>
+
+<p>Using shared memory to communicate with complex data structures is
+pretty much equivalent to dynamic linking.</p></dd>
+
+
<dt id="GPLAndPlugins">If I write a plug-in to use with a GPL-covered
program, what requirements does that impose on the licenses I can
use for distributing my plug-in?
<span class="anchor-reference-id">(<a href="#GPLAndPlugins"
>#GPLAndPlugins</a>)</span></dt>
<dd><p>
-It depends on how the program invokes its plug-ins. If the program
-uses fork and exec to invoke plug-ins, then the plug-ins are separate
-programs, so the license for the main program makes no requirements
-for them.</p>
-
-<p>If the program dynamically links plug-ins, and they make function
-calls to each other and share data structures, we believe they form a
-single program, which must be treated as an extension of both the main
-program and the plug-ins. This means you must license the plug-in
-under the GPL or a GPL-compatible free software license and distribute
-it with source code in a GPL-compliant way.</p>
-
-<p>If the program dynamically links plug-ins, but the communication
-between them is limited to invoking the ‘main’ function of
-the plug-in with some options and waiting for it to return, that is a
-borderline case.</p></dd>
+Please see this question <a href="#GPLPlugins">for determining when
+plug-ins and a main program are considered a single combined program
+and when they are considered separate works</a>.</p>
+
+<p> If the main program and the plugins are a single combined program
then this means
+you must license the plug-in under the GPL or a GPL-compatible free
+software license and distribute it with source code in a GPL-compliant
+way. A main program that is separate from its plug-ins makes no
+requirements for the plug-ins. </p></dd>
<dt id="GPLPluginsInNF">Can I apply the
- GPL when writing a plug-in for a non-free program?
+ GPL when writing a plug-in for a nonfree program?
<span class="anchor-reference-id">(<a href="#GPLPluginsInNF"
>#GPLPluginsInNF</a>)</span></dt>
<dd><p>
-If the program uses fork and exec to invoke plug-ins, then the
-plug-ins are separate programs, so the license for the main program
-makes no requirements for them. So you can use the GPL for a plug-in,
-and there are no special requirements.</p>
-
-<p>If the program dynamically links plug-ins, and they make function
-calls to each other and share data structures, we believe they form a
-single program, which must be treated as an extension of both the main
-program and the plug-ins. This means that combination of the
-GPL-covered plug-in with the non-free main program would violate the
-GPL. However, you can resolve that legal problem by adding an
-exception to your plug-in's license, giving permission to link it with
-the non-free main program.</p>
+ Please see this question <a href="#GPLPlugins">for determining when
+plug-ins and a main program are considered a single combined program
+and when they are considered separate programs</a>.</p>
+<p> If they form a
+single combined program this means that combination of the GPL-covered
+plug-in with the nonfree main program would violate the GPL. However,
+you can resolve that legal problem by adding an exception to your
+plug-in's license, giving permission to link it with the nonfree main
+program.</p>
<p>See also the question <a href="#FSWithNFLibs">I am
-writing free software that uses a non-free
library.</a></p></dd>
+writing free software that uses a nonfree
library.</a></p></dd>
-<dt id="NFUseGPLPlugins">Can I release a non-free program
+<dt id="NFUseGPLPlugins">Can I release a nonfree program
that's designed to load a GPL-covered plug-in?
<span class="anchor-reference-id">(<a href="#NFUseGPLPlugins"
>#NFUseGPLPlugins</a>)</span></dt>
-<dd><p>
-It depends on how the program invokes its plug-ins. For instance, if
-the program uses <em>only</em> simple fork and exec to invoke and
-communicate with plug-ins, then the plug-ins are separate programs, so
-the license of the plug-in makes no requirements about the main
-program.</p>
-<p>If the program dynamically links plug-ins, and they make function
-calls to each other and share data structures, we believe they form a
-single program, which must be treated as an extension of both the main
-program and the plug-ins. In order to use the GPL-covered plug-ins,
-the main program must be released under the GPL or a GPL-compatible
-free software license, and that the terms of the GPL must be followed
-when the main program is distributed for use with these plug-ins.</p>
-
-<p>If the program dynamically links plug-ins, but the communication
-between them is limited to invoking the ‘main’ function of
-the plug-in with some options and waiting for it to return, that is a
-borderline case.</p>
+<dd><p>
+ Please see this question <a href="#GPLPlugins">for determining when
+plug-ins and a main program are considered a single combined program
+and when they are considered separate programs</a>.</p>
+<p>
+If they form a single combined program then the
+main program must be released under the GPL or a GPL-compatible free
+software license, and the terms of the GPL must be followed when
+the main program is distributed for use with these plug-ins.</p>
-<p>Using shared memory to communicate with complex data structures
-is pretty much equivalent to dynamic linking.</p>
+<p>However, if they are separate works then the license of the plug-in
+makes no requirements about the main program.</p>
<p>See also the question <a href="#FSWithNFLibs">I am
-writing free software that uses a non-free
library.</a></p></dd>
+writing free software that uses a nonfree
library.</a></p></dd>
<dt id="LinkingWithGPL">You have a GPL'ed program that I'd like
@@ -1955,7 +1972,7 @@
An “aggregate” consists of a number of separate programs,
distributed together on the same CD-ROM or other media. The GPL permits
you to create and distribute an aggregate, even when the licenses of the
-other software are non-free or GPL-incompatible. The only condition is
+other software are nonfree or GPL-incompatible. The only condition is
that you cannot release the aggregate under a license that prohibits users
from exercising rights that each program's individual license would
grant them.</p>
@@ -1991,8 +2008,8 @@
href="/licenses/why-assign.html">best position to enforce the GPL</a>
in court against violators, we should keep the copyright status of the
program as simple as possible. We do this by asking each contributor
-to either assign the copyright on <span class="removed"><del><strong>his
contribution</strong></del></span> <span
class="inserted"><ins><em>contributions</em></ins></span> to the FSF, or
-disclaim copyright on <span class="removed"><del><strong>it and thus put it in
the public domain.</p></strong></del></span> <span
class="inserted"><ins><em>contributions.</p></em></ins></span>
+to either assign the copyright on contributions to the FSF, or
+disclaim copyright on contributions.</p>
<p>We also ask individual contributors to get copyright disclaimers from
their employers (if any) so that we can be sure those employers won't
@@ -2107,8 +2124,8 @@
You cannot incorporate GPL-covered software in a proprietary system.
The goal of the GPL is to grant everyone the freedom to copy,
redistribute, understand, and modify a program. If you could
-incorporate GPL-covered software into a non-free system, it would have
-the effect of making the GPL-covered software non-free too.</p>
+incorporate GPL-covered software into a nonfree system, it would have
+the effect of making the GPL-covered software nonfree too.</p>
<p>A system incorporating a GPL-covered program is an extended version of
that program. The GPL says that any extended version of the program
@@ -2119,7 +2136,7 @@
<p>However, in many cases you can distribute the GPL-covered software
alongside your proprietary system. To do this validly, you must make
-sure that the free and non-free programs communicate at arms length,
+sure that the free and nonfree programs communicate at arms length,
that they are not combined in a way that would make them
effectively a single program.</p>
@@ -2417,15 +2434,14 @@
<dt id="StolenCopy">If someone steals
a CD containing a version of a GPL-covered program, does the GPL
- give <span class="removed"><del><strong>him</strong></del></span> <span
class="inserted"><ins><em>the theif</em></ins></span> the right to redistribute
that version?
+ give the thief the right to redistribute that version?
<span class="anchor-reference-id">(<a href="#StolenCopy"
>#StolenCopy</a>)</span></dt>
<dd><p>
If the version has been released elsewhere, then the thief
probably does have the right to make copies and redistribute them
-under the GPL, but if <span
class="removed"><del><strong>he</strong></del></span> <span
class="inserted"><ins><em>the theif</em></ins></span> is imprisoned for
stealing the <span class="removed"><del><strong>CD he</strong></del></span>
<span class="inserted"><ins><em>CD,
-they</em></ins></span> may have to wait until
-<span class="removed"><del><strong>his</strong></del></span> <span
class="inserted"><ins><em>their</em></ins></span> release before doing
so.</p>
+under the GPL, but if the thief is imprisoned for stealing the CD,
+they may have to wait until their release before doing so.</p>
<p>If the version in question is unpublished and considered by a company
to be its trade secret, then publishing it may be a violation of trade
@@ -2672,7 +2688,7 @@
<dt id="NonFreeTools">Can I release
- a program under the GPL which I developed using non-free tools?
+ a program under the GPL which I developed using nonfree tools?
<span class="anchor-reference-id">(<a href="#NonFreeTools"
>#NonFreeTools</a>)</span></dt>
<dd><p>
@@ -2680,7 +2696,7 @@
study it, or record it, usually makes no difference for issues
concerning the licensing of that source code.</p>
-<p>However, if you link non-free libraries with the source code, that
+<p>However, if you link nonfree libraries with the source code, that
would be an issue you need to deal with. It does not preclude
releasing the source code under the GPL, but if the libraries don't
fit under the “system library” exception, you should affix
@@ -2824,18 +2840,18 @@
</p></dd>
-<dt id="PortProgramToGL">If I port my program to GNU/Linux,
+<dt id="PortProgramToGPL">If I port my program to GNU/Linux,
does that mean I have to release it as free software under the GPL
or some other Free Software license?
- <span class="anchor-reference-id">(<a href="#PortProgramToGL"
- >#PortProgramToGL</a>)</span></dt>
+ <span class="anchor-reference-id">(<a href="#PortProgramToGPL"
+ >#PortProgramToGPL</a>)</span></dt>
<dd><p>
In general, the answer is no—this is not a legal requirement. In
specific, the answer depends on which libraries you want to use and what
their licenses are. Most system libraries either use the <a
href="/licenses/lgpl.html">GNU Lesser GPL</a>, or use the GNU GPL
plus an
exception permitting linking the library with anything. These libraries
-can be used in non-free programs; but in the case of the Lesser GPL, it
+can be used in nonfree programs; but in the case of the Lesser GPL, it
does have some requirements you must follow.</p>
<p>Some libraries are released under the GNU GPL alone; you must use a
@@ -3075,7 +3091,7 @@
kind of DRM technology you like. However, if you do this, section 3
says that the system will not count as an effective technological
“protection” measure, which means that if someone breaks the
-DRM, <span class="removed"><del><strong>he</strong></del></span> <span
class="inserted"><ins><em>she</em></ins></span> will be free to distribute
<span class="removed"><del><strong>his</strong></del></span> <span
class="inserted"><ins><em>her</em></ins></span> software too, unhindered by the
DMCA
+DRM, she will be free to distribute her software too, unhindered by the DMCA
and similar laws.</p>
<p>As usual, the GNU GPL does not restrict what people do in software,
@@ -3111,9 +3127,9 @@
checked the software for a valid cryptographic signature before it
would function. In that specific case, you would be required to
provide anyone who owned the device, on demand, with the key to sign
-and install modified software on <span
class="removed"><del><strong>his</strong></del></span> <span
class="inserted"><ins><em>the</em></ins></span> device so that it will run. If
+and install modified software on the device so that it will run. If
each instance of the device uses a different key, then you need only
-give each purchaser <span
class="removed"><del><strong>the</strong></del></span> <span
class="inserted"><ins><em>a</em></ins></span> key for <span
class="removed"><del><strong>his</strong></del></span> <span
class="inserted"><ins><em>that</em></ins></span> instance.</p></dd>
+give each purchaser a key for that instance.</p></dd>
<dt id="v3VotingMachine">Does GPLv3 require that voters be able to
@@ -3209,16 +3225,38 @@
<span class="anchor-reference-id">(<a href="#v2v3Compatibility"
>#v2v3Compatibility</a>)</span></dt>
<dd><p>
-No. Some of the requirements in GPLv3, such as the requirement to
-provide Installation Information, do not exist in GPLv2. As a result,
-the licenses are not compatible: if you tried to combine code released
-under both these licenses, you would violate section 6 of GPLv2.</p>
+No. Many requirements have changed from GPLv2 to GPLv3, which
+means that the precise requirement of GPLv2 is not present in GPLv3,
+and vice versa. For instance, the Termination conditions of GPLv3 are
+considerably more permissive than those of GPLv2, and thus different
+from the Termination conditions of GPLv2.</p>
+
+<p>
+Due to these differences, the two licenses are not compatible: if you
+tried to combine code released under GPLv2 with code under GPLv3, you
+would violate section 6 of GPLv2.</p>
<p>However, if code is released under GPL “version 2 or
later,” that is compatible with GPLv3 because GPLv3 is one of the
options it permits.</p></dd>
+<dt id="InstInfo">Does GPLv2 have a requirement about delivering
installation
+information?
+ <span class="anchor-reference-id">(<a href="#InstInfo"
+ >#InstInfo</a>)</span></dt>
+
+<dd><p>
+GPLv3 explicitly requires redistribution to include the full necessary
+“Installation Information.” GPLv2 doesn't use that term,
+but it does require redistribution to include <q>scripts used to
+control compilation and installation of the executable</q> with the
+complete and corresponding source code. This covers part, but not
+all, of what GPLv3 calls “Installation Information.”
+Thus, GPLv3's requirement about installation information is
+stronger.</p></dd>
+
+
<dt id="Cure">What does it mean to “cure” a violation of
GPLv3?
<span class="anchor-reference-id">(<a href="#Cure"
>#Cure</a>)</span></dt>
@@ -3251,7 +3289,7 @@
<dt id="v3CoworkerConveying">If I give a copy of a GPLv3-covered
program to a coworker at my company, have I “conveyed” the
- copy to <span class="removed"><del><strong>him?</strong></del></span>
<span class="inserted"><ins><em>that coworker?</em></ins></span>
+ copy to that coworker?
<span class="anchor-reference-id">(<a href="#v3CoworkerConveying"
>#v3CoworkerConveying</a>)</span></dt>
<dd><p>
@@ -3314,7 +3352,13 @@
No, because those two goals contradict each other. The GNU GPL is
designed specifically to prevent the addition of further restrictions.
GPLv3 allows a very limited set of them, in section 7, but any other
-added restriction can be removed by the user.</p></dd>
+added restriction can be removed by the <span
class="removed"><del><strong>user.</p></dd></strong></del></span>
<span class="inserted"><ins><em>user.</p>
+
+<p>More generally, a license that limits who can use a program, or for
+what,
+is <a href="/philosophy/programs-must-not-limit-freedom-to-run.html">not
+a free software license</a>.</p>
+</dd></em></ins></span>
<dt id="ConveyVsDistribute">Is “convey” in GPLv3 the same
@@ -3563,30 +3607,14 @@
the servers it interacts with?
<span class="anchor-reference-id">(<a href="#AGPLv3ServerAsUser"
>#AGPLv3ServerAsUser</a>)</span></dt>
-<span class="removed"><del><strong><dd><p>
-This should not be required in any typical server-client
-relationship. AGPLv3</strong></del></span>
-<span class="inserted"><ins><em><dd>
- <p>AGPLv3</em></ins></span> requires a program to offer source code
to “all
-users interacting with it remotely through a computer network.” <span
class="removed"><del><strong>In most server-client architectures, it simply
-wouldn't be reasonable to argue that</strong></del></span>
-<span class="inserted"><ins><em>It doesn't matter if you
call</em></ins></span> the <span class="removed"><del><strong>server operator
is</strong></del></span> <span
class="inserted"><ins><em>program</em></ins></span> a
-<span class="removed"><del><strong>“user” interacting
with</strong></del></span> <span class="inserted"><ins><em>“client”
-or a “server,”</em></ins></span> the <span
class="removed"><del><strong>client in any meaningful
-sense.</p>
-
-<p>Consider HTTP as an example. All HTTP clients expect servers to
-provide certain functionality: they should send specified
responses</strong></del></span>
-<span class="inserted"><ins><em>question you need</em></ins></span> to
-<span class="removed"><del><strong>well-formed requests. The
reverse</strong></del></span> <span
class="inserted"><ins><em>ask</em></ins></span> is <span
class="inserted"><ins><em>whether or</em></ins></span> not <span
class="removed"><del><strong>true: servers cannot assume
-that the client will do anything in particular with the data they
-send. The client may be a web browser, an RSS reader,</strong></del></span>
<span class="inserted"><ins><em>there is</em></ins></span> a <span
class="removed"><del><strong>spider,</strong></del></span> <span
class="inserted"><ins><em>reasonable
-expectation that</em></ins></span> a
-<span class="removed"><del><strong>network monitoring tool, or some
special-purpose program. The server
-can make absolutely no assumptions about what the client</strong></del></span>
<span class="inserted"><ins><em>person</em></ins></span> will
-<span class="removed"><del><strong>do—so there's no meaningful way for
the server operator to</strong></del></span> be
-<span class="removed"><del><strong>considered</strong></del></span> <span
class="inserted"><ins><em>interacting with the program
-remotely over</em></ins></span> a <span class="removed"><del><strong>user of
that software.</p></dd></strong></del></span> <span
class="inserted"><ins><em>network. </p></dd></em></ins></span>
+<dd>
+ <p>AGPLv3 requires a program to offer source code to “all
+users interacting with it remotely through a computer network.”
+It doesn't matter if you call the program a “client”
+or a “server,” the
+question you need to ask is whether or not there is a reasonable
+expectation that a person will be interacting with the program
+remotely over a network. </p></dd>
<dt id="AGPLProxy">For software that runs a proxy server licensed
under the AGPL, how can I provide an offer of source to users
@@ -3878,7 +3906,7 @@
Information document, www.gnu.org/prep/maintain. -->
-<p>Copyright © 2014, 2015, 2016 Free Software Foundation,
Inc.</p>
+<p>Copyright © 2014, 2015, 2016, 2017 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
@@ -3888,7 +3916,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2016/07/25 15:28:11 $
+$Date: 2017/12/15 18:59:40 $
<!-- timestamp end -->
</p>
</div>
Index: distros/po/distros.it-diff.html
===================================================================
RCS file: distros/po/distros.it-diff.html
diff -N distros/po/distros.it-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ distros/po/distros.it-diff.html 15 Dec 2017 18:59:39 -0000 1.1
@@ -0,0 +1,194 @@
+<!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>/distros/distros.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.77 -->
+<title>GNU/Linux Distros
+- GNU Project - Free Software Foundation</title>
+<link rel="alternate" title="Free GNU/Linux distributions"
+ href="http://www.gnu.org/distros/distros.rss";
+ type="application/rss+xml" />
+<!--#include virtual="/distros/po/distros.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>GNU/Linux Distros</h2>
+
+<p>
+Free <span class="removed"><del><strong>GNU/Linux system</strong></del></span>
distributions (or “distros”) <span class="inserted"><ins><em>of
+the <a href="/gnu/linux-and-gnu.html">GNU/Linux
system</a></em></ins></span> only
+include and only propose free software. They reject non-free
+applications, non-free programming platforms, non-free drivers,
+non-free firmware “blobs”, and any other non-free software
+and documentation. If they discover that by mistake some had been
+included, they remove it.
+</p>
+
+<h3 id="freeDistros">Free GNU/Linux Distros</h3>
+<p>
+We recommend that you use a free GNU/Linux system distribution, one that does
+not include proprietary software at all. That way you can be sure that you are
+not installing any non-free programs. Here is our list of such distros:<br
/>
+<a href="/distros/free-distros.html">
+Free GNU/Linux distributions</a>.</p>
+
+<p>
+All of these existing distros could use more development help. Thus,
+if you want to make an effective contribution to free GNU/Linux
+distributions, we suggest that you join the development of an existing
+free distro rather that starting a new free distro.
+</p>
+
+<h3 id="freeNonDistros">Free Non-GNU Distros</h3>
+<p>
+These system distributions are free but quite different from GNU.
+Using them is not similar to using GNU/Linux. However, they satisfy
+the same ethical criteria that we apply to GNU/Linux distros.<br />
+<a href="/distros/free-non-gnu-distros.html">
+Free Non-GNU distributions</a>.</p>
+
+<p>
+All of these existing distros could use more development help. Thus,
+if you want to make an effective contribution in this area, we suggest
+that you join the development of an existing free distro rather that
+starting a new free distro.
+</p>
+
+<h3 id="distroGuidelines">Free Distro Guidelines</h3>
+<p>
+Here is the list of problems that can prevent a distro from being
+considered entirely free:<br />
+<a href="/distros/free-system-distribution-guidelines.html">
+Guidelines for free system distributions</a>.</p>
+
+<h3 id="otherDistros">Common Distros</h3>
+<p>
+Many common and well-known GNU/Linux software distributions don't meet
+our guidelines. You can read about their problems here:<br />
+<a href="/distros/common-distros.html">
+Why we can't endorse many well-known GNU/Linux distros</a>.</p>
+
+<p>
+We appeal to the developers of these distros to remove the non-free parts and
+thus make them entirely free software.
+</p>
+
+<h3 id="optionallyFree">Optionally Free Is Not Enough</h3>
+<p>
+Some GNU/Linux distributions allow the user the option of installing only free
software. You can read:<br />
+<a href="/distros/optionally-free-not-enough.html">
+Why optionally free is not enough.</a></p>
+
+<h3 id="whyImportant">Why Is This Important?</h3>
+<p>
+When a GNU/Linux distro includes nonfree software, it causes two kinds
+of problems:</p>
+
+<ul>
+<li>If you install it, you may install and use nonfree
software.</li>
+<li>It gives people the wrong idea of what the goal is.</li>
+</ul>
+
+<p>
+The first problem is a direct problem: it affects users of the
+distro, if they install the nonfree software. However, the second
+problem is the more important one, because it affects the community as
+a whole.
+</p>
+
+<p>
+The developers of nonfree distros don't say, “We apologize for
+the presence of nonfree components in our distribution. We don't know
+what possessed us to include them. We hope that next release we will
+keep our minds on freedom.” If they did, they would have less
+of a bad influence.
+</p>
+
+<p>
+Instead, they generally present the nonfree software in their systems
+as a positive feature; they say that their goal is “the best
+possible user experience”, or something like that, rather than
+freedom. In other words, they lead people to place convenience above
+freedom — working directly against our campaign to make freedom
+the primary goal.
+</p>
+
+<p>
+The fact that these distros don't deliver freedom is why we don't
+endorse them. That they teach people not to value freedom is why
+we are strongly concerned about this issue.
+</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 & 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>
+</div>
+
+<!-- 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 <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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 © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</em></ins></span> Free Software
Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/12/15 18:59:39 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: distros/po/distros.ja-diff.html
===================================================================
RCS file: distros/po/distros.ja-diff.html
diff -N distros/po/distros.ja-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ distros/po/distros.ja-diff.html 15 Dec 2017 18:59:39 -0000 1.1
@@ -0,0 +1,194 @@
+<!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>/distros/distros.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.77 -->
+<title>GNU/Linux Distros
+- GNU Project - Free Software Foundation</title>
+<link rel="alternate" title="Free GNU/Linux distributions"
+ href="http://www.gnu.org/distros/distros.rss";
+ type="application/rss+xml" />
+<!--#include virtual="/distros/po/distros.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>GNU/Linux Distros</h2>
+
+<p>
+Free <span class="removed"><del><strong>GNU/Linux system</strong></del></span>
distributions (or “distros”) <span class="inserted"><ins><em>of
+the <a href="/gnu/linux-and-gnu.html">GNU/Linux
system</a></em></ins></span> only
+include and only propose free software. They reject non-free
+applications, non-free programming platforms, non-free drivers,
+non-free firmware “blobs”, and any other non-free software
+and documentation. If they discover that by mistake some had been
+included, they remove it.
+</p>
+
+<h3 id="freeDistros">Free GNU/Linux Distros</h3>
+<p>
+We recommend that you use a free GNU/Linux system distribution, one that does
+not include proprietary software at all. That way you can be sure that you are
+not installing any non-free programs. Here is our list of such distros:<br
/>
+<a href="/distros/free-distros.html">
+Free GNU/Linux distributions</a>.</p>
+
+<p>
+All of these existing distros could use more development help. Thus,
+if you want to make an effective contribution to free GNU/Linux
+distributions, we suggest that you join the development of an existing
+free distro rather that starting a new free distro.
+</p>
+
+<h3 id="freeNonDistros">Free Non-GNU Distros</h3>
+<p>
+These system distributions are free but quite different from GNU.
+Using them is not similar to using GNU/Linux. However, they satisfy
+the same ethical criteria that we apply to GNU/Linux distros.<br />
+<a href="/distros/free-non-gnu-distros.html">
+Free Non-GNU distributions</a>.</p>
+
+<p>
+All of these existing distros could use more development help. Thus,
+if you want to make an effective contribution in this area, we suggest
+that you join the development of an existing free distro rather that
+starting a new free distro.
+</p>
+
+<h3 id="distroGuidelines">Free Distro Guidelines</h3>
+<p>
+Here is the list of problems that can prevent a distro from being
+considered entirely free:<br />
+<a href="/distros/free-system-distribution-guidelines.html">
+Guidelines for free system distributions</a>.</p>
+
+<h3 id="otherDistros">Common Distros</h3>
+<p>
+Many common and well-known GNU/Linux software distributions don't meet
+our guidelines. You can read about their problems here:<br />
+<a href="/distros/common-distros.html">
+Why we can't endorse many well-known GNU/Linux distros</a>.</p>
+
+<p>
+We appeal to the developers of these distros to remove the non-free parts and
+thus make them entirely free software.
+</p>
+
+<h3 id="optionallyFree">Optionally Free Is Not Enough</h3>
+<p>
+Some GNU/Linux distributions allow the user the option of installing only free
software. You can read:<br />
+<a href="/distros/optionally-free-not-enough.html">
+Why optionally free is not enough.</a></p>
+
+<h3 id="whyImportant">Why Is This Important?</h3>
+<p>
+When a GNU/Linux distro includes nonfree software, it causes two kinds
+of problems:</p>
+
+<ul>
+<li>If you install it, you may install and use nonfree
software.</li>
+<li>It gives people the wrong idea of what the goal is.</li>
+</ul>
+
+<p>
+The first problem is a direct problem: it affects users of the
+distro, if they install the nonfree software. However, the second
+problem is the more important one, because it affects the community as
+a whole.
+</p>
+
+<p>
+The developers of nonfree distros don't say, “We apologize for
+the presence of nonfree components in our distribution. We don't know
+what possessed us to include them. We hope that next release we will
+keep our minds on freedom.” If they did, they would have less
+of a bad influence.
+</p>
+
+<p>
+Instead, they generally present the nonfree software in their systems
+as a positive feature; they say that their goal is “the best
+possible user experience”, or something like that, rather than
+freedom. In other words, they lead people to place convenience above
+freedom — working directly against our campaign to make freedom
+the primary goal.
+</p>
+
+<p>
+The fact that these distros don't deliver freedom is why we don't
+endorse them. That they teach people not to value freedom is why
+we are strongly concerned about this issue.
+</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 & 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>
+</div>
+
+<!-- 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 <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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 © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</em></ins></span> Free Software
Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/12/15 18:59:39 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: distros/po/distros.pl-diff.html
===================================================================
RCS file: distros/po/distros.pl-diff.html
diff -N distros/po/distros.pl-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ distros/po/distros.pl-diff.html 15 Dec 2017 18:59:39 -0000 1.1
@@ -0,0 +1,194 @@
+<!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>/distros/distros.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.77 -->
+<title>GNU/Linux Distros
+- GNU Project - Free Software Foundation</title>
+<link rel="alternate" title="Free GNU/Linux distributions"
+ href="http://www.gnu.org/distros/distros.rss";
+ type="application/rss+xml" />
+<!--#include virtual="/distros/po/distros.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>GNU/Linux Distros</h2>
+
+<p>
+Free <span class="removed"><del><strong>GNU/Linux system</strong></del></span>
distributions (or “distros”) <span class="inserted"><ins><em>of
+the <a href="/gnu/linux-and-gnu.html">GNU/Linux
system</a></em></ins></span> only
+include and only propose free software. They reject non-free
+applications, non-free programming platforms, non-free drivers,
+non-free firmware “blobs”, and any other non-free software
+and documentation. If they discover that by mistake some had been
+included, they remove it.
+</p>
+
+<h3 id="freeDistros">Free GNU/Linux Distros</h3>
+<p>
+We recommend that you use a free GNU/Linux system distribution, one that does
+not include proprietary software at all. That way you can be sure that you are
+not installing any non-free programs. Here is our list of such distros:<br
/>
+<a href="/distros/free-distros.html">
+Free GNU/Linux distributions</a>.</p>
+
+<p>
+All of these existing distros could use more development help. Thus,
+if you want to make an effective contribution to free GNU/Linux
+distributions, we suggest that you join the development of an existing
+free distro rather that starting a new free distro.
+</p>
+
+<h3 id="freeNonDistros">Free Non-GNU Distros</h3>
+<p>
+These system distributions are free but quite different from GNU.
+Using them is not similar to using GNU/Linux. However, they satisfy
+the same ethical criteria that we apply to GNU/Linux distros.<br />
+<a href="/distros/free-non-gnu-distros.html">
+Free Non-GNU distributions</a>.</p>
+
+<p>
+All of these existing distros could use more development help. Thus,
+if you want to make an effective contribution in this area, we suggest
+that you join the development of an existing free distro rather that
+starting a new free distro.
+</p>
+
+<h3 id="distroGuidelines">Free Distro Guidelines</h3>
+<p>
+Here is the list of problems that can prevent a distro from being
+considered entirely free:<br />
+<a href="/distros/free-system-distribution-guidelines.html">
+Guidelines for free system distributions</a>.</p>
+
+<h3 id="otherDistros">Common Distros</h3>
+<p>
+Many common and well-known GNU/Linux software distributions don't meet
+our guidelines. You can read about their problems here:<br />
+<a href="/distros/common-distros.html">
+Why we can't endorse many well-known GNU/Linux distros</a>.</p>
+
+<p>
+We appeal to the developers of these distros to remove the non-free parts and
+thus make them entirely free software.
+</p>
+
+<h3 id="optionallyFree">Optionally Free Is Not Enough</h3>
+<p>
+Some GNU/Linux distributions allow the user the option of installing only free
software. You can read:<br />
+<a href="/distros/optionally-free-not-enough.html">
+Why optionally free is not enough.</a></p>
+
+<h3 id="whyImportant">Why Is This Important?</h3>
+<p>
+When a GNU/Linux distro includes nonfree software, it causes two kinds
+of problems:</p>
+
+<ul>
+<li>If you install it, you may install and use nonfree
software.</li>
+<li>It gives people the wrong idea of what the goal is.</li>
+</ul>
+
+<p>
+The first problem is a direct problem: it affects users of the
+distro, if they install the nonfree software. However, the second
+problem is the more important one, because it affects the community as
+a whole.
+</p>
+
+<p>
+The developers of nonfree distros don't say, “We apologize for
+the presence of nonfree components in our distribution. We don't know
+what possessed us to include them. We hope that next release we will
+keep our minds on freedom.” If they did, they would have less
+of a bad influence.
+</p>
+
+<p>
+Instead, they generally present the nonfree software in their systems
+as a positive feature; they say that their goal is “the best
+possible user experience”, or something like that, rather than
+freedom. In other words, they lead people to place convenience above
+freedom — working directly against our campaign to make freedom
+the primary goal.
+</p>
+
+<p>
+The fact that these distros don't deliver freedom is why we don't
+endorse them. That they teach people not to value freedom is why
+we are strongly concerned about this issue.
+</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 & 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>
+</div>
+
+<!-- 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 <span class="removed"><del><strong>3.0
US.</strong></del></span> <span
class="inserted"><ins><em>4.0.</em></ins></span> 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 © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</em></ins></span> Free Software
Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+<span
class="removed"><del><strong>href="http://creativecommons.org/licenses/by-nd/3.0/us/">Creative</strong></del></span>
+<span
class="inserted"><ins><em>href="http://creativecommons.org/licenses/by-nd/4.0/">Creative</em></ins></span>
+Commons <span class="removed"><del><strong>Attribution-NoDerivs 3.0 United
States</strong></del></span> <span
class="inserted"><ins><em>Attribution-NoDerivatives 4.0
International</em></ins></span> License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2017/12/15 18:59:39 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: distros/po/free-system-distribution-guidelines.it-diff.html
===================================================================
RCS file: distros/po/free-system-distribution-guidelines.it-diff.html
diff -N distros/po/free-system-distribution-guidelines.it-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ distros/po/free-system-distribution-guidelines.it-diff.html 15 Dec 2017
18:59:39 -0000 1.1
@@ -0,0 +1,376 @@
+<!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>/distros/free-system-distribution-guidelines.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.77 -->
+<title>Free System Distribution Guidelines (GNU FSDG) - GNU Project -
Free Software Foundation</title>
+<link rel="alternate" title="Free GNU/Linux distributions"
+ href="http://www.gnu.org/distros/distros.rss";
+ type="application/rss+xml" />
+<!--#include
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Free System Distribution Guidelines (GNU FSDG)</h2>
+<!--#include virtual="/licenses/fsf-licensing.html" -->
+
+<h3 id="introduction">Introduction</h3>
+
+<p>The purpose of these guidelines is to explain what it means for an
+installable system distribution (such as a <span
class="removed"><del><strong>GNU/Linux</strong></del></span> <span
class="inserted"><ins><em><a
href="/gnu/linux-and-gnu.html">GNU/Linux</a></em></ins></span>
distribution) to
+qualify as <a href="/philosophy/free-sw.html">free</a> (libre), and
+help distribution developers make their distributions qualify.</p>
+
+<p>These guidelines are not complete. We have mentioned the issues we
+are aware of now, but we're sure there are more. We will add them
+when we come across them.</p>
+
+<p>We would like to thank the Fedora Project for their help in focusing
+these policies, and allowing us to use their own distribution license
+guidelines as a basis for this document.</p>
+
+<h3 id="complete-distros">Complete Distros</h3>
+
+<p>Our list of distributions is a guide for systems you can install in
+a computer. Therefore, it only includes distributions that are
+complete in themselves and ready to use. If a distribution is
+incomplete — if it requires further development, or presupposes
+installing other software as well — then it is not listed here,
+even if it is free software.</p>
+
+<p>An exception to this requirement and to the self-hosting
+requirement above is for <em>small system distributions</em>, which
+are distros designed for devices with limited resources, like a
+wireless router for example. Free small system distributions do not
+need to be self-hosting or complete, because it is impractical to do
+development on such a system, but it must be developable and buildable
+on top of a free complete system distribution from our list of
+distributions, perhaps with the aid of free tools distributed
+alongside the small system distribution itself.</p>
+
+<h3 id="license-rules">License Rules</h3>
+
+<p>“Information for practical use”
+includes software, documentation, fonts, and other data that has
+direct functional applications. It does not include artistic works
+that have an aesthetic (rather than functional) purpose, or statements
+of opinion or judgment.</p>
+
+<p>All information for practical use in a free distribution must be
+available in source form. (“Source” means the form of the
+information that is preferred for making changes to it.)</p>
+
+<p>The information, and the source, must be provided under an
+appropriate <a href="/philosophy/free-sw.html">free license</a>.
We
+evaluate specific licenses and list our determinations
+in <a class="reference" href="/licenses/license-list.html">our license
+list</a>, with separate sections for licenses that are suitable for
+software, documentation, fonts, and other useful works. If such a
+work is released under a disjunction of licenses, the work is free as
+long as at least one of its licenses is free; the system developers
+should follow the terms of the applicable free license(s) when they
+distribute and/or modify it.</p>
+
+<p>A free system distribution must not steer users towards obtaining
+any nonfree information for practical use, or encourage them to do so.
+The system should have no repositories for nonfree software and no
+specific recipes for installation of particular nonfree programs. Nor
+should the distribution refer to third-party repositories that are not
+committed to only including free software; even if they only have free
+software today, that may not be true tomorrow. Programs in the system
+should not suggest installing nonfree plugins, documentation, and so
+on.</p>
+
+<span class="inserted"><ins><em><p>For instance, a free system
distribution must not contain browsers
+that implement EME, the browser functionality designed to load DRM
+modules.</p></em></ins></span>
+
+<p>A free system distribution should be self-hosting. This means that
+you must be able to develop and build the system with tools that the
+system provides you. As a result, a free system distribution cannot
+include free software that can only be built by using nonfree
+software.</p>
+
+<p>There's a lot of code in most free system distributions today; the
+amount of effort it would take to audit it all directly is impractical
+for most teams. In the past, some nonfree code has accidentally been
+included in free system distributions. We don't de-list distributions
+because of this; instead, we only ask that a distribution's developers
+make a good faith effort to avoid including nonfree software, and
+commit themselves to removing such programs if any are discovered.</p>
+
+<p>Certain kinds of license situations merit special attention for people
+creating or considering free software distributions; those are
+discussed in the sections below.</p>
+
+<h3 id="nonfree-firmware">Nonfree Firmware</h3>
+
+<p>Some applications and drivers require firmware to function, and
+sometimes that firmware is distributed only in object code form, under
+a nonfree license. We call these firmware programs
+“blobs.” On most GNU/Linux systems, you'll typically find
+these accompanying some drivers in the kernel Linux. Such firmware
+should be removed from a free system distribution.</p>
+
+<p>Blobs can take many forms. Sometimes, they will be provided in
+separate files. Other times, they may be incorporated into the source
+of the driver itself—for example, it could be encoded as a large
+array of numbers. But no matter how it's encoded, any nonfree
+firmware needs to be removed from a free system.</p>
+
+<p>(To be clear, not every array of numbers in a driver is firmware.
+It's important to understand the purpose of the data before deciding
+whether or not it's appropriate for a free system.)</p>
+
+<p>Brian Brazil, Jeff Moe, and Alexandre Oliva have developed a series
+of <a class="reference"
+href="http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/">scripts
+to remove nonfree firmware</a> from a stock version of the Linux kernel.
+You may find them helpful if you would like to develop your own free
+GNU/Linux distribution—although we recommend joining development
+of an existing free distro rather than fragmenting effort by starting a
+new one. The complete source for a blob-free version of the Linux
+kernel is also available; you can learn more about this project from the
+<a class="reference" href="http://directory.fsf.org/project/linux/">Free
+Software Directory</a>.</p>
+
+<h3 id="non-functional-data">Non-functional Data</h3>
+
+<p>Data that isn't functional, that doesn't do a practical job, is
+more of an adornment to the system's software than a part of it.
+Thus, we don't insist on the free license criteria for non-functional
+data. It can be included in a free system distribution as long as its
+license gives you permission to copy and redistribute, both for
+commercial and non-commercial purposes. For example, some game
+engines released under the GNU GPL have accompanying game
+information—a fictional world map, game graphics, and so
+on—released under such a verbatim-distribution license. This
+kind of data can be part of a free system distribution, even though
+its license does not qualify as free, because it is non-functional.</p>
+
+<h3 id="trademarks">Trademarks</h3>
+
+<p>Trademarks are associated with some software. For example, the
+name of a program may be trademarked, or its interface may display a
+trademarked logo. Often, the use of these marks will be controlled
+in some way; in particular, developers are commonly asked to remove
+references to the trademark from the software when they modify
+it.</p>
+
+<p>In extreme cases, these restrictions may effectively render the
+program nonfree. It is unfair for someone to ask you to remove a
+trademark from modified code if that trademark is scattered all
+throughout the original source. As long as the practical
+requirements are reasonable, however, free system distributions may
+include these programs, either with or without the trademarks.</p>
+
+<p>Similarly, the distribution itself may hold particular trademarks.
+It is not a problem if modification requires removal of these
+trademarks, as long as they can readily be removed without losing
+functionality.</p>
+
+<p>However, it is unacceptable to use trademarks to restrict verbatim
+copying and redistribution of the whole distribution, or any part.</p>
+
+<h3 id="documentation">Documentation</h3>
+
+<p>All the documentation in a free system distribution must be released
+under an appropriate free license. Additionally, it must take care
+not to recommend nonfree software.</p>
+
+<p>In general, something that helps people who already use nonfree
+software to use the free software better with it is acceptable, but
+something that encourages users of the free software to install
+nonfree software is not.</p>
+
+<p>For example, a free system distribution may have documentation for
+users setting up dual boot systems. It could explain how to access
+filesystems of the proprietary operating system, import settings
+from it, and so on. That would be helping people install a free
+system distribution on a machine which already has proprietary
+software, which is good.</p>
+
+<p>What would be unacceptable is for the documentation to give people
+instructions for installing a nonfree program on the system, or
+mention conveniences they might gain by doing so.</p>
+
+<p>For a borderline case, a clear and serious exhortation not to use the
+nonfree program would move it to the acceptable side of the line.</p>
+
+<h3 id="patents">Patents</h3>
+
+<p>It is effectively impossible for free software developers and
+distributors to know whether or not a given piece of software
+infringes any patents: there are too many of them, they vary from
+country to country, they're often worded so as to make it hard to tell
+what they do or don't cover, and it isn't easy to tell which ones are
+valid. Therefore, we don't generally ask free system distributions to
+exclude software because of possible threats from patents. On the
+other hand, we also don't object if a distributor chooses to omit some
+software in order to avoid patent risk.</p>
+
+<h3 id="no-malware">No Malware</h3>
+
+<p>The distro must contain no DRM, no back doors, and no
spyware.</p>
+
+<h3 id="mistakes">Commitment to Correct Mistakes</h3>
+
+<p>Most distribution development teams don't have the resources to
+exhaustively check that their distribution meet all these criteria.
+Neither do we. So we expect distros to occasionally contain mistakes:
+nonfree software that slipped through, etc. We don't reject a
+distribution over mistakes. Our requirement is for the distribution
+developers to have a firm commitment to promptly correct any mistakes
+that are reported to them.</p>
+
+<h3 id="maintenance">Maintenance</h3>
+
+<p>To be listed, a distribution should be actively maintained,
+and should give the GNU Project a clear and specific way to report problems
+of nonfree software that we find out about. It should also
+inform us when the problems we have reported are fixed.</p>
+
+<h3 id="name-confusion">Name Confusion</h3>
+
+<p>We will not list a distribution whose name makes confusion with
+nonfree distributions likely. For example, if Foobar Light is a free
+distribution and Foobar is a nonfree distribution, we will not list
+Foobar Light. This is because we expect that the distinction between
+the two would be lost in the process of communicating the message.</p>
+
+<p>In particular, the principal name of the free distribution
+(“Foobar”, in this example) should not be part of the name
+of any nonfree distribution.</p>
+
+<p>Some people have thought of adding the name “GNU” to a
+free distro name to distinguish it from a nonfree one. This has two
+problems. First, the two names would not be sufficiently different,
+since the principal word in both names would be the same.</p>
+
+<p>Second, this would promote a misunderstanding of what
+“GNU” means. <a href="/gnu/linux-and-gnu.html">GNU is an
+operating system</a>, typically used with Linux as the kernel, and
+essentially all so-called “Linux” distributions are really
+GNU/Linux distributions. In this scenario,
+<em>both</em> versions are GNU/Linux, and it would be misleading to
+omit “GNU” from the name of one of them.</p>
+
+<h3 id="upstream">Contacting Upstream If You're Downstream</h3>
+
+<p>For distro developers (or anyone else) who have sent an important bug
+report for a GNU package: if it has gone unheeded by the package
+maintainer after a reasonable time (please allow at least two weeks),
+you can escalate the bug by writing to <address@hidden>.
+This is especially warranted if you can't find evidence of recent
+activity by the package maintainer.</p>
+
+<h3 id="teaching">Please Teach Users about Free Software</h3>
+
+<p>To establish lasting freedom, just giving users freedom isn't
+sufficient. It is necessary also to teach them to understand what it
+means and to demand it. Thus, we suggest and urge that free distros
+announce prominently on the screen, before login and on the default
+desktop after login, a prominent statement about freedom, such as
+“This system is freedom-respecting free/libre software” or
+something comparable, and to present a link or icon pointing at
+gnu.org or gnu.org/philosophy for further information about the
+issue.</p>
+
+<h3 id="words-to-avoid">Please Avoid Repeating Propaganda and
Confusion</h3>
+
+<p>Please see our list
+of <a href="/philosophy/words-to-avoid.html">words to avoid</a>,
which
+are either biased, misguided or misleading, and try to avoid them in
+your public statements and discussions with the public.</p>
+
+<h3 id="final-notes">Final Notes</h3>
+
+<p>We maintain a list of the <a
href="/distros/free-distros.html">free
+GNU system distributions</a> we know about. If you know about a free
+distribution that isn't listed there, please ask its developers write
+to <<a class="reference"
+href="mailto:address@hidden">address@hidden</a>> with a
description of
+their system and a link to their web page.</p>
+
+<p>We also list <a href="/distros/free-non-gnu-distros.html">free
+non-GNU system distributions</a> on the same ethical
conditions.</p>
+
+<p>If you have questions or comments about these guidelines
+themselves, feel free to send those to <<a class="reference"
+href="mailto:address@hidden">address@hidden</a>>. We hope
+that they help everyone better understand the issues that are important
+for free system distributions, and we look forward to promoting more
+of them in the future.</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 & 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>
+</div>
+
+<!-- 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. -->
+
+<p>Copyright © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</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: 2017/12/15 18:59:39 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: distros/po/free-system-distribution-guidelines.lt-diff.html
===================================================================
RCS file: distros/po/free-system-distribution-guidelines.lt-diff.html
diff -N distros/po/free-system-distribution-guidelines.lt-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ distros/po/free-system-distribution-guidelines.lt-diff.html 15 Dec 2017
18:59:40 -0000 1.1
@@ -0,0 +1,376 @@
+<!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>/distros/free-system-distribution-guidelines.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.77 -->
+<title>Free System Distribution Guidelines (GNU FSDG) - GNU Project -
Free Software Foundation</title>
+<link rel="alternate" title="Free GNU/Linux distributions"
+ href="http://www.gnu.org/distros/distros.rss";
+ type="application/rss+xml" />
+<!--#include
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Free System Distribution Guidelines (GNU FSDG)</h2>
+<!--#include virtual="/licenses/fsf-licensing.html" -->
+
+<h3 id="introduction">Introduction</h3>
+
+<p>The purpose of these guidelines is to explain what it means for an
+installable system distribution (such as a <span
class="removed"><del><strong>GNU/Linux</strong></del></span> <span
class="inserted"><ins><em><a
href="/gnu/linux-and-gnu.html">GNU/Linux</a></em></ins></span>
distribution) to
+qualify as <a href="/philosophy/free-sw.html">free</a> (libre), and
+help distribution developers make their distributions qualify.</p>
+
+<p>These guidelines are not complete. We have mentioned the issues we
+are aware of now, but we're sure there are more. We will add them
+when we come across them.</p>
+
+<p>We would like to thank the Fedora Project for their help in focusing
+these policies, and allowing us to use their own distribution license
+guidelines as a basis for this document.</p>
+
+<h3 id="complete-distros">Complete Distros</h3>
+
+<p>Our list of distributions is a guide for systems you can install in
+a computer. Therefore, it only includes distributions that are
+complete in themselves and ready to use. If a distribution is
+incomplete — if it requires further development, or presupposes
+installing other software as well — then it is not listed here,
+even if it is free software.</p>
+
+<p>An exception to this requirement and to the self-hosting
+requirement above is for <em>small system distributions</em>, which
+are distros designed for devices with limited resources, like a
+wireless router for example. Free small system distributions do not
+need to be self-hosting or complete, because it is impractical to do
+development on such a system, but it must be developable and buildable
+on top of a free complete system distribution from our list of
+distributions, perhaps with the aid of free tools distributed
+alongside the small system distribution itself.</p>
+
+<h3 id="license-rules">License Rules</h3>
+
+<p>“Information for practical use”
+includes software, documentation, fonts, and other data that has
+direct functional applications. It does not include artistic works
+that have an aesthetic (rather than functional) purpose, or statements
+of opinion or judgment.</p>
+
+<p>All information for practical use in a free distribution must be
+available in source form. (“Source” means the form of the
+information that is preferred for making changes to it.)</p>
+
+<p>The information, and the source, must be provided under an
+appropriate <a href="/philosophy/free-sw.html">free license</a>.
We
+evaluate specific licenses and list our determinations
+in <a class="reference" href="/licenses/license-list.html">our license
+list</a>, with separate sections for licenses that are suitable for
+software, documentation, fonts, and other useful works. If such a
+work is released under a disjunction of licenses, the work is free as
+long as at least one of its licenses is free; the system developers
+should follow the terms of the applicable free license(s) when they
+distribute and/or modify it.</p>
+
+<p>A free system distribution must not steer users towards obtaining
+any nonfree information for practical use, or encourage them to do so.
+The system should have no repositories for nonfree software and no
+specific recipes for installation of particular nonfree programs. Nor
+should the distribution refer to third-party repositories that are not
+committed to only including free software; even if they only have free
+software today, that may not be true tomorrow. Programs in the system
+should not suggest installing nonfree plugins, documentation, and so
+on.</p>
+
+<span class="inserted"><ins><em><p>For instance, a free system
distribution must not contain browsers
+that implement EME, the browser functionality designed to load DRM
+modules.</p></em></ins></span>
+
+<p>A free system distribution should be self-hosting. This means that
+you must be able to develop and build the system with tools that the
+system provides you. As a result, a free system distribution cannot
+include free software that can only be built by using nonfree
+software.</p>
+
+<p>There's a lot of code in most free system distributions today; the
+amount of effort it would take to audit it all directly is impractical
+for most teams. In the past, some nonfree code has accidentally been
+included in free system distributions. We don't de-list distributions
+because of this; instead, we only ask that a distribution's developers
+make a good faith effort to avoid including nonfree software, and
+commit themselves to removing such programs if any are discovered.</p>
+
+<p>Certain kinds of license situations merit special attention for people
+creating or considering free software distributions; those are
+discussed in the sections below.</p>
+
+<h3 id="nonfree-firmware">Nonfree Firmware</h3>
+
+<p>Some applications and drivers require firmware to function, and
+sometimes that firmware is distributed only in object code form, under
+a nonfree license. We call these firmware programs
+“blobs.” On most GNU/Linux systems, you'll typically find
+these accompanying some drivers in the kernel Linux. Such firmware
+should be removed from a free system distribution.</p>
+
+<p>Blobs can take many forms. Sometimes, they will be provided in
+separate files. Other times, they may be incorporated into the source
+of the driver itself—for example, it could be encoded as a large
+array of numbers. But no matter how it's encoded, any nonfree
+firmware needs to be removed from a free system.</p>
+
+<p>(To be clear, not every array of numbers in a driver is firmware.
+It's important to understand the purpose of the data before deciding
+whether or not it's appropriate for a free system.)</p>
+
+<p>Brian Brazil, Jeff Moe, and Alexandre Oliva have developed a series
+of <a class="reference"
+href="http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/">scripts
+to remove nonfree firmware</a> from a stock version of the Linux kernel.
+You may find them helpful if you would like to develop your own free
+GNU/Linux distribution—although we recommend joining development
+of an existing free distro rather than fragmenting effort by starting a
+new one. The complete source for a blob-free version of the Linux
+kernel is also available; you can learn more about this project from the
+<a class="reference" href="http://directory.fsf.org/project/linux/">Free
+Software Directory</a>.</p>
+
+<h3 id="non-functional-data">Non-functional Data</h3>
+
+<p>Data that isn't functional, that doesn't do a practical job, is
+more of an adornment to the system's software than a part of it.
+Thus, we don't insist on the free license criteria for non-functional
+data. It can be included in a free system distribution as long as its
+license gives you permission to copy and redistribute, both for
+commercial and non-commercial purposes. For example, some game
+engines released under the GNU GPL have accompanying game
+information—a fictional world map, game graphics, and so
+on—released under such a verbatim-distribution license. This
+kind of data can be part of a free system distribution, even though
+its license does not qualify as free, because it is non-functional.</p>
+
+<h3 id="trademarks">Trademarks</h3>
+
+<p>Trademarks are associated with some software. For example, the
+name of a program may be trademarked, or its interface may display a
+trademarked logo. Often, the use of these marks will be controlled
+in some way; in particular, developers are commonly asked to remove
+references to the trademark from the software when they modify
+it.</p>
+
+<p>In extreme cases, these restrictions may effectively render the
+program nonfree. It is unfair for someone to ask you to remove a
+trademark from modified code if that trademark is scattered all
+throughout the original source. As long as the practical
+requirements are reasonable, however, free system distributions may
+include these programs, either with or without the trademarks.</p>
+
+<p>Similarly, the distribution itself may hold particular trademarks.
+It is not a problem if modification requires removal of these
+trademarks, as long as they can readily be removed without losing
+functionality.</p>
+
+<p>However, it is unacceptable to use trademarks to restrict verbatim
+copying and redistribution of the whole distribution, or any part.</p>
+
+<h3 id="documentation">Documentation</h3>
+
+<p>All the documentation in a free system distribution must be released
+under an appropriate free license. Additionally, it must take care
+not to recommend nonfree software.</p>
+
+<p>In general, something that helps people who already use nonfree
+software to use the free software better with it is acceptable, but
+something that encourages users of the free software to install
+nonfree software is not.</p>
+
+<p>For example, a free system distribution may have documentation for
+users setting up dual boot systems. It could explain how to access
+filesystems of the proprietary operating system, import settings
+from it, and so on. That would be helping people install a free
+system distribution on a machine which already has proprietary
+software, which is good.</p>
+
+<p>What would be unacceptable is for the documentation to give people
+instructions for installing a nonfree program on the system, or
+mention conveniences they might gain by doing so.</p>
+
+<p>For a borderline case, a clear and serious exhortation not to use the
+nonfree program would move it to the acceptable side of the line.</p>
+
+<h3 id="patents">Patents</h3>
+
+<p>It is effectively impossible for free software developers and
+distributors to know whether or not a given piece of software
+infringes any patents: there are too many of them, they vary from
+country to country, they're often worded so as to make it hard to tell
+what they do or don't cover, and it isn't easy to tell which ones are
+valid. Therefore, we don't generally ask free system distributions to
+exclude software because of possible threats from patents. On the
+other hand, we also don't object if a distributor chooses to omit some
+software in order to avoid patent risk.</p>
+
+<h3 id="no-malware">No Malware</h3>
+
+<p>The distro must contain no DRM, no back doors, and no
spyware.</p>
+
+<h3 id="mistakes">Commitment to Correct Mistakes</h3>
+
+<p>Most distribution development teams don't have the resources to
+exhaustively check that their distribution meet all these criteria.
+Neither do we. So we expect distros to occasionally contain mistakes:
+nonfree software that slipped through, etc. We don't reject a
+distribution over mistakes. Our requirement is for the distribution
+developers to have a firm commitment to promptly correct any mistakes
+that are reported to them.</p>
+
+<h3 id="maintenance">Maintenance</h3>
+
+<p>To be listed, a distribution should be actively maintained,
+and should give the GNU Project a clear and specific way to report problems
+of nonfree software that we find out about. It should also
+inform us when the problems we have reported are fixed.</p>
+
+<h3 id="name-confusion">Name Confusion</h3>
+
+<p>We will not list a distribution whose name makes confusion with
+nonfree distributions likely. For example, if Foobar Light is a free
+distribution and Foobar is a nonfree distribution, we will not list
+Foobar Light. This is because we expect that the distinction between
+the two would be lost in the process of communicating the message.</p>
+
+<p>In particular, the principal name of the free distribution
+(“Foobar”, in this example) should not be part of the name
+of any nonfree distribution.</p>
+
+<p>Some people have thought of adding the name “GNU” to a
+free distro name to distinguish it from a nonfree one. This has two
+problems. First, the two names would not be sufficiently different,
+since the principal word in both names would be the same.</p>
+
+<p>Second, this would promote a misunderstanding of what
+“GNU” means. <a href="/gnu/linux-and-gnu.html">GNU is an
+operating system</a>, typically used with Linux as the kernel, and
+essentially all so-called “Linux” distributions are really
+GNU/Linux distributions. In this scenario,
+<em>both</em> versions are GNU/Linux, and it would be misleading to
+omit “GNU” from the name of one of them.</p>
+
+<h3 id="upstream">Contacting Upstream If You're Downstream</h3>
+
+<p>For distro developers (or anyone else) who have sent an important bug
+report for a GNU package: if it has gone unheeded by the package
+maintainer after a reasonable time (please allow at least two weeks),
+you can escalate the bug by writing to <address@hidden>.
+This is especially warranted if you can't find evidence of recent
+activity by the package maintainer.</p>
+
+<h3 id="teaching">Please Teach Users about Free Software</h3>
+
+<p>To establish lasting freedom, just giving users freedom isn't
+sufficient. It is necessary also to teach them to understand what it
+means and to demand it. Thus, we suggest and urge that free distros
+announce prominently on the screen, before login and on the default
+desktop after login, a prominent statement about freedom, such as
+“This system is freedom-respecting free/libre software” or
+something comparable, and to present a link or icon pointing at
+gnu.org or gnu.org/philosophy for further information about the
+issue.</p>
+
+<h3 id="words-to-avoid">Please Avoid Repeating Propaganda and
Confusion</h3>
+
+<p>Please see our list
+of <a href="/philosophy/words-to-avoid.html">words to avoid</a>,
which
+are either biased, misguided or misleading, and try to avoid them in
+your public statements and discussions with the public.</p>
+
+<h3 id="final-notes">Final Notes</h3>
+
+<p>We maintain a list of the <a
href="/distros/free-distros.html">free
+GNU system distributions</a> we know about. If you know about a free
+distribution that isn't listed there, please ask its developers write
+to <<a class="reference"
+href="mailto:address@hidden">address@hidden</a>> with a
description of
+their system and a link to their web page.</p>
+
+<p>We also list <a href="/distros/free-non-gnu-distros.html">free
+non-GNU system distributions</a> on the same ethical
conditions.</p>
+
+<p>If you have questions or comments about these guidelines
+themselves, feel free to send those to <<a class="reference"
+href="mailto:address@hidden">address@hidden</a>>. We hope
+that they help everyone better understand the issues that are important
+for free system distributions, and we look forward to promoting more
+of them in the future.</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 & 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>
+</div>
+
+<!-- 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. -->
+
+<p>Copyright © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</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: 2017/12/15 18:59:40 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: distros/po/free-system-distribution-guidelines.pl-diff.html
===================================================================
RCS file: distros/po/free-system-distribution-guidelines.pl-diff.html
diff -N distros/po/free-system-distribution-guidelines.pl-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ distros/po/free-system-distribution-guidelines.pl-diff.html 15 Dec 2017
18:59:40 -0000 1.1
@@ -0,0 +1,376 @@
+<!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>/distros/free-system-distribution-guidelines.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.77 -->
+<title>Free System Distribution Guidelines (GNU FSDG) - GNU Project -
Free Software Foundation</title>
+<link rel="alternate" title="Free GNU/Linux distributions"
+ href="http://www.gnu.org/distros/distros.rss";
+ type="application/rss+xml" />
+<!--#include
virtual="/distros/po/free-system-distribution-guidelines.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Free System Distribution Guidelines (GNU FSDG)</h2>
+<!--#include virtual="/licenses/fsf-licensing.html" -->
+
+<h3 id="introduction">Introduction</h3>
+
+<p>The purpose of these guidelines is to explain what it means for an
+installable system distribution (such as a <span
class="removed"><del><strong>GNU/Linux</strong></del></span> <span
class="inserted"><ins><em><a
href="/gnu/linux-and-gnu.html">GNU/Linux</a></em></ins></span>
distribution) to
+qualify as <a href="/philosophy/free-sw.html">free</a> (libre), and
+help distribution developers make their distributions qualify.</p>
+
+<p>These guidelines are not complete. We have mentioned the issues we
+are aware of now, but we're sure there are more. We will add them
+when we come across them.</p>
+
+<p>We would like to thank the Fedora Project for their help in focusing
+these policies, and allowing us to use their own distribution license
+guidelines as a basis for this document.</p>
+
+<h3 id="complete-distros">Complete Distros</h3>
+
+<p>Our list of distributions is a guide for systems you can install in
+a computer. Therefore, it only includes distributions that are
+complete in themselves and ready to use. If a distribution is
+incomplete — if it requires further development, or presupposes
+installing other software as well — then it is not listed here,
+even if it is free software.</p>
+
+<p>An exception to this requirement and to the self-hosting
+requirement above is for <em>small system distributions</em>, which
+are distros designed for devices with limited resources, like a
+wireless router for example. Free small system distributions do not
+need to be self-hosting or complete, because it is impractical to do
+development on such a system, but it must be developable and buildable
+on top of a free complete system distribution from our list of
+distributions, perhaps with the aid of free tools distributed
+alongside the small system distribution itself.</p>
+
+<h3 id="license-rules">License Rules</h3>
+
+<p>“Information for practical use”
+includes software, documentation, fonts, and other data that has
+direct functional applications. It does not include artistic works
+that have an aesthetic (rather than functional) purpose, or statements
+of opinion or judgment.</p>
+
+<p>All information for practical use in a free distribution must be
+available in source form. (“Source” means the form of the
+information that is preferred for making changes to it.)</p>
+
+<p>The information, and the source, must be provided under an
+appropriate <a href="/philosophy/free-sw.html">free license</a>.
We
+evaluate specific licenses and list our determinations
+in <a class="reference" href="/licenses/license-list.html">our license
+list</a>, with separate sections for licenses that are suitable for
+software, documentation, fonts, and other useful works. If such a
+work is released under a disjunction of licenses, the work is free as
+long as at least one of its licenses is free; the system developers
+should follow the terms of the applicable free license(s) when they
+distribute and/or modify it.</p>
+
+<p>A free system distribution must not steer users towards obtaining
+any nonfree information for practical use, or encourage them to do so.
+The system should have no repositories for nonfree software and no
+specific recipes for installation of particular nonfree programs. Nor
+should the distribution refer to third-party repositories that are not
+committed to only including free software; even if they only have free
+software today, that may not be true tomorrow. Programs in the system
+should not suggest installing nonfree plugins, documentation, and so
+on.</p>
+
+<span class="inserted"><ins><em><p>For instance, a free system
distribution must not contain browsers
+that implement EME, the browser functionality designed to load DRM
+modules.</p></em></ins></span>
+
+<p>A free system distribution should be self-hosting. This means that
+you must be able to develop and build the system with tools that the
+system provides you. As a result, a free system distribution cannot
+include free software that can only be built by using nonfree
+software.</p>
+
+<p>There's a lot of code in most free system distributions today; the
+amount of effort it would take to audit it all directly is impractical
+for most teams. In the past, some nonfree code has accidentally been
+included in free system distributions. We don't de-list distributions
+because of this; instead, we only ask that a distribution's developers
+make a good faith effort to avoid including nonfree software, and
+commit themselves to removing such programs if any are discovered.</p>
+
+<p>Certain kinds of license situations merit special attention for people
+creating or considering free software distributions; those are
+discussed in the sections below.</p>
+
+<h3 id="nonfree-firmware">Nonfree Firmware</h3>
+
+<p>Some applications and drivers require firmware to function, and
+sometimes that firmware is distributed only in object code form, under
+a nonfree license. We call these firmware programs
+“blobs.” On most GNU/Linux systems, you'll typically find
+these accompanying some drivers in the kernel Linux. Such firmware
+should be removed from a free system distribution.</p>
+
+<p>Blobs can take many forms. Sometimes, they will be provided in
+separate files. Other times, they may be incorporated into the source
+of the driver itself—for example, it could be encoded as a large
+array of numbers. But no matter how it's encoded, any nonfree
+firmware needs to be removed from a free system.</p>
+
+<p>(To be clear, not every array of numbers in a driver is firmware.
+It's important to understand the purpose of the data before deciding
+whether or not it's appropriate for a free system.)</p>
+
+<p>Brian Brazil, Jeff Moe, and Alexandre Oliva have developed a series
+of <a class="reference"
+href="http://www.fsfla.org/svn/fsfla/software/linux-libre/scripts/">scripts
+to remove nonfree firmware</a> from a stock version of the Linux kernel.
+You may find them helpful if you would like to develop your own free
+GNU/Linux distribution—although we recommend joining development
+of an existing free distro rather than fragmenting effort by starting a
+new one. The complete source for a blob-free version of the Linux
+kernel is also available; you can learn more about this project from the
+<a class="reference" href="http://directory.fsf.org/project/linux/">Free
+Software Directory</a>.</p>
+
+<h3 id="non-functional-data">Non-functional Data</h3>
+
+<p>Data that isn't functional, that doesn't do a practical job, is
+more of an adornment to the system's software than a part of it.
+Thus, we don't insist on the free license criteria for non-functional
+data. It can be included in a free system distribution as long as its
+license gives you permission to copy and redistribute, both for
+commercial and non-commercial purposes. For example, some game
+engines released under the GNU GPL have accompanying game
+information—a fictional world map, game graphics, and so
+on—released under such a verbatim-distribution license. This
+kind of data can be part of a free system distribution, even though
+its license does not qualify as free, because it is non-functional.</p>
+
+<h3 id="trademarks">Trademarks</h3>
+
+<p>Trademarks are associated with some software. For example, the
+name of a program may be trademarked, or its interface may display a
+trademarked logo. Often, the use of these marks will be controlled
+in some way; in particular, developers are commonly asked to remove
+references to the trademark from the software when they modify
+it.</p>
+
+<p>In extreme cases, these restrictions may effectively render the
+program nonfree. It is unfair for someone to ask you to remove a
+trademark from modified code if that trademark is scattered all
+throughout the original source. As long as the practical
+requirements are reasonable, however, free system distributions may
+include these programs, either with or without the trademarks.</p>
+
+<p>Similarly, the distribution itself may hold particular trademarks.
+It is not a problem if modification requires removal of these
+trademarks, as long as they can readily be removed without losing
+functionality.</p>
+
+<p>However, it is unacceptable to use trademarks to restrict verbatim
+copying and redistribution of the whole distribution, or any part.</p>
+
+<h3 id="documentation">Documentation</h3>
+
+<p>All the documentation in a free system distribution must be released
+under an appropriate free license. Additionally, it must take care
+not to recommend nonfree software.</p>
+
+<p>In general, something that helps people who already use nonfree
+software to use the free software better with it is acceptable, but
+something that encourages users of the free software to install
+nonfree software is not.</p>
+
+<p>For example, a free system distribution may have documentation for
+users setting up dual boot systems. It could explain how to access
+filesystems of the proprietary operating system, import settings
+from it, and so on. That would be helping people install a free
+system distribution on a machine which already has proprietary
+software, which is good.</p>
+
+<p>What would be unacceptable is for the documentation to give people
+instructions for installing a nonfree program on the system, or
+mention conveniences they might gain by doing so.</p>
+
+<p>For a borderline case, a clear and serious exhortation not to use the
+nonfree program would move it to the acceptable side of the line.</p>
+
+<h3 id="patents">Patents</h3>
+
+<p>It is effectively impossible for free software developers and
+distributors to know whether or not a given piece of software
+infringes any patents: there are too many of them, they vary from
+country to country, they're often worded so as to make it hard to tell
+what they do or don't cover, and it isn't easy to tell which ones are
+valid. Therefore, we don't generally ask free system distributions to
+exclude software because of possible threats from patents. On the
+other hand, we also don't object if a distributor chooses to omit some
+software in order to avoid patent risk.</p>
+
+<h3 id="no-malware">No Malware</h3>
+
+<p>The distro must contain no DRM, no back doors, and no
spyware.</p>
+
+<h3 id="mistakes">Commitment to Correct Mistakes</h3>
+
+<p>Most distribution development teams don't have the resources to
+exhaustively check that their distribution meet all these criteria.
+Neither do we. So we expect distros to occasionally contain mistakes:
+nonfree software that slipped through, etc. We don't reject a
+distribution over mistakes. Our requirement is for the distribution
+developers to have a firm commitment to promptly correct any mistakes
+that are reported to them.</p>
+
+<h3 id="maintenance">Maintenance</h3>
+
+<p>To be listed, a distribution should be actively maintained,
+and should give the GNU Project a clear and specific way to report problems
+of nonfree software that we find out about. It should also
+inform us when the problems we have reported are fixed.</p>
+
+<h3 id="name-confusion">Name Confusion</h3>
+
+<p>We will not list a distribution whose name makes confusion with
+nonfree distributions likely. For example, if Foobar Light is a free
+distribution and Foobar is a nonfree distribution, we will not list
+Foobar Light. This is because we expect that the distinction between
+the two would be lost in the process of communicating the message.</p>
+
+<p>In particular, the principal name of the free distribution
+(“Foobar”, in this example) should not be part of the name
+of any nonfree distribution.</p>
+
+<p>Some people have thought of adding the name “GNU” to a
+free distro name to distinguish it from a nonfree one. This has two
+problems. First, the two names would not be sufficiently different,
+since the principal word in both names would be the same.</p>
+
+<p>Second, this would promote a misunderstanding of what
+“GNU” means. <a href="/gnu/linux-and-gnu.html">GNU is an
+operating system</a>, typically used with Linux as the kernel, and
+essentially all so-called “Linux” distributions are really
+GNU/Linux distributions. In this scenario,
+<em>both</em> versions are GNU/Linux, and it would be misleading to
+omit “GNU” from the name of one of them.</p>
+
+<h3 id="upstream">Contacting Upstream If You're Downstream</h3>
+
+<p>For distro developers (or anyone else) who have sent an important bug
+report for a GNU package: if it has gone unheeded by the package
+maintainer after a reasonable time (please allow at least two weeks),
+you can escalate the bug by writing to <address@hidden>.
+This is especially warranted if you can't find evidence of recent
+activity by the package maintainer.</p>
+
+<h3 id="teaching">Please Teach Users about Free Software</h3>
+
+<p>To establish lasting freedom, just giving users freedom isn't
+sufficient. It is necessary also to teach them to understand what it
+means and to demand it. Thus, we suggest and urge that free distros
+announce prominently on the screen, before login and on the default
+desktop after login, a prominent statement about freedom, such as
+“This system is freedom-respecting free/libre software” or
+something comparable, and to present a link or icon pointing at
+gnu.org or gnu.org/philosophy for further information about the
+issue.</p>
+
+<h3 id="words-to-avoid">Please Avoid Repeating Propaganda and
Confusion</h3>
+
+<p>Please see our list
+of <a href="/philosophy/words-to-avoid.html">words to avoid</a>,
which
+are either biased, misguided or misleading, and try to avoid them in
+your public statements and discussions with the public.</p>
+
+<h3 id="final-notes">Final Notes</h3>
+
+<p>We maintain a list of the <a
href="/distros/free-distros.html">free
+GNU system distributions</a> we know about. If you know about a free
+distribution that isn't listed there, please ask its developers write
+to <<a class="reference"
+href="mailto:address@hidden">address@hidden</a>> with a
description of
+their system and a link to their web page.</p>
+
+<p>We also list <a href="/distros/free-non-gnu-distros.html">free
+non-GNU system distributions</a> on the same ethical
conditions.</p>
+
+<p>If you have questions or comments about these guidelines
+themselves, feel free to send those to <<a class="reference"
+href="mailto:address@hidden">address@hidden</a>>. We hope
+that they help everyone better understand the issues that are important
+for free system distributions, and we look forward to promoting more
+of them in the future.</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 & 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>
+</div>
+
+<!-- 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. -->
+
+<p>Copyright © 2014, <span
class="removed"><del><strong>2015</strong></del></span> <span
class="inserted"><ins><em>2015, 2017</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: 2017/12/15 18:59:40 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www distros/distros.it.html distros/distros.ja....,
GNUN <=