Relevant text from FSF's "GPLv3 Final Rationale" as released on 2007-06-29.
I (Bradley M. Kuhn) went through FSF's "GPLv3 Final Rationale", and pasted in any sections that seemed useful to this tutorial. There is a lot of interesting material in that particular rationale document, although much of it is probably too verbose for inclusion. I expect much of this will need to be cut out. The raw material used for this commit can be found here: http://www.gnu.org/licences/gpl3-final-rationale.pdf As I pasted in this text, I added FIXME's sometimes where it seemed the text might need work. However, I was much more extensive in just pasting here, so there's a big editing job now. As mentioned in a previous commit, the whole GPLv3 chapter is now completely disjoint with all this pasting. Finally, note that this material was originally copyrighted and licensed as follows: Copyright © 2007, Free Software Foundation, Inc. Verbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided this notice is preserved. However, I am hereby relicensing this material to CC-By-SA-4.0, with the verbal permission from John Sullivan, Executive Director of the FSF, which was given to me during a conference call on Wednesday 12 February 2014. I also confirmed that relicensing permission on IRC with johnsu01 today.
This commit is contained in:
parent
1e928fdbb8
commit
221481f33b
1 changed files with 20 additions and 0 deletions
20
gpl-lgpl.tex
20
gpl-lgpl.tex
|
@ -2823,6 +2823,16 @@ such combination occurs, including combination by dynamic linking. The final
|
|||
sentence of the paragraph adapts this requirement to the new compatibility
|
||||
provisions of section 7.
|
||||
|
||||
We have added these words to the aggregation clause to eliminate any question
|
||||
that GPLv3 alters the scope of the copyleft as understood and applied under
|
||||
GPLv2. In GPLv3, as in GPLv2, addition of modules or other parts to a program
|
||||
results in a new program based on the old program, with different functional
|
||||
characteristics created by the merger of two expressions: the original
|
||||
program and the added parts. Such added parts are ``by their nature
|
||||
extensions of'' the old program, and therefore the entire new program which
|
||||
they and the old program form must be licensed under the GPL. As subsection
|
||||
5c states, packaging of a work has no bearing on the scope of copyleft.
|
||||
|
||||
\section{GPLv3~\S6: Non-Source and Corresponding Source}
|
||||
|
||||
Section 6 of GPLv3, which clarifies and revises GPLv2 section 3, requires
|
||||
|
@ -3532,6 +3542,16 @@ addition of the cure opportunity achieves a better balance than our earlier
|
|||
section 8 drafts between facilitating enforcement of the license and
|
||||
protecting inadvertent violators against unfair results.
|
||||
|
||||
We have restructured the form of section 8 by replacing non-automatic
|
||||
termination with automatic termination coupled with opportunities for
|
||||
provisional and permanent reinstatement of rights. The revised wording does
|
||||
not alter the underlying policy or details of procedure established in the
|
||||
previous drafts, including the 60-day period of repose and 30-day cure
|
||||
opportunity for first-time violators. The restoration of automatic
|
||||
termination was motivated in part to facilitate enforcement in European
|
||||
countries. We also believe the revised wording will be easier to understand
|
||||
and apply in all jurisdictions.
|
||||
|
||||
\section{GPLv3~\S9: Acceptance}
|
||||
|
||||
% FIXME: needs some work here
|
||||
|
|
Loading…
Reference in a new issue