uruguay.html (4731B)
1 <!--#include virtual="/server/header.html" --> 2 <!-- Parent-Version: 1.96 --> 3 <!-- This page is derived from /server/standards/boilerplate.html --> 4 <!--#set var="TAGS" value="essays upholding need" --> 5 <!--#set var="DISABLE_TOP_ADDENDUM" value="yes" --> 6 <title>Lesson from Uruguay - GNU Project - Free Software Foundation</title> 7 <!--#include virtual="/philosophy/po/uruguay.translist" --> 8 <!--#include virtual="/server/banner.html" --> 9 <!--#include virtual="/philosophy/ph-breadcrumb.html" --> 10 <!--GNUN: OUT-OF-DATE NOTICE--> 11 <!--#include virtual="/server/top-addendum.html" --> 12 <div class="article reduced-width"> 13 <h2>Lesson from Uruguay</h2> 14 15 <p> 16 <em>22 July 2013</em> 17 </p> 18 <p>A bill now under consideration in Uruguay showed the Free Software 19 Foundation an important point that was missing in our list of 20 recommended government policies to promote free software. 21 The bill says that when the state develops or contracts for 22 development of software, this software must be developable in 23 a 100%-free-software environment.</p> 24 25 <p>This requirement avoids problems that can really happen. Even if 26 the source code of the solution is delivered as free software, 27 and can run on a 100%-free-software GNU/Linux system, it could be 28 trapped in other ways.</p> 29 30 <p>For example, compiling its source code could require a nonfree program. 31 Even editing its source code could require a nonfree program. Both 32 of these problems can occur when a nonfree IDE is used, and this 33 would create additional obstacles to migrating the state to free software. 34 It is wise and proper for the law to reject these methods of developing 35 computing solutions for the state.</p> 36 37 <p>Taking this into consideration, the FSF has updated its recommendations 38 for government policies to suggest that contracts require that solutions 39 be developable in 100%-free-software environments. (See “<a 40 href="/philosophy/government-free-software.html">Measures Governments Can 41 Use to Promote Free Software</a>.”)</p> 42 </div> 43 44 </div><!-- for id="content", starts in the include above --> 45 <!--#include virtual="/server/footer.html" --> 46 <div id="footer" role="contentinfo"> 47 <div class="unprintable"> 48 49 <p>Please send general FSF & GNU inquiries to 50 <a href="mailto:gnu@gnu.org"><gnu@gnu.org></a>. 51 There are also <a href="/contact/">other ways to contact</a> 52 the FSF. Broken links and other corrections or suggestions can be sent 53 to <a href="mailto:webmasters@gnu.org"><webmasters@gnu.org></a>.</p> 54 55 <p><!-- TRANSLATORS: Ignore the original text in this paragraph, 56 replace it with the translation of these two: 57 58 We work hard and do our best to provide accurate, good quality 59 translations. However, we are not exempt from imperfection. 60 Please send your comments and general suggestions in this regard 61 to <a href="mailto:web-translators@gnu.org"> 62 <web-translators@gnu.org></a>.</p> 63 64 <p>For information on coordinating and contributing translations of 65 our web pages, see <a 66 href="/server/standards/README.translations.html">Translations 67 README</a>. --> 68 Please see the <a 69 href="/server/standards/README.translations.html">Translations 70 README</a> for information on coordinating and contributing translations 71 of this article.</p> 72 </div> 73 74 <!-- Regarding copyright, in general, standalone pages (as opposed to 75 files generated as part of manuals) on the GNU web server should 76 be under CC BY-ND 4.0. Please do NOT change or remove this 77 without talking with the webmasters or licensing team first. 78 Please make sure the copyright date is consistent with the 79 document. For web pages, it is ok to list just the latest year the 80 document was modified, or published. 81 82 If you wish to list earlier years, that is ok too. 83 Either "2001, 2002, 2003" or "2001-2003" are ok for specifying 84 years, as long as each year in the range is in fact a copyrightable 85 year, i.e., a year in which the document was published (including 86 being publicly visible on the web or in a revision control system). 87 88 There is more detail about copyright years in the GNU Maintainers 89 Information document, www.gnu.org/prep/maintain. --> 90 91 <p>Copyright © 2013, 2021 Free Software Foundation, Inc.</p> 92 93 <p>This page is licensed under a <a rel="license" 94 href="http://creativecommons.org/licenses/by-nd/4.0/">Creative 95 Commons Attribution-NoDerivatives 4.0 International License</a>.</p> 96 97 <!--#include virtual="/server/bottom-notes.html" --> 98 99 <p class="unprintable">Updated: 100 <!-- timestamp start --> 101 $Date: 2021/10/01 17:02:54 $ 102 <!-- timestamp end --> 103 </p> 104 </div> 105 </div><!-- for class="inner", starts in the banner include --> 106 </body> 107 </html>