The Document Foundation Planet


December 01, 2015

Official TDF Blog

LibreOffice: Advent Tip #1

Ask LibreOffice

ASK LibreOffice

LibreOffice FAQ

LibreOffice FAQ on TDF Wiki









We are approaching the end of 2015. We have decided to celebrate the month of December with our own version of the Advent Calendar: one simple tip per day, to make the use of LibreOffice more enjoyable or more productive.

Today, December 1, we start by pointing LibreOffice users to Ask LibreOffice and to the FAQ on TDF Wiki. These two resources provide a number of tips based either on questions asked by users (Ask) or on the experience of long time LibreOffice users …

by Italo Vignoli at December 01, 2015 01:51 PM

Community, as seen from the sky

drone5During the Aarhus Conference, we have organized the usual group picture to celebrate the community, leveraging the architectural features of the DOKK1.

We have gathered on one of the large staircases leading to the first floor of the building, which were the ideal setting for a group picture.

To the surprise of the group, in addition to the usual camera picture, Dennis Borup Jakobsen has organized a “drone” session, to get a different view of the community, as seen from the sky.

The result is amazing, and has provided a different point of view on the community.



by Italo Vignoli at December 01, 2015 12:26 AM

November 29, 2015

Charles Schulz

Does the Open Document Format still matter?

One of the core topics of this blog -at least one of the main reasons it came to existence- was open standards: their benefits, their advantages, and their value as a fundamental component for digital innovation and ultimately software freedom. This is still the case of course, but today I will try to show how one open standard in particular, ODF, has failed in its approach until now and could very well make a remarkable comeback.

This is not to say that ODF is a bad idea or that it is not a good standard; it is all this and much more. However I have realized with the hindsight of several years since it became an official ISO standard that the expectations about its adoption and its development have been defined the wrong way. Hence the title of this post.

ODF-logoFew people know that the inception of ODF took place at the European Commission, when someone gathered a few consultants as well as a few employees of Sun Microsystems and other vendors, and told them that in order to get rid of a locked down market for office suites, they had to design a truly advanced format that would be submitte to ISO. The theory was that once there was a standard then the entire industry and the users themselves would feel confident using it, therefore bringing a level-playing field to the market. I was one of the people who actually bought into this theory and expressed it many times on this blog. After all, there had been many precedents, so the theory has some strong credibility even today. I now think ODF had and still has a tremendous value, but I also believe we had it backwards. Why? I think that experience is showing that in the present case, what works isn’t the availability of one standard leading to the development of an ecosystem. What works is a combination of factors that are rather independent from ODF but are strongly related to its implementation.

A well-established and indenpendant open source project with a real, multi-tiered ecosystem
I’m obviously referring to LibreOffice here; but it’s not like there wasn’t real momentum in the days of the old project. LibreOffice, however, brought two new benefits to the mix: a true independance from vendors which had not been acheived before and real progress on the development of the codebase. After the first two years of life of the LibreOffice project, results started to show, and the ecosystem around started to grow with LibreOffice. The ecosystem itself is growing both in size and the diversity. It is possible to find service providers of several kinds and combine them in order to have the full scope of service for a migration: migration experts, developers, support providers and trainers.

The fallback on Microsoft Office
Many people were highly skeptical when Redmond announced their support of ODF inside Microsoft Office; but starting with Microsoft Office 2010 the native implementation was one of quality, despite implementation differences with its Free Software competitors. Then it was feared that this ODF support would actually slow down migrations to and LibreOffice. It is not clear whether it did, but I actually happen to think that organizations considering a migration away from Microsoft Office felt more comfortable moving forward into these migrations knowing that MS Office would still be ODF capable. How much of this reverse psychology was foreseen by anyone having a take in this game is still something I’m unclear about.

You’re not alone anymore
The truth is, for many years a few pundits and experts could pull names of more or less prestigious entities that had migrated to and LibreOffice. Some of these names were public and were circulated ad nauseam. But more names started to appear on the list, and with these names, others felt LibreOffice deployments were no longer extraordinary. Migrations started to happen here and there, and soon entire regional and national governments decided to use LibreOffice. You no longer have these two, or perhaps three examples you can quote; there are much more and this creates a momentum. In other words, “people start to talk”.

In thidove-logo-2012s broad picture ODF matters little; it is not out of the equation of course, but my point is that the market still thinks in terms of solutions, services and products. It does not seem to base buying decisions on standards. Even if the development of ODF had been more active -it has recently become so, thanks to Jos van den Oever, the new chair of the OASIS ODF Technical Committee- it would have mattered little. The benefits of ODF are real, but to most CIOs they are not a reality unless translated into an actual solution, product or service they can consider relying on. In a sense, it feels like answering the vendor lock-in problem with an open standard as a file format is worse than no vendor lock-in: the CIO wants something actionnable.

The future, fortunately, looks good for ODF. In fact, it has never look better than today. ODF has stopped being the supposed foundation on which an entire ecosystem might soar and has now become the actual solution to several problems once the migration to LibreOffice has been achieved. Some of these problems are about documents archival and reuse; some others may be about simple or complex round trip interoperability. If, however, the recent momentum on the development of ODF continues, ODF will be able to expand and support the featureset of software like LibreOffice and be reused in innovative ways in content management systems and social networks through metadata and version management.

In 2006, ODF was defined as the driver for open source adoption and the golden solution to the “Office entanglement” problem. It never really did perform such roles mostly because the circumstances and time were not allowing ODF to fulfill its potential. In 2015, the landscape has changed in many ways; ODF can now be all it was meant to be by its authors through solid tools such as LibreOffice, active development and a vibrant ecosystem.

by Charles at November 29, 2015 09:21 PM

November 28, 2015

Michael Meeks

2015-11-28 Saturday.

  • Up earlyish; tried (somehow) to get GStreamer to work on Miriam's OpenSUSE 13.1 - enabled packman, burned many unhappy minutes wrestling with different versions of different things, broken gst pipelines, switching packages incrementally between vendors, installing more and more bits. I used to like VLC because it was one big lump of download that "just worked" until they decided to go with the "one hundred pieces any developer with lots of time can just plug together and debug, while no user can install or use anymore". Eventually discovered that deleting my ~/.cache/gstreamer, ~/.gstreamer* made things suddenly work: nice, sadly don't have the bad files now.
  • Breakfast - cheering. Nicki over with kids - plugged at reading around SalGraphics usage; more horrors.
  • Lunch, out to buy a new fireplace/surround in Cambridge. Anything to be rid of the 30's monstrosity we have; an interesting selection - left the esthetics to J.
  • Home; back to SalGraphics - eventually discovered that (depending on backend) we can and do end up with multiple wrappers of the same underlying OS resources; which causes my issues. Something like a rampant mis-use of multiple fdopen's on the same underlying file; fun. At least it makes sense finally.

