Changeset - 41c72f36e86a
[Not reviewed]
0 1 0
Bradley Kuhn (bkuhn) - 10 years ago 2014-11-09 22:56:35
bkuhn@ebb.org
Slightly reword.
1 file changed with 1 insertions and 1 deletions:
0 comments (0 inline, 0 general)
enforcement-case-studies.tex
Show inline comments
...
 
@@ -876,49 +876,49 @@ can be learned here:
 
  certainly be more like the script of a play and less like a Bash script.
 

	
 
\item {\bf Write build/install instructions to the appropriate level of
 
  specificity}.  The upstream engineers
 
  in this case study \hyperref[thinkpenguin-specific-host-system]{clearly did
 
    additional work to ensure functionality on a wide variety of host build
 
    systems}; this is quite rare.  When in doubt, include the maximum level
 
  of detail build engineers can provide with the CCS instructions, but also
 
  double-check to investigate if a more generalized solution (such as other
 
  host systems) work just as well for the build.
 

	
 
\item {\bf Seek to adhere to the spirit of copyleft, not just the letter of
 
  the license}.  Encouragement of users to improve and
 
  make their devices better is one of ThinkPenguin's commercial differentiators.  Copyleft advocates
 
  that other companies have undervalued the large and lucrative
 
  market of
 
  users who seek hackable devices.  By going beyond the
 
  mere minimal requirements of GPL, companies can immediately reap the
 
  benefits in that target market.
 

	
 
  \item Community-oriented enforcement organizations do not play ``gotcha''\footnote{For lack of a better
 
    phrase.} with distributors regarding GPL
 
    violations.  The goal in the GPL enforcement process is to achieve
 
    compliance and correct mistakes and annoyances.  Such organizations
 
    therefore take an ``innocent until proven guilty $\rightarrow$ guilty
 
    therefore take an ``innocent until proven guilty $\rightarrow$ assume guilty
 
    due to honest error rather than malicious action '' approach.  The goal
 
    is compliance (in direct contrast with
 
    the \hyperref[Proprietary Relicensing]{discussion in \S~\ref*{Proprietary Relicensing} about the
 
      proprietary relicensing} business model).
 
    
 
\end{enumerate}
 

	
 
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
\chapter{Bortez: Modified GCC SDK}
 

	
 
In our first case study, we will consider Bortez, a company that
 
produces software and hardware toolkits to assist OEM vendors, makers
 
of consumer electronic devices.
 

	
 
\section{Facts}
 

	
 
One of Bortez's key products is a Software Development Kit (``SDK'')
 
designed to assist developers building software for a specific class of
 
consumer electronics devices.
 

	
 
FSF received a report that the SDK may be based on the GNU Compiler
 
Collection (which is an FSF-copyrighted collection of tools for software
 
development in C, C++ and other popular languages). FSF investigated the
 
claim, but was unable to confirm the violation. The violation reporter
0 comments (0 inline, 0 general)