% gpl-lgpl.tex                                                  -*- LaTeX -*-

%      Tutorial Text for the Detailed Study and Analysis of GPL and LGPL course

%

% Copyright (C) 2003, 2004, 2005, 2006 Free Software Foundation, Inc.

% Copyright (C) 2014                   Bradley M. Kuhn

% License: CC-By-SA-4.0

% The copyright holders hereby grant the freedom to copy, modify, convey,

% Adapt, and/or redistribute this work under the terms of the Creative

% Commons Attribution Share Alike 4.0 International License.

% This text is distributed in the hope that it will be useful, but

% WITHOUT ANY WARRANTY; without even the implied warranty of

% MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

% You should have received a copy of the license with this document in

% a file called 'CC-By-SA-4.0.txt'.  If not, please visit

% https://creativecommons.org/licenses/by-sa/4.0/legalcode to receive

% the license text.

\newcommand{\defn}[1]{\emph{#1}}

\part{Detailed Analysis of the GNU GPL and Related Licenses}

\begin{center}

{\parindent 0in

\tutorialpartsplit{``Detailed Analysis of the GNU GPL and Related Licenses''}{This part} is: \\

\begin{tabbing}

Copyright \= \copyright{} 2003, 2004, 2005, 2006 \= \hspace{.2in} Free Software Foundation, Inc. \\

Copyright \= \copyright{} 2014 \= \hspace{.2in} Bradley M. Kuhn \\

Copyright \= \copyright{} 2014 \= \hspace{.2in} Anthony K. Sebro, Jr. \\

\end{tabbing}

Authors of \tutorialpartsplit{``Detailed Analysis of the GNU GPL and Related Licenses''}{this part} are: \\

Free Software Foundation, Inc. \\

Bradley M. Kuhn \\

David ``Novalis'' Turner \\

Daniel B. Ravicher \\

Tony Sebro \\

John Sullivan

\vspace{.3in}

The copyright holders of \tutorialpartsplit{``Detailed Analysis of the GNU GPL and Related Licenses''}{this part} hereby grant the freedom to copy, modify,

convey, Adapt, and/or redistribute this work under the terms of the Creative

Commons Attribution Share Alike 4.0 International License.  A copy of that

license is available at

\verb=https://creativecommons.org/licenses/by-sa/4.0/legalcode=.  }

\end{center}

\bigskip

\bigskip

\tutorialpartsplit{This tutorial}{This part of the tutorial} gives a

comprehensive explanation of the most popular Free Software copyright

license, the GNU General Public License (``GNU GPL'', or sometimes just

``GPL'') -- both version 2 (``GPLv2'') and version 3 (``GPLv3'') -- and

teaches lawyers, software developers, managers and business people how to use

the GPL (and GPL'd software) successfully both as a community-building

software into a new Free Software business and in existing, successful

enterprises.

To successfully benefit of from this part of the tutorial, readers should

understanding of how copyright law applies to software is also helpful.  The

tutorial is of most interest to lawyers, software developers and managers who

run or advise software businesses that modify and/or redistribute software

who wish to make use of existing GPL'd software in their enterprise.

to have learned the following:

\begin{itemize}

  \item The differences between GPLv2 and GPLv3.

  \item The redistribution options under the GPLv2 and GPLv3.

  \item The obligations when modifying GPLv2'd or GPLv3'd software.

  \item How to build a plan for proper and successful compliance with the GPL.

  \item The business advantages that the GPL provides.

  \item The most common business models used in conjunction with the GPL.

  \item How existing GPL'd software can be used in existing enterprises.

    differs from the GPLv2 and GPLv3, respectively.

  \item The basics to begin understanding the complexities regarding

    derivative and combined works of software.

\end{itemize}

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% END OF ABSTRACTS SECTION

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

% START OF DAY ONE COURSE

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

\chapter{What Is Software Freedom?}

Study of the GNU General Public License (herein, abbreviated as \defn{GNU

  GPL} or just \defn{GPL}) must begin by first considering the broader world

of software freedom. The GPL was not created from a void, rather, it was

created to embody and defend a set of principles that were set forth at the

founding of the GNU project and the Free Software Foundation (FSF) -- the

organization that upholds, defends and promotes the philosophy of software

freedom. A prerequisite for understanding both of the popular versions of GPL

(GPLv2 and GPLv3) and their terms and conditions is a basic understanding of

the principles behind it.  The GPL family of licenses are unlike almost all

other software licenses in that they are designed to defend and uphold these

principles.

\section{The Free Software Definition}

\label{Free Software Definition}

The Free Software Definition is set forth in full on FSF's website at

\verb0http://fsf.org/0 \verb0philosophy/free-sw.html0. This section presents

an abbreviated version that will focus on the parts that are most pertinent

to the GPL\@.

A particular program grants software freedom to a particular user if that

user is granted the following freedoms:

\begin{itemize}

\item The freedom to run the program, for any purpose.

\item The freedom to study how the program works, and modify it

\item The freedom to redistribute copies.

\item The freedom to distribute copies of  modified versions to others.

\end{itemize}

The focus on ``a particular user'' is particularly pertinent here.  It is not

uncommon for the same version of a specific program to grant these freedoms

to some subset of its user base, while others have none or only some of these

freedoms.  Section~\ref{Proprietary Relicensing} talks in detail about how

this can unfortunately happen even if a program is released under the GPL\@.

Many people refer to software that gives these freedoms as ``Open Source.''

Besides having a different political focus than those who call it Free

Software,\footnote{The political differences between the Free Software

  Movement and the Open Source Movement are documented on FSF's Web site at

  {\tt http://www.fsf.org/licensing/essays/free-software-for-freedom.html}.}

those who call the software ``Open Source'' are often focused on a side

issue.  Specifically, user access to the source code of a program is a

prerequisite to make use of the freedom to modify.  However, the important

issue is what freedoms are granted in the license of that source code.

Software freedom is only complete when no restrictions are imposed on how

these freedoms are exercised.  Specifically, users and programmers can

exercise these freedoms noncommercially or commercially.  Licenses that grant

these freedoms for noncommercial activities but prohibit them for commercial

activities are considered non-free.  Even the Open Source Initiative

(\defn{OSI}) (the arbiter of what is considered ``Open Source'') also rules

such licenses not in fitting with their ``Open Source Definition''.

In general, software for which most or all of these freedoms are

restricted in any way is called ``non-Free Software.''  Typically, the

term ``proprietary software'' is used more or less interchangeably with

``non-Free Software.''  Personally, I tend to use the term ``non-Free

Software'' to refer to noncommercial software that restricts freedom

(such as ``shareware'') and ``proprietary software'' to refer to

commercial software that restricts freedom (such as nearly all of

Microsoft's and Oracle's offerings).

Keep in mind that the none of the terms ``software freedom'', ``open source''

and ``free software'' are not known to be trademarked by any organization in

any jurisdiction.  As such, it's quite common that these terms are abused and

misused by parties who wish to bank on the popularity of software freedom.

When one considers using, modifying or redistributing a software package that

purports to be Open Source or Free Software, one \textbf{must} verify that

the license grants software freedom

Furthermore, throughout this text, we generally prefer the term ``software

freedom'', as this is the least ambiguous term available to describe software

that meets the Free Software Definition.  For example, it is well known and

often discussed that the adjective ``free'' has two unrelated meanings in

English: ``free as in freedom'' and ``free as in price''.  Meanwhile, the