On Sat, Oct 1, 2011 at 10:52 PM, Rui Maciel <rui.mac...@gmail.com> wrote: > On 09/30/2011 07:17 PM, todd rme wrote: >> >> If they don't have time to respond to all the bug reports, what makes >> you think they would have time to respond to just as many, if not >> more, emails? You would only be increasing the amount of stuff they >> need to read, further decreasing the amount of time they have to >> respond to bugs, not to mention fix them. In the end you would end up >> with the same situation: tons of emails left unanswered. > > The main problem is not how many messages, either those sent to this mailing > list or to the bug tracker, are left unanswered; it's how much time is > being wasted on a futile task. This problem is being incorrectly depicted > as one which only affects developers but in reality it affects every person > involved, including users.
That's right. The more things they have to read, the less time they have to develop. Sending what amounts to duplicate bug reports is not going to help that, it is going to make it worse. Further, it would require even more time on the part of users as well, sending a ton of emails that would not and could not help the situation. So from a user perspective this approach also makes things worse. > You claimed that developers waste time browsing some messages. Yet, it > should also be noted that filing bug reports, particularly when providing > every piece of information which may be of any interest, does demand quite a > bit of time and energy from the users. In fact, a bug report which is left > untouched by any developer ends up being a complete waste of time for the > user who submitted it, while not affecting any developer in the process. If > you hold this in consideration while you browse through KDE's bug tracker > you will get an idea of how much time the current bug tracking policy is > forcing users to waste. This, as this thread demonstrates, is a > considerable source of frustration. So, if there is really an intention to > cut on how much time is being wasted with the current process then why not > start where it really is being entirely wasted? I am not sure I understand your proposal. My point is that sending emails can only make the situation worse. It will require more time on the part of both users and developers while not addressing the underlying problem: not enough eyes and not enough time. And you don't need to lecture me on frustration with the bug reporting process. I currently have 38 unconfirmed (including 1 major data loss bug) and 17 new bugs. That only includes bugs I reported myself (not ones I have but that there was already a bug for) and it does not include wishlist items. That is exactly why I am against anything that will make it less likely that my bugs will be solved, which is exactly what sending bugs to the mailing list does. The only thing that will improve the situation is having people help in the triage process. I don't do that full-time, but I certainly do point out when bugs are duplicates or already fixed when I see them. -Todd >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
