Comment 25 for bug 146145

I agree with you that the problem is often manpower, but here we have a bigger problem: a maybe, especially out of UE, minor feature has been broken by adopting a beta version of a package. Was it necessary? No. Does it improve user experience? No. This beta has also other problems, mainly the new kbluelock is awkward (I have to reselect the device that locks the screen every time I login) and the old script that did this was able to do that AND other things, like using DCOP or DBUS to command other applications on the event of BT device appearance or disappearance.

It's obvious that something in the decision process failed, but since I don't like useless ranting, I ask: what can we do do avoid it in the future?
Do we have to become MOTU to help in these matters, or there's some kind of poll/forum/maillist where this kind of decisions are made where "normal users" can offer their opinion?
I'm not very competent in Ubuntu community workings (especially Kubuntu ones) and I have limited time to offer, but maybe I can do something useful for the next releases. But this can't be reporting bugs, since open bugs weren't enough to stop the adoption of a clearly broken package in this case.

On a more useful front, I tried to compile kdebluetooth from beta8, and I wasn't able to continue. It seems the autoconf (arrrrgh) script searches for an older version of dbus than the 7.10-shipped one (searches for dbus/connection.h but I have /usr/include/dbus-1.0/dbus/dbus-connection.h).

The kdebluetooth website seems to be "in a flux" (just migrated and registration doesn't work...). I'll maybe try svn to get a maybe newer and hopefully working version.

Ciao,
   Roberto