Elisa is a music player developed by the KDE community that strives to be simple and nice to use. We also recognize that we need a flexible product to account for the different workflows and use-cases of our users.

We focus on a very good integration with the Plasma desktop of the KDE community without compromising the support for other platforms (other Linux desktop environments, Windows and Android).

We are creating a reliable product that is a joy to use and respects our users privacy. As such, we will prefer to support online services where users are in control of their data.

In the part 1 of this series, I have talked about the following additions:

• libvlc as a music player alternative to QtMultimedia ;
• progress shown directly on the taskbar entry ;
• an improved party mode.

Today, I would like to introduce more features that will be in the future 0.4 stable version.

Undo Support when Playlist is Cleared

Elisa is currently a player with a strong focus on the current playlist. It is quite possible to have spent some time to compose a playlist. This is something valuable for the user.

What if suddenly, you hit the wrong button and lose all your work ?

A notification will be shown to undo this operation. This feature has been contributed by Jérôme Guidon. Thanks a lot for its first contribution !

Notification when the playlist is cleared

New Browsing Views

It is now possible to browse the most recently played tracks or the most frequently played ones.

The idea is to show the 50 last played tracks or the 50 most frequently played tracks.

The currently implemented browsing modes are the following:

It is planned to add more modes but that requires a way for the user to configure it to its liking before adding more.

A New Context View

Starting from a very good design work by Diego Gangl, the new context view is now able to show some of the metadata from the currently playing track like the composer, lyricist, play count, lyrics …

The current support for lyrics comes from a suggestion from Nate Graham. It is only supporting lyrics written in the track metadata. Support for online services will come in the next releases.

Optimizations And Reduced Memory Usage

Elisa is now loading the views fully on demand. It means that no memory or processing power is needed until one clicks on one of them. It also means that they no longer take resources when they are hidden.

One of the consequences is a better startup time and reduced memory usage. Another one is that when loading your music a busy indicator is shown to help understand what happen.

The model that is used to show your music is also now completely generic and should allow a much greater extensibility and customization.

One of my long term goal is to offer a way to fully customize the browsing of music to the user liking or type of music or …

Conclusion

Now is a very good time to get involved as the next version is being stabilized. You can help with code, bug reporting or triaging, documentation …

Thanks a lot to all contributors to this project be a feature, a fix, ideas, reported bugs …

Thanks a lot to the KDE community that is really providing very useful and powerful tools to project like this one.

The easiest way to do that is by using flatpak or Windows installers produced by the KDE continuous build servers. I now that some distributions also have package built on top of Git.

The Linux world has always worked with a develop and deploy model where software gets written by projects such as KDE and then distro projects pick that up, polish it and give it to the user.  No other computer environment works like this and it goes against the fashion of DevOps concepts where the people who code are empowered to deploy to the end user going through QA as appropriate.  We changed that with KDE neon where we brought the packaging into KDE making .deb packages. That integration allows for blockages and imperfections which get identified to be solved easily through the most efficient channels.  Kipi Plugins is a good example of this, KDE dropped the ball here by stopping releases. Nobody noticed until as a packager I wondered where it had gone, realised it was no longer being released and, because I work directly in the project responsible, could easily fix that in the right place.  With new containerised formats Linux is changing, and projects like KDE can now package software and send it direct to the user.  I’ll discuss this more in a future blog post but for now lets look at Snaps where last week, for the first time, KDE Applications was released with 50-odd apps available directly for all to enjoy direct from the Snap Store.

Give it a Try

First you need to install snapd which comes as default with KDE neon and Ubuntu distros but others will probably need to enable it manually.  See the Snap set up guide.

For Plasma Discover integration you should also install the Plasma Discover backend snap package, it is called ‘plasma-discover-backend-snap’  in Debian/Ubuntu/neon but the naming convention in your distro may vary.

You can now install Snap packages directly from the store which uses snap:// URLs to start Discover and install them.  You can also install snaps from the command line.

