Changeset - 22ac76ad23f7
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 9 years ago 2014-11-07 12:43:07
bkuhn@ebb.org
Add footnote describing how CCS reviews were done.
1 file changed with 7 insertions and 1 deletions:
0 comments (0 inline, 0 general)
enforcement-case-studies.tex
Show inline comments
...
 
@@ -285,7 +285,13 @@ Specifically, this chapter discusses the purchase, CCS provision, and a
 
step-by-step build and installation analysis of a specific, physical,
 
embedded electronics product.  The product in question is
 
\href{https://www.thinkpenguin.com/gnu-linux/free-software-wireless-n-broadband-router-gnu-linux-tpe-nwifirouter}{the
 
  ``TPE-NWIFIROUTER'' wireless router by ThinkPenguin}.
 
  ``TPE-NWIFIROUTER'' wireless router by ThinkPenguin}\footnote{The FSF of
 
  course performed a thorough CCS check as part of the certification process.
 
  The analysis discussed herein was independently performed by Software
 
  Freedom Conservancy without reviewing any findings of the FSF, and thus the
 
  analysis provides a ``true to form'' analysis as it occurs when Conservancy
 
  investigates a potential GPL violation.  In this case, obviously, no
 
  violation was uncovered.}
 

	
 
\section{Root Filesystem and Kernel Compilation}
 

	
0 comments (0 inline, 0 general)