November 28, 2015 05:37 PM

November 27, 2015

Michael Meeks

2015-11-27 Friday.

  • Mail chew; hackery; lunch; interviews. Poked at the SalGraphics lifecycle - which is a complete mystery; inconclusively and at length; rather important if you want to key a cache/double-buffer of the screen contents on it.

November 27, 2015 09:00 PM

Official TDF Blog

Behind the scenes at TDF: Jan Iversen, mentoring development lead

janiversensmallI started working for Document Foundation in November. I live and work in southern Spain, Malaga, a nice warm place. I wrote my first program in 1975, so I have been active in the pre-unix, pre-linux, pre-pc worlds, and have been involved in developing drivers, micro kernels and compilers. I retired from my international companies in 2011, dedicating time to open source.

LibreOffice is one of the most complex and biggest open source software packages, and at the same time one of the most well known. Today, having developed open source is a big plus on a CV, but starting …

by Italo Vignoli at November 27, 2015 09:00 AM

November 26, 2015

Michael Meeks

2015-11-26 Thursday

  • More tinderbox fixage; various nasty dependency issues, unwound a gallery build bootstrapping nasty. Plugged away at other bugs. ESC call in the afternoon, chat with Kendy. Dinner. More hackery until late.

November 26, 2015 09:00 PM

Miklos Vajna

Sanitizing member variable names in LibreOffice Writer

Robinson just branched off libreoffice-5-1 from master in LibreOffice’s core.git repository, so time to talk about what happened behind the scenes in the 5.0 → 5.1 development cycle from my side.

One stylistic detail that annoyed me for a while was the inconsistency around naming class member variables. In new code it’s common to give them an m_ (or at least an m) prefix, but in older code that wasn’t that common, and various custom hacks were invented to differentiate between pointers which point to the same memory address, but one being a parameter of a member function, and the other being a member variable.

Probably the worst scenario is when one was an abbreviation of the other, like pTable and pTbl or pCursor and pCrsr. I took this as an opportunity to play with Clang’s LibTooling, and I wrote two tools back during the Cambridge hackfest to automate the process of finding and fixing missing prefixes.

To scope the renaming, I changed all classes in the sw module having more than 20 unprefixed members to follow the above convention, hopefully this nicely improves code readability, together with the mass-rename of pointless abbreviations, also done before the branch-off, so affecting both libreoffice-5-1 and master. :-)

November 26, 2015 07:50 AM

November 25, 2015

Michael Meeks

2015-11-25 Wednesday

  • Mail chew. Fireplace salesman arrived to measure up a couple of rooms. Nursed some tinderbox breakage - odd event ordering bits throwing up pre-existing bugs; nice. Nailed a VBA unit test issue, and another writer SolarMutex issue.
  • Chat with Bjoern, Florian & Thorsten; Lunch. Crunched some update stats, board call, built ESC agenda.
  • Remembered to link to the awesome 1st Packaging as directed by my great Sister in Law & Husband, for any of your of plastic packaging needs; end advert.
  • Helped H. get setup with her first mobile buy / mend / resell iteration. Worked late, while J. at a PCC meeting. Changing global headers is insanely expensive.

November 25, 2015 09:00 PM

November 24, 2015

Michael Meeks

2015-11-24 Tuesday

  • More struggling with main-loops; product team call. Discovered that the new scheduler has the (non-optimal) idea of setting a MAX_UINT64 timeout in milliseconds to the glib main-loop timeout; and this is really a non-clever idea.
  • Also (thanks Dimstar) managed to find the SRPMs for openSUSE 13.2 which was surprisingly hard (though finding the source in the build-service is easy).
  • Plugged away; tested on windows; Norbert kindly tested on Mac; all good (encouragingly). Read stories for babes.

November 24, 2015 09:00 PM

Jan Iversen

Improving “make vs2013-ide-integration”

The make system can generate a visual studio solution with a .vcxproj file for each target (libraries as well as executables).

Having tested it, it is clear some improvement is needed.

  • it generates vcxproj for 27 out of 93 executables
    • Assumes that CXXOBJECTS is before “recipe to build executable”
    • Assumes that the 2 are together
    • for 66 executables that is not the case
  • vcxproj files are scattered in the source tree, not workdir
    • Source tree should be kept clean, without generated files
    • the vcxproj files, should be kept in e.g. workdir/vs2013
  • it only covers C++, missing java/python/javascript
  • It does not use the object files in workdir (made by make)
    • VC starts by compiling everything again, this should not be the case
  • No support for visual studio 2015

It is my intention to improve the script, step by step. Some of the problems have been added to bugzilla as easyHacks.

by jan at November 24, 2015 12:19 PM

Meeting the developers.

I attended a “hackfest” in Hamburg, Germany. The main purpose was to have a face to face session with my “bosses” (Thorsten, Bjoern and Michael). It turned out to be 2 days full of fun, I met quite a number of old friends and got some new ones.

If this is the spirit of the LibreOffice community, then the next year will be a lot of fun.

Next hackfest is in Madrid 2-4 December Madrid 2015 it will take place 5 minutes walk from Atocha (the main rail station). Don´t miss the chance, come and join us (y claro también van a hablar Español).


A good thing about a hackfest is the food, a well designed Pizza. Please remark how concentrated I work, not even looking at all the Pizzas.

by jan at November 24, 2015 12:06 PM

Samuel Mehrbrodt

Improving the Toolbars in LibreOffice

Disclaimer: This is work in progress, and it is not how it will look like in the end.

The current situation

With the Design team, we are working on improving toolbars in LibreOffice. This is part of our long-term goal, making LibreOffice “simple for beginners and powerful for experts“.

Toolbars in LibreOffice are currently quite limited: A toolbar can have icons, or custom widgets, in a row. You can switch between icon-only, icon+text or text-only display.

Allowing more flexible layout

So we want to improve Toolbars to allow a more flexible layout. The first step is to allow Toolbars to be loaded from Glade files. That technique is used all over in LibreOffice (in Dialogs and the Sidebar e.g.) to lay out widgets in a dynamic way. With that, we can have a toolbar layout like this (Mockups by Heiko):

Mockup 2
Mockup 1

Note that these images are just mockups  (subject to change)- nothing has been implemented yet.

Also this will be an optional thing – most probably we will keep a “Classic Mode” with the legacy Toolbars for the foreseeable future.

Open issues

There are some issues we need to think about, like customization and fitting these Toolbars for smaller screens.

