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-201709.en.xhtml 11KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <html newsdate="2017-09-18" type="newsletter">
  3. <head>
  4. <title>FSFE Newsletter - September 2017</title>
  5. </head>
  6. <body class="newsletter article" microformats="h-entry" id="nl-201709">
  7. <h1 class="p-name">FSFE Newsletter - September 2017</h1>
  8. <h2 id="publicmoneypubliccode">Public Money? Public Code!</h2>
  9. <p newsteaser="yes">Digital services offered and used by our public administrations are part of the critical infrastructure of 21st century democratic nations. Due to restrictive software licences, however, many public bodies do not have full control over their digital infrastructure. Although publishing publicly funded software under a free licence generates great benefits for governments and civil society, policy makers are still reluctant to improve legislation in this area. It is time to change this. At the FSFE, we want European legislation requiring that publicly financed software developed for public sector must be made publicly available under a Free and Open Source Software licence. If it is public money, it should be public code as well!</p>
  10. <p>To push our demand, the FSFE launched a new campaign last week: <a href="https://fsfe.org/news/2017/news-20170913-01">"Public Money Public Code"</a>. The campaign explains the benefits of releasing publicly funded Software under free licences with a <a href="https://publiccode.eu#about">short inspiring video</a> and an <a href="https://publiccode.eu#action">open letter</a> to sign. Furthermore, the campaign and the open letter will be used in the coming months until the European Parliament election in 2019 to highlight good and bad examples of publicly funded software development and its potential reuse.</p>
  11. <p>Initial success was overwhelming. The campaign launch was covered by many websites and news magazines over Europe. At the time of writing, the Open Letter is already signed by <a href="https://publiccode.eu/#organisations">more than 35 organisations</a> and <a href="https://publiccode.eu/openletter/all-signatures/">more than 5000 individuals</a>. Various politicians and other prominent people have publicly announced their support of the campaign, including Edward Snowden, President of Freedom of the Press Foundation:</p>
  12. <blockquote><p><em><a href="https://twitter.com/Snowden/status/908012039045386240">"Public money shouldn't write software the public isn't allowed to fix. Sign the letter, save the world: https://publiccode.eu/#action #PublicCode"</a></em></p></blockquote>
  13. <div class="captioned" style="width:80%; margin: 1.5em auto;"><a href="https://publiccode.eu">
  14. <img src="/picturebase/miscellaneous/20170913-snowden-quote-PMPC.png" alt="Eward Snowden on publiccode.eu" /></a>
  15. </div>
  16. <p>Support public code as well and sign the open letter here: <a href="https://publiccode.eu/#action">https://publiccode.eu/#action</a></p>
  17. <h2 id="softwarelicensingbestpractices">FSFE publishes Software Licensing Best Practices</h2>
  18. <p>If you want others to be able to use your code, you have to include a licence, and as a best practice you should do so in a way which can be understood by humans and computers alike. Unfortunately, endless software projects and code snippets are available in the open but still lack a proper licence. One potential reason is that attaching a licence to software - properly and in a way that is understandable - can be challenging. Making sure computers understand your licence is even more difficult. </p>
  19. <p>That is why the FSFE has begun our work to <a href="https://fsfe.org/news/2017/news-20170906-01">make managing copyrights and licences in free and open source software easier</a>. Our Software Licensing Best Practices guide will help you include license and copyright notices correctly in your software. And as we keep evaluating best practices, under <a href="https://reuse.software">https://reuse.software/</a> you will already find a few simple steps to take to make the copyright and licence of your project more easily understood.</p>
  20. <hr />
  21. <p><a href="https://fsfe.org/join/nl2017-09">Help us grow and make a difference in 2017</a></p>
  22. <hr />
  23. <h2 id="whatelsehavewedone">What else have we done? Inside and Outside the FSFE</h2>
  24. <ul>
  25. <li>The proposed European Copyright Directive restricts the rights of developers and internet users, creating barriers for the development of source code. Together with Open Forum Europe, the FSFE <a href="https://fsfe.org/news/2017/news-20170908-01">wrote a white paper</a> to help people understand the full view of the matter at stake from a software developer point of view. We will launch a campaign later this month but you can already help us to raise awareness by sharing <a href="https://savecodeshare.eu/">Save Code Share</a> widely.</li>
  26. <li>The FSFE's executive director, Jonas Öberg, published a blog post about the yearly FSFE budget, <a href="http://blog.jonasoberg.net/where-does-our-money-go/">how our finances are structured, and where the money goes</a>. </li>
  27. <li>The "Koalition Freies Wissen" ("Free Knowledge Coalition") <a href="https://fsfe.org/news/2017/news-20170829-01">created the "Digital-O-Mat"</a>, an online tool for voter information for the German federal elections on September 24th, 2017. The <a href="https://bund.digital-o-mat.de">Digital-O-Mat</a> (German) highlights the parties' positions on topics relavant to internet policy like Free Software and helps voters find their most matching party for the election to the German parliament. </li>
  28. <li>The FSFE country team Germany sent "Ask Your Candidates" questions to participating parties of the Bundestagswahl (the German federal elections) and <a href="https://fsfe.org/news/2017/news-20170905-01">published and analysed their answers</a>. (German)</li>
  29. <li>The FSFE country team Netherlands was present with a village at SHA Camp, a non-profit hacker-camp in the Netherlands. For five days, this village offered a public space to discuss, meet, hack, sing-along, and find shelter. The FSFE had its own curated track and <a href="https://blog.3rik.cc/2017/09/still-freeing-software-anyway/">the village offered multiple self-organized sessions</a>, from a Free Software Song choir to a FreedomBox install fest.</li>
  30. <li>The FSFE country team Greece supported the first edition of <a href="https://re-publica.com/en/eu17/sessions?location=Thessaloniki">Re:publica in Thessaloniki</a>, a conference about digital culture. </li>
  31. <li>The FSFE group Rhein/Main was <a href="https://k7r.eu/fsfe-at-froscon-2017/">present with a booth at Froscon</a>, at the Free Software conference at the University of Applied Sciences Bonn-Rhein-Sieg, Germany. FSFE president Matthias Kirschner also gave a talk about <a href="https://media.ccc.de/v/froscon2017-1991-limux_das_ende_eines_leuchtturm-projekts">"Limux: das Ende eines Leuchtturm-Projekts!?"</a>. (German)</li>
  32. <li>In April this year, the Digital Society Institute hosted a workshop to analyse "How secure is free software? Security record of open source and free software." The workshop included contributions from Matthias Kirschner and is <a href="https://www.esmt.org/sites/default/files/dsi_ipr5_engl-dt.pdf">now available in English and German</a> including recommendations for the private and public sector.</li>
  33. <li>We are happy to welcome three new interns: Carmen Bianca Bakker, Kristi Progri and Erik Da Silva. If you are interested in doing an internship with us, <a href="https://fsfe.org/contribute/internship">find more information on our pages</a>. </li>
  34. <li>We have a new item in the FSFE online shop: <a href="https://fsfe.org/news/2017/news-20170726-01">a non-binary pink bib</a> with the slogan "I am a fork" stitched onto the bib. Organic and fair trade.</li>
  35. </ul>
  36. <div class="captioned" style="width:80%; margin: 1.5em auto;"><img src="/picturebase/booths/20170807-village-and-team-at-SHA2017-800px.jpg" alt="The FSFE village during SHA Camp 2017 in the Netherlands." />
  37. <footer><p>The FSFE village during SHA Camp 2017 in the Netherlands.</p></footer>
  38. </div>
  39. <h2 id="donotmissit">Do not miss it! Upcoming events with the FSFE</h2>
  40. <p><a href="https://copycamp.pl/en/">CopyCamp in Warsaw</a> will be happening on 28 - 29 of September. CopyCamp is a conference that focuses on the question of how exclusive immaterial rights affect culture, education, science, technology, and Free Software. Matthias Kirschner will speak about "Limux: the loss of a lighthouse" and our policy analyst Polina Malaja about the upcoming "EU copyright reform and its implications for collaborative software development." The conference has no admission fee, but participants are asked to <a href="https://copycamp.pl/en/contact/register/">register before attending</a>. Thanks to the Foundation for Polish-German Cooperation, there are travel grants available for German residents (not only citizens), funded by the German Federal Foreign Office. </p>
  41. <h2 id="getactive">Get Active</h2>
  42. <p>Have a look at our <a href="https://publiccode.eu">"Public Money Public Code" page</a> and the PMPC video and share it with your friends, colleagues, and favorite mailing lists. Also ask them to <a href="https://publiccode.eu/openletter/">sign the open letter</a> and do this yourself. If the page is not available in your language, <a href="https://git.fsfe.org/pmpc/website/src/master/TRANSLATE.md">help us with translations</a>.</p>
  43. <h2 id="helpusimproveournewsletter">Help us improve our newsletter</h2>
  44. <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>
  45. <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 our readers to read this newsletter in their mother tongue.</p>
  46. <p>Your editor,<br />
  47. Erik Albers</p>
  48. <hr />
  49. <p><a href="https://fsfe.org/join/nl2017-09">Help us grow and make a difference in 2017</a></p>
  50. <hr />
  51. </body>
  52. <sidebar promo="about-fsfe" />
  53. <date>
  54. <original content="2017-09" />
  55. </date>
  56. <followup>donate</followup>
  57. <tags>
  58. <tag>newsletter</tag>
  59. <tag content="Reuse.Software">reuse</tag>
  60. <tag content="Public Money Public Code">PMPC</tag>
  61. <tag content="Digital-O-Mat">digitalomat</tag>
  62. <tag content="Save Code Share">savecodeshare</tag>
  63. <tag content="CopyCamp">copycamp</tag>
  64. <tag content="SHA2017">SHA2017</tag>
  65. </tags>
  66. <author id="albers" />
  67. </html>