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.

170 lines
9.0KB

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