[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses po/license-compatibility.translist...
From: |
GNUN |
Subject: |
www/licenses po/license-compatibility.translist... |
Date: |
Wed, 31 Aug 2016 12:57:56 +0000 (UTC) |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 16/08/31 12:57:56
Modified files:
licenses/po : license-compatibility.translist
Added files:
licenses : license-compatibility.ru.html
licenses/po : license-compatibility.ru-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/license-compatibility.ru.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-compatibility.translist?cvsroot=www&r1=1.2&r2=1.3
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/license-compatibility.ru-en.html?cvsroot=www&rev=1.1
Patches:
Index: po/license-compatibility.translist
===================================================================
RCS file: /web/www/www/licenses/po/license-compatibility.translist,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -b -r1.2 -r1.3
--- po/license-compatibility.translist 29 Feb 2016 01:36:34 -0000 1.2
+++ po/license-compatibility.translist 31 Aug 2016 12:57:55 -0000 1.3
@@ -4,9 +4,11 @@
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/licenses/license-compatibility.en.html">English</a> [en]</span>
<span dir="ltr"><a lang="fr" hreflang="fr"
href="/licenses/license-compatibility.fr.html">français</a> [fr]</span>
+<span dir="ltr"><a lang="ru" hreflang="ru"
href="/licenses/license-compatibility.ru.html">ÑÑÑÑкий</a> [ru]</span>
</p>
</div>' -->
<link rel="alternate" type="text/html"
href="/licenses/license-compatibility.html" hreflang="x-default" />
<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/licenses/license-compatibility.en.html" title="English" />
<link rel="alternate" type="text/html" lang="fr" hreflang="fr"
href="/licenses/license-compatibility.fr.html" title="français" />
+<link rel="alternate" type="text/html" lang="ru" hreflang="ru"
href="/licenses/license-compatibility.ru.html" title="ÑÑÑÑкий" />
<!-- end translist file -->
Index: license-compatibility.ru.html
===================================================================
RCS file: license-compatibility.ru.html
diff -N license-compatibility.ru.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ license-compatibility.ru.html 31 Aug 2016 12:57:55 -0000 1.1
@@ -0,0 +1,351 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/license-compatibility.en.html" -->
+
+<!--#include virtual="/server/header.ru.html" -->
+<!-- Parent-Version: 1.79 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>СовмеÑÑимоÑÑÑ Ð»Ð¸Ñензий и
пеÑелиÑензиÑование - ÐÑÐ¾ÐµÐºÑ GNU - Фонд
Ñвободного
+пÑогÑаммного обеÑпеÑениÑ</title>
+
+<!--#include virtual="/licenses/po/license-compatibility.translist" -->
+<!--#include virtual="/server/banner.ru.html" -->
+<h2>СовмеÑÑимоÑÑÑ Ð»Ð¸Ñензий и
пеÑелиÑензиÑование</h2>
+
+<p>РиÑаÑд СÑолмен</p>
+
+<p>ÐÑли Ð²Ñ Ñ
оÑиÑе ÑложиÑÑ Ð´Ð²Ðµ ÑвободнÑÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð² Ð¾Ð´Ð½Ñ Ð¸Ð»Ð¸ влиÑÑ Ð¸ÑÑ
однÑй
+ÑекÑÑ Ð¸Ð· одной в дÑÑгÑÑ, вÑÑÐ°ÐµÑ Ð²Ð¾Ð¿ÑоÑ,
позволÑÑÑ Ð»Ð¸ ÑÑо иÑ
лиÑензии.</p>
+
+<p>ÐÑли Ñ Ð¿ÑогÑамм одна и Ñа же лиÑензиÑ,
пÑоблем не возникаеÑ, еÑли лиÑензиÑ
+ÑоÑÑавлена ÑазÑмно, как поÑÑи вÑе лиÑензии
ÑвободнÑÑ
пÑогÑамм.<a
+href="#f1">(*)</a></p>
+
+<p>Ðо ÑÑо, еÑли лиÑензии ÑазнÑе? РобÑем мÑ
можем ÑказаÑÑ, ÑÑо неÑколÑко
+лиÑензий <em>ÑовмеÑÑимÑ</em>, еÑли еÑÑÑ ÑпоÑоб
ÑоединÑÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ ÑÑими
+ÑазнÑми лиÑензиÑми, ÑдовлеÑвоÑÑÑ Ð¸Ð¼ вÑем.
Ð ÑезÑлÑÑаÑе неÑедко полÑÑаеÑÑÑ
+пÑогÑамма, ÑаÑÑи коÑоÑой ÑаÑпÑоÑÑÑанÑÑÑÑÑ
под ÑазнÑми ÑовмеÑÑимÑми
+лиÑензиÑми — но не вÑегда. ТакаÑ
ÑоÑеÑаемоÑÑÑ Ð¸Ð»Ð¸ ее оÑÑÑÑÑÑвие
+Ñ
аÑакÑеÑизÑÐµÑ Ð´Ð°Ð½Ð½Ð¾Ðµ множеÑÑво лиÑензий и
не завиÑÐ¸Ñ Ð¾Ñ Ñого, в каком
+поÑÑдке они пеÑеÑиÑлÑÑÑÑÑ. ÐножеÑÑво
лиÑензий Ñакже дикÑÑÐµÑ ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ðº
+лиÑензии ÑовмеÑенной пÑогÑаммÑ.</p>
+
+<p>ÐÑ Ð´ÐµÐ»Ð¸Ð¼ лиÑензии на ÑÑи клаÑÑа:
либеÑалÑнÑе
+(“неогÑаниÑиÑелÑнÑе” или
“безволÑнÑе”),
+пÑомежÑÑоÑнÑе и лиÑензии Ñ Ð°Ð²ÑоÑÑким
левом. ÐибеÑалÑнÑе лиÑензии ниÑем не
+меÑаÑÑ Ð¾Ð±ÑаÑÐµÐ½Ð¸Ñ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð² неÑвободнÑÑ.
ÐиÑензии Ñ Ð°Ð²ÑоÑÑким левом
+запÑеÑаÑÑ ÑÑо, ÑÑебÑÑ, ÑÑÐ¾Ð±Ñ Ð²ÑÑкое
повÑоÑное иÑполÑзование бÑло в
+пÑогÑаммаÑ
под Ñой же лиÑензией.
ÐÑомежÑÑоÑнÑе лиÑензии налагаÑÑ Ð½ÐµÐºÐ¾ÑоÑÑе
+ÑÑÐ»Ð¾Ð²Ð¸Ñ Ð½Ð° добавление неÑвободнÑÑ
пÑогÑамм, но не пÑÑаÑÑÑÑ Ð·Ð°Ð¿ÑеÑаÑÑ ÑÑо.</p>
+
+<p>Ð Ñелом либеÑалÑнÑе неогÑаниÑиÑелÑнÑе
лиÑензии (Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ BSD,
+X11, Expat, Apache, Python и Ñ.д.) ÑовмеÑÑÐ¸Ð¼Ñ Ð´ÑÑг Ñ
дÑÑгом. Ðело в Ñом, ÑÑо
+в ниÑ
Ð½ÐµÑ ÑÑебований к дÑÑгим ÑекÑÑам,
коÑоÑÑе добавлÑÑÑÑÑ Ðº пÑогÑамме. Ðни
+даже допÑÑкаÑÑ Ð¾Ð±ÑаÑение вÑей пÑогÑаммÑ
(возможно, Ñ Ð¸Ð·Ð¼ÐµÐ½ÐµÐ½Ð¸Ñми) в
+неÑвободнÑй пÑогÑаммнÑй пÑодÑкÑ; Ñаким
обÑазом, Ð¼Ñ Ð½Ð°Ð·Ñваем иÑ
+“безволÑнÑми лиÑензиÑми”, поÑÐ¾Ð¼Ñ ÑÑо
они не говоÑÑÑ
+“неє, когда один полÑзоваÑелÑ
пÑÑаеÑÑÑ Ð¾ÑказаÑÑ Ð² Ñвободе
+дÑÑгим.</p>
+
+<p>РкомбиниÑованной пÑогÑамме под
либеÑалÑнÑми лиÑензиÑми ÐºÐ°Ð¶Ð´Ð°Ñ ÑаÑÑÑ
+оÑÑаеÑÑÑ Ð¿Ð¾Ð´ Ñвоей лиÑензией. Ðогда
пÑогÑÐ°Ð¼Ð¼Ñ ÑливаÑÑÑÑ Ð´Ð¾ Ñакой ÑÑепени,
+ÑÑо ÑаÑÑи Ñже невозможно ÑазлиÑиÑÑ, ÑÑи
ÑлиÑÑе ÑекÑÑÑ Ð´Ð¾Ð»Ð¶Ð½Ñ Ð½ÐµÑÑи на Ñебе
+вÑе лиÑензии ÑоединеннÑÑ
ÑаÑÑей.
ÐоÑколÑÐºÑ Ð²Ñе ÑÑи лиÑензии вÑе Ñавно
+либеÑалÑнÑ, ÑÑо не пÑедÑÑавлÑеÑ
пÑакÑиÑеÑкой пÑоблемÑ, Ñазве ÑÑо ÑпиÑок
+лиÑензий ÑазÑаÑÑаеÑÑÑ.<a href="#f2">(**)</a></p>
+
+<p>ÐодобнÑм же обÑазом, либеÑалÑнÑе
лиÑензии обÑÑно ÑовмеÑÑÐ¸Ð¼Ñ Ñо вÑÑкой
+лиÑензией Ñ Ð°Ð²ÑоÑÑким левом. Ð
обÑединенной пÑогÑамме ÑаÑÑи, коÑоÑÑе бÑли
+под либеÑалÑнÑми лиÑензиÑми, по-пÑежнемÑ
наÑ
одÑÑÑÑ Ð¿Ð¾Ð´ ними, но вÑÑ
+пÑогÑамма в Ñелом неÑÐµÑ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ Ñ
авÑоÑÑким левом. Родной либеÑалÑной
+лиÑензии, Apache 2.0, еÑÑÑ Ð¿Ð°ÑенÑнÑе пÑнкÑÑ,
неÑовмеÑÑимÑе Ñ GPL
+веÑÑии 2; поÑколÑÐºÑ Ñ Ð´ÑмаÑ, ÑÑо Ñакие
пÑнкÑÑ Ð¿Ð¾Ð»ÐµÐ·Ð½Ñ, Ñ Ñделал
+веÑÑÐ¸Ñ 3 GPL ÑовмеÑÑимой Ñ Ð½Ð¸Ð¼Ð¸.</p>
+
+<p>ÐдинÑÑвенное важное иÑклÑÑение
пÑедÑÑавлÑÐµÑ Ð¿ÐµÑвонаÑалÑÐ½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ BSD,
+из-за “злоÑÑного пÑнкÑа о Ñекламе”.
ÐÑо ÑÑловие ÑÑебовало
+оÑобого ÑÐ²ÐµÐ´Ð¾Ð¼Ð»ÐµÐ½Ð¸Ñ Ð²Ð¾ <em>вÑей</em> Ñекламе
<em>вÑÑкого</em> пÑодÑкÑа,
+ÑодеÑжаÑего <em>лÑбÑе</em> ÑаÑÑи пÑогÑамм,
вÑпÑÑеннÑÑ
под пеÑвонаÑалÑной
+лиÑензией BSD. ÐÑо бÑло (и еÑÑÑ) неÑовмеÑÑимо
Ñо вÑеми дейÑÑвÑÑÑими
+лиÑензиÑми Ñ Ð°Ð²ÑоÑÑким левом. ÐÑо Ñакже
Ð³Ð¾Ð»Ð¾Ð²Ð½Ð°Ñ Ð±Ð¾Ð»Ñ Ð´Ð»Ñ Ð»Ñбого
+диÑÑÑибÑÑива, поÑколÑÐºÑ ÑкапливаÑÑÑÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ñо ÑÑ
однÑми, но ÑазнÑми
+ÑÑебованиÑми к Ñекламе. Ркакой-Ñо моменÑ
диÑÑÑибÑÑив BSD ÑÑебовал ÑвÑÑе 70
+ÑазлиÑнÑÑ
Ñведомлений.</p>
+
+<p>Я по болÑÑей ÑаÑÑи ÑÑÑÑанил ÑÑÑ Ð¿ÑоблемÑ,
Ñбедив декана, Ðела ÐеÑиÑна,
+оÑганизоваÑÑ Ð¿ÑбликаÑÐ¸Ñ ÐалиÑоÑнийÑким
ÑнивеÑÑиÑеÑом в ÐеÑкли
+“модиÑиÑиÑованной лиÑензии BSD” (без
пÑнкÑа о Ñекламе) и
+пеÑевÑпÑÑка пÑогÑамм BSD под ÑÑой
лиÑензией. Ð¡ÐµÐ³Ð¾Ð´Ð½Ñ Ð¿ÐµÑвонаÑалÑÐ½Ð°Ñ Ð»Ð¸ÑензиÑ
+BSD (к ÑÑаÑÑÑÑ) пÑакÑиÑеÑки не пÑименÑеÑÑÑ,
но Ð¼Ñ Ð´Ð¾ ÑиÑ
Ð¿Ð¾Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
+пÑинимаÑÑ Ð¼ÐµÑÑ, ÑÑÐ¾Ð±Ñ <a href="/licenses/bsd.html">не
говоÑиÑÑ Ð¾
+(“единÑÑвенной”) лиÑензии BSD</a>.</p>
+
+<p>РобÑем и Ñелом, две ÑазнÑе лиÑензии Ñ
авÑоÑÑким левом неизбежно
+неÑовмеÑÑимÑ, еÑли ÑовмеÑÑимоÑÑÑ Ð½Ðµ
оговоÑена в ниÑ
ÑвнÑм обÑазом. ÐÑо не
+ÑвÑзано Ñ Ð¾Ñибкой в деÑалÑÑ
; ÑÑо ÑледÑÑвие
пÑинÑипов авÑоÑÑкого лева. СÑÑÑ
+авÑоÑÑкого лева заклÑÑаеÑÑÑ Ð² Ñом, ÑÑо
“измененнÑе и ÑаÑÑиÑеннÑе
+веÑÑии Ð´Ð¾Ð»Ð¶Ð½Ñ Ð±ÑÑÑ Ð¿Ð¾Ð´ Ñой же Ñамой
лиÑензией”. ÐÑли в лиÑензии Ð
+Ñказано, ÑÑо ÑаÑÑиÑеннÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
бÑÑÑ Ð¿Ð¾Ð´ лиÑензией Ð, а в лиÑензии
+Ð Ñказано, ÑÑо ÑаÑÑиÑеннÑе пÑогÑаммÑ
Ð´Ð¾Ð»Ð¶Ð½Ñ Ð±ÑÑÑ Ð¿Ð¾Ð´ лиÑензией Ð, Ñо ÑÑо
+неÑÑÑÑанимое ÑазноглаÑие; лиÑензиÑ
ÑовмеÑенной пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð¾Ð»Ð¶Ð½Ð° бÑÑÑ
+лиÑензией Ð <em>и</em> она должна бÑÑÑ
лиÑензией Ð. ÐÐ¾Ñ Ð¿Ð¾ÑÐµÐ¼Ñ GPL
+веÑÑии 2 неÑовмеÑÑима Ñ GPL веÑÑии 3;
избежаÑÑ ÑÑого бÑло
+невозможно. ТоÑно Ñак же ÑÑловиÑ
CC BY-SA 4.0 бÑли бÑ
+пÑинÑипиалÑно неÑовмеÑÑÐ¸Ð¼Ñ Ñ ÑÑловиÑми
CC BY-SA 3.0, и авÑоÑам не
+ÑдалоÑÑ Ð±Ñ ÑÑого избежаÑÑ.</p>
+
+<p>ЧÑÐ¾Ð±Ñ ÑгладиÑÑ Ð½ÐµÑовмеÑÑимоÑÑÑ,
пÑиÑÑÑÑÑ Ð½Ð¾Ð²Ñм веÑÑиÑм лиÑензий Ñ
авÑоÑÑким
+левом, еÑÑÑ Ð´Ð²Ð° подÑ
ода.</p>
+
+<p>ÐодÑ
од ФСÐÐ ÑоÑÑÐ¾Ð¸Ñ Ð² Ñом, ÑÑÐ¾Ð±Ñ Ð¿ÑоÑиÑÑ
лÑдей вÑпÑÑкаÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´
+“GNU GPL веÑÑии N или лÑбой более
поздней”. ÐÑо ÑовмеÑÑимо Ñ
+веÑÑией N, а Ñакже N+1 (поÑÐ¾Ð¼Ñ ÑÑо веÑÑÐ¸Ñ N+1
пÑедлагаеÑÑÑ ÐºÐ°Ðº
+ваÑианÑ). Ðогда Ð²Ñ Ð¾Ð±ÑединÑеÑе пÑогÑаммÑ
под “GPL веÑÑии 3 или
+более поздней” Ñ Ð¿ÑогÑаммами под “GPL
веÑÑии 2 или более
+поздней”, лиÑÐµÐ½Ð·Ð¸Ñ Ð¾Ð±Ñединенной
пÑогÑÐ°Ð¼Ð¼Ñ ÑвлÑеÑÑÑ Ð¸Ñ
пеÑеÑеÑением, Ñо
+еÑÑÑ “GPL веÑÑии 3 или более
поздней”.</p>
+
+<p>ÐÑ Ð½Ð°Ð´ÐµÐµÐ¼ÑÑ, ÑÑо нам никогда не
поÑÑебÑеÑÑÑ GNU GPL веÑÑии 4, но ниÑÑо
+не ÑовеÑÑенно, Ñак ÑÑо Ð¼Ñ Ð½Ðµ можем
ÑаÑÑÑиÑÑваÑÑ, ÑÑо пÑедÑÑмоÑÑели
+вÑе. ÐÑпÑÑÐºÐ°Ñ Ñвои пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GNU GPL
веÑÑии 3 или более поздней, вÑ
+ÑазÑеÑаеÑе обновление до GNU GPL веÑÑии 4,
еÑли она нам поÑÑебÑеÑÑÑ.</p>
+
+<p>ÐÑÑгой подÑ
од ÑоÑÑÐ¾Ð¸Ñ Ð² Ñом, ÑÑÐ¾Ð±Ñ Ð²
каждой веÑÑии лиÑензии ÑвнÑм обÑазом
+допÑÑкаÑÑ Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ðµ до более поздниÑ
веÑÑий. ÐÑо-Ñо и Ð´ÐµÐ»Ð°ÐµÑ Creative
+Commons: напÑимеÑ, в CC BY-SA веÑÑии 4.0
(ÑекÑÑей веÑÑии) лÑбомÑ
+полÑзоваÑÐµÐ»Ñ ÑвнÑм обÑазом ÑазÑеÑено
обновлÑÑÑÑÑ Ð´Ð¾ более поздниÑ
веÑÑий
+CC BY-SA, как ÑолÑко они поÑвÑÑÑÑ. Mozilla Foundation
Ñакже полÑзÑеÑÑÑ
+ÑÑим подÑ
одом.</p>
+
+<p>ТолÑко лиÑензии GNU пÑедоÑÑавлÑÑÑ Ð°Ð²ÑоÑам
вÑбиÑаÑÑ, ÑазÑеÑиÑÑ Ð»Ð¸ обновление
+до бÑдÑÑиÑ
веÑÑий лиÑензии. Ðогда
в 1989 Ð³Ð¾Ð´Ñ Ñ Ð¿Ð¸Ñал пеÑвÑÑ
+веÑÑÐ¸Ñ GNU GPL, Ñ ÑаÑÑмаÑÑивал возможноÑÑÑ
обновлÑÑÑ Ð»Ð¸ÑензиÑ, как ÑÑо
+делаеÑÑÑ Ð² лиÑензиÑÑ
Creative Commons, но Ñ
подÑмал, ÑÑо пÑавилÑнее оÑÑавиÑÑ
+ÑÑо на вÑÐ±Ð¾Ñ ÐºÐ°Ð¶Ð´Ð¾Ð¼Ñ Ð°Ð²ÑоÑÑ. Таким обÑазом,
авÑÐ¾Ñ Ð¼Ð¾Ð³ вÑпÑÑкаÑÑ Ð¿ÑогÑаммÑ
+либо “ÑолÑко под GPL веÑÑии 1”, либо
под “GPL
+веÑÑии 1 или более поздней”.</p>
+
+<p>ÐÑоÑло вÑемÑ, и Ñ ÑÑал ÑомневаÑÑÑÑ Ð²
мÑдÑоÑÑи ÑÑого ÑеÑениÑ. Такие
+пÑогÑаммÑ, как Linux, коÑоÑÑе допÑÑкаÑÑ
ÑолÑко Ð¾Ð´Ð½Ñ Ð²ÐµÑÑÐ¸Ñ GNU GPL и
+оÑвеÑгаÑÑ Ð¾Ð±Ð½Ð¾Ð²Ð»ÐµÐ½Ð¸Ñ, на пÑакÑике
пÑиводÑÑ Ðº неÑовмеÑÑимоÑÑи.<a
+href="#f3">(***)</a> Ðозможно, нам ÑледÑÐµÑ Ð²ÐºÐ»ÑÑиÑÑ
пÑÐ½ÐºÑ Ð¾Ð± обновлении в
+GPL веÑÑии 4, еÑли веÑÑÐ¸Ñ 4 нам
когда-нибÑÐ´Ñ Ð¿Ð¾Ð½Ð°Ð´Ð¾Ð±Ð¸ÑÑÑ.</p>
+
+<p>ÐекоÑоÑÑе лиÑензии Ñ Ð°Ð²ÑоÑÑким левом
допÑÑкаÑÑ ÑоÑеÑÐ°Ð½Ð¸Ñ Ð¿ÑогÑамм под ÑазнÑм
+авÑоÑÑким левом Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ Ñвного пÑнкÑа о
пеÑелиÑензиÑовании, даÑÑего
+ÑазÑеÑение помеÑаÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ дÑÑгÑÑ
лиÑÐµÐ½Ð·Ð¸Ñ Ñ Ð°Ð²ÑоÑÑким
+левом. ÐапÑимеÑ, в CeCILL даеÑÑÑ Ñвное
ÑазÑеÑение пеÑелиÑензиÑоваÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ GNU GPL веÑÑии 2 и более
поздниÑ
. ÐÑли пÑогÑамма Ð
+ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð¿Ð¾ CeCILL, а Ð²Ñ Ñ
оÑиÑе
ÑовмеÑÑиÑÑ ÐµÐµ Ñ Ð¿ÑогÑаммой Ð,
+коÑоÑÐ°Ñ ÑаÑпÑоÑÑÑанÑеÑÑÑ Ð¿Ð¾ GPL веÑÑии 3
или более поздней, Ñо в CeCILL
+Ñказано, ÑÑо ÑÑо допÑÑÑимо и ÑÑо
обÑединеннÑе пÑогÑÐ°Ð¼Ð¼Ñ Ð´Ð¾Ð»Ð¶Ð½Ñ
+ÑаÑпÑоÑÑÑанÑÑÑÑÑ Ð¿Ð¾ GPL веÑÑии 3 или
более поздней.</p>
+
+<p>Явное ÑазÑеÑение
пеÑелиÑензиÑоваÑÑ — ÑÑо не Ñо же
Ñамое, ÑÑо
+ÑовмеÑÑимоÑÑÑ (Ñ
оÑÑ Ð¿ÐµÑелиÑензиÑование
Ð¼Ð¾Ð¶ÐµÑ ÑделаÑÑ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ ÑовмеÑÑимой Ñ
+лиÑензией дÑÑгой пÑогÑаммÑ), и оно не
взаимно. ÐапÑимеÑ, в CeCILL даеÑÑÑ
+Ñвное ÑазÑеÑение пеÑелиÑензиÑоваÑÑ
пÑогÑÐ°Ð¼Ð¼Ñ Ð½Ð° GNU GPL, но GNU GPL не
+допÑÑÐºÐ°ÐµÑ Ð¿ÐµÑелиÑензиÑование на CeCILL.
Таким обÑазом, нелÑÐ·Ñ Ð¾Ð±ÑединиÑÑ ÑÑи
+две пÑогÑÐ°Ð¼Ð¼Ñ Ð Ð¸ Ри ÑаÑпÑоÑÑÑанÑÑÑ
ÑезÑлÑÑÐ°Ñ Ð¿Ð¾Ð´ CeCILL; ÑÑо бÑло бÑ
+наÑÑÑением GPL в оÑноÑении пÑогÑÐ°Ð¼Ð¼Ñ Ð. ÐÑÑ
обÑединеннÑÑ Ð¿ÑогÑÐ°Ð¼Ð¼Ñ ÑазÑеÑено
+вÑпÑÑкаÑÑ ÑолÑко под GPL ÑооÑвеÑÑÑвÑÑÑиÑ
веÑÑий.</p>
+
+<p>ÐодобнÑм обÑазом CC BY-SA 4.0 Ñвно
ÑазÑеÑÐ°ÐµÑ Ð¿ÐµÑелиÑензиÑование
+измененнÑÑ
веÑÑий на GNU GPL веÑÑии 3, но GPL
веÑÑии 3 не
+допÑÑÐºÐ°ÐµÑ Ð¿ÐµÑелиÑензиÑÐ¾Ð²Ð°Ð½Ð¸Ñ Ð½Ð° CC BY-SA.
ÐÐ»Ñ Ð¿ÑогÑамм ÑÑо никогда не
+должно бÑÑÑ Ð¿Ñоблемой; по заÑÐ²Ð»ÐµÐ½Ð¸Ñ Creative
Commons, его лиÑензии не
+пÑедназнаÑÐµÐ½Ñ Ð´Ð»Ñ Ð¿ÑогÑамм, Ð´Ð»Ñ Ð½Ð¸Ñ
пÑедназнаÑена GNU GPL. Ðо еÑÑÑ ÑабоÑÑ
+дÑÑгиÑ
видов, Ñакие как ÑеÑÑежи аппаÑаÑÑÑÑ
и Ñ
ÑдожеÑÑвеннÑе вÑÑавки в
+игÑаÑ
,— в ÑÑиÑ
пÑоизведениÑÑ
иногда
поÑвлÑÑÑÑÑ Ð¿ÑедпоÑÑлки обÑединÑÑÑ
+маÑеÑиал, вÑпÑÑеннÑй под CC BY-SA, Ñ
маÑеÑиалом, вÑпÑÑеннÑм под GNU
+GPL. ÐÑо можно ÑделаÑÑ Ð±Ð»Ð°Ð³Ð¾Ð´Ð°ÑÑ ÑвномÑ
ÑазÑеÑÐµÐ½Ð¸Ñ Ð¿ÐµÑелиÑензиÑоваÑÑ Ð²
+CC BY-SA.</p>
+
+<p>Ð ÑожалениÑ, CC BY-SA 4.0 не ÑазÑеÑаеÑ
пеÑелиÑензиÑоваÑÑ Ð½Ð°
+бÑдÑÑие веÑÑии GPL. Ðам, когда вÑ
пеÑелиÑензиÑÑеÑе маÑеÑиал под
+CC BY-SA 4.0 на GPL, надо <a
+href="/licenses/rms-why-gplv3.html#future-proofing">ÑказаÑÑ ÑÐµÐ±Ñ Ð²
каÑеÑÑве
+поÑÑедника, опÑеделÑÑÑего веÑÑиÑ
лиÑензии</a>, ÑÑÐ¾Ð±Ñ ÑказаÑÑ, ÑазÑеÑÐµÐ½Ñ Ð»Ð¸
+бÑдÑÑие веÑÑии GPL Ð´Ð»Ñ ÑÑого маÑеÑиала. ÐÑли
когда-нибÑÐ´Ñ Ð±ÑÐ´ÐµÑ GPL
+веÑÑии 4 и Creative Commons ÑеÑÐ¸Ñ Ð¿Ð¾Ð·Ð²Ð¾Ð»Ð¸ÑÑ
пеÑелиÑензиÑоваÑÑ Ñ
+CC BY-SA на GPL веÑÑии 4, Ð²Ñ ÐºÐ°Ðº поÑÑедник
ÑможеÑе задним ÑиÑлом
+ÑанкÑиониÑоваÑÑ GPL веÑÑии 4 Ð´Ð»Ñ ÑÑого
пеÑелиÑензиÑованного маÑеÑиала.
+(ÐмеÑÑо ÑÑого можно Ñакже попÑоÑиÑÑ
авÑоÑов ÑÑого маÑеÑиала непоÑÑедÑÑвенно
+вÑдаÑÑ ÑазÑеÑение.)</p>
+
+<p>ÐбÑÑÐ½Ð°Ñ Ð¡ÑандаÑÑÐ½Ð°Ñ Ð¾Ð±ÑеÑÑвеннаÑ
лиÑÐµÐ½Ð·Ð¸Ñ GNU и СÑандаÑÑÐ½Ð°Ñ Ð¾Ð±ÑеÑÑвеннаÑ
+лиÑÐµÐ½Ð·Ð¸Ñ GNU ÐÑÑеÑо (GNU AGPL) пÑедÑÑавлÑÑÑ Ð´Ð²Ðµ
ÑазлиÑнÑÑ
лиÑензии Ñ
+авÑоÑÑким левом, Ñак ÑÑо они, еÑÑеÑÑвенно,
неÑовмеÑÑимÑ. ÐÑ ÑвнÑм обÑазом
+ÑÑÑановили оÑобого Ñода ÑовмеÑÑимоÑÑÑ
Ð¼ÐµÐ¶Ð´Ñ Ð½Ð¸Ð¼Ð¸: иÑÑ
однÑй ÑекÑÑ Ð¿Ð¾Ð´ GNU GPL
+веÑÑии 3 можно вклÑÑаÑÑ Ð² Ð¾Ð´Ð½Ñ Ð¿ÑогÑаммÑ
Ñ Ð´ÑÑгим иÑÑ
однÑм ÑекÑÑом,
+вÑпÑÑеннÑм под GNU GPL ÐÑÑеÑо. ÐÑо ÑазÑеÑено,
поÑÐ¾Ð¼Ñ ÑÑо в обеиÑ
лиÑензиÑÑ
+ÑÑо оговаÑиваеÑÑÑ ÑвнÑм обÑазом, и в
ÑезÑлÑÑаÑе полÑÑаеÑÑÑ Ð¿Ñоизведение, на
+коÑоÑое ÑаÑпÑоÑÑÑанÑеÑÑÑ GNU GPL ÐÑÑеÑо.
Ðднако пÑоÑÑо пеÑелиÑензиÑоваÑÑ
+пÑогÑÐ°Ð¼Ð¼Ñ Ñ GNU GPL (Ñ “более поздними
веÑÑиÑми“ или без ниÑ
) на
+GNU AGPL и наобоÑÐ¾Ñ Ð½ÐµÐ»ÑзÑ; ни одна из лиÑензий
ÑÑого не допÑÑкаеÑ. ÐбÑаÑиÑе
+Ñакже внимание, ÑÑо GNU AGPL веÑÑии 3 не
ÑвлÑеÑÑÑ “более поздней
+веÑÑией” обÑÑной GNU GPL веÑÑии 2, поÑомÑ
ÑÑо GNU AGPL и GNU GPL
+пÑедÑÑавлÑÑÑ Ð´Ð²Ð° ÑазлиÑнÑÑ
ÑÑда
лиÑензий.</p>
+
+<p>ÐенÑÑÐ°Ñ ÑÑандаÑÑÐ½Ð°Ñ Ð¾Ð±ÑеÑÑвеннаÑ
лиÑÐµÐ½Ð·Ð¸Ñ GNU веÑÑии 3 в
+дейÑÑвиÑелÑноÑÑи пÑедÑÑавлÑеÑ
СÑандаÑÑнÑÑ Ð¾Ð±ÑеÑÑвеннÑÑ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ GNU
+веÑÑии 3 Ñ Ð½ÐµÐºÐ¾ÑоÑÑми дополниÑелÑнÑми
ÑазÑеÑениÑми. Ð Ñазделе 7
+GPL веÑÑии 3 говоÑиÑÑÑ, ÑÑо
дополниÑелÑнÑе ÑазÑеÑÐµÐ½Ð¸Ñ Ð²Ñегда можно
+ÑдалиÑÑ, Ñем ÑамÑм Ð²Ñ Ð¿Ð¾Ð»ÑÑаеÑе Ñе же
пÑогÑÐ°Ð¼Ð¼Ñ Ð¿Ð¾Ð´ обÑÑной GNU GPL
+веÑÑии 3. ÐÑли пÑогÑамма допÑÑкаеÑ
пÑименение под GNU LGPL
+веÑÑии 2 или более поздней, ее можно
пеÑелиÑензиÑоваÑÑ Ð½Ð° GPL
+веÑÑии 3 или более поздней; Ð´Ð»Ñ ÐºÐ°Ð¶Ð´Ð¾Ð¹
бÑдÑÑей GPL веÑÑии N (N
+> 3) Ð¼Ñ Ð±Ñдем делаÑÑ LGPL веÑÑии N,
ÑоÑÑоÑÑей из GPL веÑÑии N Ñ
+дополниÑелÑнÑми ÑазÑеÑениÑми.</p>
+
+<p>ЧÑо каÑаеÑÑÑ GNU LGPL веÑÑии 2.1, Ñо в ней
ÑвнÑм обÑазом ÑазÑеÑено
+пеÑелиÑензиÑование на GNU GPL веÑÑии 2 или
более поздней.</p>
+
+<p>ÐÑомежÑÑоÑнÑе лиÑензии вклÑÑаÑÑ Ð² ÑебÑ
ÑÑÑеÑÑвеннÑе ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¿Ð¾
+ÑаÑпÑоÑÑÑанениÑ, но не ÑвлÑÑÑÑÑ
лиÑензиÑми Ñ Ð°Ð²ÑоÑÑким левом. ÐÑимеÑами
+ÑакиÑ
лиÑензий ÑвлÑÑÑÑÑ ÐбÑеÑÑвеннаÑ
лиÑÐµÐ½Ð·Ð¸Ñ Eclipse и ÐбÑеÑÑвеннаÑ
+лиÑÐµÐ½Ð·Ð¸Ñ Mozilla. ÐÑомежÑÑоÑнÑе лиÑензии, как
пÑавило, неÑовмеÑÑÐ¸Ð¼Ñ Ð½Ð¸ Ñ
+какими лиÑензиÑми Ñ Ð°Ð²ÑоÑÑким левом,
поÑÐ¾Ð¼Ñ ÑÑо иÑ
ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð½Ðµ допÑÑкаÑÑ
+ÑаÑпÑоÑÑÑанение обÑединенной пÑогÑаммÑ
под лиÑензией Ñ Ð°Ð²ÑоÑÑким
+левом. ÐбÑеÑÑÐ²ÐµÐ½Ð½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ Mozilla
допÑÑÐºÐ°ÐµÑ Ð¿ÐµÑелиÑензиÑование на GNU
+GPL, кÑоме ÑлÑÑаев, когда в пÑогÑамме ÑÑо
ÑвнÑм обÑазом запÑеÑено.</p>
+
+<p>ÐаконеÑ, ÑÑо можно ÑказаÑÑ Ð¾ двойном
лиÑензиÑовании?<a href="#f4">(****)</a>
+ÐÐ²Ð¾Ð¹Ð½Ð°Ñ Ð»Ð¸ÑÐµÐ½Ð·Ð¸Ñ Ð¿ÑедÑÑавлÑÐµÑ Ð´Ð¸Ð·ÑÑнкÑиÑ:
ÑÑо знаÑиÑ, ÑÑо пÑогÑамма
+пÑедоÑÑавлÑÐµÑ Ð½Ð° вÑÐ±Ð¾Ñ Ð´Ð²Ðµ или более
ÑазлиÑнÑÑ
лиÑензий. ÐапÑимеÑ, ÑÑаÑÑе
+веÑÑии Perl пÑедоÑÑавлÑли две лиÑензии:
дизÑÑнкÑÐ¸Ñ Ð¡ÑандаÑÑной обÑеÑÑвенной
+лиÑензии GNU и ÐÑÑиÑÑиÑеÑкой лиÑензии. ÐÑо
ознаÑало, ÑÑо каждÑй полÑзоваÑелÑ
+мог вÑбÑаÑÑ Ð¸ пеÑеÑаÑпÑоÑÑÑанÑÑÑ Perl под
Ñой или дÑÑгой лиÑензией, или под
+дизÑÑнкÑией обеиÑ
, как и Ñам вÑпÑÑк Perl.
ÐизÑÑнкÑÐ¸Ñ ÑовмеÑÑима Ñ Ð½Ð°Ð±Ð¾Ñом
+дÑÑгиÑ
лиÑензий, еÑли Ñ
оÑÑ Ð±Ñ Ð¾Ð´Ð½Ð° из
лиÑензий в дизÑÑнкÑии ÑовмеÑÑима Ñ
+ÑÑим набоÑом.</p>
+
+<p>Ðогда Ð²Ñ Ð²ÑбиÑаеÑе лиÑÐµÐ½Ð·Ð¸Ñ Ð´Ð»Ñ ÑвоиÑ
пÑогÑамм, вÑбиÑайÑе, пожалÑйÑÑа, GNU
+GPL веÑÑии 3 или более поздней или
какÑÑ-Ñо ÑовмеÑÑимÑÑ Ñ ÑÑим
+лиÑензиÑ. Таким обÑазом Ð²Ñ ÑделаеÑе Ñвои
пÑогÑÐ°Ð¼Ð¼Ñ ÑоÑеÑаемÑми поÑÑи Ñо вÑем
+коÑпÑÑом ÑвободнÑÑ
пÑогÑамм. ÐÑÐ±Ð¾Ñ GPL или
AGPL веÑÑии 3 или более
+поздней заÑиÑÐ¸Ñ Ñакже ÑÐ²Ð¾Ð±Ð¾Ð´Ñ Ð²ÑеÑ
полÑзоваÑелей вÑеÑ
веÑÑий ваÑей пÑогÑаммÑ
+наилÑÑÑим обÑазом.</p>
+
+<h3 id="footnotes">ÐÑимеÑаниÑ</h3>
+
+<p id="f1"><b>*</b> ÐÐ»Ð°Ð²Ð½Ð°Ñ Ð¸Ð· пÑименÑемÑÑ
в
наÑÑоÑÑее вÑÐµÐ¼Ñ Ð»Ð¸Ñензий, коÑоÑаÑ
+неÑовмеÑÑима Ñама Ñ Ñобой — лиÑензиÑ
TeXа: еÑли две пÑогÑаммÑ
+лиÑензиÑÐ¾Ð²Ð°Ð½Ñ Ñак, как TeX, Ð½ÐµÑ ÑазÑеÑенного
ÑпоÑоба ÑаÑпÑоÑÑÑанÑÑÑ Ð¸Ñ
+обÑединеннÑÑ Ð²ÐµÑÑиÑ.</p>
+
+<p>ÐиÑÐµÐ½Ð·Ð¸Ñ TeXа допÑÑÐºÐ°ÐµÑ ÑаÑпÑоÑÑÑанение
модиÑиÑиÑованной веÑÑии ÑолÑко в
+ÑоÑме пеÑвонаÑалÑной веÑÑии Ñ Ñайлом
ÑазлиÑий. ÐÑли Ри Ð ÑазделÑно
+лиÑензиÑÐ¾Ð²Ð°Ð½Ñ Ñаким обÑазом, а заÑем
обÑединÑÑÑÑÑ, Ñо ÑаÑпÑоÑÑÑанение
+обÑединенной пÑогÑÐ°Ð¼Ð¼Ñ ÐºÐ°Ðº Ð Ñ Ñайлом
изменений наÑÑÑÐ°ÐµÑ Ð»Ð¸ÑензиÑ
+Ð. РаÑпÑоÑÑÑанение ее как Ð Ñ Ñайлом
изменений наÑÑÑÐ°ÐµÑ Ð»Ð¸ÑензиÑ
+Ð. РаÑпÑоÑÑÑанение лÑбÑм дÑÑгим обÑазом
наÑÑÑÐ°ÐµÑ Ð¾Ð±Ðµ лиÑензии.</p>
+
+<p>Ðе ÑлÑÑайно TeX вÑпÑÑÑили в 1982 годÑ: Ñ
ÑеÑ
Ð¿Ð¾Ñ Ð½Ð°Ñе ÑообÑеÑÑво
+наÑÑилоÑÑ Ð¿Ð¸ÑаÑÑ ÑазÑмнÑе лиÑензии.</p>
+
+<p id="f2"><b>**</b> ÐÑи ÑаÑпÑоÑÑÑанении в ÑоÑме иÑÑ
одного ÑекÑÑа обÑÑно доÑÑаÑоÑно
+оÑÑавлÑÑÑ ÑÐ²ÐµÐ´Ð¾Ð¼Ð»ÐµÐ½Ð¸Ñ Ð¾ лиÑензиÑÑ
в иÑÑ
одном ÑекÑÑе в Ñом виде, в каком они
+еÑÑÑ; ÑÑÐµÐ±Ð¾Ð²Ð°Ð½Ð¸Ñ Ð¾ дополниÑелÑнÑÑ
лиÑензионнÑÑ
ÑведомлениÑÑ
в либеÑалÑнÑÑ
+лиÑензиÑÑ
, как пÑавило, дейÑÑвÑÑÑ Ð¿Ñи
ÑаÑпÑоÑÑÑанении ÑкомпилиÑованнÑÑ
+Ñайлов без иÑÑ
одного ÑекÑÑа.</p>
+
+<p id="f3"><b>***</b> Рдополнение, GPL веÑÑии 2 вÑе
же позволÑÐµÑ Ð´ÐµÐ»Ð°ÑÑ Ð´Ð²Ð¾Ð¸ÑнÑе
+ÑÐ°Ð¹Ð»Ñ Ð½ÐµÑвободнÑми Ñ Ð¿Ð¾Ð¼Ð¾ÑÑÑ Ð°Ð¿Ð¿Ð°ÑаÑÑÑÑ,
коÑоÑÐ°Ñ ÑабоÑÐ°ÐµÑ ÑолÑко Ñо
+ÑпеÑиалÑно подпиÑаннÑми Ñайлами; кÑоме
Ñого, GPL веÑÑии 2 не допÑÑкаеÑ
+ÑаÑпÑоÑÑÑанение двоиÑнÑÑ
Ñайлов
ÑоÑÑенÑами, как и пеÑÐ²Ð°Ñ Ð²ÐµÑÑиÑ
+лиÑензии. РвеÑÑии 3 Ð¼Ñ Ð¸ÑпÑавили ÑÑо
и кое-ÑÑо дÑÑгое, но Ð¼Ñ Ð½Ðµ
+можем измениÑÑ Ð²ÐµÑÑÐ¸Ñ 2.</p>
+
+<p id="f4"><b>****</b> ÐекоÑоÑÑе необÑÑÑнимо
ÑпоÑÑеблÑÑÑ Ð²ÑÑажение “двойное
+лиÑензиÑование” Ð´Ð»Ñ Ð¾Ð±Ð¾Ð·Ð½Ð°ÑениÑ
пÑодажи иÑклÑÑений, но ÑÑо
+злоÑпоÑÑебление ÑзÑком. См. <a
href="/philosophy/selling-exceptions.html">
+ÐÑодажа иÑклÑÑений</a>. ÐбÑаÑиÑе внимание,
ÑÑо еÑли лиÑензиÑ, коÑоÑаÑ
+пÑодаеÑÑÑ Ð² каÑеÑÑве иÑклÑÑениÑ, вÑдаеÑÑÑ
на лÑбÑе пÑогÑаммÑ, не вÑ
одÑÑие в
+обÑÑнÑй ÑвободнÑй вÑпÑÑк, Ñо ÑÑо не
пÑодажа иÑклÑÑений — ÑÑо
+неÑвободнÑе пÑогÑаммÑ.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.ru.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>ÐожалÑйÑÑа, пÑиÑÑлайÑе обÑие запÑоÑÑ
ÑÐ¾Ð½Ð´Ñ Ð¸ GNU по адÑеÑÑ <a
+href="mailto:address@hidden"><address@hidden></a>. ÐÑÑÑ Ñакже <a
+href="/contact/">дÑÑгие ÑпоÑÐ¾Ð±Ñ ÑвÑзаÑÑÑÑ</a> Ñ
Ñондом. ÐÑÑеÑÑ Ð¾
+неÑабоÑаÑÑиÑ
ÑÑÑлкаÑ
и дÑÑгие попÑавки
или пÑÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¼Ð¾Ð¶Ð½Ð¾ пÑиÑÑлаÑÑ Ð¿Ð¾
+адÑеÑÑ <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>. -->
+ÐÑ ÑÑаÑалиÑÑ ÑделаÑÑ ÑÑÐ¾Ñ Ð¿ÐµÑевод ÑоÑнÑм и
каÑеÑÑвеннÑм, но иÑклÑÑиÑÑ
+возможноÑÑÑ Ð¾Ñибки Ð¼Ñ Ð½Ðµ можем.
ÐÑиÑÑлайÑе, пожалÑйÑÑа, Ñвои замеÑÐ°Ð½Ð¸Ñ Ð¸
+пÑÐµÐ´Ð»Ð¾Ð¶ÐµÐ½Ð¸Ñ Ð¿Ð¾ пеÑÐµÐ²Ð¾Ð´Ñ Ð¿Ð¾ адÑеÑÑ <a
+href="mailto:address@hidden"><address@hidden></a>.
+</p><p>Ð¡Ð²ÐµÐ´ÐµÐ½Ð¸Ñ Ð¿Ð¾ кооÑдинаÑии и
пÑедложениÑм пеÑеводов наÑиÑ
ÑÑаÑей Ñм. в
+<a href="/server/standards/README.translations.html">“Ð
ÑководÑÑве по
+пеÑеводам”</a>.</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 © 2016 Free Software Foundation, Inc.</p>
+
+<p>ÐÑо пÑоизведение доÑÑÑпно по <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.ru">лиÑензии
+Creative Commons Attribution-NoDerivs (<em>ÐÑÑибÑÑÐ¸Ñ —
Ðез
+пÑоизводнÑÑ
пÑоизведений</em>) 4.0
ÐÑемиÑнаÑ</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.ru.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<em>Ðнимание! РподгоÑовке ÑÑого пеÑевода
ÑÑаÑÑвовал ÑолÑко один Ñеловек. ÐÑ
+можеÑе ÑÑÑеÑÑвенно ÑлÑÑÑиÑÑ Ð¿ÐµÑевод, еÑли
пÑовеÑиÑе его и ÑаÑÑкажеÑе о
+найденнÑÑ
оÑибкаÑ
в <a
+href="http://savannah.gnu.org/projects/www-ru">ÑÑÑÑкой гÑÑппе
пеÑеводов
+gnu.org</a>.</em></div>
+
+<p class="unprintable"><!-- timestamp start -->
+Ðбновлено:
+
+$Date: 2016/08/31 12:57:55 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: po/license-compatibility.ru-en.html
===================================================================
RCS file: po/license-compatibility.ru-en.html
diff -N po/license-compatibility.ru-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ po/license-compatibility.ru-en.html 31 Aug 2016 12:57:55 -0000 1.1
@@ -0,0 +1,318 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.79 -->
+<title>License Compatibility and Relicensing
+- GNU Project - Free Software Foundation</title>
+ <!--#include virtual="/licenses/po/license-compatibility.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>License Compatibility and Relicensing</h2>
+
+<p>by Richard Stallman</p>
+
+<p>If you want to combine two free programs into one, or merge code from
+one into the other, this raises the question of whether their licenses
+allow combining them.</p>
+
+<p>There is no problem merging programs that have the same license, if it
+is a reasonably behaved license, as nearly all free licenses
+are.<a href="#f1">(*)</a></p>
+
+<p>What then when the licenses are different? In general we say that
+several licenses are <em>compatible</em> if there is a way to merge
+code under those various licenses while complying with all of them.
+The result, often, is a program with parts under various different
+compatible licenses—but not always. Such combinability, or the
+absence of it, is a characteristic of a given set of licenses, and is
+not dependent on what order you mention them in. The set of licenses
+also controls which license is required for the combined program.</p>
+
+<p>We divide licenses into three classes: lax (also
+“permissive” or “pushover”), intermediate, and
+copyleft. A lax license does nothing to interfere with putting the
+code into proprietary software. A copyleft license prohibits that, by
+requiring all reuse to be in programs under the same license. An
+intermediate license puts some conditions on adding proprietary code
+but does not try to prohibit it.</p>
+
+<p>In general, lax permissive licenses (modified BSD, X11, Expat, Apache,
+Python, etc.) are compatible with each other. That's because they
+have no requirements about other code that is added to the program.
+They even permit putting the entire program (perhaps with changes)
+into a proprietary software product; thus, we call them
+“pushover licenses” because they can't say
+“no” when one user tries to deny freedom to others.</p>
+
+<p>In a combination of programs under lax licenses, each part carries the
+license it came with. When the code is merged to the point that the
+parts can't be distinguished any more, that merged code should carry
+all the licenses of the merged parts. Since all the licenses are lax
+anyway, this causes no practical problem except that the list of
+licenses gets long.<a href="#f2">(**)</a></p>
+
+<p>By the same token, lax licenses are usually compatible with any
+copyleft license. In the combined program, the parts that came in
+under lax licenses still carry them, and the combined program as a
+whole carries the copyleft license. One lax license, Apache 2.0, has
+patent clauses which are incompatible with GPL version 2; since I
+think those patent clauses are good, I made GPL version 3 compatible
+with them.</p>
+
+<p>The one important exception is the original BSD license, because of
+the “obnoxious advertising clause.” This condition required a
+specific notice in <em>all</em> advertising of <em>any</em> product
+containing <em>any</em> code released under the original BSD license.
+This was, and is, incompatible with all actual copyleft licenses. It
+was also a pain in the neck for every distro, as programs accumulated
+with similar but different advertising requirements. At one point, a
+BSD distro required over 70 different notices.</p>
+
+<p>I mostly eliminated this problem by convincing a dean, Hal Varian, to
+arrange for UC Berkeley to publish the “modified BSD
+license” (without the advertising clause) and rerelease the code
+of the Berkeley System Distribution under that. Nowadays the original
+BSD license is (fortunately) rarely used, but we must still take care
+<a href="/licenses/bsd.html">not to talk about “the” BSD
+license</a>.</p>
+
+<p>In general, two different copyleft licenses are unavoidably
+incompatible unless they have explicit compatibility provisions. This
+is not due to a mistake in the details; it's inherent in the idea of
+copyleft. The idea of copyleft is that “Modified and extended
+versions must be under the same license.” If license A says extended
+programs must be under license A, and license B says extended programs
+must be under license B, they have an irreconcilable disagreement; the
+license of the combined program would have to be A, <em>and</em> it would
+have to be B. This is why GPL version 2 is incompatible with GPL
+version 3; it could not be avoided. Likewise, the conditions of
+CC-BY-SA 4.0 would be inherently incompatible with those of CC-BY-SA
+3.0, and the authors could not have avoided this.</p>
+
+<p>There are two approaches for smoothing out the incompatibility
+inherent in new versions of copyleft licenses.</p>
+
+<p>The FSF uses the approach of asking people to release programs under
+“GNU GPL version N or any later version.” This licensing is
+compatible with version N, and also with N+1 (because it offers
+version N+1 as an option). When you combine code under “GPL 3 or
+later” with code under “GPL 2 or later”, the license
+of the combination is their intersection, which is “GPL 3 or
+later”.</p>
+
+<p>We hope we will never need to make a GNU GPL version 4, but nothing is
+perfect and we can't assume we have anticipated all the issues. By
+releasing your code under GNU GPL 3 or later, you permit your code to
+upgrade to GNU GPL version 4 if we ever need one.</p>
+
+<p>The other approach is to make each version of the license explicitly
+allow upgrading to later versions. This is what Creative Commons
+does: for instance, CC-BY-SA version 4.0 (the current version)
+explicitly permits any user to upgrade to later versions of CC-BY-SA
+once those exist. The Mozilla Foundation also uses this approach.</p>
+
+<p>Only the GNU licenses give authors a choice about whether to permit
+upgrades to future license versions. When I wrote the first version
+of the GNU GPL, in 1989, I considered including a license upgrade
+option as is found now in CC licenses, but I thought it more correct
+to give that choice to each author. Thus, the author could release a
+program either under “GPL 1 only” or “GPL 1 or
+later.”</p>
+
+<p>Since then, I have come to question the wisdom of that decision.
+Programs such as Linux, which allow only one GNU GPL version and
+reject license upgrades, cause practical
+incompatibility.<a href="#f3">(***)</a> Perhaps we should include an
+upgrade clause in GPL version 4, if we ever need a version 4.</p>
+
+<p>Some copyleft licenses allow cross-copyleft combinations with an
+explicit relicensing clause giving permission to put the code under a
+different copyleft license. For instance, the CeCILL gives explicit
+permission to relicense code to GNU GPL version 2 and later versions.
+If program P is under the CeCILL, and you want to combine it with
+program Q that's under GPL version 3 or later, the CeCILL says you can
+do that and put the combination or merged code under GPL version 3 or
+later.</p>
+
+<p>Explicit relicensing permission is not the same thing as compatibility
+(though relicensing code can make it compatible with other code) and
+it is not symmetrical. For instance, the CeCILL gives explicit
+permission to relicense code to GNU GPL, but the GNU GPL does not
+permit relicensing to the CeCILL. Thus, you can't combine those two
+programs P and Q and distribute the combination under the CeCILL; that
+would violate the GPL in its use of program Q. The only permitted way
+to release that combined program is under the appropriate GPL
+version(s).</p>
+
+<p>Likewise, CC-BY-SA 4.0 explicitly permits relicensing modified
+versions to GNU GPL version 3, but GPL version 3 does not permit
+relicensing to CC-BY-SA. This issue should never arise for software
+code; Creative Commons says its licenses are not meant for code, and
+says that the license to use for code is the GNU GPL. But there are
+other kinds of works, such as hardware designs or game art, where you
+might have occasion to merge material released under CC-BY-SA with
+material released under the GNU GPL. This can be done through
+CC-BY-SA's explicit relicensing permission.</p>
+
+<p>Unfortunately, CC-BY-SA 4.0 does not permit relicensing to future GPL
+versions. What you should do, when you relicense material under
+CC-BY-SA 4.0 to the GPL, is <a
+href="/licenses/rms-why-gplv3.html#future-proofing">specify
+yourself as a license version proxy</a> to indicate whether future GPL
+versions have been authorized for that material. If someday there is
+a GPL version 4 and Creative Commons decides to allow relicensing from
+CC-BY-SA to GPL version 4, you as proxy will be able to retroactively
+authorize use of that relicensed material under GPL version 4.
+(Alternatively, you can ask the authors of that material to give
+permission right away.)</p>
+
+<p>The ordinary GNU General Public License and the GNU Affero General
+Public License are two different copyleft licenses, so they are
+naturally incompatible. We have set up a special kind of explicit
+compatibility between them: you can include source code under the GNU
+GPL version 3 together with other source code under the GNU Affero GPL
+in a single combined program. This is permitted because both of those
+licenses explicitly say so, and the effect is that the GNU AGPL
+applies to the combined program. However, you can't simply relicense
+code from the GNU GPL (with or without “or later”) to the
+GNU Affero GPL, or vice versa; neither of these licenses gives
+permission for that. Note also that the GNU Affero GPL version 3 is
+not a “later version” of the ordinary GNU GPL version 2,
+because the GNU Affero GPL and the GNU GPL are two different series of
+licenses.</p>
+
+<p>The GNU Lesser General Public License, version 3, is really the GNU
+General Public License version 3 plus some added extra permissions.
+GPL version 3 (section 7) says you can always remove added
+permissions, and by doing so you get the same code under the ordinary
+GNU GPL version 3. If a program permits use under GNU LGPL
+version 3 or later, you can relicense it to GPL version 3 or later;
+for each future GPL version N (N > 3), we will make an LGPL version
+N which consists of the GPL version N plus added permissions.</p>
+
+<p>As for GNU Lesser GPL version 2.1, that explicitly permits relicensing
+to GNU GPL version 2 or later.</p>
+
+<p>Intermediate licenses are those which have substantive requirements
+on redistribution but are not copyleft licenses. Examples include the
+Eclipse Public License and the Mozilla Public License. Intermediate
+licenses tend to be incompatible with any copyleft licenses because
+their requirements don't permit the combined program to be under the
+copyleft license. The Mozilla Public License permits relicensing to
+the GNU GPL except when the code explicitly denies this
+permission.</p>
+
+<p>Finally, what about dual licensing?<a href="#f4">(****)</a> A dual
+license is a disjunction: it means that the same program carries a
+choice of two or more different licenses. For instance, older
+versions of Perl carried a dual license: the disjunction of the
+Artistic License and the GNU General Public License. This meant that
+each user could choose to use and redistribute Perl under one license
+or the other, or under both in disjunction like the Perl release
+itself. A disjunction is compatible with a set of other licenses if
+any one of the license choices in the disjunction is compatible with
+that set.</p>
+
+<p>When you choose a license for your code, please choose GNU GPL version
+3 or later, or some license compatible with that. This is the way to
+make your code combinable with nearly all the corpus of free software.
+Choosing GPL or AGPL, version 3 or later, will also do the utmost to
+defend freedom for all users of all versions of your code.</p>
+
+<h3 id="footnotes">Footnotes</h3>
+
+<p id="f1"><b>*</b> The main license in actual use that isn't
+reasonably behaved is the license of TeX: if two programs are licensed
+just the way TeX is, there is no authorized way to distribute a merged
+version of them.</p>
+
+<p>The TeX license permits distribution of a modified version only in
+the form of the original version plus a differences file. If A and B
+are separately released that way, then merged, distributing the merged
+program as A plus a change file violates the license of B.
+Distributing this as B plus a change file violates the license of A.
+Distributing this in any other way violates both licenses.</p>
+
+<p>It is no coincidence that TeX was released in 1982: our community has
+learned, since then, to write reasonably behaved licenses.</p>
+
+<p id="f2"><b>**</b> When distributing in source code
+form, it is usually sufficient to leave the license notices in the
+source code as they stand; extra license notice requirements typically
+only come up for lax licenses when distributing binaries without the
+source code.</p>
+
+<p id="f3"><b>***</b> In addition, GPL version 2 still allows binaries
+to be made nonfree by hardware that rejects all but special signed
+binaries, and still does not allow distribution of binaries by
+torrent, as it did when first published. We fixed those things and
+others in version 3, but we can't change version 2.</p>
+
+<p id="f4"><b>****</b> Some inexplicably use the term “dual
+licensing” to refer to selling exceptions, but that is an abuse
+of language. See <a href="/philosophy/selling-exceptions.html">
+Selling Exceptions</a>. Note that if the license sold as an exception
+includes any code that is not in the ordinary free release, that's not
+selling exceptions, that's nonfree software.</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 © 2016 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: 2016/08/31 12:57:55 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- www/licenses po/license-compatibility.translist...,
GNUN <=