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

Wordsmith whole section.

Browse source
This commit is contained in:
Bradley M. Kuhn 2014-03-19 18:32:45 -04:00
parent edcdf9977a
commit 8ce1870cef
1 changed files with 22 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

43
gpl-lgpl.tex
View file

@ -2208,37 +2208,38 @@ sorts of individuals and even for-profit companies. Nevertheless, in
attempting to understand GPLv3 after the fact, the materials available from
the GPLv3 process have a somewhat ``drinking from the firehose'' effect.
This chapter seeks to explain GPLv3 to newcomers, who perhaps are familiar
with GPLv2. Those who wish a to head to the firehose and take a diachronic
approach to GPLv3 study by reading the step-by-step public drafting process
GPLv3 (which occurred from Monday 16 January 2006 through Monday 19 November
2007) should visit \url{http://gplv3.fsf.org/}.
with GPLv2 and who did not participate in the GPLv3 process.
Those who wish to drink from the firehose and take a diachronic approach to
GPLv3 study by reading the step-by-step public drafting process GPLv3 (which
occurred from Monday 16 January 2006 through Monday 19 November 2007) should
visit \url{http://gplv3.fsf.org/}.
\section{Understanding GPLv3 As An Upgraded GPLv2}
Ultimately, GPLv2 and GPLv3 co-exist as active licenses in regular use. As
discussed in Chapter\~ref{tale-of-two-copylefts}, GPLv1 was never in regular
use alongside GPLv2. However, given GPLv2's widespread popularity and
discussed in Chapter\~ref{tale-of-two-copylefts}, GPLv1 was never regularly
used alongside GPLv2. However, given GPLv2's widespread popularity and
existing longevity by the time GPLv3 was published, it is not surprising that
some licensors have continued to prefer GPLv2-only or GPLv2-or-later as their
preferred license. GPLv3 has gained major adoption by many projects, old and
new, but many projects have not upgraded due to (in some cases) mere laziness
and (in other cases) policy preference for some of GPLv2's terms.
some licensors still prefer GPLv2-only or GPLv2-or-later. GPLv3 gained major
adoption by many projects, old and new, but many projects have not upgraded
due to (in some cases) mere laziness and (in other cases) policy preference
for some of GPLv2's terms and/or policy opposition to GPLv3's terms.
Given this ``two GPLs'' world is the one we all live in, it makes sense to
consider GPLv3 in terms of how it differs from GPLv2. Also, most of the best
GPL experts in the world must deal regularly with both licenses, and
admittedly have decades of experience of GPLv2 while the most experience with
GPLv3 that's possible is by default less than a decade.
These two factors usually cause even new students of GPL to start with GPLv2
and move on to GPLv3, and this tutorial follows that pattern.
Given this ``two GPLs world'' is reality, it makes sense to consider GPLv3 in
terms of how it differs from GPLv2. Also, most of the best GPL experts in
the world must deal regularly with both licenses, and admittedly have decades
of experience of GPLv2 while the most experience with GPLv3 that's possible
is by default less than a decade. These two factors usually cause even new
students of GPL to start with GPLv2 and move on to GPLv3, and this tutorial
follows that pattern.
Overall, the changes made in GPLv3 admittedly \textit{increased} the
complexity of the license. The FSF stated at the start of the GPLv3 process
that they would have liked to oblige those who have asked for a simpler and
shorter GPL\@. Ultimately, the FSF gave priority to making GPLv3 do the job
that needs to be done to build a better copyleft. Obsession for concision
should never trump software freedom.
shorter GPL\@. Ultimately, the FSF gave priority to making GPLv3 a better
copyleft in the spirit of past GPL's. Obsession for concision should never
trump software freedom.
\section{GPLv3~\S0: Giving In On ``Defined Terms''}