Welcome to The Document Foundation Planet

This is a feed aggregator that collects what LibreOffice and Document Foundation contributors are writing in their respective blogs.

To have your blog added to this aggregator, please mail the website@global.libreoffice.org mailinglist or file a ticket in Redmine.


Tuesday
28 February, 2017


face

It has taken a while, but we’ve finally uploaded the last batch of presentations (for which we have video) from last year’s LibreOffice Conference in Brno, Czech Republic. You can see all of the videos in the embedded playlist below – click the list button in the top-left corner to navigate through the videos.

Alternatively, scroll on for a full list of presentations. You can do a search in your browser for topics of interest (eg “ODF” or “LibreOffice Online”), or for presenters. Happy viewing, and we look forward to seeing you at this year’s conference in Rome!

Full list of presentations:


Monday
27 February, 2017


face

Next up in our regular series of interviews with LibreOffice developers and contributors is Stanislav Horáček, who helps with localization in the Czech native language community.

LibreOffice contributor Stanislav HoráčekWhere are you from, and what is your nickname on IRC?

I am from the Czech Republic, and you can find me on IRC using the nicknames “horacek” or “strepon”.

Do you work for a LibreOffice-related company or just contribute in your spare time?

Just in my spare time – and that’s why there is a gap between my plans and reality 🙂

How did you get involved with LibreOffice?

Several years ago, I tried to set up custom page numbering in Writer, which was described in the built-in Help – but the Help page was written in half Czech, half English. Because I was glad that I discovered the solution of my problem, I decided to complete the page translation. As I found translating quite relaxing, that page was just a beginning…

What areas of the project do you normally work on?

Czech localization mainly; plus some corrections or bug reports for issues that I find when translating. Some time in the future, I would also like to go deeper into coding of extensions. They can be extremely helpful and it’s a pity that they are not widely promoted currently. For instance, I see a nice opportunity to use LibreOffice as a convenient front-end to another tools.

What was your initial experience of contributing to LibreOffice like?

From the beginning, I met helpful and encouraging people and I really appreciate that most of the discussions are constructive, with facts more important than feelings. I think these are the most precious properties that the community has; they made LibreOffice become my number one open source project. On the other hand, whenever I see a lack of them, I image that one more potential contributor could be demotivated…

Moreover, LibreOffice has a great advantage in that it is so widespread. I was – and still I am – impressed that you can really easily make improvements which will appear on screens of millions of people.

Which is your preferred text editor?

For LibreOffice related stuff, I use a universal text editor called Geany. But in general, I like also specialized editors or IDEs.

What do you do when you’re not working on LibreOffice?

I would say my hobbies are typically Czech, like beer drinking 🙂 You can also see me during the holidays in some of the European mountains, amongst lots of other Czech tourists. And who knows, maybe one day contributing to free software will be our national interest as well…

Thanks Stanislav. And to anyone reading this who wants to help out with translation and localisation of LibreOffice, get involved! Your contributions can make a huge difference, and will help to bridge digital divides across the globe.


face

Italo Vignoli hat mich über meine Arbeit bei der Document Foundation befragt. Das englischsprachige Interview findet ihr im Blog der Stiftung.


face

As you may know i was participating in this year Gerrit User Summit, 12th-13th November 2016, followed by Developer Hackathon in Mountain View, CA.

There were plenty of great talks, including EMail ingestion, Atomicity with change-sets, Gerrit analytics, Update on new and shiny UI, called PolyGerrit, based on Google’s own Polymer project, Zero-downtime Gerrit upgrades and what’s new and in Gerrit 2.12, 2.13 and coming next 2.14 releases.

I gave a talk about the status of my work on implementation of Bazel build for Gerrit.

After the user conference we had couple of days of Gerrit developer hackathon, where I continued to work on Bazel build implementation for Gerrit, approaching the feature parity with Buck build implementation. During the hackathon I uploaded a CL for removing Buck build, so that the new Gerrit version is going to be built and released with Bazel only.

