Source files of,,,,, and Contribute:
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.

133 lines
6.4 KiB

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <html newsdate="2017-02-14">
  3. <head>
  4. <title>European Free Software Policy Meeting 2017</title>
  5. </head>
  6. <body>
  7. <h1>European Free Software Policy Meeting 2017</h1>
  8. <p newsteaser="yes">Building on the experience from last year's <a href="">successful
  9. pre-FOSDEM meeting</a>, the <a href="">Free
  10. Software Foundation Europe</a> and <a href="">OpenForum Europe</a> recently
  11. continued the tradition of bringing together active Free Software groups
  12. a day before the FOSDEM event, in order to discuss public policy related
  13. actions at both the EU and the national levels. This year, the meeting
  14. focused on encouraging exchanges of views between individual citizens
  15. and decision-makers, by providing practical first-hand information on topics
  16. relating to Free Software in public policy.</p>
  17. <p>The session started with Sebastian Raible (parliamentary assistant to
  18. Julia Reda (a Member of the European Parliament)), who gave a <a href="">presentation
  19. about Free Software developments from the perspective of the European Parliament</a>. He explained
  20. the progress of the <a href="">Free and Open Source Software Audit (or FOSSA) programme</a>, which
  21. was extended for another three years at the end of 2016, and explained
  22. that one of the main changes to the programme is that now it includes a
  23. new “bug bounty” incentive scheme, rewarding the discovery and reporting
  24. of new software bugs. Participants highlighted their concerns over the
  25. methodology of FOSSA, and the need to focus on its aim, namely, support
  26. for the security of the Free Software projects.</p>
  27. <p>Next, Pierre Damas (Head of Sector, Digital Services at the Directorate
  28. General of Information Technologies of the European Commission) shared
  29. with the group some of the <a href="">Commission's plans</a> for
  30. updating its <a href="">Open Source Software Strategy</a>, identifying
  31. the key barriers and motivations for adopting it in practice. According
  32. to Pierre Damas, although within the Commission Free Software is technically now
  33. treated equally with its proprietary counterparts, there remains a lack
  34. of political will to back up the mainstream adoption of Free Software technologies
  35. within the EU institutions. According to him, the next step for the updated
  36. Open Source Strategy in the Commission is the "digital transformation" of
  37. areas such as "cloud", big data, and the "Internet of Things".</p>
  38. <div class="captioned left" style="max-width: 650px; width: 53%">
  39. <a href="/graphics/2017-policy-meeting.jpg">
  40. <img src="/graphics/2017-policy-meeting.jpg" alt="Policy meeting" width="100%"/>
  41. </a>
  42. </div>
  43. <p>Jaana Sahk-Labi (from the Estonian Permanent Representation to the EU) <a href="">presented
  44. Estonia's national framework for supporting the implementation of Free Software</a>. Estonia is
  45. considered to be the leader in e-Government at the EU level, and is planning
  46. to highlight e-Government topics during its presidency of the Council of
  47. the EU, in the second half of 2017. One of the main challenges for the
  48. Estonian government in the upcoming presidency will be the right approach
  49. for future-proofing "no legacy" policies that continue after the term of
  50. Estonia's presidency has come to an end. Consequently, Estonia is preaching
  51. for a digital revolution in the EU institutions.</p>
  52. <p>Laurent Joubert (from the French government) <a href="">presented
  53. the Open Source Contribution Policy Template</a> which has been drafted
  54. by numerous representatives from governments, non-governmental
  55. organisations, companies, international organisations and academic sector
  56. as a part of the <a href="">Open
  57. Government Partnership</a>. The aim of this template is to provide an easily
  58. shareable and ready-to-use template for governments – as well as other
  59. public administrations - to set up a policy for code contributions made
  60. by civil servants, which have to be open by default. The ultimate goal of
  61. such a policy is to facilitate, share and reuse the code developed by and
  62. for public administrations.</p>
  63. <p>The speakers' presentations were followed by a round table discussion, engaging
  64. the participants in considering the possibility creating a dashboard, which
  65. would serve as a tool for advocacy groups to assess best practices and
  66. policies for supporting Free Software and Open Standards (OS) in Member States. Part
  67. of the discussion was dedicated to finding ways to evaluate the existing
  68. national or regional policies which support Free Software. A couple of identified
  69. indicators of "openness" were: the level of Free Software usage; and the fact of
  70. using global analytics of online procedures. In addition, certain other
  71. criteria will also need to be taken into account: transparency of how Free Software
  72. is adopted in the public sector; the implementation of the policy in practice; and
  73. product maturity. The participants agreed to start working on listing the
  74. parameters which would describe "best behaviour" on the part of government, with
  75. a view to developing concrete steps or actions to support governments to
  76. achieve this.</p>
  77. <p>The meeting was a stepping-stone, paving the way for a bigger collaboration
  78. on how to promote public policies supporting Free Software across Europe. We hope to continue
  79. the collaboration and to coordinate our actions in order to collectively
  80. make a difference on the policy level.</p>
  81. </body>
  82. <tags>
  83. <tag>front-page</tag>
  84. <tag content="Policy">Policy</tag>
  85. <tag content="Open Standards">Open Standards</tag>
  86. <tag content="European Commission">European Commission</tag>
  87. <tag contet="European Parliament">European Parliament</tag>
  88. <tag content="Public Administration">publicadministration</tag>
  89. </tags>
  90. <author id="malaja"/>
  91. </html>