www/licenses po/200104_seminar.translist 200104...

[GNUN]

CVSROOT:        /web/www
Module name:    www
Changes by:     GNUN <gnun>     18/11/30 22:57:51

Modified files:
        licenses/po    : 200104_seminar.translist 
Added files:
        licenses       : 200104_seminar.zh-cn.html 
        licenses/po    : 200104_seminar.zh-cn-en.html 

Log message:
        Automatic update by GNUnited Nations.

CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/200104_seminar.zh-cn.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/200104_seminar.translist?cvsroot=www&r1=1.11&r2=1.12
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/200104_seminar.zh-cn-en.html?cvsroot=www&rev=1.1

Patches:
Index: po/200104_seminar.translist
===================================================================
RCS file: /web/www/www/licenses/po/200104_seminar.translist,v
retrieving revision 1.11
retrieving revision 1.12
diff -u -b -r1.11 -r1.12
--- po/200104_seminar.translist 25 Jul 2015 14:28:15 -0000      1.11
+++ po/200104_seminar.translist 1 Dec 2018 03:57:51 -0000       1.12
@@ -5,10 +5,12 @@
 <span dir="ltr" class="original"><a lang="en" hreflang="en" 
href="/licenses/200104_seminar.en.html">English</a>&nbsp;[en]</span> &nbsp;
 <span dir="ltr"><a lang="de" hreflang="de" 
href="/licenses/200104_seminar.de.html">Deutsch</a>&nbsp;[de]</span> &nbsp;
 <span dir="ltr"><a lang="fr" hreflang="fr" 
href="/licenses/200104_seminar.fr.html">français</a>&nbsp;[fr]</span> &nbsp;
+<span dir="ltr"><a lang="zh-cn" hreflang="zh-cn" 
href="/licenses/200104_seminar.zh-cn.html">简体中文</a>&nbsp;[zh-cn]</span> 
&nbsp;
 </p>
 </div>' -->
 <link rel="alternate" type="text/html" href="/licenses/200104_seminar.html" 
hreflang="x-default" />
 <link rel="alternate" type="text/html" lang="en" hreflang="en" 
href="/licenses/200104_seminar.en.html" title="English" />
 <link rel="alternate" type="text/html" lang="de" hreflang="de" 
href="/licenses/200104_seminar.de.html" title="Deutsch" />
 <link rel="alternate" type="text/html" lang="fr" hreflang="fr" 
href="/licenses/200104_seminar.fr.html" title="français" />
+<link rel="alternate" type="text/html" lang="zh-cn" hreflang="zh-cn" 
href="/licenses/200104_seminar.zh-cn.html" title="简体中文" />
 <!-- end translist file -->

Index: 200104_seminar.zh-cn.html
===================================================================
RCS file: 200104_seminar.zh-cn.html
diff -N 200104_seminar.zh-cn.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ 200104_seminar.zh-cn.html   1 Dec 2018 03:57:50 -0000       1.1
@@ -0,0 +1,221 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/200104_seminar.en.html" -->
+
+<!--#include virtual="/server/header.zh-cn.html" -->
+<!-- Parent-Version: 1.78 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>FSFç ”è®¨ä¼šï¼šè¯¦ç»†ç ”ç©¶å’Œåˆ†æžGPL和LGPL - GNU工程 - 
自由软件基金会</title>
+<meta name="CREATED" content="20031124;15182100" />
+
+<!--#include virtual="/licenses/po/200104_seminar.translist" -->
+<!--#include virtual="/server/banner.zh-cn.html" -->
+<h2>FSFç ”è®¨ä¼šï¼šè¯¦ç»†ç ”ç©¶å’Œåˆ†æžGPL和LGPL</h2>
+<blockquote>
+<p>哥伦比亚法学院，纽约哥伦比亚大学，NY 
2004年1月20日（上午9:00 - 下午6:00）
+</p></blockquote>
+
+<p>这是一个为期一天的逐节讲解最流行的自由软件版权许可证——GNU通用å
…¬å…±è®¸å¯è¯ï¼ˆGNU
+GPL）的课程，它教育律师、软件开发者
、管理人员和商业人士如何在初创的自由软件行业和现有的、运作良好的企业中成功地应用GPL（以及使用GPL授权的软件）。
+</p>
+
+<h3>前提条件</h3>
+
+<p>与会者应当å…
·æœ‰è½¯ä»¶å¼€å‘流程的常规知识。对版权法如何应用在软件上有一定的了解也会有所帮助。</p>
+
+<h3>受众</h3>
+
+<p>对本课程最有兴趣的受众应该是律师、软件开发者
和软件行业（或者
客户是软件行业）的管理人员，他们会使用GNU
+GPL或LGPL修改/再发布软件，或者希望在å…
¶ä¸šåŠ¡ä¸­ä½¿ç”¨çŽ°æœ‰çš„GPL和LGPL软件。
+</p>
+<p>本课程会包含下列的内容，并有充
足的时间进行答疑和讨论。
+</p>
+
+<h3>午餐演讲嘉宾</h3>
+
+<p><a href="http://emoglen.law.columbia.edu/";>Eben
+Moglen</a>教授将进行午餐演讲。Moglen教授是哥伦比亚法学院的法律和法学历史教授，他是我国版权、专利以及被提议的&ldquo;广播æ
 ‡è®°&rdquo;方面最著名的学者
