Re: Re: bugzilla situation

On Sunday 26 February 2012 13:56:41 Kevin Krammer wrote: > On Friday, 2012-02-24, Martin Gräßlin wrote: > > On Friday 24 February 2012 19:32:10 Andras Mantia wrote: > > > On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote: > > > > Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia : > > >

Re: bugzilla situation

On Friday, 2012-02-24, Martin Gräßlin wrote: > On Friday 24 February 2012 19:32:10 Andras Mantia wrote: > > On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote: > > > Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia : > > If you can moderate it, it means you have time and resource to do

Re: bugzilla situation

On Sat, Feb 25, 2012 at 03:06, dE . wrote: > I tend to think closing duplicate bugs and checking wish list issues can be > done by a non-developer contributers. In which case there should be an > option by which a particular user can be CCd to for a specific program(s). > There should be an entry a

Re: bugzilla situation

On 02/22/12 20:41, David Faure wrote: On Wednesday 22 February 2012 16:15:45 Giorgos Tsiapaliwkas wrote: Hello, Toma's blog post inspired me to send you this mail. Right now our bugzilla is a mess. We have so many

Re: bugzilla situation

Am 24.02.2012, 18:32 Uhr, schrieb Andras Mantia : If you can moderate it, it means you have time and resource to do it, so you could have done until now as well. You cannot moderate bugzilla atm. (maybe Dr. Konqui is, but then you will also lose valid reports). Any other suggestion? Regard

Re: Re: bugzilla situation

On Friday 24 February 2012 20:36:12 Andras Mantia wrote: > On Friday, February 24, 2012 07:28:33 PM Martin Gräßlin wrote: > > > User asking on distro/KDE mailinglist/forum/IRC because xyz does not > > > work. > > > > > > > > > > > > 1. he gets an answer > > > 1.1 known bug > > > 1.2 me too -> the u

Re: Re: bugzilla situation

On Friday 24 February 2012 20:31:46 Andras Mantia wrote: > On Friday, February 24, 2012 06:51:11 PM Martin Gräßlin wrote: > > -> first level support > > > > issues are not opened on the bug tracker but in a user support management > > system - e.g. forums.kde.org. Only if the supporters figure out

Re: bugzilla situation

On Friday, February 24, 2012 07:28:33 PM Martin Gräßlin wrote: > > User asking on distro/KDE mailinglist/forum/IRC because xyz does not work. > > > > > > > > 1. he gets an answer > > 1.1 known bug > > 1.2 me too -> the user might open a bug report > > 1.3 it works like this… > > > > > > > > 2. he

Re: bugzilla situation

On Fri, Feb 24, 2012 at 8:44 AM, Andras Mantia wrote: > On Thursday, February 23, 2012 04:57:16 PM David Edmundson wrote: >> > First of all, the bugzilla is supposed to be a communication tool between >> > the user and the developer. >> Or is it? >> >> If I understand Martin correctly, he wants bu

Re: Re: bugzilla situation

On Friday 24 February 2012 19:27:09 Sven Burmeister wrote: > > yes, of course, we have to help the users. But they need to get a tool for > > user support, not a tool for developer communication. We need a > > first-level- support to help the users. Developers are the > > third-level-support. > I d

Re: bugzilla situation

On Friday, February 24, 2012 06:51:11 PM Martin Gräßlin wrote: > -> first level support > > issues are not opened on the bug tracker but in a user support management > system - e.g. forums.kde.org. Only if the supporters figure out that there > is a real bug, they will open a bug report. This is

Re: Re: bugzilla situation

On Friday 24 February 2012 19:11:12 Sven Burmeister wrote: > Am Freitag, 24. Februar 2012, 08:06:41 schrieb Martin Gräßlin: > > > My claim is that most of that "user support" only ends-up in bugzilla > > > because people did not get help somewhere else, e.g. because only > > > developers are famili

Re: bugzilla situation

Am Freitag, 24. Februar 2012, 18:51:11 schrieb Martin Gräßlin: > On Friday 24 February 2012 19:32:10 Andras Mantia wrote: > > On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote: > > > Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia : > > > > Bugzilla is not a to-do list, it is for what e

Re: bugzilla situation

Am Freitag, 24. Februar 2012, 08:06:41 schrieb Martin Gräßlin: > > My claim is that most of that "user support" only ends-up in bugzilla > > because people did not get help somewhere else, e.g. because only > > developers are familiar enough with the code to understand the issue. > > No, that is c

Re: bugzilla situation

On 2012-02-22, David Faure wrote: > up with was the few cases where bugs turned into actual political flamewars; > his answer was obviously "give rights to everyone, and remove rights when > someone abuses them". This is also what we do for SVN/GIT, so why don't we do > this for bugzilla? Presu

