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 @@
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 MVP 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 diff --git a/www/conservancy/static/copyleft-compliance/firmware-liberation.html b/www/conservancy/static/copyleft-compliance/firmware-liberation.html index 70bb440d0b121986dd08a46dbd01c1992619b5c8..0cb7ee711869dce0f451aa5837e66bbbac59165d 100644 --- a/www/conservancy/static/copyleft-compliance/firmware-liberation.html +++ b/www/conservancy/static/copyleft-compliance/firmware-liberation.html @@ -15,9 +15,9 @@ and improvement of the released software for users.
Simply enforcing the GPL is an important first step, and Conservancy continues our efforts in that - regard. However, We can + regard. However, we can replicate the - success found with OpenWRT only by a substantial + success found with OpenWrt only by a substantial effort after enforcement occurs to turn the compliant source release into a viable alternative firmware for the platform.
@@ -59,7 +59,7 @@ and improvement of the released software for users. of their own technology is a powerful proposition that has rarely been demonstrated. -When alternative firmware projects like OpenWRT exist for IoT devices, +
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.
@@ -96,7 +96,7 @@ and improvement of the released software for users. 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. @@ -105,7 +105,7 @@ and improvement of the released software for users.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.
Traditionally, our community has relied exclusively on volunteers to take @@ -118,7 +118,7 @@ and improvement of the released software for users.
creation and development. (In our last fiscal year, Conservancy funded 160 contributors to work on FOSS.) -In the initial phase of this grant, Conservancy will select a specific +
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.
@@ -164,6 +164,6 @@ and improvement of the released software for users.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.
+ be adroit in our approach to ensure success. {% endblock %}