If you look at the KDE page on the Snap Store you can see the 50+ packages we have available today.  Most of the packages are fairly simple apps such as games and education apps, future work is to do many more KDE apps.

Snap Store? Channels? Who controls this?

Snaps follow a similar model to other large providers like Android, iPhone, Windows, Steam, etc with a centralised store, in this case run by our friends at Canonical.

There is a KDE publisher account on the Snap Store which is currently controlled by your friendly KDE neon team.  Anyone can make their own publisher account, and there’s a nifty feature to mark it as a collaboration between several accounts. For example Kdenlive is made by the Kdenlive Jean-Baptiste but the KDE account also has access.

The Snap Store features channels intended for software in different stages  of their development cycle, this mirrors quite closely what we do in KDE neon for our .deb archives.  Most users will only care about the Stable channel offering thoroughly tested software.

There is also the Candidate channel for testing builds of released software. The Edge channel is for Git master builds same as Unstable in KDE neon and the Beta channel is for Git beta branch builds same as Beta edition in neon. By default Snap will only install stuff from Stable and you have to ask explicitly for other channels but this is a great way to be testing pre-release software.

When uploading to the Snap Store for the first time there is a manual review package by archive admins which is similar to uploading new stuff to Ubuntu or many other distros, you also need manual review when you first upload a Snap package which asks for special permissions such as talking to DBus. The reviewers are nice people inside Canonical who you can ping on the Snap forums if you need to.

You might notice the KDE publisher page on the Snap store is missing a load of icons and other met data such as screenshots. These should come from AppStream files but AppStream support is still working its way into the Store backend and build tool snapcraft so not all the icons are there yet. It seems we need to work out how to use a newer snapcraft on KDE neon servers to get all these magic features sorted.

Snapd runs on your system and takes care of downloading and installing the packages. It will update Snap packages automatically so you can be confident you’ve got the latest and greatest provided by the publisher.

How’s it Built?

Snap packages are built with a snapcraft.yaml file to define how and what needs to be built by a tool called snapcraft.

In KDE neon, we have a load of Git repos for our .deb packagingm and we have reused these for our Snap packages. The neon repos are documented on the KDE wiki, and asa KDE project, all KDE dev account holders have full access. For example, KAtomic has a snapcraft.yaml file , a metadata icon and .desktop file.

Here at KDE neon tower, we have a team of guinea pigs building our .deb packages. , We have repurposed the same guinea pigs to build these snap packages. , The build jobs get created on KDE neon Jenkins servers and when someone triggers them (any KDE dev has access), the build is made on the floating cloud of guinea pigs. If successful, it is uploaded to the Snap Store.

KDE neon Tower

This is nice, but is still not as integrated as it should be. Newly released sources are built and uploaded to the Candidate channel on the Snap Store, which then needs manual review before moving to the Stable channel. Thist should get automated using openQA.

And there’s not really any need for any of it to reside on the KDE neon servers, everything should be even more tightly integrated with the rest of KDE and built as part of the new invent.kde.org CI system, and then uploaded from there. It shouldn’t be the responsibility of KDE neon team to make these, it should be done as part of the app development process.  So jump on board and enter a new world for empowered, rapidly released software!

To find out more about the Snap format follow the tutorials, read the docs and browse the notes on KDE paticular stuff.

by

The Short Of The Long

(or tl;dr)

The Long of the Short

(or gimme all that juicy stuff)

2009: The Gluon Years

2010: The Age of Bretzn

1. Build app using some IDE
2. ?
3. have users download app from e.g. opendesktop.org's software categories

You might notice a similarity between this and the concepts we described in Gluon's vision. In this project, however, we did indeed achieve the goal, at least for some Linux distributions, by using the then newly renamed Open Build Service to do the heavy lifting of actually building packages. We did this through creating a plugin for Qt Creator which created a set of basic OBS instructions, upload sources, and then once OBS had created packages, distribute those automatically using the Open Collaboration Services API, for which we created an extension supposed to interact with OBS directly. You might be forgiven for not having heard too much about this effort; while it did in fact work, it was perhaps a little more like a proof of concept than an actual, finished product, and after six months of work, we ran out of funds and i had to find somewhere else to pay my rent.

