Changeset - bf85191e636f
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-11-12 16:32:05
bkuhn@ebb.org
Add subsections for GPLv2§2 discussion.

The GPLv2§2 has gotten long enough that it really needed subsections.
1 file changed with 3 insertions and 1 deletions:
0 comments (0 inline, 0 general)
gpl-lgpl.tex
Show inline comments
...
 
@@ -1576,48 +1576,50 @@ For many, this is where the ``magic'' happens that defends software
 
freedom upon redistribution.  GPLv2~\S2 is the only place in GPLv2
 
that governs the modification controls of copyright law.  If users
 
distribute modified versions a GPLv2'd program, they must follow the terms of GPLv2~\S2 in making
 
those changes.  Thus, this sections ensures that the body of GPL'd software, as it
 
continues and develops, remains Free as in freedom.
 

	
 
To achieve that goal, GPLv2~\S2 first sets forth that the rights of
 
redistribution of modified versions are the same as those for verbatim
 
copying, as presented in GPLv2~\S1.  Therefore, the details of charging money,
 
keeping copyright notices intact, and other GPLv2~\S1 provisions are intact
 
here as well.  However, there are three additional requirements.
 

	
 
\subsection{The Simpler Parts of GPLv2~\S2}
 

	
 
The first (GPLv2~\S2(a)) requires that modified files carry ``prominent
 
notices'' explaining what changes were made and the date of such
 
changes. This section does not prescribe some specific way of
 
marking changes nor does it control the process of how changes are made.
 
Primarily, GPLv2~\S2(a) seeks to ensure that those receiving modified
 
versions know the history of changes to the software.  For some users,
 
it is important to know that they are using the standard version of
 
program, because while there are many advantages to using a fork,
 
there are a few disadvantages.  Users should be informed about the
 
historical context of the software version they use, so that they can
 
make proper support choices.  Finally, GPLv2~\S2(a) serves an academic
 
purpose --- ensuring that future developers can use a diachronic
 
approach to understand the software.
 

	
 
GPLv2~\S2(c), a relatively simple section, requires that any program which
 
(before modification) ``normally reads commands interactively when run'' and
 
displays or prints legal information also display all copyright notices,
 
warranty disclaimer, modification indications and a pointer to the license,
 
even in modified versions.  The requirement is relatively simple, and relates
 
to an important policy goal of copyleft: downstream users should be informed
 
of their rights.  Its implications and details are straightforward and
 
simple.
 

	
 
\medskip
 
\subsection{GPLv2~\S2(b)}
 

	
 
Meanwhile, GPLv2~\S2(b) requires careful and extensive study.  Its four short lines embody
 
the some of the essential legal details of ``share and share alike''.  These 46 words are
 
considered by some to be the most worthy of careful scrutiny because
 
GPLv2~\S2(b), and they
 
can be a source of great confusion when not properly understood.
 

	
 
In considering GPLv2~\S2(b), first note the qualifier: it \textit{only} applies to
 
derivative, combined and/or modified works that ``you distribute or publish''.  Despite years of
 
education efforts on this matter, many still believe that modifiers
 
of GPL'd software \textit{must} publish or otherwise
 
share their changes.  On the contrary, GPLv2~\S2(b) {\bf does not apply if} the
0 comments (0 inline, 0 general)