[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses license-list.it.html license-recom...
|
From: |
GNUN |
|
Subject: |
www/licenses license-list.it.html license-recom... |
|
Date: |
Fri, 15 Dec 2017 14:59:12 -0500 (EST) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 17/12/15 14:59:11
Modified files:
licenses : license-list.it.html
license-recommendations.it.html
license-recommendations.ja.html
licenses/po : license-list.it-diff.html
Added files:
licenses/po : license-recommendations.it-diff.html
license-recommendations.ja-diff.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-list.it.html?cvsroot=www&r1=1.110&r2=1.111
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-recommendations.it.html?cvsroot=www&r1=1.5&r2=1.6
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-recommendations.ja.html?cvsroot=www&r1=1.21&r2=1.22
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-list.it-diff.html?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-recommendations.it-diff.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-recommendations.ja-diff.html?cvsroot=www&rev=1.1
Patches:
Index: license-list.it.html
===================================================================
RCS file: /web/www/www/licenses/license-list.it.html,v
retrieving revision 1.110
retrieving revision 1.111
diff -u -b -r1.110 -r1.111
--- license-list.it.html 30 Sep 2017 21:00:08 -0000 1.110
+++ license-list.it.html 15 Dec 2017 19:59:11 -0000 1.111
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/license-list.en.html" -->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/license-list.it.po">
+ https://www.gnu.org/licenses/po/license-list.it.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/license-list.html"
+ --><!--#set var="DIFF_FILE" value="/licenses/po/license-list.it-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/licenses/license-list.en.html" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.79 -->
@@ -100,6 +105,7 @@
</style>
<!--#include virtual="/server/banner.it.html" -->
+<!--#include virtual="/server/outdated.it.html" -->
<h2>Licenze varie e commenti relativi</h2>
<div class="toc">
@@ -2594,7 +2600,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2017/09/30 21:00:08 $
+$Date: 2017/12/15 19:59:11 $
<!-- timestamp end -->
</p>
Index: license-recommendations.it.html
===================================================================
RCS file: /web/www/www/licenses/license-recommendations.it.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- license-recommendations.it.html 8 Feb 2016 06:34:38 -0000 1.5
+++ license-recommendations.it.html 15 Dec 2017 19:59:11 -0000 1.6
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/license-recommendations.en.html"
-->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/license-recommendations.it.po">
+ https://www.gnu.org/licenses/po/license-recommendations.it.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/license-recommendations.html"
+ --><!--#set var="DIFF_FILE"
value="/licenses/po/license-recommendations.it-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/licenses/license-recommendations.en.html" -->
<!--#include virtual="/server/header.it.html" -->
<!-- Parent-Version: 1.77 -->
@@ -9,6 +14,7 @@
<!--#include virtual="/licenses/po/license-recommendations.translist" -->
<!--#include virtual="/server/banner.it.html" -->
+<!--#include virtual="/server/outdated.it.html" -->
<h2>Come scegliere una licenza per i propri progetti</h2>
<!--#include virtual="/licenses/fsf-licensing.it.html" -->
@@ -299,7 +305,7 @@
<p class="unprintable"><!-- timestamp start -->
Ultimo aggiornamento:
-$Date: 2016/02/08 06:34:38 $
+$Date: 2017/12/15 19:59:11 $
<!-- timestamp end -->
</p>
Index: license-recommendations.ja.html
===================================================================
RCS file: /web/www/www/licenses/license-recommendations.ja.html,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -b -r1.21 -r1.22
--- license-recommendations.ja.html 5 Feb 2016 01:00:20 -0000 1.21
+++ license-recommendations.ja.html 15 Dec 2017 19:59:11 -0000 1.22
@@ -1,4 +1,9 @@
-<!--#set var="ENGLISH_PAGE" value="/licenses/license-recommendations.en.html"
-->
+<!--#set var="PO_FILE"
+ value='<a href="/licenses/po/license-recommendations.ja.po">
+ https://www.gnu.org/licenses/po/license-recommendations.ja.po</a>'
+ --><!--#set var="ORIGINAL_FILE" value="/licenses/license-recommendations.html"
+ --><!--#set var="DIFF_FILE"
value="/licenses/po/license-recommendations.ja-diff.html"
+ --><!--#set var="OUTDATED_SINCE" value="2017-10-16" --><!--#set
var="ENGLISH_PAGE" value="/licenses/license-recommendations.en.html" -->
<!--#include virtual="/server/header.ja.html" -->
<!-- Parent-Version: 1.77 -->
@@ -8,6 +13,7 @@
<!--#include virtual="/licenses/po/license-recommendations.translist" -->
<!--#include virtual="/server/banner.ja.html" -->
+<!--#include virtual="/server/outdated.ja.html" -->
<h2>ããªãèªèº«ã®ä½åã«ã©ã¤ã»ã³ã¹ãé¸æããæ¹æ³</h2>
<!--#include virtual="/licenses/fsf-licensing.ja.html" -->
@@ -182,7 +188,7 @@
<p class="unprintable"><!-- timestamp start -->
æçµæ´æ°:
-$Date: 2016/02/05 01:00:20 $
+$Date: 2017/12/15 19:59:11 $
<!-- timestamp end -->
</p>
Index: po/license-list.it-diff.html
===================================================================
RCS file: /web/www/www/licenses/po/license-list.it-diff.html,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- po/license-list.it-diff.html 30 Sep 2017 01:29:52 -0000 1.1
+++ po/license-list.it-diff.html 15 Dec 2017 19:59:11 -0000 1.2
@@ -246,7 +246,7 @@
GNU General Public License (GPL) version 3</a>
<span class="anchor-reference-id">
(<a href="#GNUGPL">#GNUGPL</a>)
- (<a <span
class="removed"><del><strong>href="#GNUGPL">#GNUGPLv3</a>)</strong></del></span>
<span
class="inserted"><ins><em>href="#GNUGPLv3">#GNUGPLv3</a>)</em></ins></span>
+ (<a href="#GNUGPLv3">#GNUGPLv3</a>)
</span></dt>
<dd>
<p>This is the latest version of the GNU GPL: a free software license,
and
@@ -283,7 +283,7 @@
GNU Lesser General Public License (LGPL) version 3</a>
<span class="anchor-reference-id">
(<a href="#LGPL">#LGPL</a>)
- (<a <span
class="removed"><del><strong>href="#LGPL">#LGPLv3</a>)</span></dt></strong></del></span>
<span
class="inserted"><ins><em>href="#LGPLv3">#LGPLv3</a>)</span></dt></em></ins></span>
+ (<a href="#LGPLv3">#LGPLv3</a>)</span></dt>
<dd>
<p>This is the latest version of the LGPL: a free software license, but
not
a strong copyleft license, because it permits linking with nonfree
@@ -381,11 +381,11 @@
<p>This license is a free software license, compatible with the GPL
thanks to the relicensing option in section 4(c)(ii).</p></dd>
-<dt><a <span
class="inserted"><ins><em>id="ClarifiedArtistic"</em></ins></span> href=
+<dt><a id="ClarifiedArtistic" href=
"http://gianluca.dellavedova.org/2011/01/03/clarified-artistic-license/">
- Clarified Artistic <span
class="removed"><del><strong>License</a></dt></strong></del></span>
<span class="inserted"><ins><em>License</a>
+ Clarified Artistic License</a>
<span class="anchor-reference-id">
- (<a
href="#ClarifiedArtistic">#ClarifiedArtistic</a>)</span></dt></em></ins></span>
+ (<a
href="#ClarifiedArtistic">#ClarifiedArtistic</a>)</span></dt>
<dd>
<p>This license is a free software license, compatible with the GPL. It
is the minimal set of changes needed to correct the vagueness of the <a
@@ -974,18 +974,27 @@
license for one, we recommend the Apache 2.0 license since it protects
users from patent treachery.</p></dd>
-<dt><a id="Wx"></a>WxWidgets License <span
class="anchor-reference-id">(<a
href="#Wx">#Wx</a>)</span></dt>
+<span class="removed"><del><strong><dt><a
id="Wx"></a>WxWidgets</strong></del></span>
+
+<span class="inserted"><ins><em><dt id="Wx">WxWidgets
Library</em></ins></span> License
+<span class="anchor-reference-id">(<a
href="#Wx">#Wx</a>)</span></dt>
<dd>
<p>The WxWidgets license is a GPL-compatible free software license. It
-consists of the <a href="/licenses/old-licenses/lgpl-2.0.html">LGPL
2.0</a>
-or any later version, plus an additional permission allowing binary
-distributions that use the library to be licensed under terms of the
-distributor's choice (including proprietary). Like the LGPL it is a
-weak copyleft license, so we recommend it <a
-href="/licenses/why-not-lgpl.html"> only in special
+consists of the <a <span
class="removed"><del><strong>href="/licenses/old-licenses/lgpl-2.0.html">LGPL</strong></del></span>
<span
class="inserted"><ins><em>href="/licenses/old-licenses/lgpl-2.0.html">GNU
+Lesser GPL</em></ins></span> 2.0</a> or any later version, plus an
additional permission
+allowing binary distributions that use the library to be licensed
+under terms of the distributor's choice (including proprietary). <span
class="removed"><del><strong>Like the LGPL it</strong></del></span> <span
class="inserted"><ins><em>It</em></ins></span>
+is a weak <span class="removed"><del><strong>copyleft
license,</strong></del></span> <span class="inserted"><ins><em>copyleft, even
weaker than the LGPL,</em></ins></span> so we recommend
+it <a href="/licenses/why-not-lgpl.html"> only in special
circumstances</a>.</p>
</dd>
+<span class="inserted"><ins><em><dt id="Wxwind">WxWindows Library License
+<span class="anchor-reference-id">(<a
href="#Wxwind">#Wx</a>)</span></dt>
+<dd>
+<p>An older name for the <a href="#Wx">WxWidgets Library
license</a>.</p>
+</dd></em></ins></span>
+
<dt><a id="X11License"
href="http://directory.fsf.org/wiki/License:X11">
X11 License</a>
<span class="anchor-reference-id">
@@ -1155,7 +1164,7 @@
<p>However, there is no reason not to use programs that have been
released
under the original BSD license.</p></dd>
-<dt><a <span class="inserted"><ins><em>id="CeCILL-B"
href="https://directory.fsf.org/wiki/License:CeCILL-B">
+<dt><a id="CeCILL-B"
href="https://directory.fsf.org/wiki/License:CeCILL-B">
CeCILL-B version 1</a>
<span class="anchor-reference-id">(<a
href="#CeCILL-B">#CeCILL-B</a>)</span>
</dt>
@@ -1180,7 +1189,7 @@
<p>Please do not release software under this
license.</p></dd>
-<dt><a</em></ins></span> id="CDDL"
+<dt><a id="CDDL"
href="http://directory.fsf.org/wiki/License:CDDLv1.0">
Common Development and Distribution License (CDDL), version 1.0</a>
<span class="anchor-reference-id"> (<a
href="#CDDL">#CDDL</a>)</span></dt>
@@ -1252,8 +1261,24 @@
infringement suits specifically against Contributors to the EPL'd
program.</p></dd>
+<dt><a <span class="inserted"><ins><em>id="EPL2"
href="http://directory.fsf.org/wiki/License:EPLv2.0">
+ Eclipse Public License Version 2.0</a>
+ <span class="anchor-reference-id">(<a
href="#EPL2">#EPL2</a>)</span></dt>
+<dd>
+<p>In terms of GPL compatibility, the Eclipse Public License version
+2.0 is essentially equivalent to version 1.0. The only change is that
+it explicitly offers the option of designating the GNU GPL version 2
+or later as a “secondary license” for a certain piece of
+code.</p>
+
+<p>If an initial contributor releases a specific piece of code and
+designates GNU GPL version 2 or later as a secondary license, that
+provides explicit compatibility with those GPL versions for that
+code. (Doing so is roughly equivalent, for users, to releasing that
+piece of code under a dual license, EPL | GPL.) However, the EPL2
+without this designation remains incompatible with the
GPL.</p></dd>
-<dt><a id="EUPL"
href="http://directory.fsf.org/wiki/License:EUPLv1.1">
+<dt><a</em></ins></span> id="EUPL"
href="http://directory.fsf.org/wiki/License:EUPLv1.1">
European Union Public License (EUPL) version 1.1</a>
<span class="anchor-reference-id">(<a
href="#EUPL">#EUPL</a>)</span></dt>
<dd>
@@ -2710,7 +2735,7 @@
<p class="unprintable">Updated:
<!-- timestamp start -->
-$Date: 2017/09/30 01:29:52 $
+$Date: 2017/12/15 19:59:11 $
<!-- timestamp end -->
</p>
</div>
Index: po/license-recommendations.it-diff.html
===================================================================
RCS file: po/license-recommendations.it-diff.html
diff -N po/license-recommendations.it-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/license-recommendations.it-diff.html 15 Dec 2017 19:59:11 -0000
1.1
@@ -0,0 +1,311 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/licenses/license-recommendations.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>How to choose a license for your own work
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/license-recommendations.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to choose a license for your own work</h2>
+
+<!--#include virtual="/licenses/fsf-licensing.html" -->
+
+<blockquote><p>
+To see whether a given license is free or not,
+see <a href="/licenses/license-list.html">our license list page</a>
+and the <a href="/philosophy/free-sw.html">definition of free
software</a>.
+</p></blockquote>
+
+<h3 id="intro">Introduction</h3>
+
+<p>People often ask us what license we recommend they use for their
+project. We've written about this publicly before, but the
+information has been scattered around between different essays, FAQ
+entries, and license commentaries. This article collects all that
+information into a single source, to make it easier for people to
+follow and refer back to.</p>
+
+<p>These recommendations are for works designed to do practical jobs.
+Those include software, documentation, and some other things. Works of
+art, and works that state a point of view, are different issues; the GNU
+Project has no general stand about how they should be released, except
+that they should all be usable without nonfree software (in
+particular, <a href="http://defectivebydesign.org/">without
DRM</a>).
+However, you might want to follow these recommendations for art works
+that go with a particular program.</p>
+
+<p>The recommendations apply to licensing a work that you
+create—whether that's a modification of an existing work, or a
+new original work. They do not address the issue of combining
+existing material under different licenses. If you're looking for
+help with that, please check <a href="/licenses/gpl-faq.html">our GPL
+FAQ</a>.</p>
+
+<p>After you see what we recommend here, if you'd like advice, you can
+write
+to <a href="mailto:address@hidden"><address@hidden></a>.
+Note that it will probably take a few weeks for the licensing team to
+get back to you; if you get no response in a month, please write
+again.</p>
+
+<h3 id="contributing">Contributing to an existing project</h3>
+
+<p>When you contribute to an existing project, you should usually release
+your modified versions under the same license as the original work.
+It's good to cooperate with the project's maintainers, and using a
+different license for your modifications often makes that cooperation
+very difficult. You should only do that when there is a strong reason
+to justify it.</p>
+
+<p>One case where using a different license can be justified is when you
make
+major changes to a work under a non-copyleft license. If the version you've
+created is considerably more useful than the original, then it's worth
+copylefting your work, for all the same
+<a href="/copyleft/copyleft.html">reasons we normally recommend
+copyleft</a>. If you are in this situation, please follow the
+recommendations below for licensing a new project.</p>
+
+<p>If you choose to release your contributions under a different
+license for whatever reason, you must make sure that the original
+license allows use of the material under your chosen license. For
+honesty's sake, show explicitly which parts of the work are under
+which license.</p>
+
+<h3 id="software">Software</h3>
+
+<p>We recommend different licenses for different projects, depending
+mostly on the software's purpose. In general, we recommend using the
+strongest copyleft license that doesn't interfere with that purpose.
+Our essay <a href="/copyleft/copyleft.html">“What
+is Copyleft?”</a> explains the
+concept of copyleft in more detail, and why it is generally the best
+licensing strategy.</p>
+
+<p>For most programs, we recommend that you use the most recent
+version of the <a href="/licenses/gpl.html">GNU General Public License
+(GPL)</a> for your project. Its strong copyleft is appropriate for
+all kinds of software, and includes numerous protections for users'
+<span class="removed"><del><strong>freedom.</p></strong></del></span>
+<span class="inserted"><ins><em>freedom. Please give permission to use future
license versions as
+well—in other words, make the license notice say that your
+program is covered by GPL version 3 or later.</p>
+
+<p>Here is more advice about <a href="/licenses/gpl-howto.html">how
+to release a program under the GNU GPL</a>.</p></em></ins></span>
+
+<p>Now for the <span
class="removed"><del><strong>exceptions.</p></strong></del></span> <span
class="inserted"><ins><em>exceptions, where it is better to use some other
+licenses instead of the GNU GPL.</p></em></ins></span>
+
+<h4 id="small">Small programs</h4>
+
+<p>It is not worth the trouble to use copyleft for most small
+programs. We use 300 lines as our benchmark: when a software
+package's source code is shorter than that, the benefits provided by
+copyleft are usually too small to justify the inconvenience of making
+sure a copy of the license always accompanies the software.</p>
+
+<p>For those programs, we recommend
+the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+License 2.0</a>. This is a pushover (non-copyleft) software license
+that has terms to prevent contributors and distributors from suing for
+patent infringement. This doesn't make the software immune to threats
+from patents (a software license can't do that), but it does prevent
+patent holders from setting up a “bait and switch” where
+they release the software under free terms then require recipients to
+agree to nonfree terms in a patent license.</p>
+
+<p>Among the lax pushover licenses, Apache 2.0 is best; so if you
+are going to use a lax pushover license, whatever the reason,
+we recommend using that one.</p>
+
+<h4 id="libraries">Libraries</h4>
+
+<p>For libraries, we distinguish three kind of cases.</p>
+
+<p>Some libraries implement free standards that are competing against
+restricted standards, such as Ogg Vorbis (which competes against MP3
+audio) and WebM (which competes against MPEG-4 video). For these
+projects, widespread use of the code is vital for advancing the cause
+of free software, and does more good than a copyleft on the project's
+code would do.</p>
+
+<p>In these special situations, we recommend
+the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+License 2.0</a>.</p>
+
+<p>For all other libraries, we recommend some kind of copyleft. If
+developers are already using an established alternative library
+released under a nonfree license or a lax pushover license, then we
+recommend using the <a href="/licenses/lgpl.html">GNU Lesser General
+Public License (LGPL)</a>.</p>
+
+<p>Unlike the first case, where the library implements an ethically
+superior standard, here adoption for its own sake will not accomplish
+any special objective goal, so there's no reason to avoid copyleft
+entirely. However, if you require developers who use your library to
+release their whole programs under copyleft, they'll simply use one of
+the alternatives available, and that won't advance our cause either.
+The Lesser GPL was designed to fill the middle ground between these
+cases, allowing proprietary software developers to use the covered
+library, but providing a weak copyleft that gives users freedom
+regarding the library code itself.</p>
+
+<p>For libraries that provide specialized facilities, and which do not
+face entrenched noncopylefted or nonfree competition, we recommend
+using the plain GNU GPL. For the reasons why,
+read <a href="/licenses/why-not-lgpl.html">“Why you shouldn't
+use the Lesser GPL for your next library”</a>.</p>
+
+<h4 id="server">Server Software</h4>
+
+<p>If it is likely that others will make improved versions of your
+program to run on servers and not distribute their versions to anyone
+else, and you're concerned that this will put your released version at
+a disadvantage, we recommend the <a href="/licenses/agpl.html">GNU
+Affero General Public License (AGPL)</a>. The AGPL's terms are almost
+identical to the GPL's; the sole substantive difference is that it has
+an extra condition to ensure that people who use the software over a
+network will be able to get the source code for it.</p>
+
+<p>The AGPL's requirement doesn't address the problems that can arise
+<em>for users</em> when they entrust their computing or their data
to
+someone else's server. For instance, it won't stop
+<a href="/philosophy/who-does-that-server-really-serve.html">Service
+as a Software Substitute (SaaSS)</a> from denying users'
+freedom—but most servers don't do SaaSS. For more about these
+issues, read <a href="/licenses/why-affero-gpl.html">“Why the
+Affero GPL”</a>.</p>
+
+<h3 id="documentation">Documentation</h3>
+
+<p>We recommend the <a href="/licenses/fdl.html">GNU Free
+Documentation License (GFDL)</a> for tutorials, reference manuals and
+other large works of documentation. It's a strong copyleft license
+for educational works, initially written for software manuals, and
+includes terms which specifically address common issues that arise
+when those works are distributed or modified.</p>
+
+<p>For short, secondary documentation works, such as a reference card,
+it is better to use
+the <a href="/licenses/license-list.html#GNUAllPermissive"> GNU
+all-permissive license</a>, since a copy of the GFDL could hardly fit
+in a reference card. Don't use CC-BY, since it is incompatible with
+the GFDL.</p>
+
+<p>For man pages, we recommend the GFDL if the page is long, and
+the <a href="/licenses/license-list.html#GNUAllPermissive"> GNU
+all-permissive license</a> if it is short.</p>
+
+<p>Some documentation includes software source code. For instance, a
manual
+for a programming language might include examples for readers to follow.
+You should both include these in the manual under the FDL's terms, and
+release them under another license that's appropriate for software. Doing
+so helps make it easy to use the code in other projects. We recommend that
+you dedicate small pieces of code to the public domain using <a
href="http://creativecommons.org/about/cc0">CC0</a>, and
+distribute larger pieces under the same license that the associated
+software project uses.</p>
+
+<h3 id="data">Other data for programs</h3>
+
+<p>This section discusses all other works for practical use that you
+might include with software. To give you some examples, this includes
+icons and other functional or useful graphics, fonts, and geographic
+data. You can also follow them for art, though we wouldn't criticize
+if you don't.</p>
+
+<p>If you are creating these works specifically for use with a software
+project, we generally recommend that you release your work under the
+same license as the software. There is no problem in doing so
+with the licenses we have recommended:
+GPLv3, LGPLv3, AGPLv3, and GPLv2 can all be applied to any kind of
+work—not just software—that is copyrightable and has a clear
+preferred form for modification. Using the same license as the
+software will help make compliance easier for distributors, and avoids
+any doubt about potential compatibility issues. Using a different
+free license may be appropriate if it provides some specific practical
+benefit, like better cooperation with other free projects.</p>
+
+<p>If your work is not being created for use with a particular software
+project, or if it wouldn't be appropriate to use the same license as
+the project, then we only recommend that you choose a copyleft license
+that's appropriate for your work. We have some of these <a
href="/licenses/license-list.html#OtherLicenses">listed on
+our license list</a>. If no license seems especially
+appropriate, the <a href="/licenses/license-list.html#ccbysa">Creative
Commons Attribution-ShareAlike</a>
+license is a copyleft that can be used for many different kinds of
+works.</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 © 2011, 2013, 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 19:59:11 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
Index: po/license-recommendations.ja-diff.html
===================================================================
RCS file: po/license-recommendations.ja-diff.html
diff -N po/license-recommendations.ja-diff.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/license-recommendations.ja-diff.html 15 Dec 2017 19:59:11 -0000
1.1
@@ -0,0 +1,311 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
+<!-- Generated by GNUN -->
+<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en" lang="en">
+<head>
+<meta http-equiv="content-type" content="text/html; charset=utf-8" />
+<title>/licenses/license-recommendations.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>How to choose a license for your own work
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/licenses/po/license-recommendations.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>How to choose a license for your own work</h2>
+
+<!--#include virtual="/licenses/fsf-licensing.html" -->
+
+<blockquote><p>
+To see whether a given license is free or not,
+see <a href="/licenses/license-list.html">our license list page</a>
+and the <a href="/philosophy/free-sw.html">definition of free
software</a>.
+</p></blockquote>
+
+<h3 id="intro">Introduction</h3>
+
+<p>People often ask us what license we recommend they use for their
+project. We've written about this publicly before, but the
+information has been scattered around between different essays, FAQ
+entries, and license commentaries. This article collects all that
+information into a single source, to make it easier for people to
+follow and refer back to.</p>
+
+<p>These recommendations are for works designed to do practical jobs.
+Those include software, documentation, and some other things. Works of
+art, and works that state a point of view, are different issues; the GNU
+Project has no general stand about how they should be released, except
+that they should all be usable without nonfree software (in
+particular, <a href="http://defectivebydesign.org/">without
DRM</a>).
+However, you might want to follow these recommendations for art works
+that go with a particular program.</p>
+
+<p>The recommendations apply to licensing a work that you
+create—whether that's a modification of an existing work, or a
+new original work. They do not address the issue of combining
+existing material under different licenses. If you're looking for
+help with that, please check <a href="/licenses/gpl-faq.html">our GPL
+FAQ</a>.</p>
+
+<p>After you see what we recommend here, if you'd like advice, you can
+write
+to <a href="mailto:address@hidden"><address@hidden></a>.
+Note that it will probably take a few weeks for the licensing team to
+get back to you; if you get no response in a month, please write
+again.</p>
+
+<h3 id="contributing">Contributing to an existing project</h3>
+
+<p>When you contribute to an existing project, you should usually release
+your modified versions under the same license as the original work.
+It's good to cooperate with the project's maintainers, and using a
+different license for your modifications often makes that cooperation
+very difficult. You should only do that when there is a strong reason
+to justify it.</p>
+
+<p>One case where using a different license can be justified is when you
make
+major changes to a work under a non-copyleft license. If the version you've
+created is considerably more useful than the original, then it's worth
+copylefting your work, for all the same
+<a href="/copyleft/copyleft.html">reasons we normally recommend
+copyleft</a>. If you are in this situation, please follow the
+recommendations below for licensing a new project.</p>
+
+<p>If you choose to release your contributions under a different
+license for whatever reason, you must make sure that the original
+license allows use of the material under your chosen license. For
+honesty's sake, show explicitly which parts of the work are under
+which license.</p>
+
+<h3 id="software">Software</h3>
+
+<p>We recommend different licenses for different projects, depending
+mostly on the software's purpose. In general, we recommend using the
+strongest copyleft license that doesn't interfere with that purpose.
+Our essay <a href="/copyleft/copyleft.html">“What
+is Copyleft?”</a> explains the
+concept of copyleft in more detail, and why it is generally the best
+licensing strategy.</p>
+
+<p>For most programs, we recommend that you use the most recent
+version of the <a href="/licenses/gpl.html">GNU General Public License
+(GPL)</a> for your project. Its strong copyleft is appropriate for
+all kinds of software, and includes numerous protections for users'
+<span class="removed"><del><strong>freedom.</p></strong></del></span>
+<span class="inserted"><ins><em>freedom. Please give permission to use future
license versions as
+well—in other words, make the license notice say that your
+program is covered by GPL version 3 or later.</p>
+
+<p>Here is more advice about <a href="/licenses/gpl-howto.html">how
+to release a program under the GNU GPL</a>.</p></em></ins></span>
+
+<p>Now for the <span
class="removed"><del><strong>exceptions.</p></strong></del></span> <span
class="inserted"><ins><em>exceptions, where it is better to use some other
+licenses instead of the GNU GPL.</p></em></ins></span>
+
+<h4 id="small">Small programs</h4>
+
+<p>It is not worth the trouble to use copyleft for most small
+programs. We use 300 lines as our benchmark: when a software
+package's source code is shorter than that, the benefits provided by
+copyleft are usually too small to justify the inconvenience of making
+sure a copy of the license always accompanies the software.</p>
+
+<p>For those programs, we recommend
+the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+License 2.0</a>. This is a pushover (non-copyleft) software license
+that has terms to prevent contributors and distributors from suing for
+patent infringement. This doesn't make the software immune to threats
+from patents (a software license can't do that), but it does prevent
+patent holders from setting up a “bait and switch” where
+they release the software under free terms then require recipients to
+agree to nonfree terms in a patent license.</p>
+
+<p>Among the lax pushover licenses, Apache 2.0 is best; so if you
+are going to use a lax pushover license, whatever the reason,
+we recommend using that one.</p>
+
+<h4 id="libraries">Libraries</h4>
+
+<p>For libraries, we distinguish three kind of cases.</p>
+
+<p>Some libraries implement free standards that are competing against
+restricted standards, such as Ogg Vorbis (which competes against MP3
+audio) and WebM (which competes against MPEG-4 video). For these
+projects, widespread use of the code is vital for advancing the cause
+of free software, and does more good than a copyleft on the project's
+code would do.</p>
+
+<p>In these special situations, we recommend
+the <a href="http://www.apache.org/licenses/LICENSE-2.0">Apache
+License 2.0</a>.</p>
+
+<p>For all other libraries, we recommend some kind of copyleft. If
+developers are already using an established alternative library
+released under a nonfree license or a lax pushover license, then we
+recommend using the <a href="/licenses/lgpl.html">GNU Lesser General
+Public License (LGPL)</a>.</p>
+
+<p>Unlike the first case, where the library implements an ethically
+superior standard, here adoption for its own sake will not accomplish
+any special objective goal, so there's no reason to avoid copyleft
+entirely. However, if you require developers who use your library to
+release their whole programs under copyleft, they'll simply use one of
+the alternatives available, and that won't advance our cause either.
+The Lesser GPL was designed to fill the middle ground between these
+cases, allowing proprietary software developers to use the covered
+library, but providing a weak copyleft that gives users freedom
+regarding the library code itself.</p>
+
+<p>For libraries that provide specialized facilities, and which do not
+face entrenched noncopylefted or nonfree competition, we recommend
+using the plain GNU GPL. For the reasons why,
+read <a href="/licenses/why-not-lgpl.html">“Why you shouldn't
+use the Lesser GPL for your next library”</a>.</p>
+
+<h4 id="server">Server Software</h4>
+
+<p>If it is likely that others will make improved versions of your
+program to run on servers and not distribute their versions to anyone
+else, and you're concerned that this will put your released version at
+a disadvantage, we recommend the <a href="/licenses/agpl.html">GNU
+Affero General Public License (AGPL)</a>. The AGPL's terms are almost
+identical to the GPL's; the sole substantive difference is that it has
+an extra condition to ensure that people who use the software over a
+network will be able to get the source code for it.</p>
+
+<p>The AGPL's requirement doesn't address the problems that can arise
+<em>for users</em> when they entrust their computing or their data
to
+someone else's server. For instance, it won't stop
+<a href="/philosophy/who-does-that-server-really-serve.html">Service
+as a Software Substitute (SaaSS)</a> from denying users'
+freedom—but most servers don't do SaaSS. For more about these
+issues, read <a href="/licenses/why-affero-gpl.html">“Why the
+Affero GPL”</a>.</p>
+
+<h3 id="documentation">Documentation</h3>
+
+<p>We recommend the <a href="/licenses/fdl.html">GNU Free
+Documentation License (GFDL)</a> for tutorials, reference manuals and
+other large works of documentation. It's a strong copyleft license
+for educational works, initially written for software manuals, and
+includes terms which specifically address common issues that arise
+when those works are distributed or modified.</p>
+
+<p>For short, secondary documentation works, such as a reference card,
+it is better to use
+the <a href="/licenses/license-list.html#GNUAllPermissive"> GNU
+all-permissive license</a>, since a copy of the GFDL could hardly fit
+in a reference card. Don't use CC-BY, since it is incompatible with
+the GFDL.</p>
+
+<p>For man pages, we recommend the GFDL if the page is long, and
+the <a href="/licenses/license-list.html#GNUAllPermissive"> GNU
+all-permissive license</a> if it is short.</p>
+
+<p>Some documentation includes software source code. For instance, a
manual
+for a programming language might include examples for readers to follow.
+You should both include these in the manual under the FDL's terms, and
+release them under another license that's appropriate for software. Doing
+so helps make it easy to use the code in other projects. We recommend that
+you dedicate small pieces of code to the public domain using <a
href="http://creativecommons.org/about/cc0">CC0</a>, and
+distribute larger pieces under the same license that the associated
+software project uses.</p>
+
+<h3 id="data">Other data for programs</h3>
+
+<p>This section discusses all other works for practical use that you
+might include with software. To give you some examples, this includes
+icons and other functional or useful graphics, fonts, and geographic
+data. You can also follow them for art, though we wouldn't criticize
+if you don't.</p>
+
+<p>If you are creating these works specifically for use with a software
+project, we generally recommend that you release your work under the
+same license as the software. There is no problem in doing so
+with the licenses we have recommended:
+GPLv3, LGPLv3, AGPLv3, and GPLv2 can all be applied to any kind of
+work—not just software—that is copyrightable and has a clear
+preferred form for modification. Using the same license as the
+software will help make compliance easier for distributors, and avoids
+any doubt about potential compatibility issues. Using a different
+free license may be appropriate if it provides some specific practical
+benefit, like better cooperation with other free projects.</p>
+
+<p>If your work is not being created for use with a particular software
+project, or if it wouldn't be appropriate to use the same license as
+the project, then we only recommend that you choose a copyleft license
+that's appropriate for your work. We have some of these <a
href="/licenses/license-list.html#OtherLicenses">listed on
+our license list</a>. If no license seems especially
+appropriate, the <a href="/licenses/license-list.html#ccbysa">Creative
Commons Attribution-ShareAlike</a>
+license is a copyleft that can be used for many different kinds of
+works.</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 © 2011, 2013, 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 19:59:11 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+</pre></body></html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/licenses license-list.it.html license-recom...,
GNUN <=