File diff 344d52ba632c → 20a3b7757aa8
www/conservancy/static/copyleft-compliance/enforcement-strategy.html
Show inline comments
...
 
@@ -252,15 +252,15 @@
 

	
 
<p>Conservancy, after years of analyzing its successes and failures of
 
  previous GPL compliance litigation, has developed — in conjunction with
 
  litigation counsel over the last year — new approaches to litigation
 
  strategy.  We believe this will bring to fruition the promise of copyleft:
 
  a license that ensures the rights and software freedoms of hobbyists who
 
  seek full control and modifiability of devices they own. With the benefit
 
  of this grant, Conservancy plans to accelerate these plans in 2020 and to
 
  keep the public informed at every stage of the process.</p>
 
  seek full control and modifiability of devices they own. Conservancy plans
 
  to accelerate these plans in late 2020 into early 2021 and we'll keep the
 
  public informed at every stage of the process.</p>
 

	
 
<h3 id="persistent-non-litigation-enforcement">Persistent Non-Litigation Enforcement</h3>
 

	
 
<p>While we will seek damages to cover our reasonable costs of this work, we
 
  do not expect that any recovery in litigation can fully fund the broad base
 
  of work necessary to ensure compliance and the software freedom it brings.
...
 
@@ -272,24 +272,24 @@
 
  devices we previously had no idea contained Linux, and we’ll begin our
 
  diligent and unrelenting work to achieve software freedom for the owners of
 
  those devices. We will also build more partnerships across the technology
 
  sector and consumer rights organizations to highlight the benefit of
 
  copyleft to not just hobbyists, but the entire general public.</p>
 

	
 
<h3 id="alternative-firmware-project">Alternative Firmware Project</h3>
 
<h3 id="alternative-firmware-project"><a href="/copyleft-compliance/firmware-liberation.html">Alternative Firmware Project</a></h3>
 

	
 
<p>The success of the OpenWrt project, born from GPL enforcement, has an
 
  important component. While we’ve long hoped that volunteers, as they did
 
  with OpenWrt and SamyGo, will take up compliant sources obtained in our GPL
 
  enforcement efforts and build alternative firmware projects, history shows
 
  us that the creation of such projects is not guaranteed and exceedingly
 
  rare.</p>
 

	
 
<p>Traditionally, our community has relied exclusively on volunteers to take
 
  up this task, and financial investment only comes after volunteers have put
 
  in the unfunded work to make an MVP alternative firmware. While volunteer
 
  in the unfunded work to make an <acronym title="minimal viable product">MVP</acronym> alternative firmware. While volunteer
 
  involvement remains essential to the success of alternative firmware
 
  projects, we know from our fiscal sponsorship work that certain aspects of
 
  FOSS projects require an experienced charity to initiate and jump-start
 
  some of the less exciting aspects of FOSS project creation and
 
  development.</p>