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
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

71 lines
2.1 KiB

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