之一。他也是自由软件基金会的董事成员之一和基金会的总法律顾问。Moglen教授还在SCO对IBM的案件方面著述颇丰。
+</p>
+<dl>
+<dt>自由软件的原则和自由软件的定义
+</dt>
+<dd>
+<p>介绍推动我们创建这些许可证的道德原则。不同于追求将软件锁定为专有物品的å
…¶ä»–许可证，GPL和LGPLæ—¨åœ¨æŽˆäºˆåˆ›æ–°ã€å­¦ä¹ 
和提高以自由。这些原则影响着许可证政策的决定。我们向盈利性企业展示&ldquo;自由软件&rdquo;概念（æ—
 
论是否收费，该软件都保证复制、分享、修改和再发布的自由）的定义。
+</p>
+</dd>
+<dt>GNU通用公共许可证（GPL）的序言
+</dt>
+<dd>
+<p> 
序言阐述了该许可证的目的。序言提出了许可证遵循的详细条款和条件的缘由。我们详细讨论一下序言的用词，以展示它是如何构建了整个法律细节。
+</p>
+</dd>
+<dt> GPL，第0节：定义及其他
+</dt>
+<dd>
+<p> 
GPL的第0节定义和阐述了构成该版权许可证基础的条款。我们会探讨这些定义以及许可证的版权范围。</p>
+</dd>
+<dt>GPL，第1èŠ‚ï¼šå‡†è®¸å…¨æ–‡é€å­—å¤åˆ¶æºç 
+</dt>
+<dd>
+<p> 第1节定义了仅复制软件源代ç 
çš„条款。我们会讨论这些规则如何操作以及GPL源代ç 
çš„å‘å¸ƒè€…çš„è¦æ±‚å’Œä¹‰åŠ¡ï¼Œæ— 论他们是选择收费还是å…
è´¹å‘布。</p>
+</dd>
+<dt>衍生作品：法规和判例法</dt>
+<dd>
+<p> æ— 
论是一般的自由软件还是遵循GPL和LGPL的自由软件都非常依赖于衍生作品的概念，å›
 为独立于（非衍生自）自由软件的软件不必
遵循用于自由软件的许可证条款。如果作品是自由软件的衍生作品，那么许可证条款被触发，该作品就有义务遵从原始自由软件发布时遵循的许可证条款。å›
 
此，我们要问的只是，什么是&ldquo;衍生作品&rdquo;？我们会指出该问题的答案与被问及的法庭有å
…
³ã€‚我们也会展示现有最好的背景信息，以构建一个在快速变化的软件版权法领域å†
…，对一般情况下什么应该被认为是衍生作品的有效理解。</p>
+</dd>
+<dt> GPL，第2èŠ‚ï¼šå‡†è®¸æºç è¡ç”Ÿä½œå“</dt>
+<dd>
+<p> 
第2节提出GPL软件产生衍生作品的规则。我们会讨论本节的目的以及GPL与我们讨论的衍生作品的版权条件的å
…³ç³»ã€‚我们还会详细解释如何准备和GPL兼容的源ç 
è¡ç”Ÿä½œå“ã€‚</p>
+</dd>
+<dt> GPL，第3节：准许创建二进制衍生作品</dt>
+<dd>
+<p> 仅有源ç 
çš„发布对有技术的客户和用户没有问题，但是大多数人还希望有可执行的二进制。第3节准许了创建和发布此类二进制作品。我们会解释GPL对相å
…³å‘布的源代ç 
çš„要求该如何操作，以及发布GPL二进制软件时有哪些选项。我们会ç
 ”究这些选项的优点和缺点。</p>