2016: Splitting Frameworks

2017-2018: Folksonomic Adaptations

2019: Bundles of Discoveries

You promised me screenshots!

---

The word of the day is: Sunshine. Because we seem to have it now, yay! :)

The KDE Applications 19.04 release announcement (read it if you haven't, it's very complete) mentions some of the applications are available at the snap store, but forgets to mention flathub.

Just wanted to bring up that there's also some of the applications available in there https://flathub.org/apps/search/org.kde.

All the ones that are released along KDE Applications 19.04 were updated on release day (except kubrick that has a compilation issue and will be updated for 19.04.1 and kontact which is a best and to be honest i didn't particularly feel like updating it)

If you feel like helping there's more applications that need adding and more automation that needs to happen, so get in touch :)

The KMyMoney development team is proud to present version 5.0.4 of its open source Personal Finance Manager.

It took us a while, and now it is ready: KMyMoney 5.0.4 comes with updated documentation. As usual, problems have been reported by our users and the development team worked hard to fix them in the meantime. Besides that, one or the other long standing bug has been fixed. The result of this effort is the brand new KMyMoney 5.0.4 release.

Despite even more testing we understand that some bugs may have slipped past our best efforts. If you find one of them, please forgive us, and be sure to report it, either to the mailing list or on bugs.kde.org.

From here, we will continue to fix reported bugs, and working to add many requested additions and enhancements, as well as further improving performance.

Please feel free to visit our overview page of the CI builds at https://kmymoney.org/build.php and maybe try out the lastest and greatest by using a daily crafted AppImage version build from the stable branch.

The details

One fix needs special mentioning: 406608 which deals with customized budget reports. KMyMoney supports two types of budget reports. One only containing the budget information and the other, more detailed report, providing also information about the actual situation. In the past this bug caused all customized budget reports to contain the detailed version after loading the file from disk. In case you encounter this scenario and want to see only the budget values in your customized report, please delete the customized report and re-create from the base report to fix the problem.

Here is the list of the bugs which have been fixed. A list of all changes between v5.0.3 and v5.0.4 can be found in the ChangeLog.

• 368159 Report Transactions by Payee omits transactions lacking category
• 390681 OFX import and unrecognized <FITID> tag
• 392305 Not all Asset accounts are shown during OFX import
• 396225 When importing a ofx/qif file, it does not show me all my accounts
• 396978 Stable xml file output
• 400761 Cannot open files on MacOS
• 401397 kmymoney changes group permissions
• 403745 in import dialog, newly-created account doesn’t appear in pulldown menu
• 403825 Transaction validity filter is reset when re-opening configuration
• 403826 Transactions without category assignment are not shown in report
• 403885 Buying / selling investments interest / fees round to 2 decimal places even when currency is to 6 decimal places
• 403886 No way to set/change investment start date in investment wizard
• 403955 After an action, the cursor returns to top of page and does not remain in a similar position to when action was started
• 404156 Can’t select many columns as memo
• 404848 Crash on “Enter Next Transcation”
• 405061 No chart printing support
• 405329 CPU loop reconciling if all transactions are cleared
• 405817 CSV importer trailing lines are treated as absolute lines
• 405828 Budget problems
• 405928 Loss of inserted data in transaction planner
• 406073 Change of forecast method is not reflected in forecast view
• 406074 Unused setting “Forecast (history)” for home view
• 406220 Crash when deleting more than 5000 transactions at once
• 406509 “Find Transaction…” dialog focus is on “Help” button instead of “Find”
• 406525 Subtotals are not correctly aggregated when (sub-)categories have the same name
• 406537 Encrypted file cannot be saved as unencrypted
• 406608 Custom report based on Annual Budget incorrectly getting Actuals
• 406714 Home view shows budget header twice

If you’re celebrating Easter, we’ve got a gift for you: week 67 in KDE’s Usability & Productivity initiative! And if not… well you get it anyway!

New Features

• The KWin window manager now has initial support for using the proprietary NVIDIA driver in a Wayland session (Erik Kurzinger, KDE Plasma 5.16.0)

Bugfixes & Performance Improvements

• System Settings pages written in QML that are opened standalone now have the correct window height by default. This fixes the Fonts, Workspace Behavior, Mouse, Touchpad, and Launch Feedback pages (Marco Martin, KDE Frameworks 5.58):
  
• Fixed a common Plasma crash (David Edmundson, KDE Plasma 5.16.0)
• Kate and other tabbed editors using the KTextEditor framework no longer display the dreaded “ambiguous shortcut” warning dialog when switching tabs with the ctrl+page up/page down keyboard shortcuts because the “move insertion point to top/bottom of viewport” shortcuts have been changed to be alt+home/end (Cnristoph Cullman, KDE Frameworks 5.58)
• Fuel consumption conversion in KRunner now produces the correct results (Michal Malý, KDE Frameworks 5.58)
• Fixed a regression in dolphin that was preventing the “Create New” button from being added to the toolbar (me: Nate Graham, and Kai Uwe Broulik, KDE Applications 19.04.1)
• Mobile phones plugged into your computer no longer show two identical “Open with File Manager” items in the Device Notifier (me: Nate Graham, KDE Applications 19.08.0):
  

User Interface Improvements

• It’s now possible to replace a widget with an alternative one when in panel edit mode (Björn Feber, KDE Plasma 5.16.0):
  
• Discover now lets you force-quit it if you try to quit while it’s doing stuff–of course, it’s up to you to live with the consequences! (Aleix Pol Gonzalez, KDE Plasma 5.16.0)
• The Login Screen (SDDM) System Settings page got a visual overhaul (Filip Fila, KDE Plasma 5.16.0):
  
• It’s no longer necessary to check the “Force Rasterization” checkbox in Okular’s print settings to enable the page scaling options (Michael Weghorn, KDE Applications 19.08.0)

Next week, your name could be in this list! Not sure how? Just ask! I’ve helped mentor a number of new contributors recently and I’d love to help you, too! You can also check out https://community.kde.org/Get_Involved, and find out how you can help be a part of something that really matters. You don’t have to already be a programmer. I wasn’t when I got started. Try it, you’ll like it! We don’t bite!

If you find KDE software useful, consider making a donation to the KDE e.V. foundation.

Kipi Plugins is a set of app plugins for manipulating images.  They use libkipi which is released as part of KDE Applications.  It used to get standalone releases and was then moved to be part of Digikam releases.  Since Digikam 6 they have been deprecated by Digikam in favour of their new plugin framework DPlugins.  While in KDE Frameworks the Purpose Framework is another newer project covering similar features.

However Kipi Plugins are still supported by KDE apps KPhotoAlbum, Gwenview, Spectacle so they shouldn’t disappear yet.

I’ve made a new release available for download now.

https://download.kde.org/stable/kipi-plugins/

Versioned 5.9.1 because it is little changed from the previous release done inside Digikam which was 5.9.0.

Tagged commit b1352149b5e475e0fbffb28a7b5fe13503f24dfe

Sha256 Sum: 04b3d31ac042b901216ad8ba67dafc46b58c8a285b5162b51189833f6d015542

Signed by me Jonathan Riddell <jr@jriddell.org>

This will become part of KDE Applications in its next release scheduled for August and will follow the KDE Applications version numbers.

by

One of the things which makes Plasma so attractive is the officially supported option to customize also the style, and that beyond colors and wallpaper, to allow users to personalize the look to their likes. And designers have picked up on that and did a good set of custom designs (store.kde.org lists at the time of writing 454 themes).

Intended changes and unintended changes

In the 11 years since Plasma was released first (January 11, 2008) there has been some evolution of the theming options. Sadly also sometimes regressions in the support of older options were introduced, mainly in the early phase of Plasma 5 when code was ported to QtQuick 2 and the new default theme Breeze did not expose the regression or even triggered some changes for its special needs or for simplifications it allowed.

Given Breeze as default was pleasing to most, and possibly some alternative theme designers were lost during the longer phase from a pleasing KDE4 to an again pleasing Plasma 5, and new theme designers made their themes directly matching latest Plasma 5 Theme support, the piled-up regressions were not a real issue for those contributing.

Well, not a real issue unless on started to restore an old theme like “Fluffy Bunny”. And was wondering why it looks broken. And then wondering the same while playing with all the other old themes still available on store.kde.org.

So much partially good artwork being broken made my heart bleed, and in the absence of own designer abilities it was time to document the regressions as well as fix some code where possible to restore previous variability.

Teaching Porting to Plasma 5

So, theme designers, please find a a new page on techbase.kde.org about Porting Themes to latest Plasma 5. It lists the changes known so far and what to do for them. Please extend the list if something is yet missing. One might test the fixes in the code against one’s themes with latest development versions of Plasma using Live images.

Fresh old Air & Oxygen

And even the Oxygen & Air themes, the default Plasma themes during KDE4 times, while being maintained as official themes part of current Plasma releases, had suffered some small regressions (e.g. analog clocks hands rotation point or progressbar height). No more, with Plasma 5.16 the visual experience of Oxygen & Air should be closer to the original.

Luxury on the borders results in bad looks

Sadly there is one thing which is not so easy to fix: Plasma code now assumes for any frames (like with borders of panels & pop-up dialogs) that the actual border visuals are negligible and the margin from the outside to the content is the same, with border on the side enabled or not. With luxurious decorated borders (like Fluffy Bunny or Spoons Original) this sadly results in bad looking bigger margins on sides where the border is disabled (see details). Which is sad especially given that High DPI display actually would allow more fanciness, even more when in the future Flat design gets replaced by whatever new trend. My passive dreams & hopes are on for Plasma 6

Separating Plasma 5 compatible themes on store.kde.org

And while there now is a list of things to do to make old themes work again, many themes on store.kde.org no longer are maintained. There is talk about separating those, e.g. at time of Plasma 5.16 release, so there would be a clean list of working and maintained themes for latest Plasma 5.

As you can read in the official Creator 4.9.0 release announcement, Qt Creator now uses the KSyntaxHighlighting Framework for providing the generic highlighting.

This is a nice step for the wider adoption of this MIT licensed part of the KDE Frameworks.

And this is not just an one-way consumption of our work.

The framework got actively patches back that make it more usable for other consumers, too, like Kate ;=)

