I have spent the entire day thus far going through bug reports on bugs.kde.org for plasma and krunner. This has resulted in a number of fixes and patches. Unfortunately the bulk of my time has been spent triaging bugs that really don't end up providing value; worst are the ones where I triage them and the reporter decides that, despite my response, I haven't quite understood things properly and so continues to engage on the bug report further wasting my time. As such the cost to the user (less software) is too well hidden compared to the cost of reporting a new bug or replying to an existing one (which is the least expensive thing to do).
There no real moral to this story, really. I do wish we had a better bug reporting and triaging system that supported real work flow, external bug repository tracking and other sane features, but I really see no solution to broken user habits. There are too many users, and too many stubborn people.
Update: It just occurred to me to mention that if you have a request or a thought about things (versus a straight forward bug report, e.g. "I did $FOO and Plasma crashed" or "I searched in KRunner for $FOO, but it returned $BAR instead"), try the mailing list (panel-devel at kde dot org) first. bugs.kde.org is insanely inneficient compared to the mailing list both in terms of time it takes to use it as well as discussion usefulness (threading, for one). If an action item comes out of the mailing list discussion, then create a report on bugs.kde.org that is succinct and to the point.
On a more positive note, I went out to Banff with my houseguest, W., on the weekend. We spent time wandering around the town (buying waaay too much fudge =), wandering through museums, wandering through forests (where we took pictures of various deer and ate wonderful little sandwiches we made amongst the trees) ... essentially a lot of peaceful wandering in the sunshine.
Much less stressful than dealing with bugs.kde.org all day, but also less productive for Plasma ;)