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.

134 lines
7.1KB

  1. <?xml version="1.0" encoding="UTF-8" ?>
  2. <html newsdate="2016-04-01" type="newsletter">
  3. <version>1</version>
  4. <head>
  5. <title>FSFE Newsletter - April 2016</title>
  6. </head>
  7. <body microformats="h-entry">
  8. <h1 class="p-name">FSFE Newsletter - April 2016</h1>
  9. <h2 id="eu-radio-directive-threatens-software-freedom">EU Radio Directive
  10. threatens software freedom</h2>
  11. <p>We published our position on the Radio Equipment Directive 2014/53/EU
  12. (adopted in May 2014) that demands from device manufacturers to check each
  13. device software's compliance. At first sight, this may sound reasonable
  14. but it has highly negative implications on user rights and Free Software,
  15. fair competition, innovation, environment, and volunteering – mostly
  16. without large benefits for security. The directive needs to be implemented
  17. in member states before 13 June 2016. We have <a href="/activities/radiodirective/">formulated several proposals
  18. to EU institutions and EU member states with concrete steps to solve
  19. these issues.</a></p>
  20. <h2 id="us-government-demands-publicly-financed-software-to-be-published-as-free-software">US government demands publicly financed software to be published as Free Software</h2>
  21. <p>As one of our main goals for 2016 is to push for the demand of
  22. all publicly funded software to be published as Free Software in the EU,
  23. we are positive to see some concrete steps in this direction happening
  24. across the Atlantic. In particular, in the beginning of March, the US
  25. Government published a <a href="https://sourcecode.cio.gov/SourceCodePolicy.pdf">draft
  26. of Source Code Policy</a> for the public to comment upon until 11 April.
  27. The policy <a href="https://k7r.eu/us-government-commits-to-publish-publicly-financed-software-under-free-software-licenses/">requires every public agency to publish their custom-build
  28. software as Free Software for other public agencies as well as for the
  29. general public to use, study, share and improve the software.</a></p>
  30. <p>We would like the EU to follow this example and come up with similar
  31. policies on the European level. If you have any feedback or comments in
  32. regard to the US Source Code Policy, please send them to <a href="https://lists.fsfe.org/mailman/listinfo/discussion">our English
  33. discussion list</a> or directly to Matthias Kirschner. We would like to
  34. make sure to consider your feedback before talking with European
  35. politicians about this topic.</p>
  36. <h2 id="from-the-community">From the community</h2>
  37. <ul>
  38. <li><p>Björn Schiessle <a href="http://blog.schiessle.org/2016/03/14/federated-sharing-whats-new-in-owncloud-9-0/">blogged about the new feature of the ownCloud 9.0 the Federation App</a> that
  39. allows users to exchange their Federated Cloud ID-s and share data
  40. between their "clouds" more easily.</p></li>
  41. <li><p>Sergey Matveev
  42. <a href="https://blogs.fsfe.org/stargrave/archives/158">summarised the GoVPN
  43. Free Software daemon: why it was born, which tasks it is aimed to solve,
  44. and its technical overview</a> in his blogpost.</p></li>
  45. <li><p>Guido Arnold <a href="https://blogs.fsfe.org/guido/2016/03/fsfe-meeting-in-frankfurt-with-talk-about-free-software-licenses/">wrote about the Fellowship meeting in Frankfurt which also included
  46. a talk about Free Software licenses by Michael Stehmann</a>.</p></li>
  47. <li><p>Guido Günther <a href="http://honk.sigxcpu.org/con/Contatacs__CardDAV__Calypso_and_the_N900.html">posted
  48. a follow-up to calendar synchronisation with Calypso, syncEvolution and
  49. the N900 running Maemo</a>.</p></li>
  50. </ul>
  51. <h2 id="what-else-have-we-done">What else have we done?</h2>
  52. <ul>
  53. <li><p>Founding member of FSFE, <a href="http://www.fsf.org/news/library-freedom-project-and-werner-koch-are-2015-free-software-awards-winners">Werner Koch received this year's Free Software award for
  54. the Advancement of Free Software for his GnuPG project</a>. The Award for
  55. the Advancement of Free Software is given annually to an individual who has
  56. made a great contribution to the progress and development of Free Software.</p></li>
  57. <li><p>Our <a href="https://k7r.eu/chemnitzer-linuxtage-misunderstandings-compulsory-routers-and-new-black-nocloud-t-shirts/">president Matthias Kirschner and the German coordinator Max
  58. Mehl gave talks at Chemnitzer Linuxtage</a>. The event was a success with
  59. most of our merchandise and promotional material disappearing quickly
  60. from the booth handled by Reinhard Müller, Katja Müller, Max Mehl and
  61. Fabian Keil.</p></li>
  62. <li><p>Our volunteers in Berlin participated in the <a href="http://www.fsf.org/news/anti-drm-activists-go-to-w3c-meeting-to-protest-digital-restrictions-management-in-web-standards">FSF campaign against digital restrictions
  63. proposed by W3C in the web HTML standard</a>. Digital restrictions in Web
  64. standards would make it easier and more politically acceptable to impose
  65. restrictions on users.</p></li>
  66. <li><p>FSFE was present with a booth at <a href="https://logancij.com/">CIJ
  67. Logan Symposium</a>, a conference dedicated to gather leading journalists,
  68. hacktivists, legal and security experts to discuss freedom of press and
  69. digital rights. The list of the speakers at the CIJ event included Edward
  70. Snowden, who also <a href="http://www.fsf.org/blogs/community/recapping-day-zero-of-libreplanet-2016">gave
  71. a keynote at Libreplanet</a>, a Free Software conference organised by FSF.</p></li>
  72. </ul>
  73. <h2 id="take-action">Take Action</h2>
  74. <p>To all awesome translators out there! Help us to expand our outreach
  75. by updating the <a href="/contribute/spreadtheword.en.html">'Spread
  76. the Word' page</a> for ordering our promotional material into your
  77. language. Currently, the page exists in English, German, Dutch and
  78. Albanian but it would be great to include any other languages into this
  79. list too.</p>
  80. <h2 id="good-free-software-news">Good Free Software news</h2>
  81. <p><a href="http://sflc.in/press-release-indian-patent-office-says-no-to-software-patents/">Indian Patent Office said no to software patents</a> in its updated
  82. guidelines that clearly state that any patent claim that lies only in
  83. software will not be permitted under Indian patent law. Poland's new
  84. <a href="https://joinup.ec.europa.eu/community/osor/news/polish-egovernment-strategy-advocates-open-source">eGovernment strategy recommends that publicly financed software for
  85. a new system of public registers should be considered to be published
  86. under a Free Software licence</a>. Sweden has <a href="https://joinup.ec.europa.eu/community/osor/news/sweden-updates-list-mandatory-it-standards">updated the list of 'Open IT standards' that can be made mandatory when
  87. procuring software and related services</a>. To make it to the list IT
  88. standards must be developed openly and publicly, must not constrain
  89. reuse of the standard, and standard-essential patents should be made
  90. freely available.</p>
  91. <p>Thanks to all the
  92. <a href="/contribute/contribute.html">volunteers</a>
  93. ,
  94. <a href="https://my.fsfe.org/donate">Fellows</a>
  95. and
  96. <a href="/donate/thankgnus.html">corporate donors</a>
  97. who enable our work,</p>
  98. <p>your editors Polina Malaja and Jonas Öberg, <a href="/index.html">FSFE</a></p>
  99. </body>
  100. <sidebar promo="about-fsfe"/>
  101. <date>
  102. <original content="2016-04-01"/>
  103. </date>
  104. <followup>donate</followup>
  105. <tags>
  106. <tag key="newsletter"/>
  107. </tags>
  108. </html>