Am Samstag, 7. Januar 2012, 16:28:32 schrieb Sven Burmeister:
Am Freitag, 6. Januar 2012, 20:54:45 schrieb Martin Schlander: - be stricter about upstream bugs in bnc Reality is that most upstream bugs reported at bnc will not get fixed. This means that the reporter will be frustrated because his report stays unanswered and he does not get a fix from openSUSE. Yet it also means that because he did not report upstream, upstream cannot fix it and if it was fixed upstream because somebody else reported it the reporter does not know and cannot report back to openSUSE. So I would suggest to only allow openSUSE-specific bugs and bugs that link to an upstream bug or patch and act as reminder.
The rule here is already there, see http://en.opensuse.org/openSUSE:Bugreport_KDE and especially http://en.opensuse.org/openSUSE:Bugreport_KDE#Report_at_bugzilla.novell.com_... But there are a few reasons why it does not always work * Lack of manpower * Sometimes, at least for me, it is not always clear, if a bug is caused by KDE or lower in the stack. So if you have no time to do some tests such a bug easily remains unanswered. But many bugs are closed as upstream and people are told to report bugs first upstream and to reopen if a fix is available there. It can also happen that one leaves some clearly upstream reports open, after they have been reported there, so that they are more easily found and avoiding duplicated reports on bnc by this. And IMHO the number of useful reports, this means with a link to a fixed upstream report and the commit has increased with 12.1. So this works to some extend already today. Of course it would really help if there were a few people more doing bug triage. If someone wants to helps, here is the howto for KDE on openSUSE: http://en.opensuse.org/openSUSE:Bug_Screening_KDE It is a bit out of date in some of the details, but one should get the idea. Christian -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org