Source files of,,,,, and Contribute:
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.

140 lines
5.8 KiB

  1. <?xml version="1.0" encoding="utf-8"?>
  2. <html newsdate="2017-03-14" type="newsletter">
  3. <version>1</version>
  4. <head>
  5. <title>FSFE Newsletter - March 2017</title>
  6. </head>
  7. <body microformats="h-entry">
  8. <h1 class="p-name">FSFE Newsletter - March 2017</h1>
  9. <h2 id="the-chronicles-of-limux">The Chronicles of LiMux</h2>
  10. <p>In February, the news about LiMux shook the
  11. world. LiMux, a project run by the city of Munich and completed
  12. in 2013, constitutes one of the finest examples of
  13. vendor-neutral administration based on Free Software; during
  14. its execution phase, 15,000 personal computers and laptops used
  15. by public administrations were migrated to Free Software.</p>
  16. <p>In a surprise move, a coalition of parties filed a motion
  17. with minimal lead time before the city council, asking for the
  18. abolishment of the project and the return into proprietary
  19. solutions.</p>
  20. <p>The response by the community was immediate and formidable.
  21. FSFE's Deputy Coordinator for Germany, Björn Schießle,
  22. <a href="/news/2017/news-20170301-01">describes
  23. what followed</a>. An ad-hoc coalition was formed by the
  24. FSFE, the Document Foundation, KDE and OSBA, collecting
  25. questions around the motion and its related processes. Members
  26. of the city council were contacted prior to the public hearing
  27. and FSFE supporters in Germany and Austria were invited to
  28. engage, contacting politicians on the issue.
  29. <a href="">Media coverage
  30. in multiple languages</a> was additionally created.</p>
  31. <p>During the public hearing, participating parties quoted some
  32. of our questions, and admitted they had never before
  33. received so much input from the public. The result of the
  34. hearing was a modified motion passed on February 15,
  35. calling the administration to propose a strategy for the
  36. unification of the city's client-side IT architecture by the
  37. end of 2020, building on a yet-to-be-developed proprietary
  38. client and guaranteeing maximal compatibility with the existing
  39. solutions.</p>
  40. <p>The FSFE does not claim LiMux has solved all the
  41. problems. However, we do claim these problems are mostly
  42. of organisational nature, and as such must be disconnected from
  43. the technical side. Public infrastructure must remain
  44. independent of single software vendors, and invest into common
  45. assets, which are provided by Free Software.</p>
  46. <hr />
  47. <p>Help us grow and make a difference in 2017
  48. <a href="">
  50. <hr />
  51. <h2 id="what-else-have-we-done?-inside-and-Outside-the-fsfe">
  52. What else have we done? Inside and Outside the FSFE</h2>
  53. <ul>
  54. <li>For #IloveFS, André <a href=""> translated</a> the Free Software song.</li>
  55. <li>After last year's successful pre-FOSDEM meeting, the FSFE
  56. and OpenForum Europe continued the tradition of bringing
  57. together active Free Software stakeholders during a prior to
  58. FOSDEM public policy related event.
  59. <a href="/news/2017/news-20170214-02">This
  60. year's meeting</a> offered the opportunity to individual
  61. citizens and decision-makers to exchange their views on the
  62. basis of practical first-hand information concerning Free
  63. Software in public policy.</li>
  64. <li>For 16 years, FSFE has been present at FOSDEM with a booth,
  65. numerous volunteers and staff. Reinhard Müller, FOSDEM booth
  66. coordinator,
  67. <a href="">
  68. describes in his report</a> the great atmosphere among the
  69. booth volunteers and how an outstanding amount of merchandise
  70. and promotional material was distributed during the 2 days of
  71. the event.</li>
  72. <li><a href="">In 2016, Europe
  73. welcomed three new umbrella organizations</a> for Free
  74. Software (and hardware) projects: Public Software CIC, The
  75. Commons Conservancy, and the Center for the Cultivation of
  76. Technology. Standing by the needs of the community, the
  77. brand-new organisations provide a legal entity for projects
  78. to join, with regards to donations, accounting, grants, legal
  79. compliance, or even sophisticated governance. These
  80. administrative services allow projects to focus on
  81. technical and community matters.</li>
  82. </ul>
  83. <h2 id="get-active">Get active</h2>
  84. <p>We're still able to accept additional student interns for
  85. 2017. If you're currently studying and are required to do an
  86. internship as part of your studies, or if you've not yet
  87. graduated and want to do a voluntary internship, you should
  88. <a href="/news/2017/news-20170116-01">apply
  89. now</a>.</p>
  90. <h2 id="help-us-to-improve-our-newsletter">Help us to improve
  91. our newsletter</h2>
  92. <p>If you see some news you think should be included, forward
  93. it to us. If you'd like to share any thoughts, send them to us.
  94. The address is as always We're looking
  95. forward to hearing from you!</p>
  96. <p>Thanks to all
  97. <a href="/contribute/contribute.html">
  98. volunteers</a>,
  99. <a href="">
  100. supporters</a> and
  101. <a href="/donate/thankgnus.html">
  102. donors</a> who make our work possible.</p>
  103. <p>your editors Olga Gkotsopoulou and Jonas Öberg
  104. <a href="/">FSFE</a></p>
  105. <hr />
  106. <p>Help us grow and make a difference in 2017
  107. <a href="">
  109. <hr />
  110. </body>
  111. <sidebar promo="about-fsfe" />
  112. <date>
  113. <original content="2017-03" />
  114. </date>
  115. <followup>donate</followup>
  116. <tags>
  117. <tag key="newsletter"/>
  118. </tags>
  119. </html>