Various typo fixes and wordsmith changes.
This commit is contained in:
parent
344d52ba63
commit
20a3b7757a
2 changed files with 12 additions and 12 deletions
|
@ -255,9 +255,9 @@
|
|||
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>
|
||||
|
||||
|
@ -275,7 +275,7 @@
|
|||
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
|
||||
|
@ -286,7 +286,7 @@
|
|||
|
||||
<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
|
||||
|
|
|
@ -15,9 +15,9 @@ and improvement of the released software for users.</p>
|
|||
|
||||
<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
|
||||
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
|
||||
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>
|
||||
|
||||
|
@ -59,7 +59,7 @@ and improvement of the released software for users.</p>
|
|||
of their own technology is a powerful proposition that has rarely been
|
||||
demonstrated.</p>
|
||||
|
||||
<p>When alternative firmware projects like OpenWRT exist for IoT devices,
|
||||
<p>When alternative firmware projects like OpenWrt exist for IoT devices,
|
||||
non-technical users can replace the software on their devices and benefit
|
||||
from custom, community-controlled software. Technical users are more likely
|
||||
to contribute knowing their efforts will be meaningful.</p>
|
||||
|
@ -96,7 +96,7 @@ and improvement of the released software for users.</p>
|
|||
yield increased responsiveness by violators throughout the industry. (A
|
||||
similar outcome occurred after our BusyBox-related litigation in 2006.)
|
||||
This expected change in behavior will open opportunities to replicate the
|
||||
OpenWRT approach in another embedded electronic subindustry. Fast action
|
||||
OpenWrt approach in another embedded electronic subindustry. Fast action
|
||||
will be necessary; most IoT products have an 18 month lifecycle, so we seek
|
||||
to quickly identify the right subindustry, gain compliance there, and move
|
||||
on to the next phase.</p>
|
||||
|
@ -105,7 +105,7 @@ and improvement of the released software for users.</p>
|
|||
|
||||
<p>While we’ve long hoped that volunteers would take up compliant sources
|
||||
obtained in our GPL enforcement efforts and build alternative firmware
|
||||
projects as they did with OpenWRT, history shows us that the creation of
|
||||
projects as they did with OpenWrt, 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
|
||||
|
@ -118,7 +118,7 @@ and improvement of the released software for users.</p>
|
|||
creation and development. (In our last fiscal year, Conservancy funded 160
|
||||
contributors to work on FOSS.)</p>
|
||||
|
||||
<p>In the initial phase of this grant, Conservancy will select a specific
|
||||
<p>In the initial phase, Conservancy will select a specific
|
||||
class of device. Upon achieving compliant source releases in that
|
||||
subindustry through GPL enforcement, Conservancy will launch an alternative
|
||||
firmware project for that class of device.</p>
|
||||
|
@ -164,6 +164,6 @@ and improvement of the released software for users.</p>
|
|||
<p>Finally, Conservancy will be prepared and willing to recognize temporary
|
||||
failure and setbacks in a particular subindustry and pivot quickly to
|
||||
choosing a different class of devices. This project is ambitious, and we’ll
|
||||
be adept in our approach to ensure success.</p>
|
||||
be adroit in our approach to ensure success.</p>
|
||||
|
||||
{% endblock %}
|
||||
|
|
Loading…
Reference in a new issue