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-201803.en.xhtml 8.5KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174
  1. <?xml version="1.0" encoding="utf-8"?>
  2. <html newsdate="2018-03-20" type="newsletter">
  3. <head>
  4. <title>FSFE Newsletter - March 2018</title>
  5. </head>
  6. <body class="newsletter article" microformats="h-entry" id="nl-201803">
  7. <h1 id="fsfe-newsletter-march-2018">FSFE Newsletter March 2018</h1>
  8. <h2 id="italy-at-the-forefront-of-european-legislation-for-public-code">
  9. Italy at the forefront of European legislation for public code</h2>
  10. <p newsteaser="yes">With the FSFE&apos;s <a href="https://publiccode.eu">
  11. Public Money? Public Code!</a> campaign not only do we demand that code
  12. paid for by the people should be available to the people. We also
  13. highlight good examples of public code so other decision makers can learn
  14. from it. One very good example is
  15. <a href="http://www.agid.gov.it/cad/art-68-analisi-comparativa-soluzioni">
  16. Article 68</a> and
  17. <a href="http://www.agid.gov.it/cad/art-69-riuso-soluzioni-standard-aperti">
  18. Article 69</a> of the &quot;Codice Amministrazione Digitale&quot;, an
  19. Italian law requiring public administrations inside Italy to prefer
  20. internally made solutions and Free Software solutions over proprietary
  21. ones. In addition, these administrations have the duty to share the source
  22. code and documentation of any software developed with public money.
  23. These laws put Italy at the forefront of European legislation in favour of
  24. public code.</p>
  25. <p>Unfortunately, so far the law lacks proper implementation. In that light,
  26. the FSFE&apos;s country team in Italy ran an
  27. <a href="https://fsfe.org/campaigns/askyourcandidates/askyourcandidates">
  28. Ask Your Candidates campaign</a> in which they
  29. <a href="https://fsfe.org/news/2018/news-20180219-01">asked the political
  30. parties about their stand on Free Software</a> and the implementation of
  31. the aforementioned Articles 68 and 69 after the national elections on
  32. March 4.</p>
  33. <p>FSFE Italy received very positive replies and many parties
  34. <a href="https://fsfe.org/news/2018/news-20180302-01.html">took a
  35. favourable stand towards Free Software</a>. Such a big consensus across
  36. these parties gives hope to open up a lot of possibilities for progress
  37. towards the use of Free Software at the state level in Italy and a better
  38. implementation of Articles 68 and 69 of the &quot;Codice Amministrazione
  39. Digitale&quot;. As a match to this, the team &quot;Developers
  40. Italia&quot;, who are in charge of further implementation of the Articles
  41. 68 and 69,
  42. <a href="https://twitter.com/developersITA/status/964060999899860992">sent
  43. out their love for Free Software</a> on I love Free Software day.</p>
  44. <h2 id="read-our-detailed-ilovefs-report">Read our detailed IloveFS
  45. report</h2>
  46. <p>As promised in the last newsletter, we now have a
  47. <a href="/news/2018/news-20180308-01">detailed report about our IloveFS
  48. campaign in 2018</a>. In the report, you will not only read about some
  49. highlights that happened for this year&apos;s IloveFS. Thanks to our
  50. current intern Jan, we also have an analysis and visualisation of 439
  51. &apos;I Love Free Software&apos; messsages containing the
  52. <em>&#35;IloveFS</em> hashtag. The scraper Jan used for his analysis is
  53. written in GNU R and <a href="https://git.fsfe.org/janwey/ilfs-data">
  54. published as Free Software</a>.</p>
  55. <p>While every year we are happy to see so many people celebrating I
  56. love Free Software day, we also encourage you to express your Free
  57. Software love every day :)</p>
  58. <hr />
  59. <p><a href="/join/nl2018-03">Join our community of freedom fighters.</a></p>
  60. <hr />
  61. <h2 id="what-else-have-we-done-inside-and-outside-the-fsfe">What else have
  62. we done? Inside and Outside the FSFE</h2>
  63. <ul>
  64. <li>Paul Boddie reflects on
  65. <a href="https://blogs.fsfe.org/pboddie/?p=1978">the hobbyism and
  66. volunteerism attitude</a> in many Free Software projects and what
  67. this means for the valuation of the actual work that is done,
  68. examining Python language development as an example.</li>
  69. <li>Isabel Drost Fromm
  70. <a href="http://blog.isabel-drost-fromm.de/posts/proxies-considered-harmful.html">
  71. argues against people acting as mediators</a> as the only interface
  72. between their employer and a Free Software project.</li>
  73. <li>Carmen Bianca Bakker
  74. <a href="https://www.carmenbianca.eu/en/post/2018-03-09-how-we-conduct-ourselves/">
  75. reflects on the recently updated FreeBSD Code of Conduct</a>, examines
  76. the included dangers of positive discrimination, and states how
  77. a non-biased, welcoming Code of Conduct can indeed
  78. help dogs and cats to live happily ever after.</li>
  79. <li>Daniel Pocock
  80. <a href="https://danielpocock.com/swisspost-swissid-another-nail-in-the-coffin-sovereignty">
  81. reflects on the newly-introduced SwissID</a>, and its potential dangers
  82. to privacy and democratic referendums.</li>
  83. <li>Erik Albers asked our community on multiple channels to let
  84. the FSFE know about upcoming Free Software events in 2018 that are
  85. of interest to the FSFE community. Thanks to our current intern
  86. Vincent they all ended up in <a href="https://wiki.fsfe.org/Events">
  87. the FSFE&apos;s wiki calendar</a> so our teams and community can use
  88. them to organise their attendance.</li>
  89. <li>Björn Schießle, the FSFE&apos;s country coordinator Germany, gave a
  90. talk about
  91. <a href="https://www.schiessle.org/articles/2017/11/14/software-freedom-in-the-cloud/">
  92. software freedom in the cloud</a> at &quot;Chemnitzer
  93. Linuxtage&quot; in Chemnitz, Germany.</li>
  94. <li>Erik Albers was giving a
  95. <a href="https://platform.internetfreedomfestival.org/en/IFF2018/public/schedule/custom/478">
  96. talk about Public Money? Public Code!</a> at the Internet Freedom
  97. Festival in Valencia, Spain.</li>
  98. <li>The new born local FSFE group in Madrid had its first meeting on
  99. <a href="https://wiki.fsfe.org/Events/2018/0222-encuentro-local-madrid">
  100. February 22</a> and
  101. <a href="https://wiki.fsfe.org/Events/2018/0303-encuentro-grupo-local-madrid">
  102. March 3</a>.</li>
  103. <li>The FSFE has been present with a booth at &quot;Chemnitzer
  104. Linuxtage&quot; in Chemnitz (Germany), at T3chfest in Madrid
  105. (Spain), and at the Internet Freedom Festival in Valencia
  106. (Spain).</li>
  107. </ul>
  108. <h2 id="get-active">Get Active</h2>
  109. <p>If you have not done so yet, let us know your favorite Free Software
  110. event that you think is or should be in interest for the FSFE community to
  111. set up a booth at or participate in with a talk or workshop. The simplest
  112. way to do so is by sending a mail to <a href="mailto:contactATfsfeDOTorg">
  113. contact@fsfe.org</a> with the subject &quot;Free Software event
  114. 2018&quot;. Please state what the event is about, how many participants
  115. are expected, and the main language used. Before informing us, please
  116. check if we do not already have it
  117. <a href="http://blog.3rik.cc/2018/03/free-software-events-in-europe-in-2018/">
  118. in our list</a>.</p>
  119. <p>If you are visiting any other events regularly or soon, be it a big
  120. conference or a local meet-up, equip yourself with some FSFE promotion
  121. material that you can <a href="/promo">order at no charge</a>.</p>
  122. <h2 id="contribute-to-our-newsletter">Contribute to our newsletter</h2>
  123. <p>If you would like to share any thoughts, pictures, or news, send them to
  124. us. As always, the address is <a href="mailto:newsletterATfsfeDOTorg">
  125. newsletter@fsfe.org</a>. We&#39;re looking forward to hearing from
  126. you!</p>
  127. <p>Thanks to our community, all the
  128. <a href="/contribute/contribute">volunteers</a>, <a href="/join">
  129. supporters</a> and <a href="/donate/thankgnus">donors</a> who make our
  130. work possible. And thanks to
  131. <a href="/contribute/translators/translators">our translators</a>, who
  132. enable you to read this newsletter in your mother tongue.</p>
  133. <p>Your editors, <br />
  134. Erik Albers and Max Mehl</p>
  135. <hr />
  136. <p><a href="https://fsfe.org/join/nl2018-03">Join our community of freedom
  137. fighters.</a></p>
  138. <hr />
  139. </body>
  140. <sidebar promo="about-fsfe" />
  141. <date>
  142. <original content="2018-03" />
  143. </date>
  144. <followup>donate</followup>
  145. <tags>
  146. <tag>newsletter</tag>
  147. <tag content="Italy">it</tag>
  148. <tag content="I love Free Software">ilovefs</tag>
  149. <tag content="Ask Your Candidates">ayc</tag>
  150. <tag content="Public Code">pmpc</tag>
  151. </tags>
  152. <author id="albers" />
  153. <author id="mehl" />
  154. </html>