+</dd>
+<dt>GPL中隐含的专利授权</dt>
+<dd>
+<p> 
专利权通常在许可证中使用详尽的语言授权。然而，书面明确表达并不是专利持有人进行专利授权的唯一方式。即使没有书面语言，专利持有人也可以通过行为或表现进行专利授权。GPL不åŒ
…
含专利授权的明确语言表达。这是否意味着GPL对许可证发布è€
…的专利授权比å…
¶ä»–许可证要少呢？或着，是否GPL，没有使用明确的语言，从而比å
…
¶ä»–自由软件许可证以及&ldquo;开源&rdquo;许可证的专利授权更多呢？
+</p>
+<p>我们会考虑这些问题并给出详尽的解答。</p>
+</dd>
+<dt>GPL，第4节：许可证的终止
+</dt>
+<dd>
+<p> 第4节讲的是对违反GPL许可证者
进行权利终结。我们会讨论如何终结、这对违反者
意味着什么、违反的风险在哪里以及一般如何恢复权利。我们简要地讲述了第4节是如何作为GPL的æ
 ¸å¿ƒæ‰§æ³•å·¥å…·æ¥ä½¿ç”¨çš„。
+</p>
+</dd>
+<dt>GPL，第5节：许可证的接受
+</dt>
+<dd>
+<p> GPL并非合同，对它的接受也和接受合同不太一æ 
·ã€‚我们会讨论在管辖GPL的专利规则范畴内
，接受是怎么工作的。</p>
+</dd>
+<dt>GPL，第6节：禁止进一步的限制</dt>
+<dd>
+<p> 不能在GPLè½¯ä»¶ä¸Šé™„åŠ å…¶ä»–è¶…
越GPL已经授权的条款。我们会讨论如何使用第6节来确保这些额外的条款不会被åŠ
 进来。我们会简要讨论此节如何导致和GPL不å…
