KDE announced its three voted goals for the next two years at Akademy 2026 in Graz, Austria. Goals are where the project directs extra effort, and this set is unusually pragmatic.

KDE for Enterprises and Deployments

The headline, and the one that says something about where KDE thinks it can grow.

The work items are not desktop polish. They are the things that decide whether an IT department can deploy a desktop across a few thousand machines:

• LDAP integration in Plasma
• Password expiry support
• SSO-based accounts and logins
• Improved network printer settings
• Headless remote and terminal support

None of that is exciting and all of it is blocking. A desktop that cannot authenticate against the existing directory, cannot enforce a password policy, and cannot be managed without someone sitting at it is not a candidate for a corporate rollout regardless of how good it looks.

The SSO item is the most consequential. Corporate environments are built on single sign-on, and a desktop that makes users type a second set of credentials is a desktop that generates helpdesk tickets. If you want to understand the mechanism KDE is targeting, our Authelia guide covers the same pattern at the self-hosted scale.

Headless remote and terminal support is the sleeper. It matters for thin clients, for VDI, and for the growing number of deployments where the desktop session runs somewhere other than the desk.

Better documentation

The description is refreshingly blunt about the problem: eliminating outdated, misleading and duplicative documentation, improving tutorials, and creating a contributor guide.

Duplicative and misleading are the operative words. KDE’s documentation problem has rarely been absence. It has been three pages describing the same feature, written across a decade, with no indication of which one still applies. That is worse than nothing, because it costs the reader time before it costs them accuracy.

The contributor guide is the part with compounding returns. Every hour spent making it easier to start contributing buys back more than an hour later, and it is consistently the work that gets deferred because it helps people who are not in the room yet.

Next Generation Styling

Two halves, split between designers and engineers:

• Designers work on Ocean, a design system intended to produce a uniform look rather than a collection of individually reasonable decisions
• Engineers work on Union, the theming engine underneath it

This is the correct division. Plasma’s flexibility has always been its identity and also its inconsistency: enormous configurability with no single source of truth about how things should look, so applications drift apart. A design system plus a theming engine built to express it is the structural fix rather than a coat of paint.

It is also a multi-year effort, which is presumably why it is a two-year goal and not a release note.

Where this leaves Plasma

The goals run alongside ordinary development. Plasma 6.8 is in post-beta polishing while 6.9 starts picking up activity, and recent work has included auto-scrolling and dwell clicking and faster panel autohide.

Goals are not roadmaps. They signal where extra attention goes when developers have discretion, which over two years tends to matter more than any single release does.

The enterprise choice is the one to watch. GNOME has held the institutional Linux desktop largely by default, through Red Hat and Ubuntu shipping it. KDE deciding to compete there on the unglamorous requirements rather than on features is a more serious challenge than it first appears.