We will focus on Writer first, on the two main toolbars (at the top). We are not yet sure what will happen with the 38 other toolbars we have in Writer (e.g. for image manipulation or table tools). Currently they keep popping up at different places, and we would like to get so uniformity in there. Basically we have three different options (Sidebar, NotebookBar or leave them as they are). This will need some more discussion at  a later point.

The current goal is to improve the layout of the toolbars itself. We expect the first results in LibreOffice 5.2 (Q4 2016).


Please note that we are not going to abandon the Sidebar. We expect the Toolbar and Sidebar to complement each other, not to compete with each other. One idea how that might look is that the Toolbar provides access to the most used commands and properties, while the Sidebar gives more advanced options.

Another concern many users have, is that the new Toolbar would take up too much vertical screen space. We are trying to address this concern and make the improved Toolbar not eat up much more space than currently the two default Toolbars at the top have.

Some users have suggested to drop the Toolbar completely and focus on the Sidebar only. The most common argument is that you have plenty of horizontal space on today’s screens, but little vertical space. However, this argument is only true with a single-page document in a full screen window. This doesn’t take into account multi-page documents (two pages displayed side-by-side) or two windows displayed next to each other. In both of these cases, the Sidebar might take away too much space to work efficiently. This is one of the reasons, why we continue to keep the Toolbar at the top.

Get in touch!

Ideas? Suggestions? Leave a comment below!