Re: Re: bugzilla situation

On Friday 24 February 2012 19:32:10 Andras Mantia wrote: > On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote: > > Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia : > > > Bugzilla is not a to-do list, it is for what else... a bug (and > > > wishlist) > > > reporting tool for users. > > >

Re: bugzilla situation

On Friday, February 24, 2012 06:10:23 PM Thomas Lübking wrote: > Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia : > > Bugzilla is not a to-do list, it is for what else... a bug (and wishlist) > > reporting tool for users. > > The problem here that this is noise prone and the low entropy isn't > h

Re: bugzilla situation

Am 24.02.2012, 09:44 Uhr, schrieb Andras Mantia : Bugzilla is not a to-do list, it is for what else... a bug (and wishlist) reporting tool for users. The problem here that this is noise prone and the low entropy isn't helping anyone (and i'm not talking about users should not state their o

Re: bugzilla situation

On Friday 24 February 2012, Ben Cooksley wrote: > On Fri, Feb 24, 2012 at 11:41 AM, Kevin Ottens wrote: > > On Thursday 23 February 2012 17:39:12 Trever Fischer wrote: > >> Random, possibly entirely unhelpful suggestion: Perhaps using our > >> redmine install of projects.kde.org for this kind of t

Re: bugzilla situation

On Friday 24 February 2012, Martin Gräßlin wrote: > On Friday 24 February 2012 21:03:42 Ben Cooksley wrote: > > On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin ... > > > Consider that we have to ask again and again for all those things to > > > find out in the end that it is a known issue with $f

Re: bugzilla situation

On Fri, 24 Feb 2012, Alex Merry wrote: On 24/02/12 09:22, Thorsten Zachmann wrote: Why not have a state for bugs that you know are worth fixing? Then the developers can concentrate on those and Other people can do the initial cleaning to get the bugs to a state they can be closed or the proper

Re: bugzilla situation

On 24/02/12 09:22, Thorsten Zachmann wrote: Why not have a state for bugs that you know are worth fixing? Then the developers can concentrate on those and Other people can do the initial cleaning to get the bugs to a state they can be closed or the proper state set. That would be "assigned", I'

Re: bugzilla situation

On Thursday, February 23, 2012 04:57:16 PM David Edmundson wrote: > > First of all, the bugzilla is supposed to be a communication tool between > > the user and the developer. > Or is it? > > If I understand Martin correctly, he wants bugzilla to be "a list of > things broken in my app", not a com

Re: bugzilla situation

On Friday, February 24, 2012 08:06:41 Martin Gräßlin wrote: > Consider that we have to ask again and again for all those things to find > out in the end that it is a known issue with $foo driver in combination > with $bar feature. All these things could so easily be handled by a first > level supp

Re: Re: Re: bugzilla situation

On Friday 24 February 2012 21:03:42 Ben Cooksley wrote: > On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin wrote: > > On Friday 24 February 2012 02:15:54 Sven Burmeister wrote: > >> Am Mittwoch, 22. Februar 2012, 19:00:26 schrieb Martin Gräßlin: > >> > Personally I'm not sure whether the MeeGo bugz

Re: Re: bugzilla situation

On Fri, Feb 24, 2012 at 8:06 PM, Martin Gräßlin wrote: > On Friday 24 February 2012 02:15:54 Sven Burmeister wrote: >> Am Mittwoch, 22. Februar 2012, 19:00:26 schrieb Martin Gräßlin: >> > Personally I'm not sure whether the MeeGo bugzilla can be compared to >> > the KDE one (technical oriented vs.

Re: Re: bugzilla situation

On Friday 24 February 2012 02:15:54 Sven Burmeister wrote: > Am Mittwoch, 22. Februar 2012, 19:00:26 schrieb Martin Gräßlin: > > Personally I'm not sure whether the MeeGo bugzilla can be compared to > > the KDE one (technical oriented vs. user oriented). From my personal > > experience (KWin bugtra

Re: bugzilla situation

Am Mittwoch, 22. Februar 2012, 19:00:26 schrieb Martin Gräßlin: > Personally I'm not sure whether the MeeGo bugzilla can be compared to > the KDE one (technical oriented vs. user oriented). From my personal > experience (KWin bugtracker is felt > 90 % a user support forum) My claim is that most of

Re: bugzilla situation

Am Mittwoch, 22. Februar 2012, 12:38:38 schrieb Antonis Tsiapaliokas: > For e.x., someone is a core developer, someone is on release team or > someone else is a sysadmin and some others are taking critical decisions > about the feature of KDE. I don't think that neither of them was there > where h

Re: bugzilla situation

