> On Wed, Apr 23, 2014 at 7:19 AM, Bradley M. Kuhn <[email protected]> wrote: > > Here's a brief list of the main things I ask for on a new enforcement > > matter: > > Some of this is already in the tutorial book I've been putting together > > (see: https://www.gitorious.org/gpl-compliance-tools/tutorial/ )
Robinson Tryon wrote: > Is there a place where builds of the compliance book are uploaded? It could > be very helpful to be able to point directly at this type of basic > checklist, e.g. when someone new shows up to this list with a potential GPL > violation and asks for our help. First, it's more than just a compliance book. There's only two sections on compliance. Most of it is a detailed walk-through of GPL. I've titled it: "Copyleft and the GNU General Public License: A Comprehensive Tutorial", and thus it has to cover compliance and enforcement (after all), but not exclusively those topics. Second, there's no auto build process for the LaTeX sources (patches welcome ;), but I've been keeping a current PDF [0] version on a URL of my personal website: http://ebb.org/bkuhn/articles/copyleft-book.pdf I will make sure that URL is permanently stable and redirects to the "right place" if there ever is a "right place" in the future. :) Finally, the compliance section is written as "advice to would-be violators". I wrote it originally as a document to help me prepare when I started giving public talks on the issues of GPL compliance back in the mid-2000s, and it's been edited heavily by both me and Aaron Williamson since then, but ultimately it's still just a summary of what I talk about in one-hour presentation on compliance. Thus, the info isn't presented in the best possible way for the average poster on this list (who are mostly violation reporters/discoverers, not violators). I'd thus love a chapter that discussed "advice to violation reporters and investigators", and as I said, patches/merge-requests welcome under CC-By-SA-4.0. :) Long term, I want to write a CCS tutorial chapter too. When there are major updates, I'll post notice to this list. [0] The HTML build of from LaTeX sources is broken at the moment. tex4ht has changed a lot since I set it up, and since the LaTeX sources were taken from nearly a dozen different historical documents that I and others had written, there isn't consistent use of tex4ht-isms to properly generate HTML. (Man, this thing needs an issue tracker as well now, huh? I'll file a bug that I need a bug tracker ... <Segmentation fault> ;) -- bkuhn