I would like to thank Firma Frobese GmbH for sponsoring travel cost for my participation.


Wednesday
22 February, 2017


face
  • Excited to be demoing a new Ubuntu / Snap based solution alongside Ubuntu and Nextcloud at MWC Barcelona.
  • Also pleased to see AMD release Ryzen Making 16 threads accessible to everyone - helping your LibreOffice compiles (and load times of course too); good stuff.

face

FOSDEM banner

FOSDEM is the biggest gathering of free and open source software (FOSS) developers in Europe. It takes place every year in early February, at the Université Libre in Brussels, and it’s a great event for discovering new technology, exchanging ideas and generally enjoying the community around FOSS.

This year, the Open Document Editors devroom was home to many talks and presentations about LibreOffice – including development, design, documentation, LibreOffice Online and other topics.

We have now uploaded all of the videos to our YouTube channel, so click play below to start watching (and use the icon in the top-left to choose others in the playlist). Alternatively, scroll on for a full list of presentations and links to the videos.

Full list of presentations:

Like what you see? Click here to get involved – you too could be presenting awesome new technology in the future!


Tuesday
21 February, 2017


face
  • Mail, financials with Tracie, call with Eloy; then Ash & Kendy. Built ESC stats. Out to cubs in the evening with M. - ran a code-breaking table with several fun encoding schemes.

face

The typical day of an executive director

My work consists of both administrative tasks – like accounting, correspondence, budget and contractual topics – as well as overseeing our team and making projects come to life. Whenever I have some spare time, I try to contribute to the German native-language community, the marketing project and our infrastructure.

The e-mail flow is quite massive with a couple of hundreds e-mails per day coming in as personal messages as well as on dozens of mailing lists, so my morning usually starts with prioritizing tasks and mails to structure my day’s work.

2016 so far for LibreOffice and for TDF: your personal perspective

2016 has been an extremely exciting year for us. LibreOffice adoption is continously growing, so is the community, and we welcomed several new members to our Advisory Board. Lots of events around the world took place, and every year when we compile the annual report it becomes obvious how much enthusiasm, dedication and passion our contributors have for LibreOffice.

What do you see as the most important challenges for TDF in 2017 and beyond?

During the last years, TDF has grown, which comes with costs in terms especially of time to define processes, establish structures and learn together. Right now, we gained routine for many tasks, so there’s room to grow and run more exciting tasks and projects.

With regards to LibreOffice, I think that mobile devices and online options are key to success, and of course, lowering the entry barriers to our community even further and growing the volunteer base, mentoring newcomers and keep people attracted to the community will always be an important part of our agenda.

Where do you see TDF and LibreOffice in 2020? And in 2025?

Looking at the short history of time during which LibreOffice and TDF have grown – we’ve been on the market since September 2010 – it’s hard to foresee where we will be in a couple of years. What we see and have today is way beyond our dreams, so I don’t even dare to guess what will come in the future. My hope and sincere conviction is that TDF will be a strong home for our projects, a welcoming and supportive environment for contributors from all around the world, breaking the barriers of languages, cultures, religion, beliefs and even timezones. I really feel like I have friends around the world, which is a wonderful feeling.

You have been with the project since day one: which is your opinion about what we have achieved, and what we could have achieved?

I am very proud of what we have achieved and where we stand. I feel sincere gratitude for being part of something so very special, for having friends around the world, for having the chance to contribute to something that does good for so many. The support we’re seeing from all over the world is just amazing.

Of course, we always can get better. Lowering the entry barriers even


Monday
20 February, 2017


face
  • Poked mail; sync. with Kendy, consultancy call. Out for a walk, lunch. Back to financials / 2017 projections and calls.

Sunday
19 February, 2017


face
  • NCC in The Stable in the morning; Tony & Anne back for lunch, played a game; quartet practice, tea & read babies.

Saturday
18 February, 2017


face
  • Up rather late; breakfast; slugged variously. Driven home with babes and more Green Ring-ness. Relaxed variously & watched Robin Hood, Prince of Thieves.

