fidzu : KDE

19 Oct 2026 8:50am GMT

Bending is the hardest thing to learn on a harmonica, mostly because you can't see it. You change the shape of your mouth and throat, and the only feedback is whether the note sounds right, which is exactly what a beginner can't judge yet.

The bending trainer is the screen in Harmonicon for practising that, one bend at a time. There's no song and no score. You pick a hole, play, and see where your pitch goes.

The screen has three parts: a settings strip at the top, the target card in the middle, and the harmonica diagram on the right.

Settings

Setup picks the harmonica key and the pitch detector (here, "C harp · FFT"). Scope and Practice control the drill, covered below. Then there's a metronome with tempo, click and straight/shuffle feel, and Advanced.

Setup and Advanced open as floating panels, so the pitch display doesn't move while you're using it.

The target card

The card shows the current target, here hole 2 draw bent a half step, and how it has gone for you so far.

The line under the title only reports on the selected hole. Silence, the wrong hole and an unstable signal each get their own message. You only get a cents reading when you're actually near the target.

The rail runs from the natural note (G4) to the target band (F#4). While you play, a marker shows your pitch and a trail of dots shows the last few seconds, so you can see whether you slid in smoothly, scooped, overshot or held still. On holes with several bend depths, the shallower ones are marked along the way.

Below the rail are three separate numbers: distance from the target, stability, and how long you've held it.

Natural and Target play both notes as reference tones. Check natural note is optional: play the hole unbent and the trainer measures where that reed really sits on your harmonica, then judges the hole against that instead of the textbook value.

The diagram

The diagram shows every note the harmonica can make, by hole and technique. Blue notes are blown and orange notes are drawn, so overblows are blue even though they sound above the draw note.

Click a cell (or use Tab, the arrow keys and Enter) to make it the target. A hint for the selected bend appears underneath.

After some practice the diagram doubles as a progress map. Each cell is tinted by how reliably you control that bend, with a bar along the bottom showing the same thing, so it's readable without telling red from green.

Practice and the drill

Practice sets what counts as one success:

• Free exploration: nothing, just play.
• Find and hold: reach the target and stay there.
• Bend and release: go down to the target and back to the natural note.
• Repeated bends: bend on the metronome beats.
• Bend ladder: step through each bend depth and back.
• Overbend response: attack and release an overblow or overdraw.

Scope sets which targets the drill uses: First bends (holes 2 and 3 draw, the default), All bends, Blow bends, Overbends, or Custom, where you click cells to add or remove them.

With Drill on, the trainer picks targets from that scope, favouring ones you haven't tried, control less well, or haven't practised lately. It moves on when you complete the practice shape. Skip moves on immediately, and silence doesn't count against you: an attempt only counts once the microphone hears that hole. Progress is saved between sessions.

Advanced

Advanced sets the tolerance, hold time, attempt timeout, A4 reference, and how much history and smoothing the rail uses. It also shows stats for the current attempt: mean distance, spread, best hold, and vibrato speed and width.

The trainer only reports pitch. It doesn't claim anything about breath, embouchure or reed health, because a microphone can't measure those.

Esc or the back arrow leaves the trainer, and drill progress is saved on the way out. The code is on GitHub.

18 Oct 2026 12:00am GMT

Since Tellico is turning 25 years old, I decided to use the current generative AI tools to create several new entry templates. There may be some quirks I didn't find, but they cover a variety of layouts and design themes. Install them from within Tellico via the Settings ➜ Templates dialog. They're also in the Tellico Add-ons Repository. Enjoy!

Modern

Anniversary

Dark Orbit

Jewel Case

Vintage Catalog

17 Oct 2026 5:06pm GMT

Depending exactly on when I mark the date, Tellico is turning 25 years old this month. The ChangeLog tells me I released Bookcase 0.1 on November 4, 2001. Bookcase was the original name of the application. I renamed it to Tellico after I was contacted by another software developer.

I thought it would be fun to look back at a few of the milestones.

November 2001

Bookcase 0.1 is released.

February 2002

Bookcase 0.2 is released, notable since the second release is harder than the first, right?

November 2003

The first home page goes live.

January 2004

Images are added to the collection for Bookcase 0.8. along with several new collection types.

September 2004

Bookcase is renamed Tellico, with version 0.12 the first release with the new name.

May 2005

The tellico-users mailing list is first established, hosted by Novell Forge.

September 2005

Tellico 1.0 is released!

June 2006

Templates for what later became KDE Store were launched.

May 2009

Tellico moves into KDE Extragear, hosted by KDE itself, and away from Novell Forge (which shut down not too long after).

August 2009

Tellico gets its own domain name, tellico-project.org. Having a dedicated domain finally implies a real project, no?

September 2009

Tellico 2.0, the first release for KDE4, is made available. I was very excited about it but rather quickly found a bug.

May 2011

Tellico followed the lead of many programs and transitioned from subversion to git.

November 2016

Tellico 3.0 is released, the first version using Qt5 and KDE Frameworks 5.

February 2022

The first testing version of Tellico for Windows is built.

September 2024

Tellico 4.0 is released, the first version to leverage Qt6 and KDE Frameworks 6.

All told, it's been a fun journey, with fits and spurts of development or personal life leading to a pause. I use Tellico for my books, videos, old music albums, and coin collection, personally. We'll see how long it continues!

17 Oct 2026 4:50pm GMT

Just a teaser of a small thing I'm working on.

Our amazing meta-meta-builder tool kde-builder (just like its predecessor kdesrc-build) is indispensable if you're building many KDE things from source.

The only problem I have with it is that it is overly verbose. It generates ~10 lines of text for each project it compiles. This requires a lot of scrolling for people with a slight OCD (like me) that want to keep track of everything built and everything that failed to build while the tool is working.

For this reason, I wrote a Python (go figure, me and Python) script that processes the output from kde-builder and renders it in a terse single-page dashboard.

The dashboard shows the project that is currently being built, a list of projects that failed to build and a list of projects that were built successfully. It also collects all optional dependencies that different projects reported as missing and lists which projects have those dependencies.

It also allows for an easy access to build logs - just click on the failing project, and it will open its error.log in $PAGER (in a separate TMUX tab if you are using TMUX).

Similar to this, if you click on a project that reported some optional dependency, it will open cmake.log so that you can see all the dependencies that project has.

I'll publish it to invent when I clean up the code a bit, and when I fix some of the remaining issues.

17 Oct 2026 3:35pm GMT

I spent last week in Bern, Switzerland, for the second edition of the Open Transport Community Conference, attending that but also being part of the organizer team.

Open Transport Community Conference

Compared to last year the event has grown quite a bit. The event got merged with the OTP Summit, a yearly event by the OpenTripPlanner community with a lot of overlap in topics.

Besides the two unconference days there now also were two less structured "hack days". Due to venue constraints those had to happen before the unconference part, which worked for the larger project teams that already knew each other and had prepared agendas, but would probably have been better the other way around for new people not knowing anyone yet.

A lot of work had also gone into moving the event under the umbrealla of the FOSSGIS e.V.. That enabled us to handle sponsors and (optional) paid tickets this year, to cover lunch for all days. And it hopefully put the event on a sustainable base for years to come.

There were about 140 people attending at the peak, from all over Europe as well as a few people from North America. German speakers were still over-represented, while e.g. the French community was clearly under-represented. We had a good mix of people representing different roles and stakeholders though, covering transport operators, public agencies, standardization, research, politics, FOSS and Open Data projects, etc.

I'm very happy we managed to find an organization to host the event again with SBB and opentransportdata.swiss. Hopefully we can continue this, and keep rotating between different countries, to give more people a chance to attend.

Hack Days

So much for the organizer perspective, now to the content. During the hack days I mainly discussed Transitous and KDE Itinerary topics:

• Meta stations in Transitous, ie. what happens when you search for a journey from Paris to London. The expectations there is usually not an exact route between city center points, but between appropriate major transport hubs such as major railway stations or airports. Large cities can have more than one of those though, which means all of those should be considered (ie. treating those as one "meta station"). It's however non-trivial to define exactly what the expected outcome is here, and we went through many different approaches for which we found unfixable counter-examples. There's two possible approaches left now that could work generically and mode-independent, those would need to be implemented for more wider testing.
• Geocoding issues in Itinerary, ie. searching for locations resulting in unexpected or confusing results. Jonah improved result merging for this, and we found some issues with parsing Photon responses that added misleading results.
• Decoding Spanish and Norwegian train ticket barcodes. Updates to the Train Ticket Wiki and the Train Ticket Kaitai Spec repository are under way.
• Implementing the MOTIS journey refresh API for KPublicTransport. Turned out the partial results we were seeing there were due to not setting all required parameters correctly.

There's of course many more things that other people worked on, see for example the notes in the Transitous wiki. Transitous now also covering the Chinese railway system is another significant outcome.

Máté showed an experimental iOS port of Itinerary. The amount of code changes needed for that throughout the stack looked manageable from what I saw, and the first patches to KDE Frameworks are already being upstreamed now. The big challenge for bringing that to production is the building, packaging and delivery part though.

Unconference

Session planning for the unconference part went a lot smoother this time, despite having fewer rooms for parallel sessions. The selected topics seemed even broader than last year.

• Evolving data standard like GTFS, GTFS-Flex, NeTEx and SIRI. I'm particularly excited seeing the community getting more and more actively involved in shaping these.
• Deckplan data. This is very relevant for wheelchair accessibility but also when traveling with bikes or a stroller. Also nice to see that the standardization work there isn't limited to trains but contains anything from a simple bus to a larger ferry.
• Opened Data. Somehow this term stuck, referring to all kinds of legal, technical or political approaches to obtain data that isn't voluntarily Open Data.
• Crowd-sourcing data. When data cannot be obtained or isn't available, people are increasingly looking for ways to fill those gaps themselves, with increasing scope and creativity.
• Ticket standards. A somewhat niche topic, but an amazing examples of how the entire domain got infiltrated and taken over by the community, from reverse engineering a few years ago to now working on the next generation EU ticket standard with an official mandate. We need more of this.
• Dynamic traffic data. This has already been a hot topic at OSM events recently, with various bits of ongoing work presented here.
• C-ITS was also a prominent topic in this context, but also for e.g. priorizing public transport at traffic lights and the additional security implications that come with it.
• Routing algorithms and journey planners like MOTIS and OpenTripPlanner, as consumers of much of the above.
• Aligning schedule, stop and infrastructure data with OpenStreetMap, as well as upstreaming data to OSM or building OSM QA tooling. This matters as we ultimately route on the OSM data, and for that need to be able to match e.g. realtime elevator data to the right OSM object.

There were also more sessions this time focusing on primarily political aspects rather than technical ones, such as passenger rights and illegal border controls.

We also had a small session about onboarding in the Open Transport community in general and the conference in particular. Open Transport encompasses a lot of different very specialized topics meanwhile, with many of the conversations being very jargon- and abbreviation-heavy, which can be off-putting.

Much of this has grown organically over time from local and fragmented efforts, so it's not always easy to find who to talk to about a specific topic. We recently added the Open Transport Community Matrix space to make it easier to find the right communication channel, ideally we'd also turn the open-transport.org website into a more general entry point. Help welcome.

Most sessions have notes that can be found in the wiki, next to the lightning talk slides.

Outlook

The event got again very positive feedback, people seemed to enjoy it and consider it useful, as e.g. also Brede's report indicate. There's clearly interest and demand for a third edition, but we still need a venue and people doing the work for this. If you happen to have a lead on a venue or want to help out by other means, please get in touch, via the conference Matrix channel or by email.

There's several options to meet before that as well, a few members of the Transitous team will be at the upcoming OSM Hackweekend in Berlin next week for example, and there's already work ongoing for organizing the Open Transport presence at 40C3 and FOSDEM 2027.

17 Oct 2026 7:45am GMT

Welcome to a new issue of This Week in Plasma!

This week we released Plasma 6.8, but we didn't stop there: work on Plasma 6.9 has been coming in hot and heavy, and there's a lot to talk about! So let's jump right in:

Notable new features

Plasma 6.9

The Weather Report widget has received massive changes: a new layout that includes per-hour temperature and precipitation forecasts, and support for weather forecasts from Open-Meteo. (Bohdan Onofriichuk and tusooa the west wind, kdeplasma-addons MR #1037, KDE Bugzilla #451767)

Plasmas's on-screen keyboard has been extensively re-worked, and now includes multiple desirable features: the option for a full-size keyboard including arrow and modifier keys; a flick keyboard for Japanese; and distinct layouts not tied to system locales. (Devin Lin, plasma-keyboard MR #109)

The Night Light feature now lets you temporarily enable or disable it for a specific period of time, independent of its normal schedule. (Vlad Zahorodnii, kwin work item #321)

If you'd prefer your System Tray icons to be really small, you can now configure them that way. (Jin Liu, plasma-workspace MR #6978)

Notable UI improvements

Plasma 6.8.1

Plasma now shows an OSD when you use the keyboard to increase the brightness when it's already at its maximum level, just like it already does when when you do try to increase the volume when that is at its maximum level. (Pavel Radzivilovsky, KDE Bugzilla #505558)

Plasma 6.9

Clipboard-related keyboard shortcuts shown in System Settings are now grouped into their own section, rather than in the generic "Plasma Workspace" section. And the feature to basically rotate the entire clipboard history up or down (such that a new item becomes the top one, and you can easily paste it) now uses that terminology to make it easier to figure out how the feature works. (Taras Oleksyn and Tomáš Hnyk, plasma-workspace MR #7208, KDE Bugzilla #467252)

Plasma no longer shows a notification about a new screen being connected if it's a virtual output. But if it's a real physical screen, the notification now shows more information about that screen. (Kai Uwe Broulik, plasma-workspace MR #7233, plasma-workspace MR #7195)

Removing a network on System Settings' Wi-Fi & Networking page no longer hides the right pane until you select a new network in the sidebar. (Taras Oleksyn, KDE Bugzilla #511362)

On operating systems that configure Discover to use both PackageKit and "offline upgrades", the page that includes details of every package being updated now also tells you the current package versions, not just the new ones. (Taras Oleksyn, KDE Bugzilla #500663)

Qt 6.13.0

Qt now renders fonts with hinting when using a scale factor over 100%. (Infinality, Qt Bug #128874)

Notable bug fixes

Plasma 6.6.7

Fixed a bug that made Plasma's built-in RDP server crash when the client uses a very large pointer. (Curious J Tuber, kpipewire MR #285)

Plasma no longer fails to launch on a system with a broken MIME type database. (Kai Uwe Broulik, plasma-workspace MR #7214)

Fixed a bug that made section headers go missing on System Settings' Bluetooth page when using a language other than English. (Kai Uwe Broulik, bluedevil MR #270)

You can now disable the "running out of disk space" notification, if you'd like. (Kai Uwe Broulik, plasma-workspace MR #7202)

Plasma 6.7.6

Fixed a bug that made Plasma's built-in RDP system unstable when using the Microsoft RDP client on Android. (Yury MonZon, KDE Bugzilla #520260)

Fixed a bug that prevented the feature to save your current settings as a new Global Theme from successfully saving whether or not the panel should float. (Marco Martin, KDE Bugzilla #526843)

Plasma 6.8.1

Fixed a bug in the Task Manager widget that would occasionally make Plasma crash. (David Edmundson, plasma-workspace MR #7149)

Plasma's built-in RDP system is now more reliable when receiving connections from the Microsoft RDP client on Windows. (Mauricio de Lima, krdp MR #251)

Fixed a few cases in the Audio Volume widget and its System Settings page where tooltips showed un-escaped HTML or ate ampersands. (Tobias Fella, plasma-pa MR #433)

Fixed a bug that made the Kup backup system's background daemon auto-start when it wasn't actually being used. (Iyán Méndez Veiga, kup MR #68)

Plasma 6.9

KRunner-powered search fields once again find power-related items like "Shut Down" and "Restart" without you having to type out the entire text. (Ramil Nurmanov, KDE Bugzilla #522158)

On System Settings' Region & Language page, languages can now be dragged up and down in their list view without functional and visual glitches. (Vsevolod Stopchanskyi, plasma-workspace #7189)

Task Manager tooltips for Flatpak apps now always show media and volume controls when needed. (Kai Uwe Broulik, KDE Bugzilla #518840)

Frameworks 6.32

Fixed a bug in the Breeze icon theme that resulted in GTK apps that respect the icon theme displaying certain Breeze icons at the wrong size. (Alexey Varfolomeev, KDE Bugzilla #493975)

Qt 6.12.1

Fixed a bug in Qt that could occasionally keep Plasma from quitting properly during logout when any panels had a visible Pager widget on them. (David Edmundson, KDE Bugzilla #525727)

WirePlumber 0.5.19

Bluetooth devices renamed in the audio settings now correctly use their new name throughout the UI. (Julian Bouzas, wireplumber issue #1043)

How you can help

KDE has become important in the world, and your time and contributions have helped us get there. As we grow, we need your support to keep KDE sustainable.

Would you like to help put together this weekly report? Introduce yourself in the Matrix room and join the team!

Beyond that, you can help KDE by directly getting involved in any other projects. Donating time is actually more impactful than donating money. Each contributor makes a huge difference in KDE - you are not a number or a cog in a machine! You don't have to be a programmer, either; many other opportunities exist.

You can also help out by making a donation! This helps cover operational costs, salaries, travel expenses for contributors, and in general just keeps KDE bringing Free Software to the world.

To get a new Plasma feature or a bug fix mentioned here

Push a commit to the relevant merge request on invent.kde.org.

17 Oct 2026 12:00am GMT

This is the release schedule the release team agreed on

https://community.kde.org/Schedules/KDE_Gear_26.12_Schedule

Dependency freeze is in less than 3 weeks (November 5) and feature freeze one
week after that. Get your stuff ready!

16 Oct 2026 10:15pm GMT

Let's go for my web review for the week 2026-42.

---

The importance of communities around software

Tags: tech, foss, licensing, community, ethics, governance

Good reminder that licensing is only one signal. The governance is what matters for Free Software communities. This means looking at more than just the license to pick your folks.

https://lumi.codeberg.page/blog/software-community.html

The RSS Universe - Readers, Tools & Standards

Tags: tech, rss, self-hosting

Nice resource listing many tools available around RSS. Plenty to choose from including self-hostable options (but not only).

https://toolbox.rss.here.now/

WING COMMANDER III to get a surprise remaster

Tags: tech, gaming, culture, history

OK, now that's a blast from the past. I liked this game.

https://thewertzone.blogspot.com/2026/10/wing-commander-iii-to-get-surprise.html

Triple-A Minesweeper

Tags: tech, gaming, satire

OK, that's a funny one. You thought there was no back story to minesweeper? Time to see it differently.

https://minesweeper.mikelacher.com/

How Amazon pushes up prices all across the Internet

Tags: tech, amazon, business, criticism

Or how Amazon manages to enshittify things even outside of its platform…

https://www.not-ship.com/how-amazon-pushes-up-prices-all-across-the-internet/

'Unprecedented' Cyberattack cripples supermarket fridges across Europe

Tags: tech, iot, security

Looks like connecting everything isn't the best idea after all.

https://www.tomshardware.com/tech-industry/cyber-security/unprecedented-cyberattack-cripples-supermarket-fridges-across-europe-as-hackers-activate-automatic-defrosting-delivery-and-store-prices-also-impacted-by-incident

How Technology Empowers-and Imperils-Dictators

Tags: tech, ai, machine-learning, gpt, fake-news, surveillance, politics

Interesting opinion piece on how autocracies benefit greatly from the current AI arm race. But the short term benefit will also create new weaknesses.

https://www.schneier.com/blog/archives/2026/10/how-technology-empowers-and-imperils-dictators.html

AI agents aren't 'going rogue.' Frontier labs are skipping security basics

Tags: tech, ai, machine-learning, gpt, security

Between this and the scrapers behavior… the disregard for infrastructure and best practices is obvious. It's just another externality those so called "labs" don't want to deal with. And well, it makes for a marketing stunt each time isn't it?

https://www.csoonline.com/article/4234854/ai-agents-arent-going-rogue-frontier-labs-are-skipping-security-basics.html

Steering AI Beyond Automation

Tags: tech, ai, economics, research

I'm not agreeing with some of the points in here. That said the core position of "it should be about collaboration not automation" I'm very much aligned with. It's after all at the center of how we designed AI systems in my team twenty years ago. We really wanted systems helping the user in their task. It was about co-constructing the result with the support of the machine rather than answers from some kind of "oracle".

https://www.normaltech.ai/p/steering-ai-beyond-automation

My self-hosted infrastructure with Incus OS

Tags: tech, infrastructure, incus, self-hosting

Looks like a very neat setup. Probably a few good ideas to borrow in there.

https://dataswamp.org/~solene/2026-10-15-selfhosting-infrastructure-incus-os.html

Branches in branch-free code

Tags: tech, cpu, compiler, security

Interesting case of the compiler not generating the code you'd expect on some platforms. The problem is that it can bring security implications you don't want.

https://00f.net/2026/10/09/llvm-compiles-branch-free-code-into-branches-on-risc-v/

Lifeguard is a static analyzer to detect Lazy Imports incompatibilities in Python

Tags: tech, python, linting, tools

Early days but this could help better use lazy imports in Python. It's not exactly a transparent process.

https://github.com/Facebook/lifeguard

2D Vehicle Physics Prototype

Tags: tech, game, physics, simulation

Nice! A recreation of the 2D physics simulation used in the very first GTA. Loved that game and it had a very nice feel in its simulation at the time.

https://patkerr.co.uk/2d-vehicles/

CSS for underlines

Tags: tech, html, css

This is finally a solved problem. No more ugly border workaround.

https://www.rubenerd.au/css-for-underlines/

The Boots Theory of Software Architecture

Tags: tech, architecture, business

Unexpected metaphor but it kind of works. Indeed, architecture work is expensive, that doesn't make it unnecessary.

https://kevlinhenney.medium.com/the-boots-theory-of-software-architecture-e18cf0fa5a1b

The geometric model of maintenance

Tags: tech, maintenance, estimates

The article equates effort with lines of code a bit too much for my taste. That said I think this model can be useful to describe how maintenance works in a given project.

https://entropicthoughts.com/geometric-model-of-maintenance

How To Sound Smart When Talking About Charts

Tags: tech, data-visualization

Aphorisms and ideas on how to treat data visualization properly.

https://graphpaper.substack.com/p/how-to-sound-smart-when-talking-about

You Can't Change Your Boss

Tags: management, work

Unfortunately it's true. Terrible bosses are generally the one who can't handle feedback and so won't change.

https://jacobian.org/2026/oct/12/you-cant-change-your-boss/

---

Bye for now!

16 Oct 2026 11:09am GMT

Kdenlive development for the 26.12 release is very active, and we would like to request some feedback regarding two of the upcoming features.

Title Editor

One of the feature is related to the title editor. Our title editor has always been functional but rather limited. A new feature was recently implemented by klg that allows having different font styles in a single text block.

Note that several other great improvements were made by other contributors, like: Undo/redo support, implemented by Jaimukund Bhan, and Copy/paste support, implemented by chocolate image.

Relative paths for projects

The second large change is the switch to relative paths in project files. This means that if your videos or images are in the same folder as the project file (or a subfolder), you can easily move your work to another drive and reopen it without issue. This should really improve the experience for people editing projects on several computers, or switching between different operating systems. And this should also fix issues for teams doing collaborative work with projects on network drives or removable drives.

How you can help

We did some regression testing and have some unit tests for both these new features, of course, but some real-life scenarios may not be covered, which is why having feedback from testers is very valuable to us. Download the binaries from the link below and use this development version (26.11.70) to test the steps as described below, then report your findings in the comments section.

To test the title editor changes

The goal is to ensure existing titles display exactly as before and that there are no changes to the position or attributes of the titles.

1. Open your project files, ensure your existing titles display and render correctly.
2. Save your project to a new file, try to reopen and ensure it still displays and renders fine.

To test the relative paths changes

The goal is to ensure that all files in existing projects are correctly found, that you can render, save, open again, and all files are still correctly found.

1. Open your projects, ensure that all files appear correctly.
2. Check in the project settings that the project folder is correctly detected (default location, parent folder, or custom folder).
3. Check that rendering works correctly (no missing images ore videos).
4. Save the project with a new name (Save As), then repeat steps 1 thru 3.
5. If you sometimes edit from multiple computers, save the project under a new name and ensure that you can open and save the project file correctly from your different computers.

Download

Linux Appimage can be downloaded from Kdenlive's unstable download folder. Make it executable from your file manager before running it.

Windows installer can be downloded from Kdenlive's unstable download folder.

Development Flatpak can be installed from KDE's cdn server.

16 Oct 2026 8:30am GMT

Today KDE releases a bugfix update to KDE Plasma 6, versioned 6.6.7.

Plasma 6.6 was released in February 2026 with many feature refinements and new modules to complete the desktop experience.

This release adds three months' worth of new translations and fixes from KDE's contributors. The bugfixes are typically small but important and include:

KDE today announces the release of Plasma 6.6.7: the first bugfix release in the Plasma 6.6 Long-Term Support (LTS) series, which will still receive bugfixes and backports for a period of 3 years. Plasma 6.6.7 includes numerous bug fixes, improvements, and backports, addressing issues reported by users and developers, improving the overall quality of the desktop.

View full changelog

16 Oct 2026 12:00am GMT

For more than 20 years, I've been part of the KDE community, one of the largest and most impactful Free and Open Source software community world-wide. Yesterday, KDE turned 30 and this went accompanied with the premiere of the KDE documentary.
As former release manager, Plasma core developer and KDE e.V. board member, I've also been interviewed. A fairly prominent NPC role went out to Skippie, my cat.

Lately, I have been back into Free Software development, working on two apps that are closely related to hobbies of mine. Watch this space for news! Something nice has been cooking!

15 Oct 2026 2:32pm GMT

Tagoross published its first open content package, one day after KDE turned thirty. Two good days in a row Yesterday was a great day for me. KDE turned thirty years old. The KDE documentary, published to celebrate the anniversary, was delightful. Today is no less special for me. The first Tagoross package This morning, Tagoross … Continue reading Tagoross releases its first open content package on AI openness

15 Oct 2026 11:00am GMT

We are happy to announce the release of Qt Creator 21 Beta2.

15 Oct 2026 8:49am GMT

When I joined KDE in 1999 I already thought of it as a mature project. I used the KDE desktop every day, and I was delighted with what it could do and how it felt. I had no idea that this would be one of the most impactful decisions of my life, or where it would lead me.

Today we are celebrating the 30th anniversary of the original announcement of KDE. The project is still alive and kicking. I still use it every day, just like millions of other people. Not only because it's great software, but because of the values it embodies.

KDE stands for freedom and being able to shape your own destiny. As the KDE vision says: "A world in which everyone has control over their digital life and enjoys freedom and privacy." While I originally joined for the technology, this is what made me stay.

One of my favorite pictures illustrating the spirit of the community is the group picture of Akademy in Dublin in 2006. Brilliant people having fun working towards a shared purpose of digital freedom.

KDE gets a wonderful present for its birthday. The KDE documentary is premiering today. It tells the story of the founding, the rapid early development, and the license conflicts. How it became a solid product used by many people, and then put it all at risk with KDE 4. How we learned from that and turned it into this extremely resilient and lively community it still is today. I'm happy I could contribute to this story, and that I'm one of the people telling it in the documentary.

For me, KDE shaped my career and my life, and gave me the opportunity to grow and learn. It led to things I would never have expected when I started: my code running on millions of computers, talking to hundreds of developers at conferences, sitting at the negotiation table with Nokia in Helsinki, consulting as an expert in the German parliament. And much more.

Today, KDE is maybe stronger than ever. We reached a lot of new users with the Steam Deck. The Sovereign Tech Fund is investing more than a million euros in KDE. With the strategic goals the community set this year, we are addressing enterprise, documentation, and styling. It shows how much the project has matured, beyond what I could ever have imagined. It also shows in its contributors. While contributors leave over time, new generations come in every year and keep the community growing over the long run, combining stability and rejuvenation.

I'm proud and grateful. Proud of what the KDE community achieved. Grateful that I could be part of this amazing group of people. A team nobody could have hired.

Happy birthday, KDE.

14 Oct 2026 12:28pm GMT

14 Oct 2026 9:34am GMT