Source: https://k.copyleft.org/guide/changelog/2a42c6fb7e481099aa3253281e6ea47ba8541dd0/comprehensive-gpl-guide.tex
Timestamp: 2018-10-20 15:37:57
Document Index: 130308158

Matched Legal Cases: ['§3', '§3', '§3', '§3', '§3', '§3', '§3', '§3']

guide Changelog /comprehensive-gpl-guide.tex
Changelog - /comprehensive-gpl-guide.tex @ d7ff8bd6ff1f - showing 52 out of 52 revisions
bkuhn d7ff8bd6ff1f
Additional connecting text for irrevocability discussion. A forward reference is added to connect to the irrevocability section, and one transition sentence added in the irrevocability section itself, since it&apos;s another "digression" from the walk-through of GPLv2 in these sections.
Pamela Chestek d2b784546039
More detail on Irrevocability of GPLv2 This section, fit in just after the detailed discussion of GPLv2 Section 6, explains in futher detail various arguments for why the GPLv2 is irrevocable.
bkuhn 851be52e624c
Rework two compliance guide sections in Background Some of the text pasted in earlier commits was certainly useful, but needed a complete rework. Also, the text pasted was far too terse, and more detail was needed. Therefore, I&apos;ve moved text around and build a more comprehensive Background section. I&apos;ve moved the burgeoning "Understanding Who&apos;s Enforcing" section into the Background chapter and made it complete. Probably the most bizarre (?) change I&apos;ve made here is coining this acronym COGEO. This is non-optimal for sure, and I&apos;ve added a FIXME to seek a better term.
bkuhn a1b059184c96
Incorporate useful text from a third party work. Software Freedom Law Center, a small law firm specializing in Open Source, recently published its so-called "Guide to GPL Compliance, Second Edition": http://softwarefreedom.org/resources/2014/SFLC-Guide_to_GPL_Compliance_2d_ed.html The Firm&apos;s document is substantially less comprehensive than this one; however, their document contained a few phrases and paragraphs that seemed useful and accurate. This commit incorporates the useful material from that work into this one (as permitted by the CC BY-SA 4.0 license, which the Software Freedom Law Center applied to their work). The useful sections have been pasted without proper textual integration into the appropriate sections of this tutorial. A few are currently commented out entirely and marked with appropriate FIXME&apos;s. Meanwhile, the text that seems immediately useful is *not* commented out, and is marked with "FIXME-URGENT". Additional work is now required to integrate the new text properly into this tutorial. Careful readers who compare this commit with The Firm&apos;s document will find that I passed on inclusion of some seemingly useful material. Unfortunately, The Firm&apos;s text contained some inaccuracies, and frames discussion primarily from a for-profit perspective. More disturbingly, a few statements even directly contradicted the FSF&apos;s stated policies. Of course, The Firm clearly claims "this document does not express the views, intentions, policy, or legal analysis of any SFLC clients or client organizations", but I could not in good conscience adopt, as the official advice in this tutorial, any text that conflicts with the FSF&apos;s policies, nor will I incorporate any puffery that subtly kowtows to for-profit corporate interests. Nevertheless, given The Firm&apos;s perceived stature, I briefly considered including policy-conflicting statements, attributing them as alternative third-party opinions; many of the FSF&apos;s own opinions were already incorporated in that manner earlier this year. Indeed, I will not prima facie reject future patches that integrate such statements naturally for this tutorial. However, I feel that the didactic value of including The Firm&apos;s attributed dissenting opinions in this tutorial does not outweigh my editing effort required for such additional textual integration. Regarding Software Freedom Law Center&apos;s copyrights included herein, I took the following specific actions to comply with CC By SA 4.0: §3(a)(1)(a)(i): This log message indicates Software Freedom Law Center as the source of the material herein committed. §3(a)(1)(a)(i): Copyright notices at the top level of the document, as well as those in individual parts, are updated to include the 2014 copyright notice from the Software Freedom Law Center. §3(a)(1)(a)(ii-v): The project already referred to and included a copy §3(b)(1): of CC BY SA 4.0 International and its URL. §3(a)(2): The attribution information is fully included in this Git repository. §3(a)(3): I and this project have received no such request. §3(b)(1): The license of the larger work was already CC BY SA 4.0 International. §3(b)(3): No such conditions are imposed.
bkuhn 99fccc120c55
PDF output doesn&apos;t have enough space here.
bkuhn 54f94ca0a919
FIXME regarding inconsistent code example formats
bkuhn 3ee46d677044
A few FIXMEs for formatting hacks.
bkuhn a45f702c2ab4
Formatting fixes for copyright notices.
bkuhn 05d02bfff430
Various temp changes to handle printing it this weekend.
bkuhn 077622c17749
Note that sources are available.
donaldr3 a8b25085c254
changed modified GPL note to say explanation instead of additional permission
bkuhn ee9e86642a07
Properly update and format copyright notices and title pages.
Tony Sebro 844bf4ba5b34
Updated analysis of derivative works.
bkuhn 4cea1c46451f
Relevant text from GPLv3 First Discussion Draft Rationale of 2006-01-16. I carefully went through FSF&apos;s First Discussion Draft Rationale, which was published on Monday 16 January 2006 and merged in any relevant text and descriptions that might be of use in this tutorial. The raw material used for this commit can be found here: http://gplv3.fsf.org/gpl-rationale-2006-01-16.html Specifically, a copy of the LaTeX sources are here: http://gplv3.fsf.org/gpl-rationale-2006-01-16.tex As I merged in this text, I added FIXME&apos;s where it seemed the text was incomplete or referred to parts of GPLv3 draft text that disappeared in later versions. Finally, note that this material was originally copyrighted and licensed as follows: Copyright © 2006 Free Software Foundation, Inc. Verbatim copying and distribution of this entire article are permitted worldwide, without royalty, in any medium, provided this notice, and the copyright notice, are 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.
bkuhn a700a8caa60d
I&apos;m starting to think Conny looks better. Long term, as mentioned in a previous commit, we should look at the memoir package.
bkuhn 76284eab94fe
new command for when tutorials are split apart. First arg is what to say when it&apos;s by itself, second arg is for when they are integrated.
bkuhn dd4bec31c086
Notes about formatting and possible later use of memoir, fancyhdr for now.
bkuhn e4dc938c8c97
Word smith.
bkuhn 33bfee7702dc
It&apos;s for lawyers too.
bkuhn 7ad226003dbe
Create and update copyright notice and licensing information.
bkuhn f54257ba6595
Move stuff to make the ToC with now ...&apos;s and numbers to another file, and comment it out by default.
bkuhn bf4b3db60bbe
Incorporate enforcement case studies part into full book. This required removing much of the seminar-specific content, and reformatting.
bkuhn 9eb3c521b0cf
Incorporate the compliance guide into main text of the book. This required resectioning the entire compliance guide to be &apos;one level up&apos;. It furthermore required a few other formatting and related changes.
bkuhn 16ffbf69c53f
Correct licensing information so that it properly mentions licensing of licenses.
bkuhn f5c0cdc91905
Remove license text appendix from gpl-lgpl.tex and place it in its own file. Really, all these license texts should go at the very end behind all other materials.
bkuhn 52962a2af723
Temporarily added this code to generate a ToC without page numbers. I doubt this will be kept permanently. I learned this from: http://tex.stackexchange.com/questions/55465/remove-dots-page-numbers-from-toc
bkuhn 2230849e9358
Move table of contents before the Preface.
bkuhn 4331138536c6
Get one inch margins all around.
bkuhn 5b8a5bac1186
Better title, and reformat title for title page.
bkuhn 1583f593cae5
Initial work to merge this into a single comprehensive book. This entails removing book-like parts of gpl-lgpl.tex, moving some of it into this new toplevel file, and some other formatting and related changes.