Reasons to close Wishlist items

Request for new Plasmoid

The core development team is not developing Plasmoids. This can be done by the larger community which doesn't use bugzilla.

Adding magic behavior

One of the design principle of Plasma is to not have unexpected behavior. So any request for adding functionality which is hidden and unexpected cannot be accepted. Examples are actions on mouse clicks or actions when holding a modifier. Adding options to enable the magic behavior is not acceptable.

Config options to default Plasmoids

The default Plasmoids are kept stupid and simple for a reason. They should provide only the minimum required functionality. If more functionality is required this should be done in a dedicated Plasmoid (e.g. Tasks applet vs. Icon Tasks). Adding further functionality which would need another config option is therefore not possible as it violates the KISS principle.

Changing defaults

The opinion of one (or few) cannot count as a reason to change the defaults for everyone. Plasma has most likely millions of users. Even if a wishlist item has a few thousand votes it is still rather irrelevant.

My workflow

Violates KISS.

Software Architecture

Each software architecture has advantages and disadvantages. There is no silver bullet in IT. Changes in architecture would also in many cases require a complete rewrite. This doesn't make any sense. Because of that no wishlist item in the kind of "have Plasmoids out of process" cannot be accepted.

But KDE 3!!!!

KDE 3.5 is now dead for several years. If nobody implemented the "missing feature" by now it probably means, nobody needs it.

Templates

Generic Template

Thank you for your feature suggestion and for helping to improve our software. After evaluating this feature suggestion we came to the conclusion that it doesn't fit into what we want to see for Plasma. Plasma has an architecture allowing very strong customization through individual applets and scripts. We encourage the wider KDE community to create this level of customization through 3rd party applets. It doesn't need the core Plasma developers to implement this. As the wider KDE community is not using this bugtracker, it is very unlikely that this request will be picked up by anybody and as the core developer team will not implement this feature, we have to set it as won't fix.

Request for new Plasmoid

Thank you for your suggestion for a new applet. Unfortunately the core developer team of KDE Plasma is only working on the infrastructure of Plasma and the most important applets to provide a desktop shell. Your suggestion does not fall into this category. But anyone from the wider KDE community could implement such an applet as you suggested. It doesn't need the core Plasma developers to implement this. As the wider KDE community is not using this bugtracker, it is very unlikely that this request will be picked up by anybody and as the core developer team will not implement this feature, we have to set it as won't fix.

Violating KISS (magic behavior/config options/workflow)

Thank you for your feature suggestion and for helping to improve our software. The evaluation of this feature request shows that implementing this feature would violate some of the design decisions taken for KDE Plasma. Plasma's architecture is very flexible and it is possible to exchange any applet with a different one. For strong customization we recommend to have a dedicated applet which is tailored towards a specific use case. This allows to have the default set of applets very simple while still providing advanced users the possibility to extend. This level of customization can be achieved through 3rd party applets written by the wider KDE community. It doesn't need the core Plasma developers to implement this. As the wider KDE community is not using this bugtracker, it is very unlikely that this request will be picked up by anybody and as the core developer team will not implement this feature, we have to set it as won't fix.