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!
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.
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!
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.
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.
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.
So much for the organizer perspective, now to the content. During the hack days I mainly discussed Transitous and KDE Itinerary topics:
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.
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.
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.
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.
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:
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)
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)
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 now renders fonts with hinting when using a scale factor over 100%. (Infinality, Qt Bug #128874)
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)
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)
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)
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)
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)
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)
Bluetooth devices renamed in the audio settings now correctly use their new name throughout the UI. (Julian Bouzas, wireplumber issue #1043)
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.
Push a commit to the relevant merge request on invent.kde.org.
Let’s go for my web review for the week 2026-42.
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
Tags: tech, rss, self-hosting
Nice resource listing many tools available around RSS. Plenty to choose from including self-hostable options (but not only).
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
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/
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/
Tags: tech, iot, security
Looks like connecting everything isn’t the best idea after all.
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
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?
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
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
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/
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
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/
Tags: tech, html, css
This is finally a solved problem. No more ugly border workaround.
https://www.rubenerd.au/css-for-underlines/
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
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
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
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!
Kdenlive development for the 26.12 release is very active, and we would like to request some feedback regarding two of the upcoming features.
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.
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.
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.
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.
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.
@ivan:kde.org
ngraham
project folder is correctly detected (default location, parent folder, or custom folder).
Experimental Builds
These downloads are for testing only, please do not use in production.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.
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 changelogFor 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!
