Copyleft/guide
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add better introduction to this section on defined terms,

Browse source 
including a nice anecdote.
This commit is contained in:
Bradley M. Kuhn 2014-03-19 09:54:12 -04:00
parent 3694e446db
commit 728c800bf3
1 changed files with 17 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
gpl-lgpl.tex
View file

@ -2192,7 +2192,23 @@ should never trump software freedom.
\section{GPLv3~\S0: Giving In On ``Defined Terms''} \section{GPLv3~\S0: Giving In On ``Defined Terms''}
% FIXME: intro defined terms One of lawyers' most common complaints about GPLv2 is that defined terms in
the document appear throughout. Most licenses define terms up-front.
However, GPL was always designed both as a document that should be easily
understood both by lawyers and by software developers: it is a document
designed to give freedom to software developers and users, and therefore it
should be comprehensible to that constituency.
Interestingly enough, one coauthor of this tutorial who is both a lawyer and
a developer pointed out that in law school, she understood defined terms more
quickly than other law students precisely because of her programming
background. For developers, having \verb0#define0 (in the C programming
language) or other types of constants and/or macros that automatically expand
in the place where they are used is second nature. As such, adding a defined
terms section was not terribly problematic for developers, and thus GPLv3
adds one. Most of these defined terms are somewhat straightforward and bring
forward better worded definitions from GPLv2. Herein, this tutorial
discusses a few of the new ones.
% FIXME: rewrite to FOUR new terms % FIXME: rewrite to FOUR new terms