If you want concrete examples, take a look at:

• D18982: prevent assertion in regex load
• D18996: Fix building with namespaced Qt
• D18997: Add functions returning all definitions for a mimetype or file name
• D19200: Return sorted definitions for file names and mime types
• D19215: Install DefinitionDownloader header

I hope this cooperation will continue in the future. I thank the people working on Qt Creator that made this integration possible. I hope the initial effort will pay of with less code for them to maintain on their own and more improvements of the framework for all users.

Last week I flew to Brussels for EuroLLVM followed by Bristol for ACCU.

At both conferences I presented the work I’ve been doing to make it easier for regular C++ programmers to perform ‘mechanical’ bespoke refactoring using the clang ASTMatchers tooling. Each talk was prepared specifically for the particular audience at that conference, but both were very well received. The features I am working on require changes to the upstream Clang APIs in order to enable modern tooling, so I was traveling to EuroLLVM to try to build some buy-in and desire for those features.

I previously delivered a talk on the same topic about AST Matchers at code::dive 2018. This week I presented updates to the tools and features that I have worked on during the 6 months since.

One of the new features I presented is a method of debugging AST Matchers.

Part of the workflow of using AST Matchers is an iterative development process. For example, the developer wishes to find functions of a particular pattern, and creates and ever-more-complex matcher to find all desired cases without false-positives. As the matcher becomes more complex, it becomes difficult to determine why a particular function is not found as desired.

