[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
www/licenses quick-guide-gplv3.html
|
From: |
Yavor Doganov |
|
Subject: |
www/licenses quick-guide-gplv3.html |
|
Date: |
Thu, 28 Aug 2008 11:45:29 +0000 |
CVSROOT: /web/www
Module name: www
Changes by: Yavor Doganov <yavor> 08/08/28 11:45:29
Modified files:
licenses : quick-guide-gplv3.html
Log message:
Make all sections <h3>. Use — for the long dashes.
(the-foundations-of-the-gpl): Swap freedoms 1 and 2 to match the
established numbering.
CVSWeb URLs:
http://web.cvs.savannah.gnu.org/viewcvs/www/licenses/quick-guide-gplv3.html?cvsroot=www&r1=1.5&r2=1.6
Patches:
Index: quick-guide-gplv3.html
===================================================================
RCS file: /web/www/www/licenses/quick-guide-gplv3.html,v
retrieving revision 1.5
retrieving revision 1.6
diff -u -b -r1.5 -r1.6
--- quick-guide-gplv3.html 29 Jun 2008 13:43:55 -0000 1.5
+++ quick-guide-gplv3.html 28 Aug 2008 11:45:17 -0000 1.6
@@ -27,13 +27,13 @@
copyleft, and the goals of the GPL. We'll then review the major changes in
the license to see how they advance those goals and benefit developers.</p>
<div class="section" id="the-foundations-of-the-gpl">
-<h2>The Foundations of the GPL</h2>
+<h3>The Foundations of the GPL</h3>
<p>Nobody should be restricted by the software they use. There are four
freedoms that every user should have:</p>
<ul class="simple">
<li>the freedom to use the software for any purpose,</li>
-<li>the freedom to share the software with your friends and neighbors,</li>
-<li>the freedom to change the software to suit your needs, and</li>
+<li>the freedom to change the software to suit your needs,</li>
+<li>the freedom to share the software with your friends and neighbors, and</li>
<li>the freedom to share the changes you make.</li>
</ul>
<p>When a program offers users all of these freedoms, we call it <a
class="reference external" href="/philosophy/free-sw.html">free
@@ -60,11 +60,13 @@
Mismanagement; see
<a
href="#neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">below</a>).
These laws should not
interfere with the rights the GPL grants you.</li>
-<li>Discriminatory patent deals: Microsoft has recently started telling
-people that they will not sue free software users for patent infringementâas
long as you get the software from a vendor that's paying
-Microsoft for the privilege. Ultimately, Microsoft is trying to collect
-royalties for the use of free software, which interferes with users'
-freedom. No company should be able to do this.</li>
+<li>Discriminatory patent deals: Microsoft has recently started
+telling people that they will not sue free software users for patent
+infringement—as long as you get the software from a vendor
+that's paying Microsoft for the privilege. Ultimately, Microsoft is
+trying to collect royalties for the use of free software, which
+interferes with users' freedom. No company should be able to do
+this.</li>
</ul>
<p>Version 3 also has a number of improvements to make the license easier for
everyone to use and understand. But even with all these changes, GPLv3
@@ -75,7 +77,8 @@
developers.</p>
</div>
<div class="section"
id="neutralizing-laws-that-prohibit-free-software-but-not-forbidding-drm">
-<h2>Neutralizing Laws That Prohibit Free Software â But Not Forbidding
DRM</h2>
+<h3>Neutralizing Laws That Prohibit Free Software — But Not
+Forbidding DRM</h3>
<p>You're probably familiar with the Digital Restrictions Mismanagement
(DRM) on
DVDs and other media. You're probably also familiar with the laws that
@@ -93,16 +96,17 @@
stops them from restricting others.</p>
</div>
<div class="section" id="protecting-your-right-to-tinker">
-<h2>Protecting Your Right to Tinker</h2>
-<p>Tivoization is a dangerous attempt to curtail users' freedom: the right to
-modify your software will become meaningless if none of your computers let
-you do it. GPLv3 stops tivoization by requiring the distributor to provide
-you with whatever information or data is necessary to install modified
-software on the device. This may be as simple as a set of instructions, or
-it may include special data such as cryptographic keys or information about
-how to bypass an integrity check in the hardware. It will depend on how
-the hardware was designedâbut no matter what information you need, you
-must be able to get it.</p>
+<h3>Protecting Your Right to Tinker</h3>
+<p>Tivoization is a dangerous attempt to curtail users' freedom: the
+right to modify your software will become meaningless if none of your
+computers let you do it. GPLv3 stops tivoization by requiring the
+distributor to provide you with whatever information or data is
+necessary to install modified software on the device. This may be as
+simple as a set of instructions, or it may include special data such
+as cryptographic keys or information about how to bypass an integrity
+check in the hardware. It will depend on how the hardware was
+designed—but no matter what information you need, you must be
+able to get it.</p>
<p>This requirement is limited in scope. Distributors are still allowed to
use cryptographic keys for any purpose, and they'll only be required to
disclose a key if you need it to modify GPLed software on the device they
@@ -110,11 +114,11 @@
the software on its FTP site, and measures like that are beneficial to
users. GPLv3 does not stop people from using cryptography; we wouldn't
want it to. It only stops people from taking away the rights that the
-license provides youâwhether through patent law, technology, or any
+license provides you—whether through patent law, technology, or any
other means.</p>
</div>
<div class="section" id="stronger-protection-against-patent-threats">
-<h2>Stronger Protection Against Patent Threats</h2>
+<h3>Stronger Protection Against Patent Threats</h3>
<p>In the 17 years since GPLv2 was published, the software patent landscape
has changed considerably, and free software licenses have developed new
strategies to address them. GPLv3 reflects these changes too. Whenever
@@ -130,7 +134,7 @@
other free software license.</p>
</div>
<div class="section" id="clarifying-license-compatibility">
-<h2>Clarifying License Compatibility</h2>
+<h3>Clarifying License Compatibility</h3>
<p>If you found some code and wanted to incorporate it into a GPLed project,
GPLv2 said that the license on the other code was not allowed to have any
restrictions that were not already in GPLv2. As long as that was the case,
@@ -147,7 +151,7 @@
what you can do with GPL-compatible code.</p>
</div>
<div class="section" id="new-compatible-licenses">
-<h2>New Compatible Licenses</h2>
+<h3>New Compatible Licenses</h3>
<p>In addition to clarifying the rules about licenses that are already
GPL-compatible, GPLv3 is also newly compatible with a few other licenses.
The Apache License 2.0 is a prime example. Lots of great free software is
@@ -179,7 +183,7 @@
top of the mature body of GPLed code available to them.</p>
</div>
<div class="section" id="more-ways-for-developers-to-provide-source">
-<h2>More Ways for Developers to Provide Source</h2>
+<h3>More Ways for Developers to Provide Source</h3>
<p>One of the fundamental requirements of the GPL is that when you distribute
object code to users, you must also provide them with a way to get the
source. GPLv2 gave you a few ways to do this, and GPLv3 keeps those intact
@@ -199,7 +203,7 @@
offering source, without making it harder for users to get.</p>
</div>
<div class="section"
id="less-source-to-distribute-new-system-libraries-exception">
-<h2>Less Source to Distribute: New System Libraries Exception</h2>
+<h3>Less Source to Distribute: New System Libraries Exception</h3>
<p>Both versions of the GPL require you to provide all the source necessary to
build the software, including supporting libraries, compilation scripts,
and so on. They also draw the line at System Libraries: you're not
@@ -217,15 +221,15 @@
users.</p>
</div>
<div class="section" id="a-global-license">
-<h2>A Global License</h2>
-<p>GPLv2 talks about "distribution" a lotâwhen you share the
program
-with someone else, you're distributing it. The license never says what
-distribution is, because the term was borrowed from United States copyright
-law. We expected that judges would look there for the definition.
-However, we later found out that copyright laws in other countries use the
-same word, but give it different meanings. Because of this, a judge in
-such a country might analyze GPLv2 differently than a judge in the United
-States.</p>
+<h3>A Global License</h3>
+<p>GPLv2 talks about "distribution" a lot—when you
+share the program with someone else, you're distributing it. The
+license never says what distribution is, because the term was borrowed
+from United States copyright law. We expected that judges would look
+there for the definition. However, we later found out that copyright
+laws in other countries use the same word, but give it different
+meanings. Because of this, a judge in such a country might analyze
+GPLv2 differently than a judge in the United States.</p>
<p>GPLv3 uses a new term, "convey," and provides a definition for
that term.
"Convey" has the same meaning we intended for
"distribute," but now that
this is explained directly in the license, it should be easy for people
@@ -234,7 +238,7 @@
consistently worldwide.</p>
</div>
<div class="section"
id="when-the-rules-are-broken-a-smooth-path-to-compliance">
-<h2>When the Rules Are Broken: A Smooth Path to Compliance</h2>
+<h3>When the Rules Are Broken: A Smooth Path to Compliance</h3>
<p>Under GPLv2, if you violated the license in any way, your rights were
automatically and permanently lost. The only way to get them back was to
petition the copyright holder. While a strong defense against violations
@@ -255,18 +259,20 @@
gives violators incentive to comply.</p>
</div>
<div class="section" id="the-latest-and-greatest">
-<h2>The Latest and Greatest</h2>
+<h3>The Latest and Greatest</h3>
<p>Some of these changes probably seem less important to you than others.
That's okay. Every project is different, and needs different things from
its license. But odds are that a number of these improvements will help
you and your work.</p>
-<p>And taken as a whole, all these upgrades represent something more: we made
-a better copyleft. It does more to protect users' freedom, but it also
-enables more cooperation in the free software community. But updating the
-license is only part of the job: in order for people to get the benefits it
-offers, developers need to use GPLv3 for their projects, too. By releasing
-your own software under the new license, everyone who deals with itâusers,
other developers, distributors, even lawyersâwill benefit. We
-hope you'll use GPLv3 for your next release.</p>
+<p>And taken as a whole, all these upgrades represent something more:
+we made a better copyleft. It does more to protect users' freedom,
+but it also enables more cooperation in the free software community.
+But updating the license is only part of the job: in order for people
+to get the benefits it offers, developers need to use GPLv3 for their
+projects, too. By releasing your own software under the new license,
+everyone who deals with it—users, other developers,
+distributors, even lawyers—will benefit. We hope you'll use
+GPLv3 for your next release.</p>
<p>If you'd like to learn more about upgrading your project to GPLv3, the FSF
Compliance Lab would be happy to assist you. On <a class="reference external"
href="http://www.fsf.org/licensing/";>our web site</a>, you can
find <a class="reference external"
href="http://www.fsf.org/licensing/licenses/gpl-howto.html";>basic instructions
for using the license</a>, and an <a class="reference external"
href="http://www.fsf.org/licensing/licenses/gpl-faq.html";>FAQ addressing
@@ -304,40 +310,43 @@
</p>
<p>
-Copyright © 2007 Free Software Foundation, Inc.
-<br />
+Copyright © 2007, 2008 Free Software Foundation, Inc.</p>
+<address>51 Franklin St, Fifth Floor, Boston, MA 02110, USA</address>
+<p>
Verbatim copying and distribution of this entire article are permitted
worldwide without royalty in any medium provided this notice is preserved.</p>
<p>
Updated:
<!-- timestamp start -->
-$Date: 2008/06/29 13:43:55 $
+$Date: 2008/08/28 11:45:17 $
<!-- timestamp end -->
</p>
</div>
<div id="translations">
-<h3>Translations of this page:</h3>
+<h4>Translations of this page:</h4>
-<!-- Please keep this list alphabetical. -->
-<!-- Comment what the language is for each type, i.e. de is Deutsch.-->
+<!-- Please keep this list alphabetical by language code. -->
+<!-- Comment what the language is for each type, i.e. de is German. -->
+<!-- Write the language name in its own language (Deutsch) in the text. -->
<!-- If you add a new language here, please -->
<!-- advise address@hidden and add it to -->
-<!-- - /home/www/bin/nightly-vars either TAGSLANG or WEBLANG -->
<!-- - /home/www/html/server/standards/README.translations.html -->
<!-- - one of the lists under the section "Translations Underway" -->
<!-- - if there is a translation team, you also have to add an alias -->
<!-- to mail.gnu.org:/com/mailer/aliases -->
-<!-- Please also check you have the 2 letter language code right versus -->
-<!-- <URL:http://www.w3.org/WAI/ER/IG/ert/iso639.htm> -->
-<!-- Please use W3C normative character entities -->
+<!-- Please also check you have the language code right; see: -->
+<!-- http://www.loc.gov/standards/iso639-2/php/code_list.php -->
+<!-- If the 2-letter ISO 639-1 code is not available, -->
+<!-- use the 3-letter ISO 639-2. -->
+<!-- Please use W3C normative character entities. -->
<ul>
<!-- English -->
<li><a href="/licenses/quick-guide-gplv3.html">English</a> [en]</li>
<!-- French -->
-<li><a href="/licenses/quick-guide-gplv3.fr.html">Français</a> [fr]</li>
+<li><a
href="/licenses/quick-guide-gplv3.fr.html">Français</a> [fr]</li>
</ul>
</div>
</div>
- www/licenses quick-guide-gplv3.html,
Yavor Doganov <=