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.

nl-201604.en.xhtml 7.2KB

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