Friday
17 February, 2017


face

I worked again on the language setting of ODFAuthors content for some hours. I was able to change the language setting of a lot of content items and there are only a smaller list of remaining items. Seemed I could see the light at the end of the tunnel.


face
  • Up; worked through the morning on the mail and task backlog. Out for a walk to see some ponies with the babes at Thorpness.
  • Back for lunch, and then to tackle the plumbing problems. Attacked an amazing amount of congealed fat in the sink plumbing - simply extraordinary; eventually had to cut the pipe-work out in sections and replace it with H's help.
  • Relaxed in the evening with some fine food. Couldn't sleep, hacked on socket code instead.

face

Spot the difference between the two C++ programs

struct S { int a = b, b; };
int main() { return (new S())->a; }

and

struct S { int a = b, b; };
int main() { return (new S)->a; }

Right, the first one terminates cleanly with exit code zero, while the second one does whatever it deems necessary to counter undefined behavior.

Why is that? The expression new S() means direct-initialization, which for () means value-initialization. Class S has a default constructor that is not user-provided, not deleted, and non-trivial (because non-static data member a has a default member initializer). So the instance of S is first zero-initialized, then default-initialized. Zero-initialization means that a and b are initialized to zero. Default-initialization for S means that the default constructor is called, which means that a is initialized from its default member initializer, by copying zero from b (and then b is default-initialized, leaving it alone).

On the other hand, just new S (without the parentheses) means just default-initialization (without previous zero-initialization). So, again, default-initialization for S means that the default constructor is called, which means that a is initialized from its default member initializer, copying the uninitialized b (and then b is default-initialized, leaving it uninitialized)…

Too subtle? Probably.



face

Today marks five years since The Document Foundation (TDF) was legally incorporated in Berlin, Germany. We want to celebrate this anniversary by highlighting some recent activities and events from our Native Language Projects. These communities have been instrumental to the growth of TDF and LibreOffice, and are one of our most important assets.

Turkey

The Turkish community recently attended the Academic Informatics Conference 2017 in Aksaray, from 8 to 10 of February, with several LibreOffice related activities.

A general presentation was done by Muhammet Kara and Gökhan Gurbetoğlu in the first session (first half of the first day).

In the second half of the first day, the attendees were introduced to the LibreOffice development environment, and the tools used in the process (Gerrit, Vim, Git…). The attendees were walked through the process of joining the LibreOffice community, and building the LibreOffice source code for the first time.

Attendees who had relatively older computers were provided with SSH access to a 32-core machine, courtesy of TUBITAK ULAKBIM. The last session (first half of the second day) was held like a hackfest. Questions from attendees were answered by the speakers.

LibreOffice community members were pleased to see that the participants were eager to learn about the software, and together they established a WhatsApp group for further communication. A more detailed presentation about LibreOffice development activities in Turkey was given by Gülşah Köse and Muhammet Kara on the last day (morning) of the conference.

Taiwan

The first LibreOffice QA Sprint in Taiwan – organized by Software Liberty Association Taiwan and supported by two professors of the Department of Computer Science and Engineer, National Cheng-Kung University: Professor Joseph Chung-Ping Young and Alvin Wen-Yu Su – was held in Tainan City on December 17, 2016. In this four-hour sprint the attendees found and reported many issues. Attendees were students, teachers, employees of enterprises and governments, LibreOffice developers and lecturers, and all four TDF members in Taiwan.

Early in the afternoon, a live video-session with Italo Vignoli, one of the core members of The Document Foundation, gave most of the attendees exposure to the international community for the first time.

Han Lu, a student in NCKU, summarized the issues found by attendees. After the summary, Franklin Weng explained how to report bugs on the LibreOffice Bugzilla. Also, Cheng-Chia Tseng introduced the Pootle translation platform for LibreOffice and gave some tips on how to translate LibreOffice.

Japan

