KDE's Goals

KDE is a huge and diverse community working on hundreds of projects, from our flagship Plasma desktop to knowledge bases like WikitoLearn and including teams which help cross-project such as our Visual Design Group or Promotion team.

To guide our work we have selected 3 goals to focus on over the next couple of years.

KDE is All About the Apps

KDE has over 200 applications and countless addons, plugins and Plasmoids. We offer useful services to them as projects such as Git hosting, teams of translators, designers and artists, some release management if they are part of KDE Applications. But much of the support we offer has fallen short, until recently there wasn't even an up to date website listing them all. There is no method of taking decisions on how these support services are provided and proposed changes often stall such as when the kde.org/applications did for a year.

With new packaging formats we will now be able to release apps directly to users on Linux, our main target platform. This means we need to review our processes and up our game in many areas because no more will we be able to rely on 3rd parties to finish off our software and make it useful and attractive to users, we need to do that ourselves.

KDE has many fabulous apps, let's take them out to the world!

Wayland

Wayland has been of great interest and effort to the KDE community as it aligns with our values and goals to produce software that is secure, lightweight and beautiful. See more about Wayland on our Wayland page.

This goal will prioritize tracking down and fixing the issues that keep our software from achieving feature parity with the venerable X Window system. Our focus will be our own software — KWin, Plasma and Apps — but will also be about helping the wider free software community to advance the Wayland feature set.

This is an ambitious goal. It cannot be a small team effort, and we invite the wider community to participate.

Wayland logo

Consistency

"Consistency" here means having a single solution for a particular problem rather than many different ones. This applies to application design elements, feature implementations, website structure and style, and the KDE ecosystem as a whole that, unfortunately, often suffers from redundancy.

Benefits of consistency include:

  • Increased software usability: users recognize patterns that are common across KDE applications, which makes each one easier to learn and master.
  • Stronger branding: the use of consistent visual elements throughout KDE software allows users to quickly recognize KDE products.
  • Better discoverability: users are able to quickly locate useful information on our websites and choose software that helps them achieve their goals.
  • Better maintainability: reduced code redundancy simplifies making changes to the codebase.
  • Reduced complexity of writing new software: high-quality reusable components are available, eliminating the desire to reimplement.