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
Du kannst nicht mehr als 25 Themen auswählen Themen müssen mit entweder einem Buchstaben oder einer Ziffer beginnen. Sie können Bindestriche („-“) enthalten und bis zu 35 Zeichen lang sein.

nl-201902.en.xhtml 15KB

vor 10 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
vor 10 Monaten
vor 10 Monaten
vor 10 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
vor 10 Monaten
vor 10 Monaten
vor 10 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
vor 10 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
vor 9 Monaten
vor 10 Monaten
123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <html newsdate="2019-02-12" type="newsletter">
  3. <head>
  4. <title>FSFE Newsletter - February 2019</title>
  5. </head>
  6. <body class="newsletter article" microformats="h-entry" id="nl-201902">
  7. <h1 id="fsfenewsletterfebruary2019">FSFE Newsletter February 2019</h1>
  8. <p newsteaser="yes">This month's Newsletter is introducing our new expert policy brochure "Public Money? Public Code" and reflecting the importance of source code availability for trust and security in critical IT-infrastructure. As always the Newsletter gives an overview about the talks given and the booths set-up by our community as well as a short summary of what we have done - this month including FOSDEM, 35C3, FOSS4SMEs and the Next Generation Internet. As a "get active" item, this month we encourage you to participate in our IloveFS-campaign.</p>
  9. <h2 id="fsfepublishesexpertbrochureaboutpublicmoneypubliccode">FSFE publishes expert brochure about “Public Money? Public Code!"</h2>
  10. <p>Convincing decision-makers why more public code would benefit us all should be easy. There are so many good arguments for putting publicly funded code under a Free Software licence: Tax savings, transparency, and innovation – just to name a few. But, in practice, we experience that there are still a lot of basics that need to be explained. Starting with: What is Free Software? Why should governments develop Free Software? What are Free Software business models? To answer these questions and give practical guidelines to decision-makers, we have published a policy brochure that presents the most important facts and arguments about publicly funded code. </p>
  11. <p>This <a href="https://fsfe.org/news/2019/news-20190124-01.html">publication</a> answers decision-makers' most common questions and refutes widespread misunderstandings about Free Software. In several articles and contributions from experts, the brochure presents successful Free Software use-cases and inspiring legislation that show that change is already taking place. Overall, the brochure provides practical guidance for moving the modernisation of public infrastructure forward and hints at how procurement guidelines can be updated to include the strong points of Free Software. Downloads and prints <a href="https://fsfe.org/campaigns/publiccode/brochure.html">are available under a Creative Commons license</a></p>
  12. <p>Among the contributions included in the brochure, that feature experts from various fields, is an interview with Francesca Bria, Chief Technology and Digital Innovation Officer for the City of Barcelona, who drives the modernisation of Barcelona's public infrastructure. She says: "The Barcelona City Council supports the FSFE's campaign 'Public Money, Public Code', because we need alliances to make Free Software the default setting in the public sector. The digital public infrastructure that we use should be a public good, owned and controlled by the citizens." </p>
  13. <div class="captioned" style="width:80%; margin: 1.5em auto;">
  14. <a href="https://fsfe.org/campaigns/publiccode/brochure.html"><img src="/picturebase/campaigns/pmpc/201801-pmpc-brochure-people-800px.jpg" /></a>
  15. <footer><p>Help us with a <a href="https://my.fsfe.org/donate">donation</a> to print and distribute the new FSFE expert policy brochure</p></footer>
  16. </div>
  17. <h2 id="aboutpublishingsourcecode">About publishing source code to establish trust in critical infrastructure</h2>
  18. <p>In many countries, the Chinese company Huawei is facing distrust after allegations of potential state espionage. The company is one of the largest manufacturers of 5G equipment, the upcoming generation of cellular mobile communications. To ensure that the products and the underlying infrastructure are safe, network providers and politicians proposed an inspection of the equipment's source code. <a href="https://fsfe.org/news/2019/news-20190205-01.html">The FSFE welcomes</a> this move to recognize the importance of source code availability , but is afraid that the proposed solution falls too short. Allowing inspection of the secret code by selected authorities and telephone companies might help in this specific case, but will not solve the general problem. Instead, to establish trust in critical infrastructure like 5G, it is a crucial precondition that all software code powering those devices is published under a Free and Open Source Software licence. On this basis, everyone can inspect the code, not only for backdoors, but for all security risks. Only these freedoms allow for independent and continuous security audits which will lead citizens, the economy, and the public sector to trust their communication and data exchange. Furthermore, in order to verify code integrity – so that the provided source code corresponds to the executable code running on the equipment – it is either necessary that there are reproducible builds in case of binary distribution, or that providers are brought into the position to compile and deploy the code on their own.</p>
  19. <p>"We should not only debate the Huawei case but extend the discussion to all critical infrastructure." says Max Mehl, FSFE Programme Manager. "Only with Free and Open Source Software can transparency and accountability be guaranteed. This is a long-known crucial precondition for security and trust. We expect state actors to immediately implement this solution not only for the Huawei case but for all comparable IT security issues."</p>
  20. <hr />
  21. <p><a href="/join/nl2018-02">Join our community of freedom fighters!</a></p>
  22. <hr />
  23. <h2 id="whatelsehavewedoneinsideandoutsidethefsfe">What else have we done? Inside and Outside the FSFE</h2>
  24. <ul>
  25. <li>On January 14 and 15, our project manager Gabriel Ku Wei Bin attended a kickoff meeting in Amsterdam of the <a href="https://nlnet.nl/PET/background/">Next Generation Internet</a> project, funded by the European Commission and administered by the NLNet Foundation in the Netherlands. The FSFE joins the project to provide guidance to applicant technologies involved in the project to ensure that their final products are compliant with Free Software licensing best practices.</li>
  26. <li>On January 16 and 17 the FSFE's project managers Galia Mancheva and Max Mehl joined the <a href="https://fsfe.org/activities/foss4smes/foss4smes.html">FOSS4SMEs</a> meeting in Dublin and shot videos for the online lessons the e-learning platform of the project is launching later this year. Stay tuned for further updates on the <a href="https://www.foss4smes.eu/">project’s website</a>.</li>
  27. <li>Björn Schießle, FSFE coordinator for Germany, <a href="https://2019.copyleftconf.org/schedule/presentation/12/">gave a talk</a> on using strong copyleft to build a sustainable business at the Copyleft Conference on February 4th in Brussels.</li>
  28. <li>On January 23 Alexander Sander, the FSFE's EU public policy programme manager, joined a panel at Eurocieties Society Forum in Barcelona. Sander talked about how cities and public administration can foster Free Software and involve the local ecosystem in developing digital services based on Free Software and open standards.</li>
  29. <li>Paul Boddie writes about <a href="https://blogs.fsfe.org/pboddie/?p=2386">"An Absence of Strategy?"</a> in which he argues that "installing Free Software over it" is no longer enough in the world of mobile devices. He claims that instead we need a strategy and an organisation that brings together collective efforts and practical action to identify ongoing projects and propose actual solutions towards constructing sustainable, community-driven, and user-protecting devices.</li>
  30. <li>Frank Karlitschek <a href="https://karlitschek.de/2019/01/2018-and-2019/">predicts</a> that 2019 will be a very good year for privacy, open source and decentralized <a href="/contribute/spreadtheword#nocloud">"cloud"</a> software. It could be the year where Free Software, federated and self-hosted technology hits the mainstream.</li>
  31. <li>Björn Schießle <a href="https://www.schiessle.org/articles/2019/01/02/cultural-techniques/">wrote</a> about Free Software being a "new cultural technique", a collective achievement done in a socio-cultural context, requiring social interaction and participation. And as such, it requires special attention by policy makers and society.</li>
  32. <li>Marcus Moeller, Country Coordinator of the FSFE in Switzerland, set up a Swiss association <a href="https://faircomputer.ch">Faircomputer</a> for which he and his contributors are collecting used Laptops. These devices are then checked, repaired, cleaned and equipped with Free Software. The refurbished machines are given away for free to interested people around Germany, Austria and Switzerland, only charging a small amount for the warranty to ensure they can be used without any hassle for years. </li>
  33. <li>Between Christmas and New Year, the FSFE was organising a cluster "about:freedom" together with like-minded organisations at the Chaos Communication Congress, the biggest community driven hacker congress in Germany. Inside the cluster, <a href="https://events.ccc.de/congress/2018/wiki/index.php/Assembly:Free_Software_Foundation_Europe">the FSFE was present</a> with an assembly, a booth, and running its <a href="https://events.ccc.de/congress/2018/wiki/index.php/Assembly:Free_Software_Foundation_Europe#Our_Sessions">own track</a>. From the FSFE we had Susanne speaking about her <a href="https://fahrplan.events.ccc.de/congress/2018/Fahrplan/events/9681.html">self-made "smartphone"</a> (<a href="https://media.ccc.de/v/35c3-9681-butterbrotdosen-smartphone">video</a>), Katharina Nocun about <a href="https://fahrplan.events.ccc.de/congress/2018/Fahrplan/events/9858.html">data collecting Amazon</a> (<a href="https://media.ccc.de/v/35c3-9858-archaologische_studien_im_datenmull">video</a>) and Erik Albers about <a href="https://pretalx.35c3oio.freifunk.space/35c3oio/talk/UFZYAS/">the best of Fdroid</a> (<a href="https://media.freifunk.net/v/35c3oio-74-f-droid-pimp-your-android-fork-with-the-best-free-software-apps">video</a>)</li>
  34. </ul>
  35. <div class="captioned" style="width:80%; margin: 1.5em auto;">
  36. <img src="/picturebase/booths/201812-booth-at-35c3-800px.jpg" />
  37. <footer><p>FSFE booth during 35C3, the 35th Chaos Communication Congress</p></footer>
  38. </div>
  39. <ul>
  40. <li>In the beginning of February, the FSFE was present at FOSDEM, the biggest community-driven Free Software event in Europe. We had formal and informal meetings and social evenings, and were running an information booth throughout the event. </li>
  41. <li>On January 19, FSFE joined the Dutch Linux user group NLLGG meeting in Utrecht to set up a booth and have a chat about Free Software and related topics.</li>
  42. <li>Local FSFE community meetings happened this month in <a href="https://wiki.fsfe.org/LocalGroups/Hamburg">Hamburg</a>, Bonn, <a href="https://wiki.fsfe.org/LocalGroups/RheinMain">Frankfurt (Main)</a>, <a href="https://wiki.fsfe.org/LocalGroups/Madrid">Madrid</a>, <a href="https://wiki.fsfe.org/LocalGroups/Zurich">Zurich</a> and <a href="https://wiki.fsfe.org/LocalGroups/Berlin">Berlin</a>. If you would like to see your local FSFE meeting listed here, please announce it with our <a href="https://fsfe.org/community/tools/eventregistration">improved event announcement tool</a>.</li>
  43. <li>The European Commission <a href="https://joinup.ec.europa.eu/news/eur-3000-eur-25000">expands its bug bounty programme</a> called EU-FOSSA2. Software developers who find security vulnerabilities in the selected Free Software will be awarded between EUR 3,000 and EUR 25,000 for critical bugs. </li>
  44. </ul>
  45. <h2 id="donotmissupcomingeventswiththefsfe">Do not miss: upcoming events with the FSFE</h2>
  46. <ul>
  47. <li>The FSFE will be present with a booth at Chemnitzer Linuxtage from March 16 to 17 in Chemnitz, Germany, and is looking forward to having a chat with you about Free Software or FSFE. Erik Albers, programme manager for the FSFE will <a href="https://chemnitzer.linux-tage.de/2019/en/programm/beitrag/269">give a workshop</a> about how to make the best of your Android(-fork) by using FDroid. If you like to get in contact beforehand or join the booth team, have a look at <a href="https://community.fsfe.org/t/chemnitzer-linuxtage-2019-standteam/216">the discussion</a> in our Discourse installation.</li>
  48. </ul>
  49. <h2 id="getactive">Get Active</h2>
  50. <p>On February 14, our community around the globe celebrates <a href="https://fsfe.org/campaigns/ilovefs/">"I love Free Software" Day</a>. We would like to encourage you to be part of our online campaign by creating, sharing or simply enjoying love messages all around the world dedicated to Free Software and the people behind it. Enjoy the day, share and refuel your energy!</p>
  51. <div class="captioned" style="width:80%; margin: 1.5em auto;">
  52. <a href="https://fsfe.org/campaigns/ilovefs/artwork/artwork.html"><img src="/campaigns/ilovefs/artwork/graphics/ilovefs-hashtag.png" style="border: 0 !important;" alt="I love Free Software!"/></a>
  53. </div>
  54. <p>As in previous editions, we are looking forward to seeing you spreading all kind of materials, be they texts, pictures, graphics, scripts or whatever comes to your mind, to show your love to Free Software. Throughout the day, we will share your contributions around the globe on our media channels and collect them for a nice write-up about the love you have for our communities. If you share something, remember to use the hashtag <strong>#ilovefs</strong>, or if you happen to use the <a href="https://fsfe.org/campaigns/ilovefs/artwork/artwork.html">IloveFS visuals</a> on your web platform, website or a blog, please, let us know, so we can include it in our stream.</p>
  55. <h2 id="contributetoournewsletter">Contribute to our newsletter</h2>
  56. <p>If you would like to share any thoughts, pictures, or news, send them to us. As always, the address is newsletter@fsfe.org. We're looking forward to hearing from you!</p>
  57. <p>Thanks to our community, all the <a href="https://fsfe.org/contribute/contribute">volunteers</a>, <a href="http://fsfe.org/join">supporters</a> and <a href="https://fsfe.org/donate/thankgnus">donors</a> who make our work possible. And thanks to <a href="https://fsfe.org/contribute/translators/translators">our translators</a>, who enable you to read this newsletter in your mother tongue.</p>
  58. <p>Your editor,<br />
  59. Erik Albers</p>
  60. <hr />
  61. <p><a href="/join/nl2019-02">Join our community of freedom fighters!</a></p>
  62. <hr />
  63. </body>
  64. <sidebar promo="about-fsfe" />
  65. <date>
  66. <original content="2019-02" />
  67. </date>
  68. <followup>donate</followup>
  69. <tags>
  70. <tag>front-page</tag>
  71. <tag content="Newsletter">newsletter</tag>
  72. <tag content="I love Free Software">IloveFS</tag>
  73. <tag content="Public Money? Public Code!">pmpc</tag>
  74. <tag content="FOSS4SMEs">Foss4smes</tag>
  75. <tag content="FOSDEM">fosdem</tag>
  76. <tag content="35C3">ccc</tag>
  77. </tags>
  78. <author id="albers" />
  79. </html>