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.

118 lines
6.2KB

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <html newsdate="2018-02-15">
  3. <version>1</version>
  4. <head>
  5. <title>European Free Software Policy Meeting 2018: more joint activities important for Free Software in Europe</title>
  6. </head>
  7. <body>
  8. <h1>European Free Software Policy Meeting 2018: more joint activities important for Free Software in Europe</h1>
  9. <p>
  10. Following the <a href="/news/2017/news-20170214-02.html">well-established tradition</a>
  11. of gathering active Free Software groups before FOSDEM kicks off, the
  12. FSFE once again partnered up with <a href="http://www.openforumeurope.org/">OpenForum Europe</a>
  13. for the third edition of European Free Software Policy Meeting in Brussels,
  14. the heart of European decision-making.</p>
  15. <div class="captioned" style="width:80%; margin: 1.5em auto;">
  16. <img src="graphics/pmpc-eu-foss.jpg" />
  17. </div>
  18. <p>This time the purpose of the meeting was to shed light on topics important
  19. for Free Software in public policy all over Europe, not only within the
  20. European Union; and to exchange experience for any policy action within
  21. different regions in case similar concerns for Free Software pop up. Practice
  22. shows that they often do, and this is why it is important to be informed
  23. about similar actions in other parts of Europe, in order to be able to
  24. address corresponding concerns in a timely and effective manner.</p>
  25. <p>17 different groups were represented at the European Free Software Policy
  26. Meeting 2018: from national Free Software groups to public sector representatives,
  27. and international organisations. Our participants deemed to be a diverse
  28. group, yet similar in the challenges we face on both national and European
  29. level.</p>
  30. <h2>Common challenges for Free Software in Europe and beyond</h2>
  31. <p><strong>EU Copyright reform</strong>: Article 13 of the current copyright
  32. directive proposal <a href="https://savecodeshare.eu/">can seriously hamper</a>
  33. collaborative software development, and especially Free Software, imposing
  34. the use of mandatory upload filters, and illegal monitoring of their users.
  35. As a result of this proposal code repositories can be arbitrarily removed online.
  36. The directive proposal is currently being discussed by co-legislators in
  37. the European Parliament and the Council of the European Union, which both
  38. are struggling to reach an agreement on <a href="/news/2017/news-20171130-01.html">controversial</a>
  39. Article 13. Action within the Member States to "#savecodeshare" is needed
  40. more than ever, in order to make sure that decision-makers understand the
  41. repercussions of Article 13 for Free Software.</p>
  42. <p><strong>Software patents</strong>: while the EU legislation to
  43. impose patents on software was rejected back in 2005, patentability of
  44. software insinuates itself into policy discussions through other means.
  45. In particular, the Unitary Patent Court Agreement (UPCA) may in practice
  46. impose the patentability of software in the EU. By now 15 Member States
  47. have ratified the UPCA, without such Member States as post-Brexit UK and
  48. Germany whose support is necessary in order for the Unitary Patent Court
  49. system to start to function. A <a href="http://www.nounitarysoftwarepatents.uk/">petition</a>
  50. against UPCA ratification was run in the UK, however, there is a need for
  51. remaining Member States to be aware of the practical ramifications of UPCA
  52. for innovation and especially software business in Europe.</p>
  53. <p><strong>Open Standards</strong>: standardisation policies are still
  54. being infiltrated by closed standards <a href="/activities/os/msooxml.html">disguised as "open"</a>,
  55. and tricky patent licensing practices that are only called "fair, reasonable and non-discriminatory"
  56. (<a href="/activities/os/why-frand-is-bad-for-free-software.html">FRAND</a>)
  57. in the name of greater innovation. In fact, these practices only dilute
  58. the discourse. It is time the term <a href="/activities/os/os.en.html>">"open standards"</a>
  59. is used in accordance with the Free Software definition defined through
  60. <a href="/about/basics/freesoftware.html">4 freedoms</a>,
  61. and appropriate Free Software licences as approved by
  62. <a href="https://www.gnu.org/licenses/license-list.html">Free Software Foundation</a>
  63. and <a href="https://opensource.org/licenses/alphabetical">Open Source Initiative</a>.
  64. Otherwise, we will continue facing misconceptions about (un)equal treatment
  65. of Free Software in public procurement, where Free Software can be de facto
  66. excluded as a result of policies prescribing business models.</p>
  67. <p><strong>Public Money, Public Code</strong>: "All publicly funded
  68. newly-established software should be made publicly available under Free
  69. Software licence". This is the <a href="https://publiccode.eu/">demand</a>
  70. that the FSFE together with ca 116 other organisations and Free Software
  71. projects, as well as more than 16 000 individuals are asking from politicians.
  72. The campaign is aimed at gathering evidence about public expenditure on
  73. software and other IT services in public sector, to provide information that is
  74. easily understandable for decision-makers, and to equip Free Software activists
  75. all over the world with tools to <a href="/campaigns/elections/index.html">ask their politicians</a>
  76. during national elections to make sure that software paid with taxpayers money
  77. is made freely available to the public.</p>
  78. <h2>Ways to move forward</h2>
  79. <p>The meeting once again proved that there is a need to continuously
  80. exchange ideas, update each other on concerns and victories for Free Software,
  81. and experience we gather while pursuing our mutual goals to maintain the
  82. ecosystem for Free Software to flourish. More collaboration and staying
  83. informed is necessary in order to establish the "smart network" of Free
  84. Software activists all over Europe and beyond, where more joint activities
  85. can take place. We will continue to build on that resource to share information,
  86. and update each other on activities crucial for Free Software, and to
  87. establish meaningful collaborations to address common challenges for Free
  88. Software.</p>
  89. </body>
  90. <tags>
  91. <tag key="policy">Policy</tag>
  92. <tag key="pmpc">Public Code</tag>
  93. <tag key="openstandards">Open Standards</tag>
  94. <tag key="publicadministration">Public Administration</tag>
  95. <tag key="front-page"/>
  96. </tags>
  97. <author id="malaja" />
  98. </html>