+— GPLv2§3 +
+ + +# The 11 Words That Consumed My Life + ++ GPLv2 enforcement, for embedded products, is all about the these eleven + words. + ++ I could give an entire talk on any one of these 11 words. + + Yes, I can even give 20-30 minute treatises on each use of “the”. + ++ Yet, when enforcement processes are at their best, they're about the spirit + behind these words, not the words themselves. + ++— GPLv2§3 +
+ + +# The 11 Words That Consumed My Life + ++ Basic reference rule: + + Can a developer reasonably skilled in the art of embedded software + build your sources, take the (copylefted) executables and install + them? + ++ Enforcement spends its most attention on testing CSS + “candidates” to verify that. + ++— GPLv2§3 +
+ + # CCS "Round" Reports + Evaluate each CCS candidate. @@ -309,6 +380,116 @@ to email NAME@COMPANY.com , which is how the above instructions for downloading the source were received. +# A Pristine Example + ++ Enforcement must often use a “know it when I see it” standard. + + i.e., can we take your CCS build it, and install it? + ++ We've reached compliant CCS with hundreds of companies: + + but that didn't mean the CCS was pretty. + ++ Thanks to ThinkPenguin, we finally have an example of beautiful embedded + product compliance. + +# Lessons Learned from Pristine Example + ++ The full paper for this talk is available online: + + [compliance.guide/pristine-example](http://compliance.guide/pristine-example) + + ++ It's part of the larger tutorial called [*Copyleft and the GNU General + Public License: A Comprehensive Tutorial and Guide*](https://copyleft.org/guide/) + at copyleft.org. + +# Give a roadmap in a README + ++ Scripts doesn't only mean shell scripts and Makefiles. + ++ Think of the script of a play or movie. + ++ If your build process includes human intervention … + ++ … then the script are a written explanation of what the human must +do. + ++— GPLv2§3 +
+ + +# ThinkPengiun's README + +A file called “README” at the top-level directory said: + + In order to build firmware images for your router, the following needs to be installed: + + gcc, binutils, bzip2, flex, python, perl, make, find, grep, diff, unzip, + gawk, getopt, libz-dev and libc headers. + + Please use “make menuconfig” to configure your appreciated configuration + for the toolchain and firmware. Please note that the default configuration + is what was used to build the firmware image for your router. It is advised + that you use this configuration. + + Simply running “make” will build your firmware. The build system will + download all sources, build the cross-compile toolchain, the kernel and all + chosen applications. + + To build your own firmware you need to have access to a GNU/Linux system + (case-sensitive filesystem required). + +# Make Sure It Builds + ++ Can your CCS pass this test? + + Give you source release to another developer from another department. + + Ask them to follow the instructions you wrote. + + They should get the equivalent binaries you get in building. + ++ Very few organizations bother to do this. + ++ It's probably the most useful step to verify compliance, yet *no* + compliance process recommendations I've ever seen include this. + ++— GPLv2§3 +
+ + + +# It's not “make install” + ++ Server system software can offer a “make install” that + reasonable works to meet installation requirements. + ++ Embedded products are admittedly difficult to install. + ++ To comply here, you'll usually just have write out the instructions. + ++ It is required; don't skip this part. + ++— GPLv2§3 +
+ + +# Missing hardware components + ++ Inclusion of specialized installation hardware is not a + “script”. + ++ In our ThinkPenguin example, we had to go buy a USB serial adapter to + install the modified firmware. + ++ Just tell the user what they have to go buy for the install to work. + # More Info / Talk License