Last weekend I attended FOSDEM 2019 in Brussels, and following that I stopped by the Plasma Mobile sprint while that was in town.


FOSDEM was fun and inspiring as usual, even if actually getting to see talks has become almost impossible, due to the limit amount of space and the ever growing amount of attendees. However the real value of FOSDEM for me is meeting people anyway, you can’t move a few meters without running into someone you know and want to catch up with.

Adrian and Agustín have already written about KDE’s presence. My personal highlight was Alistair’s work of bringing Plasma Mobile to RISC-V. Open Source harware and Free Software are a perfect team, and it was also very nice to see our work on bringing KDE components to Yocto being used for this.

Plasma Mobile on a RISC-V board at KDE's FOSDEM 2019 booth
Plasma Mobile on RISC-V

FOSDEM 2018 was the first test flight with a boarding pass rendered by what should become KDE Itinerary (back then using a screenshot from a desktop application on my phone). This year the flights posed no challenge for KDE Itinerary anymore, the access gates at the Brussels airport train station however did. Turns out the Code 128 one-dimensional barcodes used there are too wide for displaying them horizontally on a mobile phone screen. Obviously this got fixed meanwhile :)

Plasma Mobile Sprint

Following FOSDEM there was a week-long Plasma Mobile sprint in the Endocode office in Berlin. I couldn’t attend the full time but even a day is already immensely helpful to move things forward.

One result is that KDE Itinerary is now also available as Flatpak, in the KDE Flatpak repository. This however required a small change to how the application identifies itself, and as a side-effect where it stores its data. In case you are using the application on desktop with production data, the following commands adjust that to the new location (Android is not affected).

mv ~/.config/KDE/kde-itinerary.conf ~/.config/KDE/itinerary.conf
mv ~/.local/share/KDE/kde-itinerary  ~/.local/share/KDE/itinerary