The debugger features I wrote for AST Matchers intend to solve that problem. It is now possible to create, remove and list breakpoints, and then enable debugger output to visualize the result of attempting to match at each location. A simple example of that is shown here.

When using a larger matcher it becomes obvious that the process of matching is short-circuited, meaning that the vertically-last negative match result is the cause of the overall failure to match the desired location. The typical workflow with the debugger is to insert break points on particular lines, and then remove surplus breakpoints which do not contribute useful output.

This feature is enabled by a new interface in the Clang AST Matchers, but the interface is also rich enough to implement some profiling of AST Matchers in the form of a hit counter.

Some matchers (and matcher sub-trees) are slower/more expensive to run than others. For example, running a matcher like `matchesName` on every AST node in a translation unit requires creation of a regular expression object, and comparing the name of each AST node with the regular expression. That may result in slower runtime than trimming the search tree by checking a parameter count first, for example.

Of course, the hit counter does not include timing output, but can give an indication of what might be relevant to change. Comparison of different trees of matchers can then be completed with a full clang-tidy check.

There is much more to say about both conferences and the tools that I demoed there, but that will be for a future log post. I hope this tool is useful and helps discover and debug AST Matchers!

Today I did run again into an old problem: You need to archive a lot small and large files inside a single Git repository and you have no support for Git LFS available. You did this several year and now you ended up in a state where cloning and working with the repository is unbearable slow.

