> > > Ok, this bitter answer demonstrates that you don't know how things > > > work here (at leat in debian KDE). To put it straight, there's not > > > enought people and not enought time. If you are willing to > > > volunteer, you are very much welcome. I'm also a user and try to > > > help as much as I can, fixing bugs, dealing with the BTS and such. > > You don't get it. > > > Now, now. I know we are all busy, and it would be nice if the > > submitter had done this for you, but bug triage is ultimately the > > maintainer's job. > > There is no point yelling at a user because they didn't do your > > Who's yelling? And so on, and so forth. Hmm. A flame war in a bug report. And over a fairly trivial issue as well. Looks like things could do with a bit of cooling down. I've read most of the bug history. And I must say to the submitter: if you think 7 months is bad, you're in for bigger disappointments. There are bugs in the BTS that are over 3 years old (some even on issues not as trivial as this one...). Although in principle bug triage _is_ the job of the package maintainer(s), it is also their good right to prioritize their work, *especially* as we are all volunteers. IMO the responsibility of a maintainer for bug triage is bigger if upstream is less accessible to users. For KDE this is clearly _not_ the case. Upstream has a great BTS themselves, open to all and easy to find. They even have a nice voting system that allows users to collectively determine the priority of an issue. I myself have over the past 5 years or so made the transition from "file everything in the Debian BTS as that's my distribution" to "hey, where does this problem come from and let's file upstream if more appropriate". In the second case I may also submit a bug in Debian's BTS if I feel the maintainers or other users should be aware of the problem. Of course packaging related issues should always go to Debian's BTS, but especially for wishlist and minor issues that are clearly upstream, submitting directly to KDE's BTS is often the better solution as their manpower (and ability to judge the severity and relevance of an issue) is way greater than Debian's KDE team. I must say I'm very happy with KDE support ATM. The recent additions the team can clearly be seen in the results and in my experience maintainers are very responsive to issues raised e.g. on this list. So guys (and even gals maybe?), thanks and don't let this bother you too much. A last suggestion to the submitter: you could have tried asking here how best to proceed. Cheers, FJP (Debian and KDE user, wannabe DD and volunteer in the debian-installer project)
Attachment:
pgp2uKnzv2Mc5.pgp
Description: PGP signature