Finally: The design team is always looking for ways to improve LibreOffice. If you have anything that you think could make our GUI look cleaner, fresher, better, do not hesitate to let us know! Write to our Mailing List or join us in IRC (#libreoffice-design on freenode).

by Samuel Mehrbrodt at November 24, 2015 09:51 AM

November 23, 2015

Andreas Mantke

Further Rework of the LibreOffice Extension Site Add-On

I worked further to get the Plone add-on for the new LibreOffice extension website able to run with the new version 5 of the Content Management System (CMS). I made a lot of changes to the source code and committed my changes already to the github repository of The Document Foundation.

During my work I run into some issues with the CMS, e.g. with the workflow implementation. I made another try some hours later and got it running as expected.

I also experienced an issue with the event handling from ‚zope.lifecycleevent.interfaces‘ with ‚IObjectAddedEvent‘. However the event ‚IActionSucceededEvent‘ from ‚Products.CMFCore.interfaces‘ worked as expected.

It’s also very nice to use the Plone api instead of the getToolByName call from the Plone utilities. Makes life a bit easier.

by andreasma at November 23, 2015 09:06 PM

Official TDF Blog

LibreOffice getting ready for the next 1,000 hackers

janiversensmallBerlin, November 23, 2015 – The Document Foundation announces a renewed effort to grow the developers community beyond the threshold of 1,000 hackers reached in October 2015 (source: OpenHub), with the addition of Jan Iversen – a senior developer with a passion for mentoring, and a long experience at Apache Software Foundation – to the team.

The extraordinary growth of LibreOffice developer’s community, with a monthly average of over 16 new hackers contributing to the code since September 2010, is the result of a global mentoring effort by some of the project founders. After five years and 1,000 new developers, …

by Italo Vignoli at November 23, 2015 01:45 PM

November 21, 2015

Official TDF Blog

LibreOffice wins two open source awards at PortalProgramas

LibreOffice has won two different awards at PortalProgramas.Com, for the following categories:

  1. Mayor potencial de crecimiento (best growth potential), because it is regularly updated and is open to new features and applications;
  2. Esencial para empresas (essential for enterprises), because it covers all enterprise office automation needs without adding license costs.

empresas.2015 mayor-potencial.2015

by Italo Vignoli at November 21, 2015 05:59 PM

November 20, 2015

Andreas Mantke

Rework of a Extension Center Add-On

The LibreOffice extension site is running on Plone. I already worked on two new add-ons for the site. I created this add-ons using the Dexterity content types and the grok style (five.grok). Thus this grok style is not supported any more with the new Plone 5 release I decided to rework the add-ons and drop grok. This allows to run the add-ons with Plone 4.3.x and Plone 5 as well. I created a new fresh repository on Github and started adding the first files today.

by andreasma at November 20, 2015 09:37 PM

Caolán McNamara

Better polygon rendering in LibreOffice's Gtk3 Support

Above is how LibreOffice's "svp" backend rendered rotated text outlines in chart where the text is represented by polygon paths. Because the gtk3 backend is based on that svp backend that's what you got with the gtk3 support enabled.

After today's work above is how the svp backend now renders those paths when rendering to a cairo-compatible surface such as the gtk3 support provides.

If we mandate that "svp" only operates on cairo compatible surfaces, then we can get this niceness into android and online too, and can ditch our non-cairo text rendering code paths.

by Caolán McNamara ( at November 20, 2015 01:18 PM

November 17, 2015

Florian Reisinger

Original SI-GUI has new master locations


Just updated the master urls. Hit the “Update List of versions” button to get it and start testing

Tagged: QA, Server Installation GUI, SI-GUI, Windows

by Florian Reisinger at November 17, 2015 07:39 AM

November 16, 2015

Dennis Roczek

Editing Tabs

Since the last MediaWiki major update some “tabs” above the editing text fields were “gone”. I was asked by Pierre-Yves if these can be restored. Actually I had no clue and by accident I found out that our friends at WikiApiary do have them activated by default. So it is indeed possible. The hint on their mailing list didn’t helped very much except getting the LocalSettings.config (the config file of MediaWiki storing all custom options). At the end I was playing in the user preferences in the wiki itself and found out that it can be turned on in the user preferences under Editing: “Enable side-by-side preview“.

And the result looks like that: (the red border displays the reappearance of the tabs)

2015-11-16 23_53_46-Start


Hopefully I can improve your wiki experience. ;-)

by dennisroczek at November 16, 2015 11:05 PM

November 13, 2015

Caolán McNamara

Insert Special Character in Spelling Dialog

LibreOffice 5.1 spelling dialog now has a little toolbar to enable inserting special characters into the spelling editing widget. Also Added paste, so the insert icon isn't lonely.

by Caolán McNamara ( at November 13, 2015 10:57 AM

November 12, 2015

Gülşah Köse

Open Source Conference in Turkey

        Open Source Conference was organized this year for the first time in Ankara - capital of Turkey -. Conference is going to take 5 days, it's started 9th november and it's going to end 13th november. The conference aims to bring together key people in the public sector, to announce works on open source and free software like Pardus, enGerek, Lider Ahenk and to raise awareness. The Conference is local and unfortunately it hasn't any English websites. I hope they will add soon.

        The first day of the conference i've given a talk about LibreOffice. LibreOffice is one of the most important points for Turkey. LibreOffice is an important step for spreading of free softwares. Because this office suit can run on GNU/Linux, MacOs, and Windows. LibreOffice will take an important role in the migration to free operating systems.

        There was no active work on LibreOffice in Turkey until recently. Now there is a team in my University who works for LibreOffice. We are studying to learn LibreOffice, fixing the bugs and spreading our work and LibreOffice by blog posts and other social media tools. Thanks to Necdet Yücel for advising us in this process and thanks to helpfull LibreOffice development team. 

        You can access my presentation from here. My presentation includes following parts:
  • Libreoffice history
        I've told StarOffice, OpenOffice, Oracles's mistakes, why LibreOffice forked from OpenOffice and The Document Foundation.
  • Why we should use LibreOffice in public?
        In this part i've told principles of free software and why are they important for us.
        LibreOffice Turkish translation rate is 100% and this is the most important necessity if we want to spread LibreOffice in Turkey. (Thanks to Turkish translation team)
        No licence fee. I tried to explain this part very carefully. Because nothing should take precedence over LibreOffice is a free software. LibreOffice needs money to continue too.
        LibreOffice is improved enough to cover the needs and changable according to neccessaries. 
  •  How to support LibreOffice. How to continue LibreOffice project?
            I've told that LibreOffice needs code contributions, translation, documentation and donation -for domains, servers, developers, events etc- 
    • Which countries migrated to LibreOffice?
            I've told the countries using LibreOffice direct or indirect, reasons of unsuccesful and successful migrations.
    • What are we doing for LibreOffice in Turkey
            I've told our (LibreOffice team in University) works . We are 10 people. I explained what should be done to increase this number.

    We are planning to participate next years conference as libreoffice developers.

      by Gülşah Köse ( at November 12, 2015 08:29 PM

      November 11, 2015

      Robinson Tryon

      LibreOffice QA: Halloween Bug Hunting, and so much more!

      LibreOffice QA has been busy during the last few months!

      We just had our first BugHunting Session for the upcoming LibreOffice 5.1 release over the Halloween weekend. Testing our alpha1 builds, members of the QA Team helped to lead users, developers, and other community members in identifying and documenting problems in our very first binaries available for this release series. Having support from members of QA, L10n, Developers, members of the Design community, and regular LibreOffice users was a great sign for continued cross-team participation. We’re looking forward to seeing a similar mix of contributors during our next BugHunting Session in December.

      We identified 104 bugs during the Halloween BugHunting session, primarily from initial testing with the alpha1. Of the 74 of bugs remaining open, 80% have been triaged to previous versions, leaving only 15 bugs tied to LibreOffice 5.1. Looking at all 5.1 versions, there are only 212 open bugs pegged to this release series, with only 44 open bugs pegged against 5.1 alpha1.

      We’ve been busy with regression-hunting, performing over 550 bibisects this year, and over 200 since June. With one of our chief regression hunters and bibisect sorcerer Matthew Francis taking a well-earned respite from the cauldron of crafting new bibisect repositories and hacking on Python internals, we’re actively recruiting new QA members to help perform these binary searches on all platforms.

      In fact, with so many of our developers (and other community members) using Free Software operating systems on their workstations, there’s always a need for contributors who are running MS-Windows or OS X to help us track down OS-specific bugs. This includes not only performing bibisects, but also debugging and getting a backtrace for a crashing bug.

      Keeping our UNCONFIRMED bug count steady has been challenging. Currently hovering in the mid-500s, other important QA tasks and processes have commanded our time, and we could benefit from several more QA Team members to help shoulder the daily influx of new, untriaged bug reports. With the focus of our regular BugHunting Sessions on finding and identifying new issues in our upcoming builds, we may find it useful to host similar events that focus wholly on triage and “gardening” of the mass of existing reports in Bugzilla. Maybe we could have something like “Clean Sweep Mondays,” where we tackle the existing clutter for a set period of time, and post some quick stats such as total drop in UNCONFIRMED, # of NEEDINFO cleaned up, etc.

      Work continues on our comprehensive Media Support wiki pages, a collection of tests designed to directly verify the level of support for various image, audio, video, (and other) file formats across all of our platforms. Keeping these pages up to date ensures that they continue to be a resource for QA bug triaging as well as for our volunteers helping to answer questions on the Ask LibreOffice site. Lead by QA Team member raal, we now have initial image test results for Android, and are interested in talking with developers who’d like to expand the Android Viewer’s capabilities in this area, as well as testers who would like to expand our battery of test results for the Android OS.

      Coming up during the first weekend in December, we’re holding our BugHunting Session for the 5.1 Beta1 build. For those of you who are interested in kicking the tires and working with a still-rough-around-the-edges piece of software, your help is greatly appreciated. With a large package such as LibreOffice, it’s invaluable to have technical members our userbase exercise some of the more esoteric features of LibreOffice, and identify any minor regressions or usability concerns early-on in the release process.

      The QA Team looks forward to seeing you in IRC anytime, or stopping by one of our weekly Wednesday meetings. We’re always happy to answer your questions about bug reports, bibisecting, etc., and to helping new contributors get started with the LibreOffice community!

      by colonelqubit at November 11, 2015 09:40 PM

      Jacobo Aragunde Pérez

      Updated LibreOffice workshop at A Coruña University

      I’ve been invited to repeat the workshop about LibreOffice I conducted last year at the University of A Coruña. Contents are largely the same but I’ve done some updates, hence this short entry to share the new slides:

      It was a great session, with many interesting questions from the students. Thanks to Juan José Sánchez for the invitation! I hope to be able to repeat next year :)

      by Jacobo Aragunde Pérez at November 11, 2015 04:45 PM

      November 10, 2015

      LibreOffice Design Blog

      Hello world!

      Ladies and gentleman,

      we proudly present to you… the Libreoffice Design Team blog.

      We provide you with the latest updates about visual design, icons, usability, user experience, application workflow, user metrics, surveys, templates, and all the fancy stuff we do.…

      by LibO design and usability team at November 10, 2015 03:07 PM

      November 07, 2015

      Dennis Roczek

      HotCat finally installed

      I wanted really to improve our actual category system on the TDF wiki, but there were many reasons I did not. One of the reasons was that we don’t have any tools installed which help the user (including myself) and you have to do it “the old way” using the source code knowing the actual category.

      We had already the Extension:Gadgets installed and thus I simply imported the description and the Wikipedia Gadget HotCat. :-) It is disabled by default. You simply have to go to [[Special:Preferences]], click on the tab Gadgets and activate HotCat.

      Afterwards when visiting a page you will see at the bottom a Plus sign (+). When you click that you can easily (with suggestions!) add new categories. :-)

      For more information about this Gadget simply read Wikipedia’s manual.

      If you want more or other features installed, simply ping me. Most are very easy to install and I’m very happy if I can help you to improve our wiki. ;-)

      by dennisroczek at November 07, 2015 05:58 PM

      November 06, 2015

      Florian Effenberger

      Wie die Stiftung hinter LibreOffice funktioniert

      LibreOffice wird von tausenden Mitwirkenden aus aller Welt entwickelt, getestet, dokumentiert, übersetzt und vermarktet und von Millionen Anwendern rund um den Globus eingesetzt. Diese Gemeinschaft aus Machern und Nutzern („Community“), diese Motivation und dieses Engagement ist es, was das Programm zu dem macht, das es heute ist: die führende freie Office-Suite. Der Begriff „LibreOffice“ steht demnach für zweierlei – sowohl für das Produkt, als auch für die Menschen, die dahinter stehen.


      Wer sich unser Logo genau ansieht, der stellt fest, dass dort der Begriff LibreOffice groß und prominent geschrieben steht – ein Ausdruck der Wertschätzung und Wichtigkeit unserer Community. In kleinerer Schrift darunter steht jedoch ein zweiter Begriff: „The Document Foundation“.

      Die TDF, so die Kurzform, ist im offiziellen Sprachgebrauch eine gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts mit Sitz in Berlin. Sie fungiert als eine Art Treuhänder, der der Community unter anderem eine Rechtspersönlichkeit gibt. Die Stiftung ist zugleich Herausgeber der Software, Hüterin der Marken und Domains und verwaltet zudem die Spendengelder, die sie für die Zwecke der Stiftung einsetzt. Laut Satzung ist ihr Ziel die „Förderung und Entwicklung von Office-Software zur freien Nutzung durch jedermann“.

      In diesem unscheinbar wirkenden Satz steckt eine ganze Menge! Zum einen tritt die TDF fördernd auf, d.h. sie unterstützt Projekte, die dem Stiftungszweck entsprechen. Zum anderen tritt sie selbst auch operativ auf und stemmt Projekte aus eigener Kraft. Mit „Office-Software“ ist natürlich primär LibreOffice gemeint, doch gibt es beispielsweise mit dem „Document Liberation Project“ noch ein weiteres, wenngleich auch eher technisch orientiertes Projekt und weitere Projekte können unproblematisch hinzukommen – die Entscheidung, der Stiftung einen projektunabhängigen Namen zu geben, hat sich damit schon früh bewährt.

      Unsere Philosophie

      Der Weg zur Stiftung war dabei stets motiviert von einigen zentralen Punkten, die ihren Ausdruck in unserer Satzung gefunden haben. Diese Satzung verankert die Werte und Ideale, mit denen wir seit langer Zeit zusammenarbeiten, und formalisiert sie, beispielsweise durch das Festschreiben von Offenheit und Transparenz.

      Das Ziel der Stiftung ist die Weiterentwicklung von sowohl der Software, die sie herausgibt, als auch der dahinter stehenden Gemeinschaft – beispielsweise durch die Implementierung neuer Funktionen sowie durch die Organisation von Veranstaltungen zum Wissenstransfer.

      Als Stiftung sind wir nicht unabhängig von Sponsoren, jedoch ist unser Mantra die Unabhängigkeit von einem einzelnen Sponsor, was unter anderem durch klare Regeln für die Beteiligung von Unternehmen statuiert wird. Gleichzeitig ist unsere Aufgabe, zum Wohle der Nutzer und insbesondere der von der Stiftung verwalteten Projekte ein Ökosystem zu pflegen, von dem alle profitieren. Oftmals kommt es beispielsweise vor, dass im Rahmen von Kundenprojekten wichtige Funktionen von Drittanbietern entwickelt und anschließend der gesamten Community zur Verfügung gestellt werden. Für uns als Stiftung sind das wertvolle Beiträge, die das Produkt noch besser machen und für die Firmen ist es hilfreich, ihre Funktionen künftig direkt in den offiziellen LibreOffice-Versionen wiederzufinden, um sich zeitintensive Pflege von Parallelversionen zu ersparen. Die Stiftung selbst tritt dabei nicht am Markt auf, wir bieten weder Dienstleistungen noch Beratung oder kundenspezifische Entwicklung an.

      Um eine möglichst große Zahl von Beitragenden zu gewinnen, haben wir von Anfang an ein Augenmerk darauf geworfen, die Einstiegshürde zu senken, indem der Quelltext von LibreOffice entschlackt und modernisiert wurde. So genannte „Easy Hacks“ erleichtern neuen Entwicklern den Einstieg und Mentoren – beispielsweise im Rahmen des Google Summer of Code oder bei verschiedenen Workshops – begleiten Interessenten und erleichtern ihnen den Weg ins Projekt. Insbesondere im Bildungsbereich sind wir engagiert, bieten wir zum einen doch eine Software, die sich ideal für den Einsatz in Forschung und Lehre eignet und ermöglichen zum anderen Wissentransfer auch in Schwellenländer. Auch können Menschen leicht außerhalb des Software-Codes beitragen, beispielsweise durch Mithilfe bei der Dokumentation, bei der Übersetzung oder durch die Mitarbeit an Texten im Wiki.

      Dabei ist die TDF keinesfalls auf sich allein gestellt, sondern arbeitet mit anderen Organisationen in vielfältiger Art und Weise zusammen.

      Getreu dem Motto „aus der Community, für die Community“ wurde die Stiftungsgründung durch zahlreiche Spender aus aller Welt erst ermöglicht, die den nötigen Kapitalstock aufgebracht haben – in nur acht Tagen im Rahmen eines öffentlichen Fundraisings. Diesem Prinzip ist die Stiftung bis heute treu geblieben, denn die überwiegende Mehrheit des Spendenaufkommens sind kleine Beiträge von Privatpersonen, wobei Spenden durch Unternehmen selbstverständlich willkommen bleiben.

      Warum eine Stiftung?

      „Warum habt ihr eine Stiftung gegründet und nicht einfach einen Verein?“, so lautet eine der häufigsten Fragen, die an uns gerichtet werden. In der Tat war der Weg von der Projektgründung im September 2010 bis zur Gründung der Stiftung im Februar 2012 kein einfacher, es wurde viel diskutiert, Möglichkeiten und Optionen abgewogen, und schlussendlich fiel die Entscheidung: es sollte eine „klassische“ Stiftung nach deutschem Recht sein – zumindest fast.

      Die TDF verbindet mit ihrer Satzung wichtige Ideale einer Stiftung mit den Notwendigkeiten von Open-Source-Projekten. Zum einen sind Stiftungen auf Dauer und Stabilität ausgelegt („Stiftungen sind für die Ewigkeit“) und bieten dadurch Sicherheit für Community, Anwender und Unternehmen gleichsam. Das kommt unter anderem dadurch zum Ausdruck, dass der Stiftungszweck im Wesentlichen nicht geändert werden kann. Während sich Vereine durch die Mitglieder definieren, ist bei der Stiftungsgründung der Stifterwille entscheidend. Anders ausgedrückt ist dadurch das Risiko einer „feindlichen Übernahme“ minimiert, denn ein Verein muss, sofern er gemeinnützig ist, in der Regel Mitglieder aufnehmen, sodass „Einfluss durch Geld“ denkbar ist.

      Die Rechte, die in unserer Satzung verankert sind, sind dabei nicht nur hohle Phrasen – sie sind garantiert und schaffen damit Zukunftssicherheit für alle Projektbeteiligten und die Anwender. Das alles gibt in der Gesamtschau jedem Beitragenden eine klare Vorstellung davon, was mit seinem Beitrag passiert und in welchem Rahmen sein Engagement stattfindet.

      Die Meritokratie macht den Unterschied

      Die TDF ist meritokratisch organisiert, was nichts anderes bedeutet, als dass diejenigen, die sich um das Wohl der Stiftung verdient gemacht haben, auch ihre Geschicke lenken dürfen.

      <figure class="wp-caption aligncenter" id="attachment_115" style="width: 474px;">Organigramm der Document Foundation<figcaption class="wp-caption-text">Organigramm der Document Foundation</figcaption></figure>

      Natürlich gibt es bei uns wie in vielen anderen Organisationen einen Vorstand, der die Stiftung nach außen hin vertritt und strategische Entscheidungen fällt. Besonders bei uns ist, dass dieser aus sieben Vorständen und drei Stellvertretern besteht, die aus verschiedenen Bereichen des Projekts stammen und ebenfalls rund um den Globus verteilt sind – derzeit neben Deutschland auch England, die USA, die Schweiz und Brasilien, was die Vielfalt und Mannigfaltigkeit des Projekts widerspiegelt.

      Im Gegensatz zu manch anderen Stiftungen wird bei uns der Vorstand regelmäßig – alle zwei Jahre – durch das Kuratorium neu gewählt, genauer gesagt durch das Mitglieder-Kuratorium. In diesem Begriff kommt eine der TDF ureigene Besonderheit zum Ausdruck. Während viele Stiftungen ein kleines, oftmals eher statisch besetztes Kuratorium haben, ist das Mitglieder-Kuratorium bei uns das Organ, in dem alle Beitragenden versammelt sind. Damit nähert sich die Stiftung einem in dieser Hinsicht vorteilhaften Modell eines Vereins an.

      Jeder, der seit mindestens drei Monaten zum Wohlergehen der Stiftung beiträgt, sei es durch Entwicklung, Marketing, Dokumentation, Lokalisierung oder eine Vielzahl weiterer Betätigungen, und dies noch mindestens für sechs weitere Monate tun möchte, kann den Status als Mitglied im Kuratorium erhalten, der mit dem aktiven wie passiven Wahlrecht verbunden ist. Dabei spielt es keine Rolle, ob die Beiträge im Rahmen einer bezahlten Tätigkeit oder ehrenamtlich erfolgen. Kurzum: Jeder, der sich an der Stiftung beteiligt und sich einbringt, kann ihre Geschicke lenken, wobei der Status an die natürliche Person und nicht etwa an den Arbeitgeber geknüpft ist. Die einzige Ausnahme, die gerade nicht für die Mitgliedschaft qualifiziert, ist die Geldspende – man kann sich also nicht einkaufen. Mitglied im Kuratorium ist man übrigens immer zum Quartalsbeginn für zunächst jeweils ein Jahr, der Status wird bei anhaltenden Beiträgen aber immer wieder erneuert – dadurch ist sichergestellt, dass nur die jeweils Aktiven auch im Mitglieder-Kuratorium vertreten sind.

      Die Besetzung des Mitglieder-Kuratoriums, das derzeit aus 211 Mitgliedern aus aller Welt besteht und seit Stiftungsgründung konstant wächst, wird dabei nicht etwa durch den Vorstand geregelt, sondern durch ein eigens geschaffenes Organ der Stiftung, das Mitglieder-Komitee, für welches das Mitglieder-Kuratorium ebenfalls passiv wie aktiv wahlberechtigt ist. Das Mitglieder-Komitee hat ebenfalls eine – derzeit zum Vorstand antizyklische – Legislaturperiode von zwei Jahren und besteht aus fünf Mitgliedern und drei Stellvertretern, kann aber im Bedarfsfall auf maximal 10% der Kuratoriumsmitglieder vergrößert werden. Es regelt die Besetzung des Mitglieder-Kuratoriums willkürfrei und ist zudem für Beschwerden und Amtsenthebungsverfahren verantwortlich. Die Wahl von Vorstand und Mitglieder-Komitee werden wechselseitig überwacht.

      Neben diesen offiziellen Organen der Stiftung gibt es noch einen Beirat für Unternehmen, die sich entweder für freie Software einsetzen und über eine entsprechende Expertise verfügen, oder aber direkt an der Entwicklung und Verbreitung von LibreOffice beteiligt sind. Dieser Beirat tauscht sich regelmäßig mit dem Vorstand aus, gibt ihm wertvolle Rückmeldungen und unterstützt ihn dabei, die strategischen Weichen für die Entwicklung der Stiftung zu stellen.

      Ein weiteres Gremium der Stiftung ist das Engineering Steering Comittee, das technische Sachverständigen-Komitee. Es trifft in zumeist öffentlicher Sitzung die wegweisenden programmiertechnischen Entscheidungen des LibreOffice-Projekts und entscheidet in letzter Instanz über die Veröffentlichung neuer Versionen. Auch das ESC, so die Kurzform, ist mit Mitwirkenden aus aller Welt besetzt, die teilweise im Rahmen ihres Berufs, teilweise rein ehrenamtlich an LibreOffice mitarbeiten.

      Wir sind anders…

      Dies sind nur einige Besonderheiten der TDF, wenngleich auch mit Sicherheit die markantesten.

      Daneben gibt es eine besondere Vorkehrung gegen mögliche Interessenskonflikte: Maximal ein Drittel von Vorstand oder Mitglieder-Komitee darf aus Mitarbeitern derselben Firma  bestehen, um mögliche unerwünschte Situationen zu vermeiden.

      Damit die Einhaltung dieser Regeln auch von der Öffentlichkeit geprüft werden kann, stehen bei uns Transparenz und Offenheit im Vordergrund: Nicht nur, dass alle Vorstandssitzungen und die Entscheidung der Organe – darunter fällt auch das Mitglieder-Komitee – von Haus aus öffentlich sind, auch unsere Buchhaltung, die Budgetplanung und die meisten Mailinglisten werden öffentlich geführt.

      Natürlich gibt es gewisse Einschränkungen – auch wir haben tagtäglich mit sensiblen Informationen zu tun, die einem Geheimhaltungsbedürfnis unterliegen, beispielsweise die Namen der Spender. Solch sensible Informationen werden vor der Veröffentlichung selbstverständlich entfernt und im Sinne der Arbeitsfähigkeit der Stiftung muss auch nicht jeder Gedankengang in den Vorbereitungen zu Entscheidungsfindungen dokumentiert werden. Aber auch hier sieht die Satzung einen gesunden Ausgleich der Interessen vor, indem sie die verpflichtende Veröffentlichung von Entscheidungen vorschreibt, sobald das Geheimhaltungsbedürfnis weggefallen ist.


      Für uns als Gemeinschaft hat sich die Form der Stiftung, in der besonderen, von uns geschaffenen Ausprägung, als sehr effizient erwiesen, denn sie spiegelt genau die Ideale und Wertvorstellungen wider, unter denen wir zum Wohl aller zusammenarbeiten wollen.

      LibreOffice ist nunmehr seit fünf Jahren in aktuell über 100 Sprachen für zahlreiche Betriebssysteme auf dem Markt, die Zahl der Beitragenden wächst konstant, immer neue Anwender rund um den Erdball setzen auf die führende freie Office-Suite. Die Community ist weltweit mit viel Herzblut, Engagement und Überzeugung aktiv, und bewegt dabei Tag für Tag eine Menge, womit sie vielen Menschen die digitale Teilhabe überhaupt erst ermöglicht.

      Neben der klassischen Desktop-Variante entsteht so derzeit auch eine Version für Smartphones und Tablets, und auch für die Cloud wird es in Zukunft entsprechende Angebote geben.

      Der vorstehende Text entstand unter tatkräftiger Mithilfe von Thorsten Behrens, Andreas Mantke, Björn Michaelsen und Mike Schinagl. Zum selben Thema gibt es meine Vortragsfolien von der Ubucon 2015 sowie eine Videoaufzeichnung meines Vortrags auf der CeBIT 2014.

      by Florian Effenberger at November 06, 2015 08:58 AM

      November 04, 2015

      Miklos Vajna

      PNG export in LibreOffice Calc

      Both LibreOffice Writer and Impress has the ability to export the document as PNG, which is one way to create thumbnails for documents — i.e. being able to preview them before the real loading of the document happens. It turns out Calc did not have this feature, and given that ScModelObj also supports the css::view::XRenderable interface (just like Writer), I hoped that it won’t be too complex to add one.

      You can refer to Fridrich’s overview blog post for the complete list of steps on how to add a new filter to LibreOffice, here the following steps were needed:

      • improve DocumentToGraphicRenderer, so that it can handle that Calc does not implement the text::XTextViewCursorSupplier interface (Writer uses this one to expose the cursor is on what page)

      • register png_Portable_Network_Graphic as filter type for Calc

      • create a new calc_png_Export filter fragment

      • register a Calc graphic filters configuration type and filter group in Configuration_filter and CustomTarget_registry

      • testcase

      If you can’t wait till LibreOffice 5.1 is released to try out this new feature, you can get a daily build. :-)

      November 04, 2015 08:17 AM

      November 03, 2015

      Charles Schulz

      Join us at the Open Source Summit in Paris !

      Short announcement: I’ll be speaking at the Open Source Summit in Paris on the 18th of November: the panel discussion will be about community and contributors’ engagement (the panel is dubbed “from the individual to the collective and the collective to the individual…”). You will find more information here and on the homepage. Don’t forget to register!

      I’m quite excited by this event as it is the first time two succesful and longstanding events in Paris have merged: Linux Solutions on the one hand and the well known Open World Forum. The venue is worth a look as well: the Docks are the rehabilitated industrial area just north of Paris and close to the Stade de France.

      I look forward to two great days of discussions and meetings on Software Freedom and Open Source Software!


      by Charles at November 03, 2015 10:17 AM

      October 31, 2015

      Dennis Roczek

      new extension: CodeMirror

      A week ago I was trying to configure (again) the visual editor correctly to get it working. Sadly this is a beast and the documentation is not ideal. Especially with the actual server situation.

      After giving up and somehow by accident I found a rather new extension called CodeMirrow. This extension adds syntax highlight while editing a wiki article. We quickly notice some non functional “show changes” and “preview”. A bug ticket at Wikimedia’s Phabricator (T116829) was really fast resolved. :-)

      If you do not want to use that feature, simply click on the colorful circles in the WikiEditor bar.

      So as always: If you want to have a “special” extension installed, or believe that you found a bug, simply send me a mail. ;-)

      by dennisroczek at October 31, 2015 11:32 PM

      October 29, 2015

      Eike Rathke

      LibreOffice Hackfest at Hamburg

      Thanks to CIB, who sponsored the event with their office location, drinks and food, we again had a LibreOffice Hackfest at Hamburg on Saturday/Sunday October 24/25, and a get-together on Friday evening with the opportunity to meet also some long time colleagues from Sun and Star.

      My timeline:

      • followed a nice introduction to the help authoring extension held by Regina Henschel, for how to install and use it see the documentation in the wiki
      • changed our own implementation of rtl_math_{erf,erfc} to follow the C++11 standard's specification for input of Inf and NaN
      • added unit tests for rtl_math_{erf,erfc,expm1,log1p}
      • replaced implementation of rtl_math_{erf,erfc} with ::std::{erf,erfc}
      • attended a Gerrit inline editing introduction by David Ostrovsky (yet another time his favorite feature ;)
      • replaced implementation of rtl_math_{expm1,log1p} with ::std::{expm1,log1p}
      • dug with Regina into the help authoring extension to spot a place for switching the license text written based on the difference between existing and new file, but the convoluted agglomeration of template, fields, Basic and XSLT and the license text being an XML comment in .xhp didn't offer a quick and easy to spot solution, Kendy please take over ;)

      But, as usual no new hacker was interested in diving into Calc core code.. maybe you at one of the next Hackfests?

      See also the other achievements.

      Last but not least, the important event of ordering pizza online:

      The not to be underestimated event of ordering pizza online.
      The not to be underestimated event of ordering pizza online.

      For more and better pictures see Björn on G+


      by erAck (23@ at October 29, 2015 08:21 PM

      Naruhiko Ogasawara

      Now preparing the annual LibreOffice mini-Conference 2016 Osaka/Japan!

      Just a quick announcement.

      We, LibreOffice Japanese team, which is Japanese NLP, are preparing the annual LibreOffice mini-Conference 2016 Osaka/Japan at Jan. 9th (Sat) in Osaka, Japan.

      Thanks to GMO group (Japanese major net company), the event will be held in Synergy cafe GMO Yours Osaka, 23th floor of Grand Front Osaka building.

      This is Japanese NLP's event and every talks will be in Japanese, but every people worldwide is welcome.

      Just a quick notice about when and where, and I'll post another article when we will begin to accept proposal for papers, open a registration page, and any other events.

      See you in Osaka!

      by Naruhiko Ogasawara ( at October 29, 2015 01:14 AM

      October 26, 2015

      Florian Effenberger

      LibreOffice-Vortrag auf der Ubucon 2015

      Ich hatte auf der Ubucon 2015 in Berlin die Gelegenheit, einen Vortrag zum Thema „Fünf Jahre LibreOffice – Rückblick und Ausblick“ zu halten.

      Die Folien stehen hier zum Download zur Verfügung (PDF-Datei, 3,3 MB).

      by Florian Effenberger at October 26, 2015 02:03 PM

      October 24, 2015

      Dennis Roczek


      A week ago I rejected a request at Redmine#1514 by Samuel Mehrbrodt. He requested a change in the wiki configuration so that double clicking on a text in the wiki don’t bring you  to the edit field of that section. I rejected the ticket because there is an option in the user preferences to disable that “feature”.

      As Florian suggested I started a thread at the website mailing list requesting more input (see archives if you are not subscribed). Feel free to comment either at the website mailing list or at the Redmine ticket.

      PS: I have added a new FAQ page how to create a page containing an OpenStreetMap map.

      by dennisroczek at October 24, 2015 03:55 PM

      October 23, 2015

      Eike Rathke

      Extreme Galaxing

      Astronomers of the Ruhr University Bochum (RUB) have photographed our Milky Way Galaxy for years and fit the pieces together into one enormous 46 billion pixels image of 194 Gigabyte, viewable in an online tool.

      [via heise online (in German)]

      by erAck (23@ at October 23, 2015 11:11 PM

      Caolán McNamara

      finding UI crashes by fuzzing input events with american fuzzy lop

      As mentioned previously I've been experimenting using afl as a fuzzing engine to fuzz a stream of serialized keyboard events which LibreOffice reads and dispatches.

      Performance is still pretty poor, but by tweaking our headless mode to allow dialogs to be created, then using that headless mode for eventtesting and then hacking out the actual rendering of the UI to the headless backend I've got something that performs reasonably well enough to enable me to set a far higher limit of 50 input events per cycle and start to discover real bugs in impress.
      1. 5.1 only crash in impress sidebar under some circumstances
      2. null marked obj still in impress mark cache
      3. another null deref in impress sidebar panels
      4. crash in impress if you exit while the annotation window is open
      5. divide by zero in an impress sidebar panel
      6. another annotation window null deref issue
      7. crash on sending a keystroke to an empty impress page list widget
      8. missing dispose on annotation windows
      9. missing dispose on alive by unshown panels
      10. crash if frame is destroyed before keystroke gets to it
      11. crash if you close impress main frame while slideshow is running

      all of which is encouraging, though some of these are possibly very unlikely in real world use. But the prized find is

      intermittent crash on undo of insert slide

      because I've seen that happen plenty in the real world, and is the problem I was hoping to find.

      Turns out its been so difficult to track down because there's a timer involved which is triggered by earlier modifications to the document. To get it to crash by undoing insert slide you have to modify an object in the document, which triggers an object-modified timer, and then very quickly, before the modified-timer fires, undo insert slide. Which has the effect of impress not registering that the slide has been deleted. Some time later, in far away code, impress will crash on use of the deleted slide.

      afl-eventtesting was able to find a sequence of keystrokes (which isn't a huge surprise seeing as I primed it with some insert and undo slide sequences so it didn't have to mutate things too far before it modified a document object after an insert and before the undo) to trigger the crash and the eventtesting + headless modes of LibreOffice gave a reproducible platform where the same events happen in the same sequence without any intermediate system-ui events to throw off the delicate timing. Once the thing is reliably reproducible then its just a matter of grinding through the debugging.

      by Caolán McNamara ( at October 23, 2015 11:52 AM

      October 21, 2015

      Eike Rathke

      Back to the Future

      * assuming Hollywood PDT timezone ;)

      by erAck (23@ at October 21, 2015 11:29 PM

      October 20, 2015

      Dennis Roczek

      Better Wiki Integration

      Today Thorsten had a wonderful idea: Can we integrate dynamic maps to our events and hackfest pages in the TDFWIKI? Yes, of course we can. I even found a few minutes today to search for an extension and as it was a nobrainer, I quickly installed the extension MapSources. A few edits later I could easily use the new syntax to include a map to CIB Hamburg where the next hackfest will take place.

      The wiki FAQ has to be expanded, but I won’t have the time to do this within the next few day. :-(

      You can see a “live demo” of the new map feature at and I hope that many other pages will use that feature. ;-)

      By the way: I missed such a dynamic map feature at our conference page. Maybe we will be able to integrate a similar service for the next year. Andreas is always looking for helping hands. Get Plone and help him. ;-)

      by dennisroczek at October 20, 2015 11:04 PM

      Björn Michaelsen

      Zu Spät: Hackfest Hamburg

      Warum hast Du mir das angetan?
      Ich hab’s von einem Bekannten erfahren.

      — Die Ärtze, Debil, Zu Spät

      Its been more than two years since the last Hackfest in Hamburg! So we are indeed much too late (german: Zu Spät) with repeating this wonderful Event. Right a day after everyone updated his or her Desktop to Wily Werewolf we will meet for a weekend of happy hacking again in Hamburg!

      <figure class="wp-caption alignnone" data-shortcode="caption" id="attachment_1177" style="width: 310px">Hamburg Hackfest 2013 - carelessly stolen from Eikes Retrospective<figcaption class="wp-caption-text">Hamburg Hackfest 2013 – carelessly stolen from Eikes Retrospective</figcaption></figure>

      So now, we will meet again. You are invited to drop by this weekend, we will celebrate a bit on Friday evening (ignoring the german culinary advise in the song linked above about “Currywurst and Pommes Fritz” — I imagine we prefer Club Mate and Pizza) and hack on LibreOffice on Saturday and Sunday. Curious new faces are more then welcome!

      by bmichaelsen at October 20, 2015 08:15 PM