What now? Last time I did run into that, I archived the overfull repository to some “rest in peace” space and used git filter-branch to filter out no longer needed and too large objects from a repository copy that then will replace the old one for daily use.

There are a lot of guides available how to use git filter-branch for that. All variants I ever used were complex to do and did take very long. Especially if you need several tries to get a sane set of stuff you want to remove to gain enough space savings.

This time, I searched once more and stumbled on the BFG Repo-Cleaner. And yes, it does what it promises on the web site and it seems to be trusted enough to be advertised by e.g. GitHub, too.

Just following the steps described on their landing page allows to shrink your stuff nicely and without a lot of round-trip time.

If you still are just in the “experimenting” phase to see which space decrease one can archive with which file size filter (or which files you want to purge by removing them from master before running the tool), I recommend to swap the step

git reflog expire –expire=now –all && git gc –prune=now –aggressive

with just

git reflog expire –expire=now –all && git gc –prune=now

to not wait potential hours for the aggressive GC. For me that was good enough to get some estimate of the later size for my experiments before I settled to some final settings and did the real run.

And as always, if you touch your Git history: Do that only if you really need to, keep backups, check carefully that afterwards the repository is in some sensible state (git fsck --strict is your friend) and inform all people using that repository that they will need to do a full new clone.

Changing routines to stay productive

As a remote worker, you need to find ways to keep productivity levels high. No matter how exciting your work is, there are times in which you struggle with keeping up the pace. Looking back at my performance during the last couple of weeks of January and first few days of February, I discovered that I was getting into a productivity valley, which never happened to me after coming back from a couple of weeks vacation. I decided to do something about it before the issue had any impact in my overall performance.

• I have a little place back in my home island, La Palma, Canary Islands, Spain, where I can work comfortably. So when I feel I am not being very productive at home, I move there for a couple of weeks. It does work well for me. I decided though to try something different this time.
• I go to the office in Manchester, UK several times a year. Those weeks there are intense and change whatever dynamic I am in. I spent there a few days early in February already but I decided to go back again the last week of March.
• Once in a while, specially on Fridays, I go to coworking spaces in Málaga, specially when I am at home over three weeks in a row. This past month of March I decided to join The Living Room coworking space, in Málaga. My idea is to work there once or twice a week the coming three months. So far the experience is positive.
• The first week of March, after the Embedded World 2019 and the CIP Technical Steering Committee face to face meeting in Nürnberg, I went to Prague for a week. I rented an apartment there and a hot desk at Impact Hub coworking space. The trip gave me the opportunity to break the routine while enjoying some of the many activities that the city offers. The classical music, opera, jazz and blues scene in Prague is rich. There are plenty of theaters and clubs to go to every night. Live music is one of my passions and Prague is perfect for it.