LibreOffice Kaigi 2016.12, Japan’s annual LibreOffice conference, was organized in early December 2016 with great success! The word Kaigi is the Japanese word 会議, which means conference. The name means not only Japanese regional, but also Japanese users-specific.

Around 25 people gathered and enjoyed several talks (migration to Open Document Format in Taiwan, by Franklin Weng, LibreOffice/ODF and styles, maintaining Math and Japanese translation), along with a few lightning talks and a panel discussion.


Thursday
16 February, 2017


face

I’m working with the current ODFAuthors site for the migration to a new Plone version. I change the language settings for nearly all content items to language independent. I had to do this manually.


face
  • Poked at socket code a lot in the morning; drove to Aldeburgh with the family - listened to the Green Ring Conspiracy in the car. Chat with Philippe, ESC call. More hackery.

face

LibreOffice takes accessibility seriously, and we want to make our program as enjoyable for users with disabilities as it is for everyone else. That means we care about motor impairments and, for instance, we always provide different ways for interacting with the software. And, of course, accessibility covers a wide range of visual handicaps related with color blindness, which are taken into account to ensure that information is not only coded by color, and also to account for cases of complete blindness, where a screen reader is necessary.

Not every modification in the past went well, and we are facing some issues with the latest version. For instance, Jean-Philippe Mengual mentioned at the LibreOffice conference in Brno that it is not possible to access styles in the sidebar. While we have human interface guidelines (HIG) for the sidebar UI, it lacks on advices regarding accessibility. Therefore, the UX and the accessibility teams analyzed the current state regarding keyboard navigation and summarized the outcome into a draft that should be added to the sidebar HIG.

A lot of good ideas were discussed, though mostly discarded. For example, the access to relevant content could be simplified when some less important features are excluded from the the navigation sequence and thereby ‘hidden’ from the screen reader. The striking argument is that disabled people work together with normal users and potentially face a situation where an unexpected state occurs. So one axiom is to make all functions accessible. Another rationale is to make simplicity paramount before consistency or clearness. Having different shortcuts for parts of the UI that technically do not belong together might sound reasonable but complicates the interaction. And finally, we do not want to change the learned interactions and keep things as much simple as possible.

Guidelines

Activation

  1. Activate the accessibility mode with F6.
  2. Navigate using F6 starts at the main menu, followed by the open toolbars, and finally the sidebar.
  3. On the sidebar, land first on the open deck‘s title bar, or the sidebar‘s tab bar when the deck is closed.
  4. Leave the accessibility mode with Ctrl+F6 and go back to the document position where the navigation has started.
  5. Use Escape to go back one step in the navigation, meaning from the content to the content panel title and then to the document.

Tab bar

  1. On the tab bar, land on the tab of the active deck or the tab of the first deck when the sidebar is closed.
  2. Jump to next/previous tabs with arrow keys including the configuration button.
  3. Jump to the title of the first content panel using Enter. In case of no content panel go to the first control with Enter.
  4. Expand or collapse the deck with space but stay at the tabbar.

Deck

  1. Cycle through the content panels (e.g. Styles, Character, Paragraph etc.) per arrow up/down.
  2. Make all parts of the deck accessible including the deck title.

Content panel title

  1. Traverse the content panels of a deck using the arrow

face
https://farm4.staticflickr.com/3924/32549564340_4d0990cfa4_o.png

PDF supports screen annotations, which means it’s possible to play embedded and linked videos on top of a static image. Given that LibreOffice also supports videos, it made sense to add support for this in our PDF export filter. First, thanks to PMG who made this work possible. This is currently added for Writer and Impress.

Linked videos

Linked videos are the situation when the video is not part of the document itself, but it’s located somewhere else, e.g. a http:// location. This is helpful if you want to email around a PDF file, and want to avoid sending large files when it has video content.

tdf#104841 is about this situation, first I added support for linked videos in Impress, then also in Writer.

The result can be played using Adobe Acrobat Reader — for some reason okular on Linux is a bit confused about http:// URLs, wants to convert them to relative ones, and then fails as of today.

