File diff 95f740984e8f → 242aa60fc7b0
www/conservancy/static/copyleft-compliance/firmware-liberation.html
Show inline comments
 
{% extends "base_compliance.html" %}
 
{% block subtitle %}Copyleft Compliance Projects - {% endblock %}
 
{% block submenuselection %}EnforcementStrategy{% endblock %}
 
{% block submenuselection %}LiberateFirmware{% endblock %}
 
{% block content %}
 

	
 
<h1 id="software-freedom-conservancy-proposal-for-firmware-liberation-project">Firmware Liberation Project</h1>
 

	
 
<p>Conservancy plans to select a class of product in the Linux-based embedded
 
system space.  For this product, Conservancy will launch, or assist, a
 
project that creates a functioning alternative firmware for those devices.
 
The promise of GPL enforcement is only realized through actual, practical use
 
and improvement of the released software for users.</p>
 

	
 
<h2 id="gpl-enforcement-needs-follow-through">GPL Enforcement Needs Follow-Through</h2>
 

	
 
<p>Simply enforcing the GPL is an important first step, and Conservancy
 
  <a href="enforcement-strategy.html">continues our efforts in that
 
  regard</a>. However, we can
 
  replicate <a href="/copyleft-compliance/enforcement-strategy.html#brief-history-of-user-focused-gpl-enforcement">the
 
  success found with OpenWrt</a> <em>only by</em> a substantial
 
  effort <strong>after</strong> enforcement occurs to turn the compliant
 
  source release into a viable alternative firmware for the platform.</p>
 
                                           
 
<p>Conservancy has seen non-compliant Linux-based firmwares on refrigerators,
 
  baby monitors, virtual assistants, soundbars, doorbells, home security
 
  cameras, police body cameras, cars, AV receivers, and televisions.  We
 
  believe that building an alternative firmware for one of these classes of