On Fri, Feb 24, 2012 at 11:41 AM, Kevin Ottens wrote: > On Thursday 23 February 2012 17:39:12 Trever Fischer wrote: >> Random, possibly entirely unhelpful suggestion: Perhaps using our redmine >> install of projects.kde.org for this kind of task tracking? I'd love to see >> p.k.o be used as someth

Re: bugzilla situation

On Thursday 23 February 2012 17:39:12 Trever Fischer wrote: > Random, possibly entirely unhelpful suggestion: Perhaps using our redmine > install of projects.kde.org for this kind of task tracking? I'd love to see > p.k.o be used as something more of a central place for devs to get together > and c

Re: bugzilla situation

On Thursday, February 23, 2012 11:57:16 AM David Edmundson wrote: > > First of all, the bugzilla is supposed to be a communication tool between > > the user and the developer. > > Or is it? > > If I understand Martin correctly, he wants bugzilla to be "a list of > things broken in my app", not a

Re: bugzilla situation

> First of all, the bugzilla is supposed to be a communication tool between the > user and the developer. Or is it? If I understand Martin correctly, he wants bugzilla to be "a list of things broken in my app", not a communication tool for every user who wants to say something. In KDE Telepathy

Re: bugzilla situation

On Wednesday, February 22, 2012 04:11:57 PM David Faure wrote: > He asked me why we don't do this, and the only reply I could come > up with was the few cases where bugs turned into actual political > flamewars; his answer was obviously "give rights to everyone, and remove > rights when someone

Re: bugzilla situation

On Wed, Feb 22, 2012 at 7:11 AM, David Faure wrote: > > Doesn't sound very open > -- > David Faure, fa...@kde.org, http://www.davidfaure.fr > Sponsored by Nokia to work on KDE, incl. KDE Frameworks 5 > > First of all, the bugzilla is supposed to be a communication tool between the user and th

Re: bugzilla situation

Am 22.02.2012, 16:11 Uhr, schrieb David Faure : In case that a user finds a "true" bug, he can go to the project's irc and to ask from someone to open the new bug. Doesn't sound very open [Disclaimer: Describing a custom, proprietary and vastly expensive system ;-) No promotion, ju

Re: bugzilla situation

On Wednesday, February 22, 2012 07:00:26 PM Martin Gräßlin wrote: > Am 22.02.2012 18:13, schrieb Laszlo Papp: > >> The suggestion remains: to allow everyone to edit and close bugs, as > >> is > >> apparently the case in some other bug trackers. > > > > +1. > > > > Worked fine on the MeeGo bugzill

Re: bugzilla situation

Am 22.02.2012 18:13, schrieb Laszlo Papp: The suggestion remains: to allow everyone to edit and close bugs, as is apparently the case in some other bug trackers. +1. Worked fine on the MeeGo bugzilla for instance, I previously used. Personally I'm not sure whether the MeeGo bugzilla can be co

Re: bugzilla situation

> The suggestion remains: to allow everyone to edit and close bugs, as is > apparently the case in some other bug trackers. +1. Worked fine on the MeeGo bugzilla for instance, I previously used. Best Regards, Laszlo Papp

Re: bugzilla situation

On Wednesday 22 February 2012 11:57:25 Parker Coates wrote: > On Wed, Feb 22, 2012 at 10:23, Stefan Majewsky wrote: > > On Wed, Feb 22, 2012 at 4:11 PM, David Faure wrote: > >> "give rights to everyone, and remove rights when > >> someone abuses them". This is also what we do for SVN/GIT, so why do

Re: bugzilla situation

On Wed, Feb 22, 2012 at 10:23, Stefan Majewsky wrote: > On Wed, Feb 22, 2012 at 4:11 PM, David Faure wrote: >> "give rights to everyone, and remove rights when >> someone abuses them". This is also what we do for SVN/GIT, so why don't we do >> this for bugzilla? Presuming people are innocent upfron

Re: bugzilla situation

On Wed, Feb 22, 2012 at 4:11 PM, David Faure wrote: > "give rights to everyone, and remove rights when > someone abuses them". This is also what we do for SVN/GIT, so why don't we do > this for bugzilla? Presuming people are innocent upfront, rather than guilty What we do for SVN/Git is to give r

Re: bugzilla situation

On Wednesday 22 February 2012 16:15:45 Giorgos Tsiapaliwkas wrote: > Hello, > > Toma's blog > post lation/> inspired > me to send you this mail. > > Right now our bugzilla is a mess. We have so many bug entries which we > ca

bugzilla situation

Hello, Toma's blog post inspired me to send you this mail. Right now our bugzilla is a mess. We have so many bug entries which we can't handle. Everyone is able to open a new bug, but only a few people are able to tri