Embedded videos

https://farm3.staticflickr.com/2666/32115175413_ec6f64243a_z.jpg

tdf#105093 is the embedded video case, this is handy in case you want to create an entirely self-contained PDF, where even the video content is inside the PDF file as an embedded file.

After Impress support (and a trick around Draw vs Impress shapes) the Writer part wasn’t too complicated.

Regarding the situation around various video containers and codecs, the above code is quite agnostic. :-) On the LibreOffice side all we require is to be able to extract a key frame from the video to provide a preview image, so e.g. on Linux the support depends on what gstreamer plugins you have installed. The video content is written to the PDF file as-is, so again if it will work in the PDF reader is up to the reader’s codec support. On Linux e.g. okular uses vlc for video playback, so the range of supported formats is quite wide. The same is true on Windows, what I personally tested is LibreOffice’s VLC backend and the embedded QuickTime player in Acrobat Reader.

All of this is available on LibreOffice master towards 5.4.


Wednesday
15 February, 2017


face
  • Awoke again to the dulcet tones of the neighbours extension being drilled / compacted / etc. Hey ho - they get to enjoy our early morning piano practice I suppose.
  • Built ESC stats. Most encouraged to see that the German comment count has dropped by ~10% in the first two weeks of February - ~320 lines fewer (of 3600) thanks to: Johnny M, Michael Stahl (RedHat), Katarina Behrens (CIB), and Lukas Röllin - wonderful.
  • Sync. with Ash; interview in the evening.

Tuesday
14 February, 2017


face
  • Nice set of Valentines Day cards for the whole family; dug away at drear contract review much of the day.
  • Watched and fast-forwarded some James Bond for H. and N. in the evening. Hacked until late on improved non-blocking socket code.

face

I love free software

LibreOffice is free software. This means that it’s totally free of charge to download and use – a benefit that many people appreciate. But free software is about much more than just saving money; it’s about having freedom to control our own computers and devices. Free software is incredibly important for digital freedoms, security, privacy and civil rights. All together, free software is a movement.

So what defines free software, compared to proprietary software? The Free Software Foundation outlines four key freedoms that we should have as users of the software. Here’s a summary:

  • The freedom to run the program as you wish, for any purpose
  • The freedom to study how the program works, and change its source code
  • The freedom to redistribute copies so you can help your friends and colleagues
  • The freedom to distribute copies of your modified versions to others, so that they can benefit

Fundamental to this is the license under which the software is made available. LibreOffice is released under the Mozilla Public License Version 2.0, a free and open source license that lets everyone share the program – and gives everyone the right to study how it works and modify it.

The importance of freedom

Free software is essential to the success of LibreOffice. Because of the license it uses, anyone can join our community and help to improve the software. The low cost of ownership means that developing countries can reap the benefits of LibreOffice without having to spend large amounts of money. And no company can take LibreOffice and lock it up as proprietary, closed software forever.

Now, most LibreOffice users are not software developers. And they may ask: “Apart from the low cost, how do I benefit from LibreOffice being free software?” The best response to this is: with free software, you control your computer. With proprietary, closed software – where you can’t study how it works or modify it – the software controls you. Sure, some proprietary software may look tempting in terms of technical features, but without the four freedoms listed above, you don’t truly have control of your software, your computer and your data. Someone else does.

One common misconception is that free software means no money for developers. This simply isn’t true! While the software itself is free to download, many companies make money by providing extra services on top: documentation, technical support, and bespoke features. Look at our certified developers, for instance, and then consider all of the companies making money around the GNU/Linux ecosystem. You can develop free software, help make the world a better place, and still earn a good living as well!

A big thank you

Of course, LibreOffice is just one example of a well-known free software project. Others include GNU/Linux, Firefox and KDE – but there are thousands more. Today we celebrate the vibrant, rich and active communities around the web that are working


face

