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.

  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html newsdate="2016-05-02" type="newsletter">
  3. <head>
  4. <title>FSFE Newsletter - May 2016</title>
  5. </head>
  6. <body class="newsletter article" microformats="h-entry" id="nl-201605">
  7. <h1 class="p-name">FSFE Newsletter - May 2016</h1>
  8. <h2 id="eu-jeopardises-its-goals-in-standardisation-with-frand-licensing">EU
  9. jeopardises its goals in standardisation with FRAND licensing</h2>
  10. <p newsteaser="yes">As a part of the Digital Single Market strategy, the European Commission
  11. has <a href="">published
  12. the communication on ICT standardisation priorities</a> as one of the
  13. key factors in the digital economy. FSFE welcomes the overall approach
  14. taken in the communication in favour of more open standards and a greater
  15. inclusion of Free Software communities into standardisation processes.</p>
  16. <p>However, the document lacks proper understanding of licensing conditions
  17. of standard-essential patents in order to include Free Software into
  18. standard setting processes. In particular, FSFE <a href="">expresses
  19. its concerns in regard to the promotion of so-called "fair, reasonable,
  20. and non-discriminatory (FRAND) licensing terms</a> that in practice are
  21. incompatible with Free Software. This way, the document jeopardises every
  22. effort set by the European Commission to integrate Free Software communities
  23. into standardisation.</p>
  24. <h2 id="european-commission-vs-google-android">European Commission vs Google Android</h2>
  25. <p>On April 20, the European Commission
  26. <a href="">outlined
  27. its charges in regard to Google's business practices relating to the
  28. Android operating system</a>. According to the Commission, Google is
  29. abusing its dominant market position by pre-installing and setting Google
  30. Search, Google Play Store and Google Chrome as the default on most Android
  31. devices sold in Europe. These practices close off ways for competitive
  32. search engines to access the market.</p>
  33. <p>FSFE has previously <a href="">raised
  34. its concerns in regard to the claim against the free-of-charge distribution
  35. of Android</a> that had been raised to the European Commission by a
  36. coalition of certain online service providers who claimed that this practice
  37. is harmful to competition. We argued against that claim as it undermines
  38. the whole essence of Free Software licensing, and are pleased to see that
  39. the Commission disregarded that claim in its antitrust case against Google.</p>
  40. <h2 id="from-the-community">From the community</h2>
  41. <ul>
  42. <li><p>Guido Arnold, our education team coordinator, summarised legal
  43. aspects and possible activities to take, when <a href="">public schools make MS Office mandatory.</a></p></li>
  44. <li><p>Vitaly Repin <a href="">published
  45. the course by Richard Stallman "On the Road to the Free Digital Society"
  46. in Moodle Backup and IMS Common Cartridge formats</a>, and invites everyone
  47. to give feedback and promote the course through their channels.</p></li>
  48. <li><p>Since Let’s Encrypt has left beta testing, Michal Nazarewicz <a href="">uses and promotes this new certificate
  49. authority which provides free TLS certificates</a>: "If you're running
  50. your own server there's no excuse not to use TLS".</p></li>
  51. <li><p>Björn Schießle <a href="">blogs about a self hostable application for saving web pages, "Wallabag",
  52. and about its maintenance on a shared web hosting service</a>.</p></li>
  53. <li><p>Marcus Moeller explains how to <a href="">set up a Freedombox on a Beagle Bone Black in order to self-host a blog
  54. on freely designed hardware and without the need to use proprietary
  55. software</a>.</p></li>
  56. </ul>
  57. <h2 id="what-else-have-we-done">What else have we done?</h2>
  58. <ul>
  59. <li><p>We ran the eighth annual election for a Fellowship
  60. representative who is to represent our community and the FSFE's Fellowship
  61. in <a href="">FSFE's
  62. general assembly</a>. Although we only had one candidate, we would like to
  63. <a href="">thank
  64. and congratulate Mirko Boehm to run for the office and being elected</a>.</p></li>
  65. <li><p>We now have over 30 organisations and companies who joined us in
  66. proposing measures to EU institutions and EU member states to avoid negative
  67. implications on users' rights and Free Software imposed by the
  68. <a href="">EU
  69. Radio Equipment Directive 2014/53/EU, aka 'Radio Lockdown Directive'</a>.
  70. The joint statement is open to new signatures against negative implications
  71. that the 'Radio Lockdown Directive' poses on software freedom, users'
  72. rights, fair competition, innovation, environment, and volunteering.</p></li>
  73. <li><p>FSFE also joined a coalition of organisations that fight the
  74. negative implementations of the 'Radio Lockdown Directive' in France.
  75. Together, we signed <a href="">an
  76. open letter to the French government and French Telecommunications Regulatory
  77. Authority (ART)</a> to ensure that the implementation of the 'Radio Lockdown
  78. Directive' in France will not harm Free Software.</p></li>
  79. <li><p>On our way to become more transparent and inclusive, we published
  80. our <a href="">transparency
  81. commitment</a> in line with the guidelines from Transparency International Germany.</p></li>
  82. <li><p>A lot of our initial structure and founding documents have not
  83. been updated ever since the FSFE grew from being a small circle of volunteers
  84. into an organisation with hired staff, with a Fellowship program and a
  85. community of thousands of people. We now begun to <a href="">revise
  86. our "Self Conception"</a>, to better reflect our grown decision-making process.
  87. Jonas Öberg, FSFE's executive director, shared his thoughts on and insights
  88. about <a href="">potential future steps
  89. to FSFE's structure and membership</a> on his blog.</p></li>
  90. <li><p><a href="">On the backend of our
  91. work, we have introduced a ticket system built on OTRS</a>. Although at
  92. first sight not many people seem to be directly affected by this, our whole
  93. communication will profit over time from higher control of our workflow.
  94. Also, it shall be opened to be used by volunteers as well.</p></li>
  95. <li><p>From 13 - 15 April, FSFE's annual legal licensing workshop LLW
  96. took place in Barcelona, Spain. The event is dedicated to gather legal
  97. practitioners from all over the world to dicuss the most challenging issues
  98. in and around Free Software licensing. This year it had a record number
  99. of participants, showing the increasing interest and importance of Free
  100. Software in software licensing.</p></li>
  101. </ul>
  102. <h2 id="take-action">Take Action</h2>
  103. <p>From 2 - 4 September, 2016, the first summit of FSFE will take place,
  104. an event dedicated to our community. To make it a unique and appealing
  105. experience for everyone, we sent out a <a href="">Call
  106. for Participation</a> last week to all our Fellows and on our mailing lists.
  107. Take your chance and be part of FSFE's main event in 2016 by becoming a
  108. speaker or a volunteer, by hosting a workshop or another event.</p>
  109. <h2 id="good-free-software-news">Good Free Software news</h2>
  110. <p>Spain's Ministry of Finance and Public Administrations <a href="">published
  111. its web-based solution for archiving electronic files under a Free Software
  112. license</a>. France is also not lagging behind and recently
  113. <a href="">published
  114. the source code of the fiscal calculator used by the French fiscal
  115. administration to calculate the income taxes of individuals in France</a>.
  116. This was an outcome of the legal case in Paris' administrative court that
  117. concluded that a source code of a software written by and for public
  118. authorities can be considered as a public information that can be freely
  119. accessed.</p>
  120. <p>Thanks to all the
  121. <a href="/contribute/contribute.html">volunteers</a>
  122. ,
  123. <a href="">Fellows</a>
  124. and
  125. <a href="/donate/thankgnus.html">corporate donors</a>
  126. who enable our work,</p>
  127. <p>your editors Polina Malaja and Erik Albers, <a href="/index.html">FSFE</a></p>
  128. </body>
  129. <sidebar promo="about-fsfe"/>
  130. <date>
  131. <original content="2016-05-02"/>
  132. </date>
  133. <followup>donate</followup>
  134. <tags>
  135. <tag>newsletter</tag>
  136. </tags>
  137. </html>