The lists of authors in each part has been continually out of date and
incomplete. There are multiple examples, here are a few:
* In September 2005, John Sullivan made improvements and was not placed on
the Authors lists until I did so in a March 2014 commit.
* In March 2014, Martin Michlmayr submitted many patches, but was not
placed on the Authors lists until I did so in an April 2014 commit.
There is no easy way to keep these Authors lists current, and they aren't
necessary under CC-BY-SA-4.0 anyway, so I herein remove the Authors lists.
Additionally, previous commit added "published sources" in each part, which
is more static and easier to keep up to date and provides similar
information.
References and details regarding these published works from which some
text was incorporated already appeared in the commit logs in great
detail. The information, already fully available in the Guide's Git
logs in full compliance with CC-BY-SA-4.0 §3(a)(1-2), now appears in
summary form additionally in the compiled PDF/HTML/Postscript output.
The unicode ’ was introduced by the pasted text mention in the previous
commits. While I believe LaTeX can be configured to accept Unicode
quote equivalents, it seems simpler to me merely to replace the
character with an appropriate version that LaTeX expects in this
situation by default.
Much of the pasted text here was useful. However, some of the claims
were broad reaching, I've reigned those in. (e.g., saying "Taken
together, these provisions mean:" was a bit strong).
Also, in that specific spot, the conclusions made in the text were
described as applying to LGPLv2.1, but are clearly conclusions about
LGPLv3. I've corrected that herein.
Finally, I had to write a bunch of next text to make the pasted text
work, and also added one FIXME for later of where things could be
improved further.
This text was mostly useful as is. However, it failed to make a key
point I've often made: that the combinations created by comingling
AGPLv3'd code with GPLv3'd code may be difficult to disentangle, and
thus in practice, it may turn out that such a combination effectively
must be licensed as a whole under AGPLv3, even if technically some
copyrights included therein are GPLv3'd.
In practice, this nuance is only a technical barrier, since complying
fully with AGPLv3 automatically complies with GPLv3.
This text was (on the whole) useful as introductory text to this
tutorial's existing extensive section on GPLv3§11.
The example, however, belonged further down in the section, so I've
placed it there.