¼å®¹çš„自由软件许可证之概念。</p>
+</dd>
+<dt>GPL，第7节：与其他协议或命令的矛盾</dt>
+<dd>
+<p> æ­£å¦‚é™„åŠ åè®®ä¸èƒ½è¶…è¶ŠGPL一æ 
·ï¼Œå¤–来的协议、专利许可证或法庭命令也不能超
越GPL。我们会讨论第7节如何保证软件许可证之外的规则不能剥夺软件用户、发行è€
…和修改者的权利。
+</p>
+</dd>
+<dt>GPL，第8节：全球发布许可证的问题</dt>
+<dd>
+<p> 第8节是一个较少用到的GPLç« èŠ‚ã€‚å®ƒä¼šå¸®åŠ©ç‰ˆæƒæ‰€æœ‰è€…
处理某些被严苛法律禁止å…
¨çƒå‘布的技术。我们会解释该节如何帮助此类版权所有者。
+</p>
+</dd>
+<dt>GPL，第9节：FSF是GPL的管理员</dt>
+<dd>
+<p> 我们在此节讨论新GPL版本的更新和发布流程。</p>
+</dd>
+<dt>GPL，第10节：对GPL的版权例外</dt>
+<dd>
+<p> 第10èŠ‚æé†’è®¸å¯è¯èŽ·å–è€…ï¼Œæ ¹æ®ç‰ˆæƒæ³•å¯ä»¥æœ‰å…
¶ä»–类型的版权再授权。我们会讨论这一点是如何常常被作为商业模式来使用，我们也详细解释该商业模式的益处和不足。</p>
+</dd>
+<dt>GPL，第11节：免责声明</dt>
+<dd></dd>
+<dt>GPL，第12节：责任限制</dt>
+<dd>
+<p> å‡ ä¹Žæ‰€æœ‰çš„è½¯ä»¶è®¸å¯è¯ï¼ŒåŒ…æ‹¬è±¡GPL这æ 
·çš„è‡ªç”±è½¯ä»¶è®¸å¯è¯ï¼Œéƒ½æœ‰å…³äºŽä¿è¯å’Œè´£ä»»çš„ç« 节，一般å…
¨éƒ½å¤§å†™ã€‚å¤§å¤šæ•°éžæ³•å¾‹äººå£«ä¸ä¼šå…³å¿ƒè¿™äº›ç« 
èŠ‚çš„ç›®çš„ï¼Œä½†æ˜¯å¾‹å¸ˆä»¬éžå¸¸æ¸…æ¥šè¯¥ç« 
节的用词对许可证授权方和许可证接受方的重要性。一些人论证说GPL的第11节和第12节使之完å
…¨æ— 法依法执行。我们会思考此论证是否属实，并展示一些å…
³äºŽGPL免责声明和责任限制条款的可能解释和实现。</p>
+</dd>
+<dt>宽通用公共许可证（LGPL）</dt>
+<dd>
+<p> LGPL是GPL的&ldquo;相对减少&rdquo;版，它特别为å…
è®¸åˆ›å»ºä¸€ç±»å®šä¹‰å¥½çš„专有衍生作品而设计。不过，它禁止直接把LGPL授权的软件本身变成专有软件。
+</p>
+<p> 
我们会讨论LGPL的基本设计以及它和GPL的异同比较。我们会介绍LGPL涵盖的两类衍生作品，&ldquo;使用库的作品&rdquo;和&ldquo;基于库的作品&rdquo;，并举出å
…·ä½“事例说明哪些基于LGPL软件的专有衍生作品是å…
è®¸çš„、哪些是禁止的。
+</p>
+</dd>
+</dl>
+<h3>定价（于2003å¹´12月24æ—¥å‰é¢„å®šäº«å—æ—©é¸Ÿä¼˜æƒ ä»·ï¼‰</h3>
+<p>12月24日（含）前注册费用为$495，12月24日之后注册费为$595</p>
+<p>
+<b>资助政策：</b>年收入少于$15,000的申请者
可享受2.5折。年收入在$15,000和$30,000之间的申请者
享受5折。司法会员、学者
和非盈利机构的律师享受9æŠ˜ã€‚å¦‚æžœä½ ç¬¦åˆæ¡ä»¶ï¼Œè¯·è”ç³»John<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>或Ravi<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>或致电617.620.9640。</p>
+<p>è¦æ³¨å†Œè¯¥ç ”è®¨ä¼šï¼Œè¯·ä¸‹è½½æ³¨å†Œè¡¨ã€å¡«å¥½å¹¶ä¼ çœŸåˆ°FSF。</p>
+<p><b>CLE<sup><a
+href="#TransNote1">1</a></sup>学分：</b>成功完成整日课程的律师可以获得职业实践方面的7个纽约可转换CLE学分。</p>
+<p>签约成为FSF企业赞助者的公司每年可以获得FSFç 
”è®¨ä¼šçš„ä¸¤ä¸ªå…è´¹å¸­ä½ä»¥åŠé¢å¤–å¸­ä½çš„ä¼˜æƒ 。请联系<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>了解详情
。若要了解企业赞助者计划，请访问<a
+href="http://patron.fsf.org/";> http://patron.fsf.org</a>。</p>
+<p>本次ç 
”讨会将在纽约的哥伦比亚法学院举行。注册后即发送位置详æƒ
…。更多信息，请联系FSF的沟通总监Ravi Khanna<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>或致电1+617-620-9640。</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<h3>译注</h3>
+<ol>
+<li id="TransNote1">CLE：指纽约州的持续法律教育项目（Continuing 
Legal Education
+program）。</li>
+</ol></div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.zh-cn.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>请将有å…
³è‡ªç”±è½¯ä»¶åŸºé‡‘会（FSF）&amp;GNU的一般性问题发送到<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</a>。也可以通过<a
+href="/contact/">å…
¶ä»–联系方法</a>联系自由软件基金会(FSF)ã€‚è¯·å°†æ— æ•ˆé“¾æŽ¥ï¼Œå…
¶ä»–错误或建议发送给<a
+href="mailto:address@hidden";>&lt;address@hidden&gt;</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";>
+
+        &lt;address@hidden&gt;</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="/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 &copy; 2003, 2004, 2007, 2008, 2009, 2014, 2015 Free Software
+Foundation, Inc.</p>
+
+<p>本页面使用<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.zh-cn.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<b>å®¡æ ¡</b>:<a
+href="mailto:address@hidden";>&lt;尚卓燃（Psiace）&gt;</a><br></br>
+<b>翻译团队</b>：<a rel="team"
+href="https://savannah.gnu.org/projects/www-zh-cn/";>&lt;CTT&gt;</a>，2018。</div>
+
+<p class="unprintable"><!-- timestamp start -->
+最后更新：
+
+$Date: 2018/12/01 03:57:50 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>

