Source files of fsfe.org, pdfreaders.org, freeyourandroid.org, ilovefs.org, drm.info, and test.fsfe.org. Contribute: https://fsfe.org/contribute/web/ https://fsfe.org

news-20110418-01.en.xhtml 2.0KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869
  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html newsdate="2011-04-18">
  3. <head>
  4. <title>FSFE responds to EC consultation on procurement</title>
  5. </head>
  6. <body>
  7. <h1>FSFE responds to EC consultation on procurement </h1>
  8. <p newsteaser="yes">Free Software Foundation Europe has
  9. provided the European Commission with <a href="/activities/policy/eu/20110418.ProcurementConsultation.FSFEresponse.html">input on modernising the
  10. way</a> in which public bodies buy software and related
  11. services.</p>
  12. <p>"Across Europe, the public sector has a huge role in the
  13. software market," says Karsten Gerloff, FSFE's President. "As
  14. the European Commission is revising the rules of procurement,
  15. we want to make sure that the new regulations and practices
  16. will be much fairer to Free Software than the current ones."
  17. </p>
  18. <p>
  19. In its response to the Commission's
  20. <a href="http://ec.europa.eu/internal_market/publicprocurement/modernising_rules/consultations/index_en.htm">consultation</a>,
  21. FSFE emphasises the following points:
  22. <ul>
  23. <li>When a public body contracts out software development, it should
  24. have the right to use, study, share and improve the resulting
  25. software. This is best achieved through a Free Software
  26. license.</li>
  27. <li>Public bodies should require new solutions to be based
  28. on <a href="/activities/os/def.en.html">Open
  29. Standards</a>.</li>
  30. <li>Competitive bidding should be the rule. Negotiated procedures
  31. (direct negotiations between a public body and a seller) should
  32. remain limited to exceptional cases.</li>
  33. <li>The rules should make clear that major software upgrades should
  34. be treated in the same way as new purchases, and re-tendered in a
  35. competitive process.</li>
  36. <li>Public bodies should figure future exit costs into the total
  37. cost of any new solution.</li>
  38. </ul>
  39. </p>
  40. </body>
  41. <tags>
  42. <tag>front-page</tag>
  43. <tag>EuropeanCommission</tag>
  44. <tag>OpenStandards</tag>
  45. <tag>Procurement</tag>
  46. <tag>Policy</tag>
  47. </tags>
  48. </html>
  49. <!--
  50. Local Variables: ***
  51. mode: xml ***
  52. End: ***
  53. -->