Impact Hub Prague is a big and busy coworking space with great facilities. It is maybe too crowded for people that have concentration difficulties or many video chats, but very good for entrepreneurs and freelancers. Those who have a fixed desk there work in more quiet areas. People were very friendly and I could have a productive week.

I am in the process of slightly changing some well established routines like starting a little earlier, reducing the lunch time and trying to finish a little earlier when working from home. I might also increase the amount of time I am working standing up.

It seems that all these measures are working so far although I will need a few more weeks to confirm this impression.

Scale Summit 2019

On Friday 29th March I attended to Scale Summit 2019 in London, UK, an unconference that works under Chatham House rules bringing together “professionals from the operations and software development communities who have a particular interest in scalable, high performance systems “.

It is a fantastic event. One of the best ones I’ve been to. This is the second time I have attended and will not be the last one. The quality of the discussions is very high and people go there to learn instead of to shine, sharing experiences and asking questions.

FOSS North 2019

I was invited by the FOSS North organizers to give a talk on Tuesday 9th April. This is a 2 days, 260 participants and two tracks event, that takes place in Gothenburg, Sweden. This was the fourth edition and the next one, at the same venue, will take place on March 30th and 31st 2020.

It was my first participation at this event and my first time in Gothenburg. FOSS North is well organized, vibrant, it takes place in good facilities, there were great speakers (Adrian DeGroot, Chris Simmonds, Mirko Boehm, Molly de Blanc, Michael Kerrisk, Chris Lamb, etc), some interesting talks, the food was great… and I liked Gothenburg. There will be videos available from every session. The speakers dinner was fun and interesting, which is not always the case.

Thanks Johan for the invitation and thanks Codethink Ltd for sponsoring my trip there.

I would recommend you to watch Mirko Boehm’s keynote “Open Source, Standards Development and Patents in Europe“. I found specially interesting the view of Open Source projects from the standardization bodies point of view he provided. It is always good to receive criticism with somebody else’s eyes. Specially controversial was the point referred to meritocracy.

I heard for the very first time about Property-based testing, which is an alternative approach to Example Based Testing (like Unit Testing). I believe it is kind of a structured way of doing Fuzz Testing. I will read more about this topic because I liked it. I initially find it specially useful for regulated environments (Contract Driven Development).

I got a good amount of feedback about my talk, which had a couple of controversial slides for some. I will deliver this talk again (in Spanish), this coming month of May at OpenSouthCode. Some of the comments will help me to improve the talk, which is always a good thing. I will link the video to the Conference section of this site as soon as it is available. Meanwhile I have published the slides already.

As part of the Community Day, on Sunday 7th, I attended to the KDE workshop driven by Adrian DeGroot. I took with me my RPi3 and RPi screen with Plasma Mobile and my 10″ Lenovo tablet with openSUSE Tumbleweed and Plasma. Adrian took his 7″ device, also with Plasma so the room looked like an embedded oriented workshop.

There were several other activities from different communities in different locations across Gothenburg that same Sunday. Several companies and non-profit organizations hosted these workshops. This warming up activity was considered a success so it will take place again in the 2020 edition. There were a few booths from sponsors at the event. Most of the companies present were recruiting.

If you are in Scandinavia, think about attending to this event next year. It is a good one.

In May I will attend to OpenSouthCode and J On The Beach, both in Málaga area. See you there!

Go get  v0.8.8   from, download.kde.org^*  or  store.kde.org^*

• multi-screen fix: unload properly explicit screen docks when their screen is not available any more

Donations:

• Latte Dock 
• Latte Spacer
• Window Title Applet
• Window Buttons Applet
• Window AppMenu Applet
• Latte SlideShow 
• Latte Window Colors
• Dock and TopBar, Latte layout