Index: po/200104_seminar.zh-cn-en.html
===================================================================
RCS file: po/200104_seminar.zh-cn-en.html
diff -N po/200104_seminar.zh-cn-en.html
--- /dev/null   1 Jan 1970 00:00:00 -0000
+++ po/200104_seminar.zh-cn-en.html     1 Dec 2018 03:57:51 -0000       1.1
@@ -0,0 +1,359 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.78 -->
+<title>FSF Seminar: Detailed Study and Analysis of GPL and LGPL
+- GNU Project - Free Software Foundation</title>
+<meta name="CREATED" content="20031124;15182100" />
+<!--#include virtual="/licenses/po/200104_seminar.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>FSF Seminar: Detailed Study and Analysis of GPL and LGPL</h2>
+<blockquote>
+<p>Columbia Law
+School, Columbia University
+New York, NY
+January 20, 2004 (9:00 am - 6:00 pm)
+</p></blockquote>
+
+<p>This one-day course gives a section-by-section explanation of the
+most popular Free Software copyright license, the GNU General Public
+License (GNU GPL), and teaches lawyers, software developers, managers
+and business people how to use the GPL (and GPL'd software)
+successfully in a new Free Software business and in existing,
+successful enterprises.
+</p>
+
+<h3>Prerequisites</h3>
+
+<p>Attendees should have a general
+familiarity with software development processes.  A basic
+understanding of how copyright law typically applies to software is
+also helpful.</p>
+
+<h3>Audience</h3>
+
+<p>The
+course is of most interest to lawyers, software developers and
+managers who run (or have clients who run) software businesses that
+modify and/or redistribute software under terms of the GNU GPL or
+LGPL, or who wish to make use of existing GPL'd and LGPL'd software in
+their enterprise.
+</p>
+<p>The course will include the topics listed below, along with ample
+time for questions and discussions.
+</p>
+
+<h3>Lunchtime Speaker</h3>
+
+<p><a href="http://emoglen.law.columbia.edu/";>Eben
+Moglen</a> will be the lunchtime speaker.  Professor Moglen is
+Professor of Law and Legal History at Columbia Law School and one of
+the nation's foremost scholars on copyright, patents and the proposed
+&ldquo;Broadcast Flag&rdquo;.  He is also a member of FSF's Board of
+Directors and the foundation's General Counsel.  Professor Moglen has
+also written extensively on the SCO vs IBM lawsuit.
+</p>
+<dl>
+<dt>Free Software
+Principles and the Free Software Definition
+</dt>
+<dd>
+<p>The ethical
+principles that motivated the creation of these licenses are
+presented.  Unlike licenses that seek to lock up software in a
+proprietary fashion, the GPL and LGPL are designed to grant freedom to
+innovate, learn and improve. Those principles influence licensing
+policy decisions.  We present the specific definition of the concept
+of &ldquo;Free Software&rdquo; (software whose license grants freedoms
+to copy, share, modify and redistribute the software either gratis or
+for a fee) for for-profit companies.
+</p>
+</dd>
+<dt>Preamble of the GNU
+General Public License (GPL)
+</dt>
+<dd>
+<p> The preamble
+presents the intent of the license.  The preamble puts forth the
+motivations for the detailed terms and conditions that follow in the
+license.  We discuss the language of the preamble in detail to show
+how it frames the legal details that follow.
+</p>
+</dd>
+<dt> GPL, Section 0:
+Definitions, etc.
+</dt>
+<dd>
+<p> GPL's Section 0
+defines and presents the terms that make the basis of this copyright
+license.  We discuss those definitions and the copyright scope of the
+license.</p>
+</dd>
+<dt>GPL, Section 1:
+Grant for Verbatim Source Copying
+</dt>
+<dd>
+<p> Section 1 defines the terms for making
+source-only copies of software programs.  We discuss how those rules
+work and the requirements and obligations for distributors of GPL'd
+source, whether they choose to distribute at no charge or for
+fees.</p>
+</dd>
+<dt>Derivative Works:
+Statute and Case Law</dt>
+<dd>
+<p> Free Software
+licensing in general, and the GPL and LGPL in particular, relies
+critically on the concept of derivative work since software that is
+independent (i.e., not derivative) of Free Software need not abide by
+any of the terms of the applicable Free Software license.  If a work
+is a derivative work of Free Software, then the terms of the license
+are triggered, and one has obligations to comply with the terms of the
+Free Software license under which the original work is distributed.
+Therefore, one is left to ask, just what is a &ldquo;derivative
+work?&rdquo; We will show how the answer to that question depends on
+which court is being asked.  We also present the best background
+information available to build a working understanding of what is
+generally considered a derivate work in the rapidly changing field of
+software copyright law.</p>
+</dd>
+<dt> GPL, Section 2:
+Grants for Source Derivative Works</dt>
+<dd>
+<p> Section 2 sets
+forth the rules for creation of derivative works of GPL'd software.
+We discuss the intent of this section of GPL and how it relates to the
+copyright situation discussed in our discussion of derivative works.
+We also explain the details of preparing derivative source in a
+GPL-compliant way.</p>
+</dd>
+<dt> GPL, Section 3:
+Grants for Creating Binary Derivative Works</dt>
+<dd>
+<p> Source-only
+distribution works well for technically savvy clients and users, but
+most want runnable binary programs as well.  Section 3 gives
+permission for the creation and distribution of such binary works.  We
+explain how GPL's requirement for corresponding source code operates,
+and detail what distribution options are available to distributors of
+binary GPL'd software.  We explore the benefits and downsides of each
+of those options.</p>
+</dd>
+<dt>The Implied Patent
+Grant in GPL</dt>
+<dd>
+<p> Patent rights are
+most often granted expressly, through detailed language in a license.
+However, express patent grants are not the exclusive way rights in
+patents are granted by patentees.  Even without express language,
+patent rights can be granted by a patentee's actions or behavior.  The
+GPL contains no express patent grant.  Does that mean it grants less
+rights in the licensor's patents than other licenses which do? Or,
+does the GPL, in its silence, actually result in a grant of patent
+rights to the licensee greater than what occurs through many other
+Free Software and &ldquo;Open Source&rdquo; licenses?
+</p>
+<p>We will consider these questions and
+provide detailed answers to them.</p>
+</dd>
+<dt>GPL, Section 4:
+Termination of License
+</dt>
+<dd>
+<p> Section 4
+terminates rights under the GPL for those who violate it.  We discuss
+how such termination works, what it means for violators, what risks
+one takes in violating, and how rights are typically restored.  We
+briefly mention how Section 4 is used as the central tool in GPL
+enforcement.
+</p>
+</dd>
+<dt>GPL, Section 5:
+Acceptance of License
+</dt>
+<dd>
+<p> GPL is not a
+contract, so acceptance of the license works differently than it does
+for contracts.  We discuss how this acceptance works under the copyright
+rules that govern the GPL.</p>
+</dd>
+<dt>GPL, Section 6:
+Prohibition on Further Restrictions</dt>
+<dd>
+<p> Other licensing
+terms cannot be placed on GPL'd software that would trump the rights
+granted under GPL.  We discuss how Section 6 is used to ensure that no
+such additional restrictions occur.  We briefly discuss how this leads
+to the concept of GPL-incompatible Free Software licenses.</p>
+</dd>
+<dt>GPL, Section 7:
+Conflicts with Other Agreements or Orders</dt>
+<dd>
+<p> Just as additional
+licensing restrictions cannot trump the GPL, outside agreements,
+patent licenses or court orders cannot do so either.  We discuss how
+Section 7 ensures that other rules outside of the direct software
+license cannot take rights away from users, distributors, and
+modifiers of GPL'd software.
+</p>
+</dd>
+<dt>GPL, Section 8:
+International Licensing Issues</dt>
+<dd>
+<p> Section 8 is a
+rarely used part of the GPL that helps copyright holders when certain
+technologies are prohibited from full international distribution due
+to draconian rules elsewhere in the world.  We explain how Section 8
+helps such copyright holders.
+</p>
+</dd>
+<dt>GPL, Section 9: FSF
+as GPL's Stewards</dt>
+<dd>
+<p> We discuss how the
+update process and release of new GPL versions happens.</p>
+</dd>
+<dt>GPL, Section 10:
+Copyright Holder's Exceptions to GPL</dt>
+<dd>
+<p> Section 10 reminds
+licensees that under copyright law, other relicensing arrangements can
+be made.  We discuss how this can often be used as a business model
+and we explicate that model's benefits and downsides.</p>
+</dd>
+<dt>GPL, Section 11:
+Disclaimer of Warranties</dt>
+<dd></dd>
+<dt>GPL, Section 12:
+Limitation of Liability</dt>
+<dd>
+<p> Almost all software
+licenses, including Free Software licenses such as the GPL, contain
+sections, typically in all caps, regarding warranties and liability.
+The purposes of these sections are lost on most non-lawyers, but
+attorneys understand the importance their language provides to both
+the licensor and the licensee.  Some have argued that the GPL's
+Sections 11 and 12 render it entirely unenforceable.  We consider
+whether that is true, and present the likely interpretation and
+implementation of the GPL's Warranty Disclaimer and Liability
+Limitation provisions.</p>
+</dd>
+<dt>Lesser General
+Public License (LGPL)</dt>
+<dd>
+<p> The LGPL is a
+&ldquo;scaled back&rdquo; version of GPL, designed specifically to
+allow creation of a very well-defined class of proprietary derivative
+works.  However, it does prohibit turning the LGPL'd software itself
+directly into proprietary software.
+</p>
+<p> We discuss the
+basic design of LGPL and how it compares and contrasts with GPL.  We
+introduce the two classes of derivative works covered by LGPL,
+&ldquo;works that use the library&rdquo; and &ldquo;works based on the
+library&rdquo;, and give some concrete examples of what proprietary
+derivative works are prohibited and permitted when basing the software
+on an LGPL'd work.
+</p>
+</dd>
+</dl>
+<h3>Pricing (Book by December 24, 2003 for early registration
+discount)</h3>
+<p>$495 for registrations on or before
+December 24, 2003 and $595 after December 24</p>
+<p>
+<b>Financial Aid
+Policy:</b> Applicants with annual incomes of up to $15,000 are
+entitled to a 75% discount.  People with incomes between $15,000 and
+$30,000 receive a 50% discount.  Any member of the judiciary,
+academics or attorneys from non-profit organizations receive a 10%
+discount.  If you fall within one of these categories, please contact
+John at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or
+Ravi at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or by
+phone at 617.620.9640.</p>
+<p>To register for the
+seminar, please download
+the registration form,
+fill it in and fax it to FSF.</p>
+<p><b>CLE
+Credits: </b>Attorneys who successfully complete the day long course
+will be entitled to 7 New York Transitional CLE credits toward the
+area of Professional Practice.</p>
+<p>Companies that have
+signed up as Corporate Patrons of FSF receive two complimentary seats
+per year at FSF seminars and reduced rates for additional
+participants.  Please
+contact <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> for
+more details.  You can find out more about the Corporate Patron
+Program at <a href="http://patron.fsf.org/";>
+http://patron.fsf.org</a></p>
+<p>The seminar will be
+held at Columbia Law School in New York.  Directions will be sent
+following registration.  For more information, please contact Ravi
+Khanna, FSF's Director of Communication
+at <a href="mailto:address@hidden";>&lt;address@hidden&gt;</a> or by
+calling 1+617-620-9640.</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 &amp; GNU inquiries to
+<a href="mailto:address@hidden";>&lt;address@hidden&gt;</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";>&lt;address@hidden&gt;</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";>
+        &lt;address@hidden&gt;</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 &copy; 2003, 2004, 2007, 2008, 2009, 2014, 2015 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: 2018/12/01 03:57:51 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>