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.

623 lines
34KB

  1. <?xml version="1.0" encoding="UTF-8"?>
  2. <html newsdate="2017-12-07">
  3. <version>1</version>
  4. <head>
  5. <title>FSFE Yearly Report 2017</title>
  6. <style type="text/css">
  7. div#toc {
  8. float: left;
  9. border: solid 1px;
  10. border-color:blue;
  11. margin: .5em;
  12. margin-top:1em;
  13. margin-bottom:2em;
  14. background: rgb(240,240,240);
  15. width: 40%;
  16. }
  17. </style>
  18. </head>
  19. <body>
  20. <h1>FSFE Yearly Report 2017</h1>
  21. <p>
  22. The yearly report of the Free Software Foundation Europe gives you a breakdown
  23. in one document of important things we have done and achieved during the last 12
  24. months. Read on to find out about our activities, the campaigns we have run, the
  25. events we have visited or organised, the groups we have helped, and what
  26. resources we counted on to do it.
  27. </p>
  28. <div id="toc">
  29. <p style="text-indent:1em;">Table of content</p>
  30. <ul style="margin: 0em 1em 1em 0em;">
  31. <li><a href="#done">What we have done in 2017</a></li>
  32. <li><a href="#number">FSFE's 2017 in numbers</a></li>
  33. <li><a href="#people">The people behind FSFE</a></li>
  34. <li><a href="#end">At the end</a></li>
  35. </ul>
  36. </div>
  37. <div style="clear:both"></div>
  38. <h2 id="done">What we have done in 2017</h2>
  39. <h3>Public Money, Public Code</h3>
  40. <p>In September, we launched our Public Money, Public Code campaign. The idea is
  41. simple: Software created using taxpayers' money should be available under a free
  42. licence for everybody.</p>
  43. <p>To drive our campaign, we have set up <a href="https://publiccode.eu/">a
  44. campaign site</a>and published an open letter that everyone can sign to support
  45. our demand. To boost virality and help everyone understand the benefits of
  46. public bodies publishing their source code under free licences, we made a video
  47. (<a href="https://publiccode.eu/#about">Webpage</a> /
  48. <a href="https://download.fsfe.org/videos/pmpc/">Download</a> /
  49. <a href="https://vimeo.com/232524527">Vimeo</a> / <a href="https://youtu.be/iuVUzg6x2yo">YouTube</a>)
  50. explaining the situation. So far it is available in
  51. <a href="https://publiccode.eu/#about">English</a>,
  52. <a href="https://publiccode.eu/de/#about">German</a> and
  53. <a href="https://publiccode.eu/fr/#about">French</a>, with more languages to come.</p>
  54. <center> <video controls="controls" width="640" height="360" poster="poster.png" crossorigin="crossorigin">
  55. <source src="https://download.fsfe.org/videos/pmpc/pmpc_desktop.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' media="screen and (min-device-width:1000px)" />
  56. <source src="https://download.fsfe.org/videos/pmpc/pmpc_desktop.webm" type='video/webm; codecs="vp9, opus"' media="screen and (min-device-width:1000px)" />
  57. <source src="https://download.fsfe.org/videos/pmpc/pmpc_mobile.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' media="screen and (max-device-width:999px)" />
  58. <source src="https://download.fsfe.org/videos/pmpc/pmpc_mobile.webm" type='video/webm; codecs="vp9, opus"' media="screen and (max-device-width:999px)" />
  59. <track src="https://publiccode.eu/video-subs/webvtt/pmpc_en.vtt" kind="subtitles" srclang="en" label="English" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_de.vtt" kind="subtitles" srclang="de" label="Deutsch" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_es.vtt" kind="subtitles" srclang="es" label="Español" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_eo.vtt" kind="subtitles" srclang="eo" label="Esperanto" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_fr.vtt" kind="subtitles" srclang="fr" label="Français" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_hu.vtt" kind="subtitles" srclang="hu" label="Magyar" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_it.vtt" kind="subtitles" srclang="it" label="Italiano" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_nl.vtt" kind="subtitles" srclang="nl" label="Nederlands" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_nb.vtt" kind="subtitles" srclang="nb" label="Norsk (bokmål)" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_pt.vtt" kind="subtitles" srclang="pt" label="Português" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_sk.vtt" kind="subtitles" srclang="sk" label="Slovenský" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc
  60. _sv.vtt" kind="subtitles" srclang="sv" label="Svenska" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_tr.vtt" kind="subtitles" srclang="tr" label="Türkçe" /> <track src="https://publiccode.eu/video-subs/webvtt/pmpc_zh.vtt" kind="subtitles" srclang="zh" label="正體中文(臺灣)" />
  61. </video> </center>
  62. <p>This campaign is ongoing and still in its early stages. In fact, we intend to
  63. continue it well into 2019 at least, so as to raise awareness among candidates
  64. for the elections to the European Parliament. At the moment of writing, we have
  65. collected <a href="https://publiccode.eu/openletter/all-signatures/">over 14,000
  66. signatures</a> of our <a href="https://publiccode.eu/openletter">open
  67. letter</a>. Among the signatories are national
  68. representatives and European Parliament Members, and we have received
  69. <a href="https://publiccodde.eu/#organisations">endorsements from over 100
  70. organisations</a> and prominent players in the IT field, including security
  71. expert Edward Snowden.</p>
  72. <p>Our goal is to get elected officials to commit to policy and legislations that
  73. make publicly funded software free software by default. To that effect, we
  74. contacted ~1000 candidates for the German Federal Parliament elections and asked
  75. the addressees to &quot;implement legislation requiring that publicly financed
  76. software developed for public sector [...] be made publicly available under a
  77. Free and Open Source Software licence.&quot; from the candidates who contacted us that they support our claim, 19 are now members of parliament. Beside that the whole parliamentary group of the
  78. German Green
  79. party <a href="https://www.gruen-digital.de/2017/09/public-money-public-code-wer-es-nicht-glauben-mag-schaue-sich-die-software-zu-den-bundestagswahlen-an/">responded
  80. to our campaign in a public letter</a>, stating their support for our demand.</p>
  81. <div class="captioned" style="width:80%; margin: 1.5em auto;"><a href="https://publiccode.eu">
  82. <img src="https://pics.fsfe.org/uploads/big/5dae5dc7f959958de47d01ea151264b1.jpg" /></a>
  83. </div>
  84. <p>We will keep raising awareness for our demand in upcoming elections. To help us, <a href="https://publiccode.eu/#action">sign the open letter</a>
  85. yourself, <a href="/contribute/spreadtheword#pmpc">spread the word</a>
  86. about the campaign and <a href="https://my.fsfe.org/donate">increase our funding</a>.</p>
  87. <h3>Save Code Share</h3>
  88. <p>A new copyright proposal is currently being discussed by the EU
  89. co-legislators. Part of this proposal is Article 13, an item that will hamper our
  90. ability to collaborate with each other online. Article 13 mandates that all
  91. online hosting service providers must install an upload filter that blocks any
  92. works from being uploaded that may constitute a copyright violation and must monitor
  93. their users as well as actively seek possible copyright infringements. These
  94. fundamentally flawed filtering algorithms will ultimately decide what code
  95. developers should be allowed to share. Beside all the problems upload
  96. filters come with, there are no known filtering technologies that could accurately and
  97. reliably identify whether Free Software code is being shared in accordance with
  98. its terms and conditions.</p>
  99. <div class="captioned" style="width:80%; margin: 1.5em auto;"><a href="https://savecodeshare.eu/">
  100. <img src="https://pics.fsfe.org/uploads/big/749327249c5ab6d7295f0735bcf22af7.png" /></a>
  101. </div>
  102. <p>To combat this legislation, we launched a website
  103. to <a href="https://savecodeshare.eu/">Save Code Share</a> in collaboration with
  104. Open Forum Europe. We aim to raise awareness of the topic and work to change the
  105. proposed legislation. We published
  106. a <a href="https://savecodeshare.eu/static/assets/WhitePaper-ImpactofArticel13onSoftwareEcosystem-SaveCodeShare.pdf">white
  107. paper</a> to explain Article 13's impact on free software developers and
  108. communities, and an <a href="https://savecodeshare.eu/">Open Letter</a> that has already been
  109. signed by more than 6000 individuals, organisations and companies.</p>
  110. <p>While the European Parliament prepares to vote on its main negotiating
  111. position regarding the EU copyright directive proposal in the beginning of 2018,
  112. several parliamentary committees have already issued their opinions on Article
  113. 13. Together with Open Forum Europe, we put pressure on the vote in Civil
  114. Liberties Committee that rejected the use of upload filters when it comes to
  115. hosting works online. Now, we have to make sure that the main parliamentary
  116. effort takes our concerns into consideration, and rejects Article 13 from its
  117. negotiating position with the co-legislators in the EU Council.</p>
  118. <h3>REUSE Initiative</h3>
  119. <div class="captioned right" style="max-width: 300px; width: 30%;"> <a href="https://reuse.software/"><img src="https://pics.fsfe.org/uploads/big/6533b3e666c82977417b40486c2343f7.png" alt="Reuse logo" /></a> </div>
  120. We launched our <a href="https://reuse.software/">REUSE Initiative</a>, which
  121. advocates <a href="https://reuse.software/practices/">best practices for
  122. conveying copyright and licence information</a> for software in a standardised
  123. way which not only humans can read, but computers as well. This step
  124. can help to automate many of the processes involved in working with
  125. Free Software licences, especially for large software projects with many
  126. repositories.
  127. <p style="margin-bottom:2em">The website hosts a video (<a href="https://reuse.software/">Webpage</a> /
  128. <a href="https://download.fsfe.org/videos/reuse/">Download</a> /
  129. <a href="https://vimeo.com/241079418">Vimeo</a>) that explains the three simple
  130. steps involved in making a project REUSE compliant. Developers will also find
  131. <a href="https://reuse.software/dev/">extra resources</a>. To demonstrate the ease of
  132. making a project compliant in practice, we host a <a href="https://git.fsfe.org/reuse">number of
  133. repositories]</a> that are REUSE compliant.</p>
  134. <center>
  135. <p>
  136. <video controls="controls" poster="/img/poster.jpg" crossorigin="crossorigin" width="80%">
  137. <source src="https://download.fsfe.org/videos/reuse/reuse_software_en_desktop.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' media="screen and (min-device-width:1000px)" />
  138. <source src="https://download.fsfe.org/videos/reuse/reuse_software_en_desktop.webm" type='video/webm; codecs="vp9, opus"' media="screen and (min-device-width:1000px)" />
  139. <source src="https://download.fsfe.org/videos/reuse/reuse_software_en_mobile.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"' media="screen and (max-device-width:999px)" />
  140. <source src="https://download.fsfe.org/videos/reuse/reuse_software_en_mobile.webm" type='video/webm; codecs="vp9, opus"' media="screen and (max-device-width:999px)" />
  141. </video></p>
  142. </center>
  143. <p>Furthermore, the FSFE is writing and
  144. providing <a href="https://git.fsfe.org/reuse/reuse">a tool that will help
  145. developers</a> make their software REUSE compliant. The goal is to
  146. package the tool into the repositories of the most popular GNU/Linux
  147. distributions, so that the barriers for adoption are as low as possible.</p>
  148. <blockquote> <p>Do you like what we are doing? Then <a href="https://my.fsfe.org/donate?referrer=yearlyreport">become a supporter</a> and help us to make a difference in 2018!</p> </blockquote>
  149. <h3>10th Legal and Licensing Workshop</h3>
  150. <p>Free Software licences are just as important as free code. The Free
  151. Software movement would not survive without the legal documents that allow and
  152. enforce software to be freely shared and modified. The Legal and Licensing
  153. Workshop (LLW) is probably the most important Free Software event you have never
  154. heard of. It is aimed at the niche made up by legal experts and professionals
  155. that work with the legal system supporting Free Software.</p>
  156. <p>In 2017 we held <a href="/activities/ln/llw.html">the
  157. workshop's 10th edition</a> in Barcelona. For us this is a landmark because we
  158. have managed to get the top legal experts from a wide variety of communities,
  159. public institutions and industries travel from all over the world to come
  160. together in an event like no other in the Free Software sector. This year's LLW
  161. compliance track was all about the tools used to enforce licences and how
  162. companies can support them.</p>
  163. <p>Free Software in public administrations was another important topic discussed
  164. during the event. The aim was to discover ways of how public administrations
  165. could be more transparent and more responsible with the funds when financing the
  166. development of software. The ideas legal professionals walked away with will
  167. deeply affect society as a whole.</p>
  168. <h3>Fiduciary Licence Agreement 2.0</h3>
  169. <p>The FSFE acknowledges that the licensing of code has been well served by Free
  170. Software licences, but managing rights and content within a project over long
  171. periods of time is still a complex issue. To fix this, the FSFE has drafted the
  172. Fiduciary Licence Agreement (FLA), a well-balanced contributor agreement which
  173. gives the trustee, responsible for managing the rights within a Free Software
  174. project, power and responsibility to make sure the contributed software always
  175. remains free and open. This ensures that the project, together with all the respective
  176. contributors, are protected against any misuse of power by a new copyright
  177. holder.</p>
  178. <p>This year we have <a href="/news/2017/news-20171013-01">updated the Fiduciary
  179. Licence Agreement (FLA) to version 2.0</a> which now also covers patents, and
  180. has been reworded to be compatible with more jurisdictions and to be easier to
  181. read.</p>
  182. <p>We have joined forces with <a href="http://contributoragreements.org">ContributorAgreements.org</a>
  183. and integrated the FLA-2.0 into its Copyright Licensing Agreement (CLA)
  184. chooser/generator. This makes the use of the FLA easier both for projects
  185. and for developers</p>
  186. <div class="captioned" style="width:50%; margin: 1.5em auto;">
  187. <img src="https://pics.fsfe.org/uploads/big/bf2575c8f03b97f10812d37f07ef4ebf.jpg" alt="R2D2 with IloveFS" />
  188. <footer> <p>FLA 2.0 makes it easier to ensure that contributed software always remains free.</p> </footer>
  189. </div>
  190. <h3>European Free Software Policy Meeting</h3>
  191. <p>Apart from travelling with our booth to the community's favourite event, the
  192. day before the opening of FOSDEM, we hosted the second European Free Software
  193. Policy Meeting. We met with Sebastian Raible, parliamentary assistant to Julia
  194. Reda, MP of the EU for the German Pirate party; Pierre Damas, Head of Sector,
  195. Digital Services at the Directorate General of Information Technologies of the
  196. European Commission; Jaana Sahk-Labi from the Estonian Permanent Representation
  197. to the EU; Laurent Joubert from the French government; and members of other Free
  198. Software advocating organisations.</p>
  199. <p>Together we discussed the progress of the Free and Open Source Software Audit
  200. (or FOSSA) programme, some of the Commission's plans for updating its Open
  201. Source Software Strategy, and national projects to promote Free Software in
  202. public administration and businesses.</p>
  203. <h3>Ask your candidates</h3>
  204. <p>The FSFE's community participated in the political campaigns during the Dutch
  205. general elections, the state of North-Rhine Westphalia as well as the German
  206. federal elections.</p>
  207. <p>Our team from the Netherlands developed <a href="https://freedomvote.nl/">freedomvote.nl</a> to give voters
  208. orientation on internet policies and Free Software. A similar tool was developed
  209. by the FSFE together with a &quot;Free Knowledge Coalition&quot; for the German
  210. federal elections;
  211. the <a href="/news/2017/news-20170829-01">&quot;Digital-o-Mat&quot;</a>. This tool made it into the news of multiple national media agencies as well as
  212. the public television and attracted tens of thousands of visitors to inform
  213. themselves about internet policy topics and Free Software.We also <a href="/news/2017/news-20170905-01">asked political parties
  214. in the German elections</a> about their position on Free Software in our
  215. &quot;Ask your candidates&quot; campaign-framework.</p>
  216. <div class="captioned" style="width:80%; margin: 1.5em auto;"><a href="https://digital-o-mat.de/">
  217. <img src="https://pics.fsfe.org/uploads/big/26d7acc366c621142b36c0b6a40b3ab5.png" /></a>
  218. </div>
  219. <blockquote><p>Do you like what we are doing? Then <a href="https://my.fsfe.org/donate?referrer=yearlyreport">become a supporter</a> and help us to make a difference in 2018!</p></blockquote>
  220. <h3>New git hosting service: git.fsfe.org</h3>
  221. <p>Sharing knowledge and collaboration are two of the core principle in the Free Software society. To encourage both, This
  222. year, <a href="/news/2017/news-20170616-01.html">the FSFE opened
  223. a Git hosting service</a> for our supporters with Gitea as a web
  224. interface.</p>
  225. <p>By visiting <a href="https://git.fsfe.org/">git.fsfe.org</a>, you can share
  226. and collaborate on a platform that fully respects your freedoms. Using the
  227. graphical web interface, you can open issue reports for bugs or feature
  228. requests. git.fsfe.org can host individual projects; complex multi-project
  229. repositories for organisations, or act as a mirror for another Git repository
  230. hosted elsewhere, like on GitHub or GitLab.</p>
  231. <div class="captioned" style="width:80%; margin: 1.5em auto;">
  232. <img src="https://pics.fsfe.org/uploads/medium/9603f21f88a4f490fd9a87a6655806e1.jpg" alt="FreedomBox Install Fest in the FSFE Village" />
  233. <footer> <p>FreedomBox Install Fest in the FSFE Village during SHA 2017.</p> </footer>
  234. </div>
  235. <h3>Investigate Europe</h3>
  236. <p>We supported a network of journalists to
  237. uncover <a href="http://www.investigate-europe.eu/en/new-investigation-europes-dire-dependency-on-microsoft/">the
  238. degree at which Europe's public infrastructure is dependent on proprietary
  239. software from one single provider: Microsoft</a>. Published in 13 newspapers,
  240. magazines and online media outlets in nine different languages, the report laid
  241. bare how one company has a stranglehold on our public institutions and the
  242. negative impact this has on our budgets and freedoms. The FSFE provided the
  243. investigative journalists with leads, data and testimonials we had accumulated
  244. over years and that served as the backbone to the story.</p>
  245. <h3>LiMux: A Lighthouse goes Dark</h3>
  246. <p>This year Munich's new mayor, Dieter Reiter, a self-confessed &quot;fan of
  247. Microsoft&quot;, went out of his way to undermine the work carried out by the
  248. administration to migrate away from their proprietary IT framework and pushed
  249. for a return to proprietary software on all levels. The FSFE president Matthias
  250. Kirschner explained the background to this decision in several talks, for
  251. example <a href="http://k7r.eu/recording-for-limux-the-loss-of-a-lightouse/">at
  252. the openSUSE Conference 2017 in May</a>, with the intent of spreading insight
  253. and awareness to other organisations and Free Software advocates.</p>
  254. <p>Along with The Document Foundation, KDE, and OSBA, we campaigned to keep
  255. Free Software in the city of Munich. We reached out to all members of the city
  256. council prior to the public hearing and we sent a call for action to our German
  257. speaking supporters, asking them to get in contact with politicians. The
  258. reaction was phenomenal. During the public hearing, politicians quoted some of
  259. our questions, and said that they had never received as much input from citizens
  260. and the press before. Unfortunately, all this public pressure did not alter their decision to transition away from LiMux, Microsoft Exchange had been phased in during the talks, and the decision to switch back to proprietary software has been taken.</p>
  261. <div class="captioned" style="width:80%; margin: 1.5em auto;"><a href="https://publiccode.eu">
  262. <img src="/news/2017/graphics/IloveFS-Projektionen.jpg" alt="IloveFS - PMPC" /></a>
  263. <footer> <p>Taking the "Public Money? Public Code!" campaign out onto the streets of Berlin.</p> </footer>
  264. </div>
  265. <p>Although this is sad to see, we should use this as an opportunity to evaluate the LiMux case, and see what we -- as the Free Software Community can learn from it -- for future migrations in the public administration. In his talks <a href="https://lwn.net/Articles/737818/">Matthias raised questions to support an evaluation by the Free Software community</a>.</p>
  266. <blockquote> <p>Do you like what we are doing? Then <a href="https://my.fsfe.org/donate?referrer=yearlyreport">become a supporter</a> and help us to make a difference in 2018!</p> </blockquote>
  267. <h2 id="numbers">FSFE's 2017 in numbers</h2>
  268. <p>Having precise data will help you visualise what resources we use to carry
  269. out our activities. With that in mind, the next section reduces FSFE's 2017 to
  270. figures and numbers. <em>(As a sidenote: A lot of the data in this section, for
  271. example the number from our budget, refers to 2016 because it only became
  272. available when 2016 was over, that is, in 2017.)</em></p>
  273. <h3>Booth, events and PR</h3>
  274. <p>The FSFE has attended <a href="/events/events">no less than
  275. 75 events in the last twelve months</a>. The events we attended were of all
  276. sizes, from meetups organised by local Free Software groups, to big fairs set up
  277. by public institutions and industries, to outdoor non-profit camps. Many take
  278. our representatives all over Europe and, in the last year, the FSFE has attended
  279. events in 13 countries: Germany, the Netherlands, Switzerland, Italy,
  280. France, Spain, Albania, Austria, Sweden, Portugal, Belgium, Greece and the
  281. USA. Apart from speaking and listening to others speak, we also set up our booth
  282. at 15 venues.</p>
  283. <div class="captioned" style="width:80%; margin: 1.5em auto;"><img src="https://pics.fsfe.org/uploads/medium/a61362c7d81161d3c48bffb1a08e37c3.jpg" alt="The FSFE village during SHA Camp 2017 in the Netherlands." /> <footer><p>The FSFE village during SHA Camp 2017 in the Netherlands.</p></footer> </div>
  284. <p>At our booth you can also get <a href="/contribute/spreadtheword.html">stickers, flyers and balloons</a>. These promote
  285. Free Software, warn about clouds, advise on using free formats, and so on. In
  286. fact, you don't have to visit our booth to get your hands on these goodies: you
  287. can ask us yourself for a boxful
  288. for <a href="/contribute/spreadtheword.html">your own event at
  289. no cost</a>. In the last 12 months we have sent out 233 boxes for the
  290. recipient. Since we are talking about rather big boxes, this amounts to
  291. literally thousands of stickers, flyers and other goodies.</p>
  292. <div class="captioned" style="width:80%; margin: 1.5em auto;"><a href="/contribute/spreadtheword.html">
  293. <img src="https://pics.fsfe.org/uploads/big/9bff2b57c191cf9b19dd3057e51ac675.jpg" /></a>
  294. </div>
  295. <h3>Budget</h3>
  296. <p>In 2017 we got the final data for the 2016 budget and can reveal now that,
  297. over the last four
  298. years, <a href="/about/funds/funds.html">FSFE's income came to
  299. between 350,000 and 450,000 euros</a>, but in 2016 the amount went up to
  300. nearly <a href="/about/funds/2016.html">650,000 euros</a>, which
  301. was a nice surprise. That is over a 45% increase with regard to 2015. Most of
  302. the growth can be attributed to extraordinary donations from our generous
  303. sponsors (up by over 83%), including an inheritance from a person who wants to
  304. stay anonymous, but the supporters contributions have also increased and have
  305. done so every year, not even flagging in the worst of the economic crisis.</p>
  306. <p>That said, at the FSFE we try to be as a frugal as possible and, although
  307. costs went up a bit in 2016, the increase didn't reach 9% with regard to
  308. 2015. The biggest costs in 2016 were in our efforts to increase public
  309. awareness, where we spent 142,965 euros; our basic infrastructure costs that includes among other things
  310. our personell and office costs for management and administration where we spent 130,082 euros and our legal
  311. work where we spent 117,336 euros.</p>
  312. <div class="captioned" style="width:80%; margin: 1.5em auto;"><a href="/about/funds/funds.html">
  313. <img src="https://pics.fsfe.org/uploads/big/8900ea542abd935c420ce569f333063d.png" /></a>
  314. <footer> <p>FSFE's costs in recent years.</p> </footer>
  315. </div>
  316. <div class="captioned" style="width:80%; margin: 1.5em auto;"><a href="/about/funds/funds.html">
  317. <img src="https://pics.fsfe.org/uploads/big/5e41e605aa8e2a93ab6ccc5c9f3eb256.png" /></a>
  318. <footer> <p>FSFE's revenues in recent years.</p> </footer>
  319. </div>
  320. <p>Proportionally, the biggest growth in costs happened in the Merchandising
  321. department, which grew 16%, from 32,142 euros in 2015 to 37,464 euros in
  322. 2016. This is in line with the amount of merchandising we gave and sold to our
  323. friends and followers, which increased by 13% from 2015. This is good news,
  324. since, as our main aim for merchandising is to spread our message as far and
  325. wide as possible, this shows that year after year, the number of people that are
  326. made aware of our campaigns and activities grows.</p>
  327. <p>Our best selling garment is without a
  328. doubt <a href="/order/order#tshirt-nocloud-black">the black
  329. &quot;There is no cloud...&quot; T-shirt</a>. So far in 2017 we have sold 450 of
  330. this smart and relevant item of clothing. But clothes are far from the only kind
  331. of <a href="/order">merchandising the FSFE distributes</a>.</p>
  332. <div style="text-align:center">
  333. <table class="merchandise">
  334. <tr id="tshirt-nocloud-black">
  335. <td class="image">
  336. <a href="/order/order#tshirt"><img src="/order/2016/tshirt-nocloud-black-front-small.jpg" /></a>
  337. <a href="/order/order#tshirt"><img src="/order/2016/tshirt-nocloud-green-front-small.jpg" /></a>
  338. <a href="/order/order#tshirt"><img src="/order/2016/tshirt-gnupg-blue-front-small.jpg" /></a>
  339. <a href="/order/order#girlie"><img src="/order/2016/girlie-ilovefs-darkblue-front-small.jpg" /></a>
  340. <a href="/order/order#hooded"><img src="/order/2017/zipped-fsfs-black-front-small.jpg" /></a>
  341. <a href="/order/order#hooded"><img src="/order/2017/zipped-fsfs-burgundy-back-small.jpg" /></a>
  342. </td>
  343. </tr>
  344. </table>
  345. </div>
  346. <h2 id="people">The people behind FSFE</h2>
  347. <p>Beyond events and numbers, FSFE is about the people that make up our
  348. community. In this sections we would like to introduce you to our comunity and
  349. some of our members that too often don't get all the credit they deserve.</p>
  350. <div class="captioned" style="width:80%; margin: 1.5em auto;">
  351. <img src="https://pics.fsfe.org/uploads/medium/835918851ba82ebc2d7675a5961da4f2.jpg" />
  352. <footer> <p>Attendees of FSFE community meeting 2017.</p> </footer>
  353. </div>
  354. <blockquote> <p>Do you like what we are doing? Then <a href="https://my.fsfe.org/donate?referrer=yearlyreport">become a supporter</a> and help us to make a difference in 2018!</p> </blockquote>
  355. <h3>Our community</h3>
  356. <p>There are 5 full time employees at the FSFE: Ulrike Sliwinski is our Office
  357. Manager and the person you are most likely to talk to if your phone our office;
  358. Polina Malaja is the coordinator of the legal team and our Policy
  359. Analyst; Erik Albers is our communications and community coordinator; Jonas
  360. Öberg is the FSFE's executive director; and, finally, there's Matthias Kirschner
  361. who is the president. We also employ 1 part-time employee: Max Mehl, who is our
  362. program manager and deputy coordinator of translations. This team is joined
  363. by <a href="/about/team#interns">interns</a> for three or more
  364. months to work on specific projects and help out in general as well as
  365. occasional contractors for specific tasks. This year our interns have been: Olga
  366. Gkotsopoulou, Fernando Sanjurjo, Erik da Silva, Jonke Suhr, Carmen Bianca Bakker
  367. and Kristi Progri.</p>
  368. <p>The <a href="/about/team#council">Executive Council</a> is
  369. the body that actually executes the wishes of the members. Currently, there are
  370. 4 members in the Council: Matthias Kirschner (President), Jonas Öberg (Executive
  371. Director), Patrick Ohnewein (Financial Officer) and Heiki Lõhmus (Vice President
  372. and Translations Coordinator).</p>
  373. <p>The <a href="/about/team#general-assembly">FSFE's formal
  374. members</a> are responsible for planning, budgeting, setting the agenda and
  375. electing and recalling of the Executive Council and the Financial
  376. Officer. During 2017, we counted on 28 members, including the the 2 prior
  377. presidents, Georg Greve and Karsten Gerloff, and the 4 members of the Executive
  378. Council.</p>
  379. <p>Then we have <a href="/about/team#eu-core-team">our European
  380. Core Team</a>, consisting of the formal members plus another 15 individuals from
  381. all over Europe, and they are the people that carry out the day-to-day tasks of
  382. the organisation on a voluntary or paid basis on core issues and coordinate the
  383. many volunteers that support Free Software.</p>
  384. <p>Finally we have the all important supporters. Supporters are sympathisers
  385. that have decided to officially support the FSFE
  386. by <a href="https://my.fsfe.org/donate">joining our supporter program</a>. During
  387. 2017 we surpassed the 1,600 mark and now have supporters in more than 40
  388. countries around the world, including most European countries as well as the
  389. Unites States and Australia.</p>
  390. <h3>Introducing some of our individuals</h3>
  391. <h4>Reinhard Müller</h4>
  392. <div class="captioned right" style="max-width: 300px; width: 30%;"> <img src="https://pics.fsfe.org/uploads/big/0a57bb700b1c1a45694230e1a846c0f2.jpg" alt="Reinhard Müller" /> </div>
  393. <p>Reinhard is from Lustenau, Vorarlberg, in Austria and has been part of the
  394. FSFE for over more than 10 years. Reinhard has always carried out anonymous,
  395. often ungrateful tasks that don't get much visibility, but, without which, the
  396. FSFE would grind to a halt.</p>
  397. <p>He started out maintaining the FSFE's website, coordinating the translation
  398. team and taking care of the Fellowship database. Then, from 2007 to 2017, he
  399. took over the financial side as FSFE's official Financial Officer. In that role,
  400. Reinhard has done everything related to managing the Foundation's money, from
  401. okaying invoices, to filing out our taxes.</p>
  402. <p>However, that hasn't made Reinhard an antisocial hermit, always poring over
  403. dusty books with ink-stained fingers. Quite the contrary: if there is something
  404. Reinhard enjoys more than columns and columns of figures it is direct contact
  405. with people at events. Reinhard loves participating in fairs and tradeshows at
  406. the FSFE booth. Next time you are at Linuxtage or FOSDEM, be sure to come by and
  407. say hello. You may get lucky and witness Reinhard's legendary T-shirt folding
  408. capabilities in action and live. Something worth beholding.</p>
  409. <h4>Ulrike Sliwinski</h4>
  410. <div class="captioned right" style="max-width: 300px; width: 30%;"> <img src="/about/people/avatars/sliwinski.png" alt="Ulrike Sliwinski" /> </div>
  411. <p>But, talking of booth service and merchandise, if there is one person you can
  412. always rely on to get you sweaters and stickers, that is Ulrike. Ulrike joined
  413. the FSFE as an office assistant in 2014 on part-time contract. When we realised
  414. how much she brought to the job, we quickly asked her to become our full time
  415. office manager.</p>
  416. <p>Ulrike, as Reinhard, carries out tasks that are largely invisible to the
  417. outside world, but without which the FSFE simply wouldn't be able to run. If you
  418. phone the FSFE up for any reason, it will probably be Ulrike who solves your
  419. problem. If you ask for one of our boxes of stickers and flyers for you event,
  420. it is Ulrike who packs it and sends it off.</p>
  421. <p>Ulrike has been described by some of her colleagues as the
  422. &quot;personification of German efficiency&quot; and as someone who will not
  423. leave a task alone until it is completed to her entire satisfaction. But Ulrike
  424. is also kind, helpful and friendly, making her the perfect host for our office
  425. and booth.</p>
  426. <h4>André Ockers</h4>
  427. <div class="captioned right" style="max-width: 300px; width: 30%;"> <img src="https://pics.fsfe.org/uploads/big/79386c5101e721876d01a761a9ba6c34.jpg" alt="André Ockers" /> </div>
  428. <p>One of the FSFE's main missions is to raise awareness among the general
  429. public, in companies, in the public sector, and among politicians. Stating the
  430. obvious, the first step towards effectively raising awareness, is putting out
  431. your messages in the language of your target audience.</p>
  432. <p>That is where people like André come
  433. in. André <a href="/contribute/translators/">translates</a>
  434. most, if not all, FSFE's output into Dutch, and he does so unprompted. André
  435. translated more than 80% of FSFE's site into Dutch, and you can expect him to
  436. have a translation of every news item or press release we put out within eight
  437. hours.</p>
  438. <p>André represents all of those selfless heroes that year in and year out help
  439. us reach people of all countries in their native languages.</p>
  440. <h2 id="end">At the end</h2>
  441. <p>We like to send a big big thank you out to our community, all the countless <a href="/contribute/contribute">volunteers</a>, <a href="https://my.fsfe.org/donate">supporters</a> and <a href="/donate/thankgnus">donors</a> who who made the work of FSFE possible in 2017. Your contributions are priceless and we do our best to keep the good work going in 2018.</p>
  442. <p>If you like what we are doing, <a href="https://my.fsfe.org/donate">join the FSFE as a supporter</a> and help us working for Free Software!</p>
  443. <p>Your Free Software Foundation Europe</p>
  444. <div class="captioned" style="width:50%; margin: 1.5em auto;">
  445. <img src="https://pics.fsfe.org/uploads/medium/48edc4bde88eb8847539f879c08bfa64.jpg" />
  446. <footer> <p style="text-align:center">FSFE in action! <br /><em>(Picture CC-BY-SA 2.0 by Julie Missbutterflies)</em></p> </footer>
  447. </div>
  448. </body>
  449. <tags>
  450. <tag key="front-page"/>
  451. <tag key="annualreport">Annual report</tag>
  452. <tag key="pmpc">Public Money Public Code</tag>
  453. <tag key="savecodeshare">Save Code Share</tag>
  454. <tag key="annual-report">REUSE</tag>
  455. <tag key="community">Community</tag>
  456. <tag key="transparency">Transparency</tag>
  457. </tags>
  458. </html>