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.

135 lines
6.3 KiB

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