[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www licenses/po/200104_seminar.translist licens...
|
From: |
GNUN |
|
Subject: |
www licenses/po/200104_seminar.translist licens... |
|
Date: |
Sat, 25 Jul 2015 14:28:18 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: GNUN <gnun> 15/07/25 14:28:18
Modified files:
licenses/po : 200104_seminar.translist
210104_seminar.translist
philosophy/sco/po: subpoena.translist
proprietary/po : proprietary-interference.translist
server/source/po: source.de.po source.translist
Added files:
licenses : 200104_seminar.de.html 210104_seminar.de.html
licenses/po : 200104_seminar.de-en.html
210104_seminar.de-en.html
philosophy/sco : subpoena.de.html
philosophy/sco/po: subpoena.de-en.html
proprietary : proprietary-interference.de.html
proprietary/po : proprietary-interference.de-en.html
server/source : source.de.html
server/source/po: source.de-en.html
Log message:
Automatic update by GNUnited Nations.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/200104_seminar.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/210104_seminar.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/200104_seminar.translist?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/210104_seminar.translist?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/200104_seminar.de-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/po/210104_seminar.de-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/sco/subpoena.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/sco/po/subpoena.translist?cvsroot=www&r1=1.10&r2=1.11
http://web.cvs.savannah.gnu.org/viewcvs/www/philosophy/sco/po/subpoena.de-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/proprietary-interference.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-interference.translist?cvsroot=www&r1=1.3&r2=1.4
http://web.cvs.savannah.gnu.org/viewcvs/www/proprietary/po/proprietary-interference.de-en.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/source/source.de.html?cvsroot=www&rev=1.1
http://web.cvs.savannah.gnu.org/viewcvs/www/server/source/po/source.de.po?cvsroot=www&r1=1.1&r2=1.2
http://web.cvs.savannah.gnu.org/viewcvs/www/server/source/po/source.translist?cvsroot=www&r1=1.7&r2=1.8
http://web.cvs.savannah.gnu.org/viewcvs/www/server/source/po/source.de-en.html?cvsroot=www&rev=1.1
Patches:
Index: licenses/po/200104_seminar.translist
===================================================================
RCS file: /web/www/www/licenses/po/200104_seminar.translist,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- licenses/po/200104_seminar.translist 22 May 2015 06:07:05 -0000
1.10
+++ licenses/po/200104_seminar.translist 25 Jul 2015 14:28:15 -0000
1.11
@@ -3,10 +3,12 @@
value='<div id="translations">
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/licenses/200104_seminar.en.html">English</a> [en]</span>
+<span dir="ltr"><a lang="de" hreflang="de"
href="/licenses/200104_seminar.de.html">Deutsch</a> [de]</span>
<span dir="ltr"><a lang="fr" hreflang="fr"
href="/licenses/200104_seminar.fr.html">français</a> [fr]</span>
</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" />
<!-- end translist file -->
Index: licenses/po/210104_seminar.translist
===================================================================
RCS file: /web/www/www/licenses/po/210104_seminar.translist,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- licenses/po/210104_seminar.translist 22 May 2015 06:07:06 -0000
1.10
+++ licenses/po/210104_seminar.translist 25 Jul 2015 14:28:16 -0000
1.11
@@ -3,10 +3,12 @@
value='<div id="translations">
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/licenses/210104_seminar.en.html">English</a> [en]</span>
+<span dir="ltr"><a lang="de" hreflang="de"
href="/licenses/210104_seminar.de.html">Deutsch</a> [de]</span>
<span dir="ltr"><a lang="fr" hreflang="fr"
href="/licenses/210104_seminar.fr.html">français</a> [fr]</span>
</p>
</div>' -->
<link rel="alternate" type="text/html" href="/licenses/210104_seminar.html"
hreflang="x-default" />
<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/licenses/210104_seminar.en.html" title="English" />
+<link rel="alternate" type="text/html" lang="de" hreflang="de"
href="/licenses/210104_seminar.de.html" title="Deutsch" />
<link rel="alternate" type="text/html" lang="fr" hreflang="fr"
href="/licenses/210104_seminar.fr.html" title="français" />
<!-- end translist file -->
Index: philosophy/sco/po/subpoena.translist
===================================================================
RCS file: /web/www/www/philosophy/sco/po/subpoena.translist,v
retrieving revision 1.10
retrieving revision 1.11
diff -u -b -r1.10 -r1.11
--- philosophy/sco/po/subpoena.translist 21 May 2015 07:18:33 -0000
1.10
+++ philosophy/sco/po/subpoena.translist 25 Jul 2015 14:28:17 -0000
1.11
@@ -3,6 +3,7 @@
value='<div id="translations">
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/philosophy/sco/subpoena.en.html">English</a> [en]</span>
+<span dir="ltr"><a lang="de" hreflang="de"
href="/philosophy/sco/subpoena.de.html">Deutsch</a> [de]</span>
<span dir="ltr"><a lang="es" hreflang="es"
href="/philosophy/sco/subpoena.es.html">español</a> [es]</span>
<span dir="ltr"><a lang="fr" hreflang="fr"
href="/philosophy/sco/subpoena.fr.html">français</a> [fr]</span>
<span dir="ltr"><a lang="ru" hreflang="ru"
href="/philosophy/sco/subpoena.ru.html">ÑÑÑÑкий</a> [ru]</span>
@@ -10,6 +11,7 @@
</div>' -->
<link rel="alternate" type="text/html" href="/philosophy/sco/subpoena.html"
hreflang="x-default" />
<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/philosophy/sco/subpoena.en.html" title="English" />
+<link rel="alternate" type="text/html" lang="de" hreflang="de"
href="/philosophy/sco/subpoena.de.html" title="Deutsch" />
<link rel="alternate" type="text/html" lang="es" hreflang="es"
href="/philosophy/sco/subpoena.es.html" title="español" />
<link rel="alternate" type="text/html" lang="fr" hreflang="fr"
href="/philosophy/sco/subpoena.fr.html" title="français" />
<link rel="alternate" type="text/html" lang="ru" hreflang="ru"
href="/philosophy/sco/subpoena.ru.html" title="ÑÑÑÑкий" />
Index: proprietary/po/proprietary-interference.translist
===================================================================
RCS file: /web/www/www/proprietary/po/proprietary-interference.translist,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -b -r1.3 -r1.4
--- proprietary/po/proprietary-interference.translist 23 Jul 2015 12:57:26
-0000 1.3
+++ proprietary/po/proprietary-interference.translist 25 Jul 2015 14:28:17
-0000 1.4
@@ -3,12 +3,14 @@
value='<div id="translations">
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/proprietary/proprietary-interference.en.html">English</a> [en]</span>
+<span dir="ltr"><a lang="de" hreflang="de"
href="/proprietary/proprietary-interference.de.html">Deutsch</a> [de]</span>
<span dir="ltr"><a lang="fr" hreflang="fr"
href="/proprietary/proprietary-interference.fr.html">français</a> [fr]</span>
<span dir="ltr"><a lang="ja" hreflang="ja"
href="/proprietary/proprietary-interference.ja.html">æ¥æ¬èª</a> [ja]</span>
</p>
</div>' -->
<link rel="alternate" type="text/html"
href="/proprietary/proprietary-interference.html" hreflang="x-default" />
<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/proprietary/proprietary-interference.en.html" title="English" />
+<link rel="alternate" type="text/html" lang="de" hreflang="de"
href="/proprietary/proprietary-interference.de.html" title="Deutsch" />
<link rel="alternate" type="text/html" lang="fr" hreflang="fr"
href="/proprietary/proprietary-interference.fr.html" title="français" />
<link rel="alternate" type="text/html" lang="ja" hreflang="ja"
href="/proprietary/proprietary-interference.ja.html" title="æ¥æ¬èª" />
<!-- end translist file -->
Index: server/source/po/source.de.po
===================================================================
RCS file: /web/www/www/server/source/po/source.de.po,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -b -r1.1 -r1.2
--- server/source/po/source.de.po 25 Jul 2015 14:24:35 -0000 1.1
+++ server/source/po/source.de.po 25 Jul 2015 14:28:18 -0000 1.2
@@ -6,6 +6,7 @@
msgid ""
msgstr ""
"Project-Id-Version: source.html\n"
+"Report-Msgid-Bugs-To: address@hidden"
"POT-Creation-Date: 2015-06-06 17:55+0000\n"
"PO-Revision-Date: 2015-07-23 22:00+0200\n"
"Last-Translator: Jоегg Kоhпе <joeko (AT) online [PUNKT] de>\n"
@@ -14,7 +15,6 @@
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
-"Report-Msgid-Bugs-To: address@hidden"
#. type: Content of: <title>
msgid "Web Server Utility Sources - GNU Project - Free Software Foundation"
Index: server/source/po/source.translist
===================================================================
RCS file: /web/www/www/server/source/po/source.translist,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -b -r1.7 -r1.8
--- server/source/po/source.translist 22 May 2015 07:13:01 -0000 1.7
+++ server/source/po/source.translist 25 Jul 2015 14:28:18 -0000 1.8
@@ -3,10 +3,12 @@
value='<div id="translations">
<p>
<span dir="ltr" class="original"><a lang="en" hreflang="en"
href="/server/source/source.en.html">English</a> [en]</span>
+<span dir="ltr"><a lang="de" hreflang="de"
href="/server/source/source.de.html">Deutsch</a> [de]</span>
<span dir="ltr"><a lang="es" hreflang="es"
href="/server/source/source.es.html">español</a> [es]</span>
</p>
</div>' -->
<link rel="alternate" type="text/html" href="/server/source/source.html"
hreflang="x-default" />
<link rel="alternate" type="text/html" lang="en" hreflang="en"
href="/server/source/source.en.html" title="English" />
+<link rel="alternate" type="text/html" lang="de" hreflang="de"
href="/server/source/source.de.html" title="Deutsch" />
<link rel="alternate" type="text/html" lang="es" hreflang="es"
href="/server/source/source.es.html" title="español" />
<!-- end translist file -->
Index: licenses/200104_seminar.de.html
===================================================================
RCS file: licenses/200104_seminar.de.html
diff -N licenses/200104_seminar.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/200104_seminar.de.html 25 Jul 2015 14:28:14 -0000 1.1
@@ -0,0 +1,303 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/200104_seminar.en.html" -->
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>FSF-Seminar: Detailed Study and Analysis of GPL and LGPL</title>
+<meta name="CREATED" content="20031124;15182100" />
+<meta name="CHANGED" content="16010101;0" />
+
+<!--#include virtual="/licenses/po/200104_seminar.translist" -->
+<!--#include virtual="/server/banner.de.html" -->
+<h2>FSF-Seminar: Detailed Study and Analysis of GPL and LGPL</h2>
+<div style="font-weight: bold; text-align:
center;"><big>FSF-Seminar</big></div>
+<p style="margin-bottom: 0in;"> </p>
+<p style="margin-bottom: 0in; text-align: center;"><big><span
style="font-weight: bold;">Detailed Study and Analysis of GPL and
+LGPL<br />
+</span></big></p>
+<p style="margin-bottom: 0in; text-align: center;"><b>Columbia Law School,
Columbia University<br />
+New York, NY<br />
+January 20, 2004 (9:00 am - 6:00 pm)</b><br />
+<br />
+</p>
+<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>
+<p style="margin-bottom: 0in; margin-left:
+40px;"><i>Prerequisites:</i> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"><i>Audience:</i> 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>
+<p style="margin-bottom: 0in; margin-left: 40px;"><b>Lunchtime Speaker: </b><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 “Broadcast
+Flag”. 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>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * Free Software Principles
and the Free Software Definition
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;">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 “Free
+Software” (software whose license grants freedoms to copy, share,
+modify and redistribute the software either gratis or for a fee) for
+for-profit companies.
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * Preamble of the GNU
General Public License (GPL)
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 0:
Definitions, etc.
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 1: Grant for
Verbatim Source Copying
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * Derivative Works: Statute
and Case Law</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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 “derivative work?” 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 2: Grants
for Source Derivative Works</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 3: Grants
for Creating Binary Derivative Works</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * The Implied Patent Grant
in GPL</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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 “Open
+Source” licenses?
+</p>
+<div style="margin-left: 40px;"> </div>
+<div style="margin-left: 80px;"> We will consider these questions and provide
detailed answers to them.
+</div>
+<p style="margin-bottom: 0in; margin-left: 40px;">* GPL, Section 4:
Termination of License
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 5:
Acceptance of License
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 6:
Prohibition on Further Restrictions</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 7: Conflicts
with Other Agreements or Orders</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 8:
International Licensing Issues</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 9: FSF as
GPL's Stewards</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> We discuss how the update
process and release of new GPL versions happens.</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 10:
Copyright Holder's Exceptions to GPL</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 11:
Disclaimer of Warranties</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;">* GPL, Section 12:
Limitation of Liability</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * Lesser General Public
License (LGPL)</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> The LGPL is a “scaled
back” 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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,
+“works that use the library” and “works based on the
+library”, and give some concrete examples of what proprietary
+derivative works are prohibited and permitted when basing the software on an
+LGPL'd work.
+</p>
+<p><b>Pricing (Book by December 24, 2003 for early registration discount):</b>
+</p>
+<div style="margin-left: 40px;">$495 for registrations on or before December
24, 2003 and $595 after
+December 24<br />
+<br />
+<span style="font-family: Nimbus Roman No9 L, serif"><span
+style="text-decoration: underline;">Financial Aid Policy:</span> 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";><address@hidden></a> or
+Ravi at <a href="mailto:address@hidden";><address@hidden></a> or by phone
+at 617.620.9640.</span><br /> <br /> To register for the seminar, please
download the <a
+href="" title="Thank you for your interest. The seminar is over and
+aregistration no longer possible!">registration form</a>, fill it in and
+faxit to FSF.<br /> <br />
+</div>
+<p style="font-family: Nimbus Roman No9 L, serif"><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 style="font-family: Nimbus Roman No9 L, serif">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";><address@hidden></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 style="font-family: Nimbus Roman No9 L, serif">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";><address@hidden></a> or by calling
+1+617-620-9640.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie allgemeine Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/"><span xml:lang="en" lang="en">Free Software
+Foundation</span> kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bei der Ãbersetzung dieses Werkes wurde mit gröÃter Sorgfalt
+vorgegangen. Trotzdem können Fehler nicht völlig ausgeschlossen
+werden. Sollten Sie Fehler bemerken oder Vorschläge, Kommentare oder
+Anfragen zu diesem Dokument haben, kontaktieren Sie bitte unser
+Ãbersetzungsteam <a
+href="mailto:address@hidden@gnu.org";><address@hidden></a>.</p>
+<p>Weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen unserer Webseiten finden Sie in der <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>.
+</p>
+
+<p>
+Copyright © 2003, 2004 Free Software Foundation, Inc.
+</p>
+<p>Dieses Werk ist lizenziert unter einer <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von
+Amerika</a>-Lizenz.
+</p>
+
+<!--#include virtual="/server/bottom-notes.de.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> <a
+href="https://savannah.gnu.org/projects/www-de";><www-de></a>, 2015.</div>
+
+<p><!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2015/07/25 14:28:14 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+</div>
+</body>
+</html>
Index: licenses/210104_seminar.de.html
===================================================================
RCS file: licenses/210104_seminar.de.html
diff -N licenses/210104_seminar.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/210104_seminar.de.html 25 Jul 2015 14:28:15 -0000 1.1
@@ -0,0 +1,218 @@
+<!--#set var="ENGLISH_PAGE" value="/licenses/210104_seminar.en.html" -->
+<!--#include virtual="/server/header.de.html" -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>FSF-Seminar: Case Study and Legal Ethics</title>
+<meta name="CREATED" content="20031124;15183300" />
+<meta name="CHANGED" content="20031124;15494100" />
+
+<!--#include virtual="/licenses/po/210104_seminar.translist" -->
+<!--#include virtual="/server/banner.de.html" -->
+<h2>FSF-Seminar: Case Study and Legal Ethics</h2>
+
+<div style="font-weight: bold; text-align:
center;"><big>FSF-Seminar</big></div>
+<b></b>
+<p style="margin-bottom: 0in;"> </p>
+<p style="margin-bottom: 0in; text-align: center; font-weight: bold;"><big>GPL
Compliance Case Studies and Legal Ethics in Free Software
+Licensing</big></p>
+<p style="margin-bottom: 0in; text-align: center; font-weight:
bold;"><big>Columbia Law School, Columbia University<br />
+New York, NY<br />
+January 21, 2004 (9:00 am - 6:00 pm)<br />
+</big></p>
+<p>
+This one-day course presents the details of five different GPL compliance
+cases handled by FSF's GPL Compliance Laboratory. Each case offers unique
+insights into problems that can arise when the terms of GPL are not properly
+followed, and how diplomatic negotiation between the violator and the
+copyright holder can yield positive results for both parties.</p>
+<p>
+This course also includes a unit on the ethical considerations for attorneys
+who want to represent clients that make use of or sell Free Software
+products.</p>
+
+<p style="margin-left: 40px;"><i>Prerequisites:</i> Attendees should have
successfully completed the
+course, a <i>Detailed Study and Analysis of GPL and LGPL</i>, as the
+material from that course forms the building blocks for this material, or
+have attended a previous <i>Free Software Licensing and the GNU GPL
+Seminar</i>.
+</p>
+<p style="margin-bottom: 0in; margin-left: 40px;"><i>Audience:</i> The course
is of most interest to lawyers who have clients
+or employers that deal with Free Software on a regular basis. However,
+technical managers and executives whose businesses use or distribute Free
+Software will also find the course very helpful.
+</p>
+<p>The course will include the topics listed below, along with ample time for
+questions and discussions.
+</p>
+<p style="margin-bottom: 0in; margin-left: 40px;"><b>Lunchtime Speaker: </b><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 “Broadcast
+Flag”. 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>
+<p><b>GPL Compliance Case Studies:</b></p>
+<p style="margin-left: 40px;">* Overview of FSF's GPL Compliance Lab</p>
+<p style="margin-left: 80px;">We present a brief introduction to the work that
FSF does to enforce the GPL
+and defend the freedoms granted by Free Software.</p>
+<p style="margin-left: 40px;">* GPL Violation Case Study A
+</p>
+<p style="margin-left: 80px;">In this case study, we consider one of the most
complex and longest-running
+violations that FSF has handled. Company A distributed a derivative work of
+the GNU Complier Collection (GCC) without complete corresponding source, and
+refused to distribute any source at all to anyone who was not their direct
+customer. We follow the slow movement toward compliance and explain how FSF
+deals with sometimes belligerent violators.
+</p>
+<p style="margin-left: 40px;">* GPL Violation Case Study B</p>
+<p style="margin-left: 80px;">In this case study, we consider a contrasting
violation to Case A. Company
+B, who sold a complete GNU/Linux distribution, had worked hard to be in
+compliance, but we had nevertheless found an infraction in their compliance
+efforts. We explain how smoothly violations of this type can be resolved
+and the process that an otherwise friendly violator can expect.
+</p>
+<p style="margin-left: 40px;">* GPL Violation Case Study C</p>
+<p style="margin-left: 80px;">In this case study, we present a violation where
an entire embedded
+GNU/Linux distribution was included in a consumer electronic device. We
+consider the problems faced regarding kernel modules for device drivers for
+government-regulated hardware, and cases where both an upstream provider and
+a downstream distributor are in violation on separate matters.
+</p>
+<p style="margin-left: 40px;">* GPL Violation Case Study D</p>
+<p style="margin-left: 80px;">In this case study, we consider how to handle
the inevitable violations that
+can occur from a company that is generally committed to doing Free Software
+as a regular part of its business, but — due to experimentation with
+new cutting edge business models, or because of mere oversights — has
+occasional GPL violations or near-violations.</p>
+<p style="margin-left: 40px;"> * Good Practices for GPL Compliance
+</p>
+<p style="margin-left: 80px;">After discussing the details of the various
archetypes of GPL compliance
+efforts undertaken by FSF, we generalize what we have learned to advise on
+good practices to build a product from start to finish in compliance with
+GPL, and how to build internal policies to assure that your client or
+company is never faced with a violation report.</p>
+<p><b>Ethical Considerations for the Attorney Practicing Free Software</b></p>
+<p style="margin-left: 40px;">This portion of the course will focus on ethical
issues that may arise for
+attorneys counseling clients with respect to free software issues. Many of
+these topics have more general application, but specific discussion of the
+ways in which these issues may arise for free software clients will be
+presented.</p>
+<p style="margin-left: 40px;"> * Part I: Representing Free Software Clients</p>
+<p style="margin-left: 80px;">An attorney's ethical duties run to not just
their clients, but to potential
+clients and the general public as well. Pro bono representation of free
+software clients not only conforms with the principles set forth by most Bar
+Associations, but also provides many other benefits to an attorney. Once a
+client is retained, the duty of loyalty attaches and conflicts, be they
+direct, indirect, or political, should be identified and handled.
+</p>
+<p style="margin-left: 40px;"> * Part II: Practicing Free Software
+</p>
+<p style="margin-bottom: 0in; margin-left: 80px;">Differing ethical issues
arise in the context of counseling a client who is
+a free software licensor as opposed to one who is a free software licensee.
+Further still, representing a client who is both licensor and licensee
+presents a combination of all of these issues. Compliance investigation and
+enforcement strategies must be implemented in accordance with both the duty
+of loyalty and the duty of honesty. Likewise, performing exposure abatement
+while also defending against charges of infringement may pose problems
+within the attorney-client relationship. The ethical considerations
+relevant to each of these situations will be presented and discussed.
+</p>
+<p style="margin-left: 40px;">* Part III: More General Ethical Considerations
Relevant to Free Software
+</p>
+<p style="margin-left: 80px;">Free software counseling is but one specialty
within the realm of
+intellectual property counseling in general. A review of various topics of
+more general application, but with special relevance to free software
+counseling, will be given along with a discussion of the reasons why and
+ways in which such issues arise when representing free software clients.
+Patent prosecution and governing rules considerations are two such topics.
+</p>
+
+<p><b>Pricing (Book by December 24, 2003 for early registration
discount):</b></p>
+<div style="margin-left: 40px;">$495 for registrations on or before December
24, 2003 and $595 after
+December 24 <br />
+<br />
+<span style="font-family: Nimbus Roman No9 L, serif"><span
+style="text-decoration: underline;">Financial Aid Policy:</span> 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";><address@hidden></a> or
+Ravi at <a href="mailto:address@hidden";><address@hidden></a> or by phone
+at 617.620.9640.</span> <br /> <br />
+</div>
+
+<p style="font-family: Nimbus Roman No9 L, serif"><b>CLE Credits:</b>
Attorneys who successfully complete the day long course
+will be entitled to a total of 7.5 New York Transitional CLE credits, 3 in
+the area of Professional Practice and 4.5 toward the Ethics and
+Professionalism requirments.</p>
+<p style="font-family: Nimbus Roman No9 L, serif">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";><address@hidden></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 style="font-family: Nimbus Roman No9 L, serif">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";><address@hidden></a> or by calling
+1+617-620-9640.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+ </div>
+</div>
+
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+
+<p>
+Bitte senden Sie allgemeine Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/"><span xml:lang="en" lang="en">Free Software
+Foundation</span> kontaktieren</a>.
+<br />
+Bitte senden Sie ungültige Verweise und andere Korrekturen oder Vorschläge
+an <a href="mailto:address@hidden";><address@hidden></a>.
+</p>
+
+<p>
+Bei der Ãbersetzung dieses Werkes wurde mit gröÃter Sorgfalt
+vorgegangen. Trotzdem können Fehler nicht völlig ausgeschlossen
+werden. Sollten Sie Fehler bemerken oder Vorschläge, Kommentare oder
+Anfragen zu diesem Dokument haben, kontaktieren Sie bitte unser
+Ãbersetzungsteam <a
+href="mailto:address@hidden@gnu.org";><address@hidden></a>.</p>
+<p>Weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen unserer Webseiten finden Sie in der <a
+href="/server/standards/README.translations">LIESMICH für Ãbersetzungen</a>.
+</p>
+
+<p>Copyright © 2003, 2004 Free Software Foundation, Inc.</p>
+<p>Dieses Werk ist lizenziert unter einer <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von
+Amerika</a>-Lizenz.
+</p>
+
+<!--#include virtual="/server/bottom-notes.de.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> <a
+href="https://savannah.gnu.org/projects/www-de";><www-de></a>, 2015.</div>
+
+<p><!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2015/07/25 14:28:15 $
+
+<!-- timestamp end -->
+</p>
+</div>
+
+</div>
+</body>
+</html>
Index: licenses/po/200104_seminar.de-en.html
===================================================================
RCS file: licenses/po/200104_seminar.de-en.html
diff -N licenses/po/200104_seminar.de-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/po/200104_seminar.de-en.html 25 Jul 2015 14:28:15 -0000
1.1
@@ -0,0 +1,335 @@
+<!--#include virtual="/server/header.html" -->
+<title>FSF Seminar: Detailed Study and Analysis of GPL and LGPL</title>
+<meta name="CREATED" content="20031124;15182100" />
+<meta name="CHANGED" content="16010101;0" />
+<!--#include virtual="/licenses/po/200104_seminar.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>FSF Seminar: Detailed Study and Analysis of GPL and LGPL</h2>
+<div style="font-weight: bold; text-align: center;"><big>FSF
Seminar</big></div>
+<p style="margin-bottom: 0in;"> </p>
+<p style="margin-bottom: 0in; text-align: center;"><big><span
+ style="font-weight: bold;">Detailed Study and Analysis of GPL and
+ LGPL<br />
+</span></big></p>
+<p style="margin-bottom: 0in; text-align: center;"><b>Columbia Law
+School, Columbia University<br />
+New York, NY<br />
+January 20, 2004 (9:00 am - 6:00 pm)</b><br />
+<br />
+</p>
+<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>
+<p style="margin-bottom: 0in; margin-left:
+40px;"><i>Prerequisites:</i> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"><i>Audience:</i> 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>
+<p style="margin-bottom: 0in; margin-left: 40px;"><b>Lunchtime
+Speaker: </b><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
+“Broadcast Flag”. 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>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * Free Software
+Principles and the Free Software Definition
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;">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 “Free Software” (software whose license grants freedoms
+to copy, share, modify and redistribute the software either gratis or
+for a fee) for for-profit companies.
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * Preamble of the GNU
+General Public License (GPL)
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 0:
+Definitions, etc.
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 1:
+Grant for Verbatim Source Copying
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * Derivative Works:
+Statute and Case Law</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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 “derivative
+work?” 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 2:
+Grants for Source Derivative Works</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 3:
+Grants for Creating Binary Derivative Works</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * The Implied Patent
+Grant in GPL</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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 “Open Source” licenses?
+</p>
+<div style="margin-left: 40px;"> </div>
+<div style="margin-left: 80px;"> We will consider these questions and
+provide detailed answers to them.
+</div>
+<p style="margin-bottom: 0in; margin-left: 40px;">* GPL, Section 4:
+Termination of License
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 5:
+Acceptance of License
+</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 6:
+Prohibition on Further Restrictions</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 7:
+Conflicts with Other Agreements or Orders</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 8:
+International Licensing Issues</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 9: FSF
+as GPL's Stewards</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> We discuss how the
+update process and release of new GPL versions happens.</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 10:
+Copyright Holder's Exceptions to GPL</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * GPL, Section 11:
+Disclaimer of Warranties</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;">* GPL, Section 12:
+Limitation of Liability</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 40px;"> * Lesser General
+Public License (LGPL)</p>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> The LGPL is a
+“scaled back” 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>
+<div style="margin-left: 40px;"> </div>
+<p style="margin-bottom: 0in; margin-left: 80px;"> 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,
+“works that use the library” and “works based on the
+library”, and give some concrete examples of what proprietary
+derivative works are prohibited and permitted when basing the software
+on an LGPL'd work.
+</p>
+<p><b>Pricing (Book by December 24, 2003 for early registration
+discount):</b>
+</p>
+<div style="margin-left: 40px;">$495 for registrations on or before
+December 24, 2003 and $595 after December 24<br />
+<br />
+<span style="font-family: Nimbus Roman No9 L,
+serif"><span style="text-decoration: underline;">Financial Aid
+Policy:</span> 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";><address@hidden></a> or
+Ravi at <a href="mailto:address@hidden";><address@hidden></a> or by
+phone at 617.620.9640.</span><br /> <br /> To register for the
+seminar, please download
+the registration form,
+fill it in and fax it to FSF.<br /> <br />
+</div>
+<p style="font-family: Nimbus Roman No9 L, serif"><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 style="font-family: Nimbus Roman No9 L, serif">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";><address@hidden></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 style="font-family: Nimbus Roman No9 L, serif">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";><address@hidden></a> or by
+calling 1+617-620-9640.</p>
+
+</div>
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>
+Copyright © 2003, 2004, 2007, 2008, 2009, 2014 Free Software
+Foundation, Inc.
+</p>
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
+</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2015/07/25 14:28:15 $
+<!-- timestamp end -->
+</p>
+</div>
+
+</div>
+</body>
+</html>
Index: licenses/po/210104_seminar.de-en.html
===================================================================
RCS file: licenses/po/210104_seminar.de-en.html
diff -N licenses/po/210104_seminar.de-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ licenses/po/210104_seminar.de-en.html 25 Jul 2015 14:28:15 -0000
1.1
@@ -0,0 +1,222 @@
+<!--#include virtual="/server/header.html" -->
+<title>FSF Seminar: Case Study and Legal Ethics</title>
+<meta name="CREATED" content="20031124;15183300" />
+<meta name="CHANGED" content="20031124;15494100" />
+<!--#include virtual="/licenses/po/210104_seminar.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>FSF Seminar: Case Study and Legal Ethics</h2>
+
+<div style="font-weight: bold; text-align: center;"><big>FSF
Seminar</big></div>
+<b></b>
+<p style="margin-bottom: 0in;"> </p>
+<p style="margin-bottom: 0in; text-align: center; font-weight: bold;"><big>GPL
+Compliance Case Studies and Legal Ethics in Free Software Licensing</big></p>
+<p style="margin-bottom: 0in; text-align: center; font-weight:
bold;"><big>Columbia
+Law School, Columbia University<br />
+New York, NY<br />
+January 21, 2004 (9:00 am - 6:00 pm)<br />
+</big></p>
+<p>
+This one-day course presents the details of five different GPL
+compliance cases handled by FSF's GPL Compliance Laboratory. Each case
+offers unique insights into problems that can arise when the terms of
+GPL are not properly followed, and how diplomatic negotiation between
+the violator and the copyright holder can yield positive results for
+both parties.</p>
+<p>
+This course also includes a unit on the ethical considerations for
+attorneys who want to represent clients that make use of or sell Free
+Software products.</p>
+
+<p style="margin-left: 40px;"><i>Prerequisites:</i> Attendees should
+have successfully completed the course, a <i>Detailed Study and
+Analysis of GPL and LGPL</i>, as the material from that course forms
+the building blocks for this material, or have attended a
+previous <i>Free Software Licensing and the GNU GPL Seminar</i>.
+</p>
+<p style="margin-bottom: 0in; margin-left: 40px;"><i>Audience:</i> The
+course is of most interest to lawyers who have clients or employers
+that deal with Free Software on a regular basis. However, technical
+managers and executives whose businesses use or distribute Free
+Software will also find the course very helpful.
+</p>
+<p>The course will include the topics listed below, along with ample
+time for questions and discussions.
+</p>
+<p style="margin-bottom: 0in; margin-left: 40px;"><b>Lunchtime
+Speaker: </b><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
+“Broadcast Flag”. 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>
+<p><b>GPL Compliance Case Studies:</b></p>
+<p style="margin-left: 40px;">* Overview of FSF's GPL Compliance
+Lab</p>
+<p style="margin-left: 80px;">We present a brief
+introduction to the work that FSF does to enforce the GPL and defend the
+freedoms granted by Free Software.</p>
+<p style="margin-left: 40px;">* GPL Violation Case Study A
+</p>
+<p style="margin-left: 80px;">In this case study, we consider one of
+the most complex and longest-running violations that FSF has handled.
+Company A distributed a derivative work of the GNU Complier Collection
+(GCC) without complete corresponding source, and refused to distribute
+any source at all to anyone who was not their direct customer. We
+follow the slow movement toward compliance and explain how FSF deals
+with sometimes belligerent violators.
+</p>
+<p style="margin-left: 40px;">* GPL Violation Case Study B</p>
+<p style="margin-left: 80px;">In this case study, we consider a
+contrasting violation to Case A. Company B, who sold a complete
+GNU/Linux distribution, had worked hard to be in compliance, but we
+had nevertheless found an infraction in their compliance efforts. We
+explain how smoothly violations of this type can be resolved and the
+process that an otherwise friendly violator can expect.
+</p>
+<p style="margin-left: 40px;">* GPL Violation Case Study C</p>
+<p style="margin-left: 80px;">In this case study, we present a
+violation where an entire embedded GNU/Linux distribution was included
+in a consumer electronic device. We consider the problems faced
+regarding kernel modules for device drivers for government-regulated
+hardware, and cases where both an upstream provider and a downstream
+distributor are in violation on separate matters.
+</p>
+<p style="margin-left: 40px;">* GPL Violation Case Study D</p>
+<p style="margin-left: 80px;">In this case study, we consider how to
+handle the inevitable violations that can occur from a company that is
+generally committed to doing Free Software as a regular part of its
+business, but — due to experimentation with new cutting edge
+business models, or because of mere oversights — has occasional
+GPL violations or near-violations.</p>
+<p style="margin-left: 40px;"> * Good Practices for GPL Compliance
+</p>
+<p style="margin-left: 80px;">After discussing the details of the
+various archetypes of GPL compliance efforts undertaken by FSF, we
+generalize what we have learned to advise on good practices to build a
+product from start to finish in compliance with GPL, and how to build
+internal policies to assure that your client or company is never faced
+with a violation report.</p>
+<p><b>Ethical Considerations for the Attorney Practicing Free
+Software</b></p>
+<p style="margin-left: 40px;">This portion of the course will focus on
+ethical issues that may arise for attorneys counseling clients with
+respect to free software issues. Many of these topics have more
+general application, but specific discussion of the ways in which
+these issues may arise for free software clients will be
+presented.</p>
+<p style="margin-left: 40px;"> * Part I: Representing Free Software
+Clients</p>
+<p style="margin-left: 80px;">An attorney's ethical duties run to not
+just their clients, but to potential clients and the general public as
+well. Pro bono representation of free software clients not only
+conforms with the principles set forth by most Bar Associations, but
+also provides many other benefits to an attorney. Once a client is
+retained, the duty of loyalty attaches and conflicts, be they direct,
+indirect, or political, should be identified and handled.
+</p>
+<p style="margin-left: 40px;"> * Part II: Practicing Free Software
+</p>
+<p style="margin-bottom: 0in; margin-left: 80px;">Differing ethical
+issues arise in the context of counseling a client who is a free
+software licensor as opposed to one who is a free software licensee.
+Further still, representing a client who is both licensor and licensee
+presents a combination of all of these issues. Compliance
+investigation and enforcement strategies must be implemented in
+accordance with both the duty of loyalty and the duty of honesty.
+Likewise, performing exposure abatement while also defending against
+charges of infringement may pose problems within the attorney-client
+relationship. The ethical considerations relevant to each of these
+situations will be presented and discussed.
+</p>
+<p style="margin-left: 40px;">* Part III: More General Ethical
+Considerations Relevant to Free Software
+</p>
+<p style="margin-left: 80px;">Free software counseling is but one
+specialty within the realm of intellectual property counseling in
+general. A review of various topics of more general application, but
+with special relevance to free software counseling, will be given
+along with a discussion of the reasons why and ways in which such
+issues arise when representing free software clients. Patent
+prosecution and governing rules considerations are two such topics.
+</p>
+
+<p><b>Pricing (Book by December 24, 2003 for early registration
+discount):</b></p>
+<div style="margin-left: 40px;">$495 for registrations on or before
+December 24, 2003 and $595 after December 24 <br />
+<br />
+<span style="font-family: Nimbus Roman No9 L,
+serif"><span style="text-decoration: underline;">Financial Aid
+Policy:</span> 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";><address@hidden></a> or
+Ravi at <a href="mailto:address@hidden";><address@hidden></a> or by
+phone at 617.620.9640.</span> <br /> <br />
+</div>
+
+<p style="font-family: Nimbus Roman No9 L, serif"><b>CLE Credits:</b>
+Attorneys who successfully complete the day long course will be
+entitled to a total of 7.5 New York Transitional CLE credits, 3 in the
+area of Professional Practice and 4.5 toward the Ethics and
+Professionalism requirments.</p>
+<p style="font-family: Nimbus Roman No9 L, serif">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";><address@hidden></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 style="font-family: Nimbus Roman No9 L, serif">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";><address@hidden></a> or by
+calling 1+617-620-9640.</p>
+
+</div>
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+
+<p>
+Please send FSF & GNU inquiries to
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF.
+<br />
+Please send broken links and other corrections or suggestions to
+<a href="mailto:address@hidden";><em>address@hidden</em></a>.
+</p>
+
+<p>
+Please see the
+<a href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting
+translations of this article.
+</p>
+
+<p>Copyright © 2003, 2004, 2007, 2008, 2009, 2014 Free Software
+Foundation, Inc.</p>
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.
+</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p>Updated:
+<!-- timestamp start -->
+$Date: 2015/07/25 14:28:15 $
+<!-- timestamp end -->
+</p>
+</div>
+
+</div>
+</body>
+</html>
Index: philosophy/sco/subpoena.de.html
===================================================================
RCS file: philosophy/sco/subpoena.de.html
diff -N philosophy/sco/subpoena.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/sco/subpoena.de.html 25 Jul 2015 14:28:16 -0000 1.1
@@ -0,0 +1,236 @@
+<!--#set var="ENGLISH_PAGE" value="/philosophy/sco/subpoena.en.html" -->
+
+<!--#include virtual="/server/header.de.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>SCO: Vorladung der FSF - GNU-Projekt - Free Software Foundation</title>
+
+<!--#include virtual="/philosophy/sco/po/subpoena.translist" -->
+<!--#include virtual="/server/banner.de.html" -->
+<h2>SCO: Vorladung der FSF</h2>
+
+<p>von <strong>Bradley M. Kuhn</strong></p>
+<p>Dienstag, 18. Mai 2004</p>
+
+<p>
+Ende letztes Jahres wurden wir im Rahmen des laufenden Rechtsstreits
+zwischen SCO und IBM von SCO vorgeladen. Heute machten wir diese <a
+href="/philosophy/sco/sco-subpoena.pdf" type="application/pdf">Vorladung
+über unseren Webauftritt verfügbar</a>. Dies ist eine breitgefächerte
+Vorladung, die wirksam jedes einzelne Dokument über die GPL und jede
+Durchsetzung der GPL seit 1999 anfordert. Ebenso werden auch jedes Dokument
+und jede E-Mail angefordert, die wir mit Linus Torvalds, IBM und anderen
+Akteuren in der Gemeinschaft ausgetauscht haben. In vielen Fällen fordern
+sie um Information, die vertrauliche Kommunikation zwischen uns und unseren
+Rechtsanwälten oder zwischen uns und unseren Beitragenden darstellt.
+</p>
+
+<p>
+Da sich der SCO-Rechtsstreit hinzieht, müssen wir einige schwierige
+Entscheidungen treffen, wie man auf diese Vorladung reagiert. Wir sind
+sicher, dass wir nicht das ganze angeforderte Material vorlegen werden; wir
+werden unser rechtlich geschütztes Vertrauen nicht preisgeben, besonders
+wenn sie sich auf unsere Arbeit beziehen, die die Integrität der GPL
+wahrt. Doch unabhängig davon, ob wir die ganze Vorladung vor Gericht
+bestreiten oder nur jene Dokumente vorlegen, von denen wir meinen sie seien
+angemessen und relevant, gibt es viel Arbeit für die <span xml:lang="en"
+lang="en">Free Software Foundation</span> (FSF). Wenn wir gegen die
+Vorladung vorgehen, bedeutet das erhebliche Anwaltskosten im Zusammenhang
+mit dem Rechtsstreit. Wenn wir die Materialien vorlegen, bedeutet dies
+erhebliche Anstrengungen, um die relevanten Dokumente
+zusammenzustellen. Obwohl die direkten Kosten zurückerstattet werden, werden
+die indirekten Kosten wie Personal und Zeit von uns getragen.
+</p>
+
+<p>
+Inzwischen haben die durchgesickerten SCO-Dokumente bestätigt, was wir schon
+lange vermuteten: Microsoft hat, nachdem sie feststellten, dass die
+Verleumdungskampagne gegen die GPL keinen Erfolg hat, stattdessen ihr FUD<a
+href="#tn1" id="tn1-ref" class="transnote">[*]</a> zu einem Schnäppchenpreis
+von einem Dritten gekauft. Die âLizenzâ, die Microsoft für SCOs
+âTechnologieâ kaufte, war mehr als alles andere eine Gebühr für den
Dienst,
+den Angriff auf die Freie-Software-Bewegung und ihrer niedrigsten
+Programmebene, den Betriebssystemkern namens Linux. Nun, da es einmal âSCOâ
+gegeben hat, werden noch einige âSCOsâ folgen, um unsere Bewegung und
unsere
+Arbeit anzugreifen.
+</p>
+
+<p>
+Auch wenn wir der Ansicht sind, dass SCO keine Grundlage für die gemachten
+Behauptungen hat, heiÃt das nicht, dass unsere Gemeinschaft davon ausgehen
+sollte, dass sie nichts aus diesen Ereignissen zu lernen hat. Wir waren uns
+bei der FSF schon früh unsicher, ob SCO nur den Betriebssystemkern Linux
+oder das gesamte GNU/Linux-Betriebssystem angreifen würde. Als Inhaber der
+Urheberrechte auf die meisten Hauptkomponenten des GNU/Linux-Systems
+befürchten wir natürlich, auch wenn unser Vorgang bei der
+Urheberrechtsabtretung der beste und am gewissenhafteste in der gesamten
+Freie-Software-Welt ist, dass noch groÃe Anstrengungen erforderlich sein
+würden, um einem Richter aufzuzeigen, wie genau wir diese Aufgabe gelöst
+haben. Wir sind für SCOs taktischen Fehler dankbar, eine der tiefsten
+Taschen auf Erden, IBM, anzugreifen, die das nötige Scheckheft hat, um
+effizient gegen solch eine lästige Rechtssache vorzugehen.
+</p>
+
+<p>
+Das bedeutet jedoch nicht, dass die Arbeit der FSF erledigt ist. Neben der
+Beantwortung bzw. Diskussion der Vorladung müssen wir auch die Gemeinschaft
+darüber aufklären, warum Linux so angegriffen wurde und nicht GNU. Seit mehr
+als einem Jahrzehnt hat die FSF Projekte aufgefordert ein Verfahren zu
+entwickeln, bei dem die rechtliche Zusammenstellung der Software gesund wie
+die Softwareentwicklung als solide selbst ist. Viele
+Freie-Software-Entwickler empfanden den für die meisten GNU-Komponenten
+verwendeten Vorgang der Urheberrechtsabtretung als lästig, wir konzipierten
+und gestalteten das Verfahren jedoch mühsam neu, um die Last zu
+beseitigen. Nun hat das SCO-Fiasko der Gemeinschaft die Widerstandsfähigkeit
+gezeigt und die absolute Gewissheit gegeben, dass ein gutes, rechtlich
+vertretbares Verfahren der Zusammenstellung geschaffen werden kann. (SCO
+lieà letztendlich ihre Ansprüche gegen GNU als Ganzes fallen und
+konzentrierte sich auf das Linux-Projekt, welches für all seine wunderbaren
+technischen Leistungen ein eher lockeres rechtliches Verfahren der
+Zusammenstellung hat.) Wir haben bei der FSF gerade mit einem Projekt
+begonnen, um unser Verfahren zu dokumentieren und zu kodifizieren, damit es
+in Form eines Regelwerkes sowie dazugehöriger Software verbreitet werden
+kann, um alle anderen Freie-Software-Projekte, die ihr rechtliches Verfahren
+der Zusammenstellung festigen wollen. Organisatorische Erfahrung aus fast
+zwei Jahrzehnten in leicht verständliche Software und Dokumentation
+zusammenzufassen ist keine leichte Aufgabe, und wird sehr von Ihrer
+finanziellen Unterstützung abhängig sein, um bei dieser bedeutenden Aufgabe
+zu helfen.
+</p>
+
+<hr style="text-align:left; margin: 0 auto 0 0; width:30%;" />
+
+<p>
+Wie immer achten wir bei der FSF auf die langfristige Zukunft. SCO ist ein
+kurzzeitiger Leuchtpunkt – ein Vorläufer für
+Herausforderungen, den Freie Software ausgesetzt ist. Wir sind bestrebt eine
+Nasenlänge voraus zu sein und den Weg frei für eine rechtssichere
+Freie-Software-Zukunft zu machen.
+</p>
+
+<p>
+Wir brauchen Ihre Unterstützung, um diese Arbeit fortzusetzen. Wir bitten,
+wenn Sie noch kein <a href="http://member.fsf.org";>auÃerordentliches
+Mitglied der FSF</a> sind, jetzt beizutreten. Wenn Sie bereits vor dem
+15. Juni 2004 beigetreten sind, erhalten Sie ein Freiexemplar von Lawrence
+Lessigs neuem Buch <span xml:lang="en" lang="en" title="Freie
+Kultur"><cite>Free Culture</cite></span><a href="#tn01" id="tn01-ref"
+class="transnote">[1]</a>. Wir freuen uns, Professor Lessig als weiteres
+Mitglied im Aufsichtsrat zu feiern und sein neuestes schriftliches Werk mit
+Ihnen zu teilen, wie wir unsere Arbeit fortsetzen.
+</p>
+
+<p>
+Sollten Sie bereits ein auÃerordentliches Mitglied sein, ermutigen Sie bitte
+Bekannte sich uns anzuschlieÃen!
+</p>
+
+<p><a href="/philosophy/sco/">Weitere Texte im Zusammenhang mit SCO</a>.</p>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<strong>Anmerkungen des Ãbersetzungsteams:</strong>
+<ol id="transnote">
+<li id="tn1"><a href="#tn1-ref">[*]</a> <abbr>FUD</abbr> (engl. für <span
+xml:lang="en" lang="en"><i>Fear, Uncertainty, and Doubt</i></span>)
+<i>âFurcht, Ungewissheit und Zweifelâ</i></li>
+<li><p><strong>Weiterführende Referenzen</strong>:</p>
+<ol style="list-style-type:none">
+<li id="tn01"><a href="#tn01-ref">[1]</a> Lessig, Lawrence (2004), <a
+href="http://www.free-culture.cc/freeculture.pdf"; type="application/pdf"
+hreflang="en"><cite>Free Culture: How Big Media Uses Technology and the Law
+to Lock Down Culture and Control Creativity</cite></a>, unter:
+Free-Culture.cc. Penguin Books 2004 (abgerufen 2014-03-20)</li>
+<li> Lessig, Lawrence <a
+href="http://www.fosdoc.de/downloads/OSP_lessig_freiekultur.pdf";
+type="application/pdf" hreflang="de"><cite>Freie Kultur. Wesen und Zukunft
+der Kreativität</cite></a>, unter: fosdoc.de. Open Source Press 2006
+(abgerufen 2014-03-20)</li>
+</ol></li>
+</ol></div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Bitte senden Sie allgemeine Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/"><span xml:lang="en" lang="en">Free Software
+Foundation</span> kontaktieren</a>. Ungültige Verweise und andere
+Korrekturen oder Vorschläge können an <a
+href="mailto:address@hidden";><address@hidden></a> gesendet
+werden.</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>. -->
+Bei der Ãbersetzung dieses Werkes wurde mit gröÃter Sorgfalt
+vorgegangen. Trotzdem können Fehler nicht völlig ausgeschlossen
+werden. Sollten Sie Fehler bemerken oder Vorschläge, Kommentare oder
+Anfragen zu diesem Dokument haben, kontaktieren Sie bitte unser
+Ãbersetzungsteam <a
+href="mailto:address@hidden@gnu.org";><address@hidden></a>.</p>
+<p>Weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen unserer Webseiten finden Sie in der <a
+href="/server/standards/README.translations">LIESMICH für
Ãbersetzungen</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 3.0 US. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+<p>Copyright © 2004, 2008, 2013 Free Software Foundation, Inc.</p>
+
+<p>Dieses Werk steht unter einer <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 3.0 Vereinigte Staaten von Amerika
+Lizenz</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.de.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> <!--Jоегg Kоhпе --><a
+href="https://savannah.gnu.org/projects/www-de";><www-de></a>, 2011,
+2014.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2015/07/25 14:28:16 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+
Index: philosophy/sco/po/subpoena.de-en.html
===================================================================
RCS file: philosophy/sco/po/subpoena.de-en.html
diff -N philosophy/sco/po/subpoena.de-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ philosophy/sco/po/subpoena.de-en.html 25 Jul 2015 14:28:16 -0000
1.1
@@ -0,0 +1,178 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>The SCO Subpoena of FSF
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/philosophy/sco/po/subpoena.translist" -->
+<!--#include virtual="/server/banner.html" -->
+
+<h2>The SCO Subpoena of FSF</h2>
+
+<p>by <strong>Bradley M. Kuhn</strong></p>
+<p>Tuesday 18 May 2004</p>
+
+<p>
+Late last year, we were subpoenaed by SCO as part of the ongoing dispute
+between SCO and IBM. Today, <a href="sco-subpoena.pdf">we made that
+subpoena available on our website</a>. This is a broad subpoena that
+effectively asks for every single document about the GPL and enforcement
+of the GPL since 1999. They also demand every document and email that we
+have exchanged with Linus Torvalds, IBM, and other players in the
+community. In many cases, they are asking for information that is
+confidential communication between us and our lawyers, or between us and
+our contributors.
+</p>
+
+<p>
+As the SCO lawsuit drags on, we will have to make some tough decisions
+about how to answer this subpoena. We are certain that we will not
+produce all the material requested; we will not betray our legally
+protected confidences, particularly when they relate to our work upholding
+the integrity of the GPL. However, regardless of whether we dispute the
+whole subpoena in court, or provide those documents which we are able to
+determine are reasonable and relevant to produce, there is much work for
+FSF. If we fight the subpoena, it means substantial legal fees associated
+with litigation. If we produce materials, it means substantial effort to
+gather the relevant documents. Even though we'll be reimbursed for the
+direct costs, the indirect costs in staff time will be ours to bear.
+</p>
+
+<p>
+Meanwhile, the leaked SCO documents have confirmed what we long
+believed: Microsoft, having found that the smear campaign against GPL
+was not succeeding, has instead bought their FUD at a bargain price
+from a third party. The “license” that Microsoft bought
+for SCO's “technology” was, more than anything else, a fee
+for the service of attacking the Free Software Movement and its
+lowest-level program, the kernel named Linux. Now that there has once
+been a “SCO”, there will always be some “SCO”
+to come and attack our movement and our work.
+</p>
+
+<p>
+Even though we believe that SCO has no basis to make the claims they make,
+that does not mean our community should assume it has nothing to learn
+from these events. Early in the lawsuit, we at FSF were unsure if SCO
+would attack only the kernel Linux, or the entire GNU/Linux operating
+system. As copyright holder on most major components of the GNU/Linux
+system, we of course feared that even while our copyright assignment
+process is the best and most diligent in the whole Free Software world, we
+would still be required to expend great effort in showing a judge how
+exactly we did this job. We are grateful for SCO's tactical error of
+attacking one of the deepest pockets on earth, IBM, who has the checkbook
+needed to efficiently fight such a nuisance lawsuit.
+</p>
+
+<p>
+However, this does not mean FSF's work is done. In addition to answering
+and/or disputing the subpoena, we must also educate the community about
+why it is that Linux was attacked and GNU was not. For more than a
+decade, FSF has urged projects to build a process whereby the legal
+assembly of the software is as sound as the software development itself.
+Many Free Software developers saw the copyright assignment process used
+for most GNU components as a nuisance, but we arduously designed and
+redesigned the process to remove the onerousness. Now the SCO fiasco has
+shown the community the resilience and complete certainty that a good
+legal assembly process can create. (SCO, after all, eventually dropped
+their claims against GNU as a whole and focused on the Linux project
+which, for all its wonderful technical achievements, has a rather loose
+legal assembly process.) We have just begun a project here at FSF to
+document and codify our process, so that it can be disseminated in the
+form of a policy manual and accompanying software, to all other Free
+Software projects who wish to solidify their legal assembly process.
+Distilling nearly two decades of organizational know-how into
+easy-to-understand software and documentation is no easy task, and we will
+rely greatly on your financial support to aid us in carrying out this
+momentous task.
+</p>
+
+<hr style="text-align:left; margin: 0 auto 0 0; width:30%;" />
+
+<p>
+As always, we at FSF look to the long-term future. SCO is a
+blip—a precursor to the challenges Free Software will face. We
+strive to be ahead of that curve and lead the way for a legally
+certain future for Free Software.
+</p>
+
+<p>
+We need your support to continue this work. We ask that if you are not yet
+<a href="http://member.fsf.org";>an associate member of FSF, that you
+join now</a>. If you join before 15 June 2004, you will receive a
+complimentary print copy of Lawrence Lessig's new book, <cite>Free
+Culture</cite>. We are happy to celebrate the addition of Professor
+Lessig to our board of directors by sharing his latest written work
+with you as we continue our work.
+</p>
+
+<p>
+If you already an associate member, please encourage a friend to join!
+</p>
+
+<p><a href="/philosophy/sco/sco.html">Other Texts to Read related
+to SCO</a>.</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 3.0 US. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2004, 2008, 2013 Free Software Foundation, Inc.</p>
+
+<p>This page is licensed under a <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/3.0/us/";>Creative
+Commons Attribution-NoDerivs 3.0 United States License</a>.</p>
+
+<!--#include virtual="/server/bottom-notes.html" -->
+
+<p class="unprintable">Updated:
+<!-- timestamp start -->
+$Date: 2015/07/25 14:28:16 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
+
Index: proprietary/proprietary-interference.de.html
===================================================================
RCS file: proprietary/proprietary-interference.de.html
diff -N proprietary/proprietary-interference.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ proprietary/proprietary-interference.de.html 25 Jul 2015 14:28:17
-0000 1.1
@@ -0,0 +1,123 @@
+<!--#set var="ENGLISH_PAGE"
value="/proprietary/proprietary-interference.en.html" -->
+
+<!--#include virtual="/server/header.de.html" -->
+<!-- Parent-Version: 1.78 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Proprietärer Eingriff - GNU-Projekt - Free Software Foundation</title>
+
+<!--#include virtual="/proprietary/po/proprietary-interference.translist" -->
+<!--#include virtual="/server/banner.de.html" -->
+<h2>Proprietärer Eingriff</h2>
+
+<p>
+Diese Seite beschreibt, wie verschiedene proprietäre Programme das System
+des Benutzers verkorksen können. Sie sind der Sabotage ähnlich, jedoch nicht
+schwerwiegend genug, um sie mit dem Wort <em>Sabotage</em> zu
+betiteln. Dennoch sind sie scheuÃlich und falsch.
+</p>
+
+<ul>
+<li><p>Yahoo unterzeichnete Deal mit Oracle: das unfreies Java-Plug-in von <a
+href="http://searchengineland.com/yahoo-signs-deal-with-oracle-to-attract-new-users-via-java-installs-224097";
+title="Yahoo Signs Deal With Oracle To Attract New Users Via Java Installs,
+unter: SearchEngineLand.com 2015.">Oracle setzt die Startseite und die
+Standardsuchmaschine des Benutzers auf Yahoo</a>, sofern der Nutzer nicht
+eingreift, um dies zu unterbinden.<a href="#tn01" id="tn01-ref"
+class="transnote">[1]</a></p></li>
+</ul>
+
+<div class="translators-notes">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't have notes.-->
+<p><strong>Anmerkungen des Ãbersetzungsteams</strong>:</p>
+<ol id="transnote">
+<li><p><strong>Weiterführende Referenzen</strong>:</p>
+<ol style="list-style-type:none">
+<li id="tn01"><a href="#tn01-ref">[1]</a> Siehe auch: Search Engine Land,
+<cite><a
+href="http://www.seo-suedwest.de/1154-yahoo-deal-oracle-java-installation-standardsuche.html";>Deal
+mit Oracle: Yahoo wird bei Java-Installation Standard-Suche</a></cite>,
+unter: seo-suedwest.de 2015. (abgerufen 2015-06-29)</li>
+</ol></li></ol></div>
+</div>
+
+<!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.de.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Bitte senden Sie allgemeine Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/"><span xml:lang="en" lang="en">Free Software
+Foundation</span> kontaktieren</a>. Ungültige Verweise und andere
+Korrekturen oder Vorschläge können an <a
+href="mailto:address@hidden";><address@hidden></a> gesendet
+werden.</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>. -->
+Bei der Ãbersetzung dieses Werkes wurde mit gröÃter Sorgfalt
+vorgegangen. Trotzdem können Fehler nicht völlig ausgeschlossen
+werden. Sollten Sie Fehler bemerken oder Vorschläge, Kommentare oder
+Anfragen zu diesem Dokument haben, kontaktieren Sie bitte unser
+Ãbersetzungsteam <a
+href="mailto:address@hidden@gnu.org";><address@hidden></a>.</p>
+<p>Weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen unserer Webseiten finden Sie in der <a
+href="/server/standards/README.translations">LIESMICH für
Ãbersetzungen</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 © 2015 Free Software Foundation, Inc.</p>
+
+<p>Dieses Werk ist lizenziert unter einer <a rel="license"
+href="http://creativecommons.org/licenses/by-nd/4.0/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 4.0 International</a>-Lizenz.</p>
+
+<!--#include virtual="/server/bottom-notes.de.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong> Jоегg Kоhпе <a
+href="https://savannah.gnu.org/projects/www-de";><www-de></a>, 2015.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2015/07/25 14:28:17 $
+
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: proprietary/po/proprietary-interference.de-en.html
===================================================================
RCS file: proprietary/po/proprietary-interference.de-en.html
diff -N proprietary/po/proprietary-interference.de-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ proprietary/po/proprietary-interference.de-en.html 25 Jul 2015 14:28:17
-0000 1.1
@@ -0,0 +1,85 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.78 -->
+<title>Proprietary Interference - GNU Project - Free Software
Foundation</title>
+ <!--#include virtual="/proprietary/po/proprietary-interference.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Proprietary Interference</h2>
+
+<p>
+This page describes how various proprietary programs mess up the
+user's system. They are like sabotage, but they are not grave enough
+to qualify for the word “sabotage”. Nonetheless, they are nasty and
+wrong.
+</p>
+
+<ul>
+<li><p>Oracle made a deal with Yahoo; Oracle's nonfree Java plug-in will
+<a
href="http://searchengineland.com/yahoo-signs-deal-with-oracle-to-attract-new-users-via-java-installs-224097";>
+change the user's initial web page, and default search engine, to Yahoo</a>
+unless the user intervenes to stop it.</p></li>
+</ul>
+
+</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 © 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: 2015/07/25 14:28:17 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: server/source/source.de.html
===================================================================
RCS file: server/source/source.de.html
diff -N server/source/source.de.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/source/source.de.html 25 Jul 2015 14:28:17 -0000 1.1
@@ -0,0 +1,250 @@
+<!--#set var="ENGLISH_PAGE" value="/server/source/source.en.html" -->
+
+<!--#include virtual="/server/header.de.html" -->
+<!-- Parent-Version: 1.77 -->
+
+<!-- This file is automatically generated by GNUnited Nations! -->
+<title>Quelldateien der Internetserver-Dienstprogramme - GNU-Projekt - Free
+Software Foundation</title>
+
+<!--#include virtual="/server/source/po/source.translist" -->
+<!--#include virtual="/server/banner.de.html" -->
+<h2>Quelldateien der Internetserver-Dienstprogramme</h2>
+
+<p>(Das [<a href="/server/source/source.en.html">englischsprachige</a>]
+Dokument muss aktualisiert werden. <a
+href="/server/fsf-html-style-sheet.html"><em>--> Bitte aktualisieren
+Sie es <--</em></a>.) </p>
+
+
+<p>Um den Internetserver des GNU-Projekts zu betreiben, wird von uns
+verschiedene Freie Software eingesetzt. Die meiste ist bereits im Internet
+abrufbar, aber wir haben auch einige, die von ehrenamtlichen
+GNU-Mitwirkenden entwickelt und nie als GNU-Software freigegeben worden ist,
+da sie eher spezifisch auf unsere Bedürfnisse zugeschnitten sind. Dennoch
+finden wir, dass diese Programme auch bereitgestellt werden sollten, damit
+auch andere davon Gebrauch machen können. Dies ist eine Ãbersicht solcher
+Programme.</p>
+
+
+<h3><a id="cvs">CVS-Verzeichnisbaum</a></h3>
+
+<p>Wir empfehlen, die Skripte im üblichen <var>www</var>-CVS-Verzeichnisbaum
zu
+speichern. Dies ermöglicht <ins>beispielsweise</ins> einen einfachen
+Austausch unter verschiedenen GNU-Rechnern, auf denen ein vollständiges oder
+teilweises Abbild des <a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/?root=www";>www-Web-Projektarchivs</a>
+<ins>von GNU.org</ins> betrieben wird. Für weitere Informationen siehe das
+auf <b><a href="https://savannah.gnu.org/";>Savannah</a></b> betriebene <a
+href="https://savannah.gnu.org/cvs/?group=www";>CVS-Projektarchiv</a>.</p>
+
+
+<h3><a id="linc">linc.py</a></h3>
+
+<ul>
+ <li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/server/source/linc/?root=www";>Quellcode</a>
+(GPLv3+)</li>
+ <li>Autor: WacÅaw Jacek <a
href="mailto:address@hidden";><address@hidden></a></li>
+</ul>
+
+<p><b>LINC</b>, für <em>LINC Is Not Checklink</em>, durchsucht unseren
+Internetauftritt (oder jeden anderen) <ins>nach vorhandenen Verweisen</ins>
+und generiert einen Bericht mit <a
+href="/server/source/linc/linc-report.html">ungültigen Verweisen</a>. Das
+Programm wird wöchentlich auf <a
+href="http://fencepost.gnu.org/";>Fencepost</a> als <b><a
+href="/software/gnun/">GNUN</a></b>-Cronjob ausgeführt.</p>
+
+
+<h3><a id="planetrss">planetrss.pl</a></h3>
+
+<ul>
+ <li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/server/source/planetrss/?root=www";>Quellcode</a>
+(GPLv3+)</li>
+ <li>Autor: Shailesh Ghadge <a
+href="mailto:address@hidden";><address@hidden></a></li>
+</ul>
+
+<p>Das Perl-Skript holt und speichert <var>n</var>-Feeds mittels des RSS-Feed
+<a href="http://planet.gnu.org/";>planet.gnu.org/rss20.xml</a> vom
+Entwickler-Blog des GNU-Projektes, <a
+href="http://planet.gnu.org/";>planet.gnu.org</a>, als HTML, was dann auf der
+GNU.org-Startseite eingebunden und auf eine bestimme Anzahl Zeichen gekürzt
+wird.</p>
+
+
+<h3><a id="sitemap-generator">sitemap-generator</a></h3>
+
+<ul>
+ <li><a
+href="http://web.cvs.savannah.gnu.org/viewvc/www/server/source/sitemap-generator/?root=www";>Quellcode</a>
+(GPLv3+)</li>
+ <li>Autor: WacÅaw Jacek <a
href="mailto:address@hidden";><address@hidden></a></li>
+</ul>
+
+<p>Dieses Programm erzeugt die <a
+href="/server/sitemap.html">Seitenübersicht</a> unseres Internetauftritts
+auf Grundlage der Ordnerstruktur des Dateisystems. Es wird auf <a
+href="http://fencepost.gnu.org/";>Fencepost</a> als <a
+href="/software/gnun/">GNUN></a>-Cronjob ausgeführt.</p>
+
+
+<h3><a id="symlinks">symlinks</a></h3>
+
+<ul>
+ <li><a
+href="http://savannah.gnu.org/cgi-bin/viewcvs/www/www/symlinks/";>Quellcode</a>
+(GPLv2+)</li>
+ <li>Autor: Loic Dachary <a
href="mailto:address@hidden";><address@hidden></a></li>
+ <li>Aktuelle Version: 1.1</li>
+</ul>
+
+<p>Absicht ist, die Unfähigkeit von CVS im Umgang mit einer symbolischen
+Verknüpfung <ins>in einem Dateisystem (Dateien und Verzeichnisse), die auf
+eine andere Datei oder ein anderes Verzeichnis innerhalb des
+Verzeichnisbaums verweist,</ins> handhaben zu können. Durch hinzufügen
+<ins>von <i>.symlinks</i>-Dateien</ins> in den CVS-Verzeichnisbaum, die
+<ins>lediglich als Referenz auf die Zieldatei bzw. das Zielverzeichnis</ins>
+interpretiert werden. Ein Skript namens <b>web-symlinks</b> wird unmittelbar
+nach einem â<kbd>cvs update</kbd>â ausgeführt, um die symbolischen
Verweise
+entsprechend der in den .symlinks-Dateien enthaltenen Referenzen zu
beheben.</p>
+
+<p>Dieses Skript wird auf dem gegenwärtigen Internetauftritt nicht mehr
+benutzt. Stattdessen werden die .symlinks-Dateien in
+<i>RewriteRule</i>-Richtlinien umgewandelt. Weitere Informationen unter
+<cite><a href="/server/standards/README.webmastering.html#symlinks"
+hreflang="en">Symbolische Verweise</a></cite> im <cite><a
+href="/server/standards/README.webmastering.html" hreflang="en">Leitfaden
+für GNU-Webmaster</a></cite>.</p>
+
+
+<h3><a id="update-license">update-license.php</a></h3>
+
+<ul>
+ <li><a href="/server/source/update-license.php.txt">Quellcode</a>
(GPLv3+)</li>
+ <li>Autor: James Turner <a
+href="mailto:address@hidden";><address@hidden></a></li>
+</ul>
+
+<p>Dieses Skript kann über Webroot ausgeführt werden, um in
englischsprachigen
+HTML-Dateien den alten Text <i>âGNU Verbatim Copyingâ</i> mit dem der neuen
+CC-Lizenz [oder jede anderen Zeichenfolge, A. d. Ã.] zu ersetzen.</p>
+
+
+<h3><a id="update-recent-releases">update-recent-releases</a></h3>
+
+<ul>
+ <li><a href="/server/source/update-recent-releases">Quellcode</a></li>
+</ul>
+
+<p>Dieses Skipt generiert eine Ãbersicht <a
+href="/software/recent-releases.html">aktueller Softwarefreigaben</a> (aus
+dem <a
+href="https://lists.gnu.org/mailman/listinfo/info-gnu";>info-gnu</a>-Projektarchiv).
+Es wird auf <a href="http://fencepost.gnu.org/";>Fencepost</a> als <b><a
+href="/software/gnun/">GNUN</a></b>-Cronjob ausgeführt.</p>
+
+
+<h3><a id="webref">webref</a></h3>
+
+<ul>
+
+ <!-- <li>
+<a href="/server/source/webref.el">Source code</a> -->
+<li>Autor: Tim Bedding</li>
+ <li>Aktuelle Version: 1.0</li>
+</ul>
+
+<p>Dieses Programm, in Emacs LISP geschrieben, kann genutzt werden, um Verweise
+in HTML-Dokumenten zu überprüfen. Als Eingabedatei wird 'input.txt' genutzt,
+die eine Liste von HTML-Dokumenten enthält, und 'output.txt' als
+Ausgabedatei. Die Ausgabe enthält Informationen über ungültige Verweise. Wir
+verwenden diese, um sicherzustellen, dass alle wichtigen Dokumente
+erreichbar sind.</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.de.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Bitte senden Sie allgemeine Fragen zur FSF & GNU an <a
+href="mailto:address@hidden";><address@hidden></a>. Sie können auch die
<a
+href="/contact/"><span xml:lang="en" lang="en">Free Software
+Foundation</span> kontaktieren</a>. Ungültige Verweise und andere
+Korrekturen oder Vorschläge können an <a
+href="mailto:address@hidden";><address@hidden></a> gesendet
+werden.</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>. -->
+Bei der Ãbersetzung dieses Werkes wurde mit gröÃter Sorgfalt
+vorgegangen. Trotzdem können Fehler nicht völlig ausgeschlossen
+werden. Sollten Sie Fehler bemerken oder Vorschläge, Kommentare oder
+Anfragen zu diesem Dokument haben, kontaktieren Sie bitte unser
+Ãbersetzungsteam <a
+href="mailto:address@hidden@gnu.org";><address@hidden></a>.</p>
+<p>Weitere Informationen über die Koordinierung und Einsendung von
+Ãbersetzungen unserer Webseiten finden Sie in der <a
+href="/server/standards/README.translations">LIESMICH für
Ãbersetzungen</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 © 2014, 2015 Free Software Foundation, Inc.</p>
+
+<p>Dieses Werk ist lizenziert unter einer <a rel="license"
+href="https://creativecommons.org/licenses/by-nd/4.0/deed.de";>Creative
+Commons Namensnennung-Keine Bearbeitung 4.0 International</a>-Lizenz.</p>
+
+<!--#include virtual="/server/bottom-notes.de.html" -->
+<div class="translators-credits">
+
+<!--TRANSLATORS: Use space (SPC) as msgstr if you don't want credits.-->
+<strong>Ãbersetzung:</strong><!-- Jоегg Kоhпе, 2013, 2014, 2015.--> <a
+href="https://savannah.gnu.org/projects/www-de";><www-de></a>, 2015.</div>
+
+<p class="unprintable"><!-- timestamp start -->
+Aktualisierung:
+
+$Date: 2015/07/25 14:28:17 $
+<!-- timestamp end -->
+</p>
+</div>
+</div>
+</body>
+</html>
Index: server/source/po/source.de-en.html
===================================================================
RCS file: server/source/po/source.de-en.html
diff -N server/source/po/source.de-en.html
--- /dev/null 1 Jan 1970 00:00:00 -0000
+++ server/source/po/source.de-en.html 25 Jul 2015 14:28:18 -0000 1.1
@@ -0,0 +1,191 @@
+<!--#include virtual="/server/header.html" -->
+<!-- Parent-Version: 1.77 -->
+<title>Web Server Utility Sources
+- GNU Project - Free Software Foundation</title>
+<!--#include virtual="/server/source/po/source.translist" -->
+<!--#include virtual="/server/banner.html" -->
+<h2>Web Server Utility Sources</h2>
+
+<p>(This page needs updating. Please update it.)</p>
+
+
+<p>To maintain the GNU project web server, we use a lot of different free
+software. Most of them are already available on the Internet, but we also
+have some software which has been developed by GNU volunteers and has
+never been released as GNU software, because they are somewhat specific to
+our needs. Still, we feel that those programs should also be made
+available so that others can make use of them. This page is a list of
+such programs.</p>
+
+
+<h3><a id="cvs">CVS Tree</a></h3>
+
+<p>We recommend storing the scripts in the usual www
+CVS tree. This allows easier sharing between GNU machines that maintain
+a full or partial image of the www.gnu.org web. See the
+<a href="https://savannah.gnu.org/cvs/?group=www";>Savannah CVS page</a>,
+the “Webpages repository” information.</p>
+
+
+<h3><a id="linc">linc</a></h3>
+
+<ul>
+ <li><a
href="http://web.cvs.savannah.gnu.org/viewvc/www/server/source/linc/?root=www";>Source
code</a></li>
+ <li>Author: <a href="mailto:address@hidden";>Wacław Jacek</a></li>
+</ul>
+
+<p>LINC stands for “LINC Is Not Checklink”. It scans our
+web site (or any site) and makes a report of <a
+href="linc/linc-report.html">broken links on our web site</a>. It runs
+weekly on fencepost from user gnun's cron.</p>
+
+
+<h3><a id="planetrss">planetrss.pl</a></h3>
+
+<ul>
+ <li><a
href="http://web.cvs.savannah.gnu.org/viewvc/www/server/source/planetrss/?root=www";>Source
code</a></li>
+ <li>Author: <a href="mailto:address@hidden";>Shailesh Ghadge</a></li>
+</ul>
+
+<p>This Perl script fetches and saves N feeds from <a
+href="http://planet.gnu.org.";>planet.gnu.org</a>, using the RSS feed
+http://planet.gnu.org/rss20.xml, in html format. It is then included
+in the homepage. Each feed is truncated to M characters.</p>
+
+
+<h3><a id="sitemap-generator">sitemap-generator</a></h3>
+
+<ul>
+ <li><a
href="http://web.cvs.savannah.gnu.org/viewvc/www/server/source/sitemap-generator/?root=www";>Source
code</a></li>
+ <li>Author: <a href="mailto:address@hidden";>Wacław Jacek</a></li>
+</ul>
+
+<p>This program generates the <a href="/server/sitemap.html">sitemap of
+our web site</a>, based on its directory structure on the file
+system. It runs on fencepost in user gnun's cron.</p>
+
+
+<h3><a id="symlinks">symlinks</a></h3>
+
+<ul>
+ <li><a
href="http://savannah.gnu.org/cgi-bin/viewcvs/www/www/symlinks/";>Source
code</a></li>
+ <li>Author: <a href="mailto:address@hidden";>Loic Dachary</a></li>
+ <li>Current version: 1.1</li>
+</ul>
+
+<p>The goal is to cope with the inability of CVS to deal
+with symbolic files. By adding special files (".symlinks") into
+the CVS tree that are interpreted as specifications to build
+symbolic links. The "symlinks" script used to be run immediately
+after a "cvs update" to fix the symbolic links according to the
+specifications included in the ".symlinks" files.</p>
+
+<p>This script is no longer used on the live web site. Instead, the
+<tt>.symlinks</tt> files are transformed into RewriteRule directives.
+More information about <tt>.symlinks</tt> files can be found in the <a
+href="/server/standards/README.webmastering.html#symlinks">Symbolic
+Links</a> section of the GNU Webmaster Guidelines.</p>
+
+
+<h3><a id="update-license">update-license.php</a></h3>
+
+<ul>
+ <li><a href="/server/source/update-license.php.txt">Source code</a></li>
+ <li>Author: <a href="mailto:address@hidden";>James Turner</a></li>
+</ul>
+
+<p>This script can be ran from the webroot to traverse through English html
+files replacing the old "Verbatim copying" text with the new CC license.</p>
+
+
+<h3><a id="update-recent-releases">update-recent-releases</a></h3>
+
+<ul>
+ <li><a href="/server/source/update-recent-releases">Source code</a></li>
+</ul>
+
+<p>This script generates the <a
+href="/software/recent-releases.html">list of recent releases</a> (from
+the <a href="https://lists.gnu.org/mailman/listinfo/info-gnu";>info-gnu
+archives</a>). It runs on fencepost in user gnun's cron.</p>
+
+
+<h3><a id="webref">webref</a></h3>
+
+<ul>
+ <!-- <li><a href="/server/source/webref.el">Source code</a> -->
+ <li>Author: Tim Bedding</li>
+ <li>Current version: 1.0</li>
+</ul>
+
+<p>This is a program made in Emacs LISP that is used to check references
+in HTML documents. It takes the file input.txt as input which contains
+a list of HTML documents and outputs te file output.txt. The output
+file contains information of documents which can not be reached at all
+and documents which can only be reached by following more than two links.
+We use this to make sure that all important documents can be reached
+fairly easy from the main page.</p>
+
+</div><!-- for id="content", starts in the include above -->
+<!--#include virtual="/server/footer.html" -->
+<div id="footer">
+<div class="unprintable">
+
+<p>Please send general FSF & GNU inquiries to
+<a href="mailto:address@hidden";><address@hidden></a>.
+There are also <a href="/contact/">other ways to contact</a>
+the FSF. Broken links and other corrections or suggestions can be sent
+to <a href="mailto:address@hidden";><address@hidden></a>.</p>
+
+<p><!-- TRANSLATORS: Ignore the original text in this paragraph,
+ replace it with the translation of these two:
+
+ We work hard and do our best to provide accurate, good quality
+ translations. However, we are not exempt from imperfection.
+ Please send your comments and general suggestions in this regard
+ to <a href="mailto:address@hidden";>
+ <address@hidden></a>.</p>
+
+ <p>For information on coordinating and submitting translations of
+ our web pages, see <a
+ href="/server/standards/README.translations.html">Translations
+ README</a>. -->
+Please see the <a
+href="/server/standards/README.translations.html">Translations
+README</a> for information on coordinating and submitting translations
+of this article.</p>
+</div>
+
+<!-- Regarding copyright, in general, standalone pages (as opposed to
+ files generated as part of manuals) on the GNU web server should
+ be under CC BY-ND 4.0. Please do NOT change or remove this
+ without talking with the webmasters or licensing team first.
+ Please make sure the copyright date is consistent with the
+ document. For web pages, it is ok to list just the latest year the
+ document was modified, or published.
+
+ If you wish to list earlier years, that is ok too.
+ Either "2001, 2002, 2003" or "2001-2003" are ok for specifying
+ years, as long as each year in the range is in fact a copyrightable
+ year, i.e., a year in which the document was published (including
+ being publicly visible on the web or in a revision control system).
+
+ There is more detail about copyright years in the GNU Maintainers
+ Information document, www.gnu.org/prep/maintain. -->
+
+<p>Copyright © 2014, 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: 2015/07/25 14:28:18 $
+<!-- timestamp end --></p>
+</div>
+</div>
+</body>
+</html>
| [Prev in Thread] |
Current Thread |
[Next in Thread] |
- www licenses/po/200104_seminar.translist licens...,
GNUN <=