The Document Foundation is an independent, charitable entity and the home of LibreOffice. We have followed the developments in Munich with great concerns and like to express our disappointment to see a minority of politicians apparently ignoring the expert advice for which they’ve sought.

Rumours of the City of Munich returning to Microsoft Windows and Microsoft Office have been regularly leaking since the election of Mayor Dieter Reiter, who was described as a “Microsoft fan” when interviewed by StadtBild magazine in 2014.

Mayor Dieter Reiter asked Accenture, a Microsoft partner, to produce a report about the situation of the City of Munich’s IT infrastructure, that resulted in a 450-page document where the main issues were identified as organizational ones and not related to open source operating systems and applications.

In the age of open data and transparency in political decision making, we are glad that the report is now made available to the general public (https://www.ris-muenchen.de/RII/RII/DOK/SITZUNGSVORLAGE/4277724.pdf).

According to the report, only a minor percentage of users (between 18% and 28%, based on different applications) had severe issues related to software, which could be solved by migrating these users to Windows and MS Office. Incidentally, 15% of users acknowledged severe issues related to MS Office.

In fact, the Accenture report suggests decoupling the operating system and application to reduce dependencies at client level. To ensure this, both Windows and LiMux should be deployed in a basic configuration, which includes operating systems as well as applications, such as LibreOffice, calendar and e-mail, required by all units and self-service providers. The basic configuration should be extended depending on the application.

In spite of the suggestions, on Wednesday, February 15, Munich City Council will discuss a proposal – filed by a minority of city councillors – to install Windows 10 and MS Office 2016 on all workstations by 2020. This would cost taxpayers close to 90 million euro over the next six years, with a 35% aggravation over the 66 million euro figure suggested by Accenture.

In addition, according to estimates provided by Green Party councillors, another 15 million euros should be spent to replace or upgrade PCs which are perfect for a small footprint operating system such as Linux, but cannot support even a Windows 10 basic configuration.

Last, but not least, most expenditures related to the purchase of Microsoft licenses will contribute to the GDP of Ireland (where all Microsoft products sold in Europe are sourced from) rather than to local enterprises who support the open source solutions deployed today. This is a rather striking difference in the allocation of taxpayers money, which should be carefully considered.

Apart from the cost aggravation, the proposal under discussion ignores the main reason behind the decision to migrate from proprietary to open source software by the City of Munich, i.e. independence from a single software vendor and the move from proprietary to standard document formats.

In fact, although the proposal associates MS Office document formats


face

The Document Foundation ist eine unabhängige, gemeinnützige Stiftung und die Heimat von LibreOffice. Wir haben die Entwicklungen in München mit großer Besorgnis verfolgt und sind enttäuscht darüber, dass eine kleine Gruppe von Politikern offensichtlich den Rat genau derjenigen Experten ignoriert, die sie zuvor selbst aufgesucht haben.

Seit der Wahl von Oberbürgermeister Dieter Reiter sind regelmäßig Gerüchte über eine Rückkehr der Stadt München zu Microsoft Windows und Microsoft Office im Umlauf. Reiter wurde in einem Interview mit dem stadtbild-Magazin im Jahr 2014 als „Microsoft-Fan“ beschrieben.

Oberbürgermeister Dieter Reiter hat den Microsoft-Partner Accenture beauftragt, einen Bericht über die IT-Infrastruktur der Stadt München zu erstellen. Das Ergebnis war ein 450 Seiten langes Gutachten, in dem nicht etwa Open Source-Betriebssysteme und -Applikationen, sondern vielmehr organisatorische Themen als Problem identifiziert wurden.

In Zeiten von Open Data und Transparenz im politischen Entscheidungsprozess freut es uns, dass dieses Gutachten nun auch der Allgemeinheit zur Verfügung gestellt wird (https://www.ris-muenchen.de/RII/RII/DOK/SITZUNGSVORLAGE/4277724.pdf).

Dem Gutachten zufolge hatte nur eine sehr kleine Zahl von Anwendern (je nach Applikation zwischen 18% und 28%) größere Probleme mit den Programmen, was durch die Umstellung ihrer Arbeitsplätze auf Windows und MS Office behoben werden könnte. Bemerkenswert ist aber, dass 15% aller Anwender angegeben haben, auch größere Probleme mit MS Office zu haben.

Das Accenture-Gutachten schlägt eine Trennung von Betriebssystem und Anwendungen vor, um die clientseitigen Abhängigkeiten zu reduzieren. Um das zu gewährleisten, sollen sowohl Windows als auch LiMux jeweils in einer Basiskonfiguration zur Verfügung gestellt werden, was sowohl Betriebssystem als auch Applikationen beinhaltet, beispielsweise LibreOffice, Terminverwaltung und E-Mail, wie sie von allen Abteilungen benötigt werden. Diese Grundkonfiguration soll abhängig von der jeweiligen Anwendung erweitert werden.

Trotz dieser Empfehlung wird der Münchener Stadtrat auf Initiative einiger weniger Politiker am Mittwoch, den 15. Februar, den Vorschlag diskutieren, bis zum Jahr 2020 sowohl Windows 10 als auch MS Office 2016 auf den städtischen Arbeitsplätzen einzuführen. Das wird den Steuerzahler an die 90.000.000 € (in Worten: neunzig Millionen Euro) über die nächsten sechs Jahre kosten, eine Steigerung um 35% gegenüber den von Accenture ursprünglich vermuteten 66 Millionen.

Zusätzlich sollen laut eines Kostenvoranschlags von Stadträten der Grünen weitere 15.000.000 € (in Worten: fünfzehn Millionen Euro) dafür ausgegeben werden, alte Computer aufzurüsten oder zu ersetzen, die sich zwar perfekt für ein ressourcenschonende Betriebssystem wie Linux eignen, aber nicht einmal eine Windows 10-Basiskonfiguration unterstützen würden.

Zu guter Letzt wird ein Großteil der Ausgaben im Zusammenhang mit dem Kauf von Microsoft-Lizenzen primär die irische Wirtschaft fördern – denn von dort stammen alle in Europa verkauften Microsoft-Produkte – anstatt örtlichen Firmen zugute zu kommen, die bereits die schon vorhandenen Open-Source-Lösungen betreuen. Das ist eine ziemlich auffällige Verschiebung bei der Verteilung von Steuergeldern, die entsprechend berücksichtigt werden sollte.

Ganz abgesehen von der


face

a Free Software developer :-)

I love Free Software!
I love Free Software!


Monday
13 February, 2017


face
  • Up lateish; babes on half term holiday - team meetings; E-mail, code review with Ash. E-mail deluge, board call, chase Cyber Essentials certification; dinner, more paperwork.

Sunday
12 February, 2017


face
  • Overslept vigorously, to the stable for NCC; Claire explained Ephesians 1 well - helpful; back foor lunch. Off to pick up littlies but too late for the service. Lots of stories. Played with them in the afternoon; stories, bed.

Saturday
11 February, 2017


face

In this case, one image is better than 1,000 words, as the histogram represents donations during the first 10 days of each month, since May 2013, and doesn’t need any further comment. LibreOffice 5.3 has triggered 3,937 donations in February 2017, 1,800 more than in March 2016, and over 2,000 – sometimes over 3,000 – more than any other month. Donations are key to the life and the development of the project. Thanks, everyone.

 


face
  • Up very late indeed, slugged in bed chatting to J. & bigger babes. Late breakfast, H. out swimming with Alex, Elise & H?. Spent my time mending the toilet - new float valve is much larger than the previous one - requiring odd angles, silicone bodgery and worse.
  • Out for a walk with J. on the heath - nice. Swimmers home, for a Bourne movie with N. followed by tea & card games. Dropped Alex home. Put babes to bed.

Eike Rathke: 42

11:42 UTC

face

Today is the 42nd day of the year.
Today is Boomtime, the 42nd day of Chaos in the YOLD 3183

Older blog entries ->