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.
 
 
 
 
 
 

190 lines
11 KiB

  1. <html newsdate="2016-07-12" type="newsletter">
  2. <version>1</version>
  3. <head>
  4. <title>FSFE Newsletter - July 2016</title>
  5. </head>
  6. <body microformats="h-entry">
  7. <h1 class="p-name">FSFE Newsletter - July 2016</h1>
  8. <h2 id="eif-v.-3-the-eu-hampers-its-own-goal-to-promote-better-interoperability-with-harmful-licensing-terms">EIF v. 3:
  9. the EU hampers its own goal to promote better interoperability with harmful licensing terms</h2>
  10. <p>The FSFE provided the European Commission with <a href="/news/2016/news-20160624-01.en.html">our
  11. input in regard to the ongoing revision of the European Interoperability
  12. Framework</a> (EIF). The EIF aims to promote enhanced interoperability in
  13. the EU public sector, and is currently going through its third revision
  14. since 2004. Whilst <a href="https://ec.europa.eu/eusurvey/files/57b2ecd5-effa-4594-9ef2-47e7ecc67047">the draft version</a> gives preference to Open Standards in delivering public services, it also
  15. promotes harmful FRAND (so-called "fair, reasonable and non-discriminatory")
  16. licensing terms for standards. In practice, these are
  17. <a href="/freesoftware/standards/why-frand-is-bad-for-free-software.en.html">highly anti-competitive and unfit</a>
  18. not only for Free Software but for the whole software sector in general.
  19. In addition, the draft also ignores the proven relationship between
  20. interoperability and Free Software: many national frameworks explicitly
  21. <a href="https://wiki.fsfe.org/Migrated/EU%20Policies%20overview%3A%20Free%20Software%20and%20Open%20Standards">require
  22. their national services to be based on Free Software</a>. We
  23. <a href="/freesoftware/standards/eif-v3.en.html">asked the European
  24. Commission to address these and other shortcomings and ensure interoperability
  25. in an efficient way.</a></p>
  26. <h2 id="fsfe-summit---registration-open-and-how-to-attend">FSFE summit - Registration open and how to attend</h2>
  27. <p>From September 2nd to 4th we will be holding the first ever FSFE summit.
  28. This is <a href="/community/events/2016/summit/frontpage">the
  29. main event to bring together FSFE members and supporters from all over Europe</a>.
  30. In the last weeks our amazing team behind the FSFE summit invested their
  31. online time, coffee breaks and even their daydreams to offer you an event
  32. that is worthy of your visit and worthy of being the official celebration of
  33. 15 years of FSFE. The event is pan-European, organised for the community,
  34. includes old stagers and newcomers, and takes place in the heart of Berlin.
  35. Every day there is a new theme, built on talks about technology,
  36. freedom and society. And last but not least, there will be social events in the evening
  37. that give the opportunity to meet up, share ideas and plan new activities.</p>
  38. <p><a href="/community/events/2016/summit/attendance">Registration for the first FSFE summit is now officially open</a>. Additionally,
  39. on the very same page you find valuable information about the questions
  40. you might have about attendance. Better be quick as tickets will be "sold out"
  41. soon!</p>
  42. <p>Please be aware that our summit team is still working hard to shape an
  43. inspiring and balanced community program for you and it will be finally
  44. announced in the next weeks.</p>
  45. <h2 id="from-the-community">From the community</h2>
  46. <ul>
  47. <li><p>Given the latest news about implemented encryption in popular chat
  48. applications, <a href="https://blogs.fsfe.org/h2/2016/05/31/why-privacy-is-more-than-crypto/">Hannes Hauswedell
  49. discusses the important aspects of privacy in communication</a>, and gives
  50. some examples of current applications and ongoing projects that respect
  51. privacy on different levels. Beyond encryption, says Hannes, our privacy is
  52. in need of Free Software, device integrity and federated networks.
  53. <a href="https://framablog.org/2016/06/27/le-chiffrement-ne-suffira-pas/">Framasoft has translated this blogpost into French</a>.</p></li>
  54. <li><p>Björn Schießle blogs about the
  55. <a href="http://blog.schiessle.org/2016/07/04/history-and-future-of-cloud-federation/">History
  56. and Future of Cloud Federation</a> where he explains the concept of server-to-server
  57. sharing in Owncloud/Nextcloud and its development to a "federated cloud ID",
  58. which looks similar to an email address. Like email, "federated cloud" refers
  59. to a user on a specific server.</p></li>
  60. <li><p>GA member Torsten Grote
  61. <a href="https://blog.grobox.de/2016/the-proprietarization-of-android-google-play-services-and-apps/">writes
  62. about the ongoing proprietarisation of Android</a> and how this effectively
  63. cripples other versions of Android and makes them increasingly useless.
  64. Torsten also argues that even crippled Android versions are still an important
  65. fundament for communities to increase the people's freedom.</p></li>
  66. <li><p>Daniel Pocock writes about <a href="https://danielpocock.com/webrtc-sip-xmpp-projects-gsoc-2016">WebRTC
  67. and communications projects as part of Google Summer of Code, under the
  68. umbrella of the Debian Project</a>. His overview includes WebRTC plugins
  69. for popular CMS and web frameworks, truly peer-to-peer alternatives, and the GNU/Linux Desktop Telepathy framework.</p></li>
  70. <li><p>Erik Albers writes how EU ministers recently missed the chance to
  71. set Free Software as an integral part of their Open Access strategy and
  72. why <a href="http://blog.3rik.cc/2016/06/there-is-no-open-science-without-the-use-of-open-standards-and-free-software/">there
  73. is no Open Science without the use of open standards and Free Software</a>.</p></li>
  74. <li><p>Björn Schießle writes about
  75. <a href="http://blog.schiessle.org/2016/06/15/freedom-for-whom/">Freedom for whom</a>
  76. where he shares his thoughts about the harm which the Contributor License Agreement
  77. (CLA) causes to Free Software communities and how businesses and communities can
  78. benefit from developing complete Free Software solutions.</p></li>
  79. </ul>
  80. <h2 id="what-else-have-we-done">What else have we done?</h2>
  81. <ul>
  82. <li><p>Erik Albers, head of the Team summit, blogged on several occasions
  83. this month to share the ongoing process of organising the first ever
  84. FSFE summit. He shared insights about the
  85. <a href="http://blog.3rik.cc/2016/05/fsfe-summit-about-logo-and-pr/">PR/Logo</a>,
  86. <a href="http://blog.3rik.cc/2016/06/fsfesummit-some-updates-and-introducing-our-committee/">the summit committee</a>
  87. and <a href="http://blog.3rik.cc/2016/07/fsfesummit-registration-open/">the
  88. registration and the team behind it</a>.</p></li>
  89. <li><p>FSFE supported the creation of the
  90. <a href="/news/2016/news-20160630-01">Software Heritage
  91. initiative, an archive of Free Software code</a>. It collects programs,
  92. applications and snippets of code distributed under free licenses from a
  93. wide variety of active and defunct sources with the aim of protecting code
  94. from sinking into oblivion.</p></li>
  95. <li><p>We once had the idea of creating national chapters of the
  96. FSFE, but it turned out to be unnecessary. Matthias Kirschner now states that
  97. the <a href="https://k7r.eu/fsfe-chapter-germany-ev-officially-dissolved/">FSFE
  98. Chapter Germany e.V. has been officially dissolved</a>.</p></li>
  99. <li><p>The FSFE sent its concerns to the Vice President of the Digital
  100. Single Market Andrus Ansip, the Commissioners Elżbieta Bieńkowska, Günther
  101. Oettinger, and Margrethe Vestager in regard to
  102. <a href="/freesoftware/standards/why-frand-is-bad-for-free-software.en.html">harmful
  103. FRAND licensing terms</a> in the EU's standardisation plans.</p></li>
  104. <li><p>We joined the initiative "transparent civil society" that is now
  105. reflected in a new section in our <a href="/about/about.en.html">About Page</a>.
  106. <a href="/about/transparency-commitment.en.html">Our Transparency Commitment</a>
  107. lists all information necessary to be part of the initiative.</p></li>
  108. <li><p>FSFE Austria represented the FSFE with a booth at <a href="https://blog.widerstroem.com/weblog/6/veganmania-2016-in-wien">Veganmania 2016 in Vienna</a> (DE),
  109. at <a href="https://blog.widerstroem.com/weblog/7/fair-planet-2016-in-linz">Fair
  110. Planet 2016 in Linz</a> (DE) and at <a href="https://blog.widerstroem.com/weblog/8/linuxwochen-linz-2016">Linuxwochen
  111. Linz 2016</a>.</p></li>
  112. <li><p>FSFE's vice president, Alessandro Rubini, helped to organise the
  113. Italian Free Software Conference Confsl 2016 and
  114. <a href="https://blogs.fsfe.org/rubini/2016/06/29/confsl-2016-the-italian-free-software-conference/">represented
  115. FSFE in a dedicated session</a>.</p></li>
  116. <li><p>FSFE group Munich represented the FSFE with a
  117. <a href="https://www.softmetz.de/2016/06/13/erster-corso-leopold-2016-die-fsfe-war-dabei/">
  118. booth at the first Corso Leopold 2016</a> (DE).</p></li>
  119. <li><p>The "FreieSoftwareOG" represented the FSFE with a<a href="https://blogs.fsfe.org/fast_edi/?p=502"> booth in Offenburg</a> (DE).</p></li>
  120. </ul>
  121. <h2 id="take-action">Take action!</h2>
  122. <p><a href="/community/events/2016/summit/attendance">Get
  123. your ticket for the first FSFE summit from 2nd to 4th of September now</a>!</p>
  124. <p>Also, <a href="/community/events/2016/summit/frontpage#spreadtheword">help
  125. us to spread the word</a> in your favorite mailing list, your blog, your
  126. social media channels or share the news with your neighbours.</p>
  127. <h2 id="good-free-software-news">Good Free Software News</h2>
  128. <p>April updates us on their campaign regarding the French Digital Republic
  129. Bill wherein the <a href="https://www.april.org/en/progress-report-aprils-campaign-around-french-digital-republic-bill">French
  130. parliament has given priority to Free Software</a>. Whilst general legal
  131. framework in France is only taking baby steps in promotion of Free Software,
  132. by the end of 2018, almost <a href="https://joinup.ec.europa.eu/community/osor/news/%E2%80%98open-source-values-match-municipal-public-services%E2%80%99">70%
  133. of all workstations in the French town of Fontaine will run GNU/Linux</a>.
  134. Bulgaria, on the other hand has currently become the leading example in
  135. Free Software policies by <a href="https://thepolicy.us/bulgaria-got-a-law-requiring-open-source-98bf626cf70a#.nfmord3u7">adopting
  136. a law that requires all software written for the government to be Free
  137. Software and to be developed as such in a public repository</a>. Andalusia
  138. is keeping up with the trend and has announced that <a href="https://joinup.ec.europa.eu/community/osor/news/andalusia-renews-funds-key-open-source-projects">funding two
  139. of the region's key Free Software projects, GECOS and Guadalinux will continue</a>.
  140. Colleges in Europe are
  141. <a href="https://joinup.ec.europa.eu/community/osor/news/european-colleges-share-smes-open-source-training">creating
  142. courses to train students to help companies choose and use Free Software cloud services</a>.</p>
  143. <p>Thanks to all the <a href="/contribute/contribute.en.html">volunteers</a>,
  144. <a href="https://my.fsfe.org/donate">Fellows</a> and
  145. <a href="/donate/thankgnus.en.html">corporate donors</a>
  146. who enable our work,</p>
  147. <p>your editors Cellini, Polina and Erik, <a href="https://fsfe.org">FSFE</a></p>
  148. </body>
  149. <sidebar promo="about-fsfe"/>
  150. <date>
  151. <original content="2018-07"/>
  152. </date>
  153. <followup>donate</followup>
  154. <tags>
  155. <tag key="newsletter"/>
  156. </tags>
  157. </html>