Re: bug killing
Hi, Could someone please post a log of the discussions as I couldn't make it. Cheers, Viranch On Dec 4, 2011 12:00 AM, Aaron J. Seigo ase...@kde.org wrote: On Saturday, December 3, 2011 17:37:01 Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= wrote: On Saturday 03 December 2011 17:20:20 Aaron J. Seigo wrote: On Sunday, November 20, 2011 21:37:16 Aaron J. Seigo wrote: so .. 1700+ bugs. fun, huh? :) as an encouraging little update, thanks to everyone's combined efforts we are now down to ~1270 reports. that's ~500 fewer than when i sent the email 2 weeks ago. I want that, too. And it's only 410 bugs and kwin is down to 0. So please ehehe ;) seriously: we should do a bug days for kwin too.. maybe in january? assuming you need or could use the help for a good cleaning. Seriously: awesome job all of you. Keep that going. I'm pretty sure we can get plasma down to around 300 to 500 real bugs and that makes it managable. agreed... right now i'm looking at the 1000 mark as the next acheivable short-term goal. btw.. did a quick LOC count the other day and plasma is shipping nearly 300k LOC right now. that include Plasma Active, but not the applications, just the actual plasma bits. that doesn't include kwin, either, which itself is 92k+ LOC in kde-workspace. dr. konqi makes reporting bugs amazingly easy and pleasant now as well... given the feature-to-LOC ratio, it's quite evident why we have so many reports. but i'm quite enthused with how much progress was made in just 2 days (of admiteedly abnormal levels of effort ;) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Sunday, December 4, 2011 13:37:17 Viranch Mehta wrote: Could someone please post a log of the discussions as I couldn't make it. most of the tutorial session was captured here: http://community.kde.org/Plasma/bugdays -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Sunday, November 20, 2011 21:37:16 Aaron J. Seigo wrote: so .. 1700+ bugs. fun, huh? :) as an encouraging little update, thanks to everyone's combined efforts we are now down to ~1270 reports. that's ~500 fewer than when i sent the email 2 weeks ago. we are destined at this rate to have closed more reports than were opened over the last six months. as i write this we are 30 closures away from that. i begin to wonder how much effort it will take to get it down to under 1000 :) thanks for everyone who has helped out to achieve this. our bug database is in an increasingly healthy state and finding things to actually work on will be easier. in fact, tomorrow i will be posting a small (non-comprehensive) list of bugs we should ensure get addressed for 4.8.0, and that list is a direct result of the triaging that's been going on like made yesterday and today. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: bug killing
On Saturday 03 December 2011 17:20:20 Aaron J. Seigo wrote: On Sunday, November 20, 2011 21:37:16 Aaron J. Seigo wrote: so .. 1700+ bugs. fun, huh? :) as an encouraging little update, thanks to everyone's combined efforts we are now down to ~1270 reports. that's ~500 fewer than when i sent the email 2 weeks ago. I want that, too. And it's only 410 bugs and kwin is down to 0. So please apply your magic to reduce the bugs :-) (We are 20 bugs more than half a year ago.) Btw kwin shows what is possible when constantly triaged. We are working on it with two people. So far Plasma you would need about ten people working on it. Seriously: awesome job all of you. Keep that going. I'm pretty sure we can get plasma down to around 300 to 500 real bugs and that makes it managable. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Saturday, December 3, 2011 17:37:01 Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= wrote: On Saturday 03 December 2011 17:20:20 Aaron J. Seigo wrote: On Sunday, November 20, 2011 21:37:16 Aaron J. Seigo wrote: so .. 1700+ bugs. fun, huh? :) as an encouraging little update, thanks to everyone's combined efforts we are now down to ~1270 reports. that's ~500 fewer than when i sent the email 2 weeks ago. I want that, too. And it's only 410 bugs and kwin is down to 0. So please ehehe ;) seriously: we should do a bug days for kwin too.. maybe in january? assuming you need or could use the help for a good cleaning. Seriously: awesome job all of you. Keep that going. I'm pretty sure we can get plasma down to around 300 to 500 real bugs and that makes it managable. agreed... right now i'm looking at the 1000 mark as the next acheivable short-term goal. btw.. did a quick LOC count the other day and plasma is shipping nearly 300k LOC right now. that include Plasma Active, but not the applications, just the actual plasma bits. that doesn't include kwin, either, which itself is 92k+ LOC in kde-workspace. dr. konqi makes reporting bugs amazingly easy and pleasant now as well... given the feature-to-LOC ratio, it's quite evident why we have so many reports. but i'm quite enthused with how much progress was made in just 2 days (of admiteedly abnormal levels of effort ;) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Tue, Nov 22, 2011 at 11:08 PM, Rick Stockton rickstock...@reno-computerhelp.com wrote: On 01/-10/-28163 11:59 AM, todd rme wrote: I often encounter bugs that are duplicate, fixed, etc, and I post a comment on the bug report to that effect, but the comments seem to rarely be acted upon Todd, I cannot imagine another person, currently WITHOUT admin bugzilla rights, who is as qualified and capable of using using those rights correctly as YOU. Thank you very much! Although I think you have more confidence in my abilities than I do :) -Todd ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
Big killing is great :) I propose an actual target. Currently plasma is the second largest kde project in terms of bugs. 1514 open bugreports (excluding wishes). kmail is third with 1340 open bugs. I think a good goal would be to beat kmail and become third :) Its only 170 bugs to close. Thats totaly doable with the amount of duplicates that exist. greets Beat Asraniel Wolf ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Wednesday, November 23, 2011 14:41:35 asraniel wrote: Big killing is great :) I propose an actual target. Currently plasma is the second largest kde project in terms of bugs. 1514 open bugreports (excluding wishes). kmail is third with 1340 open bugs. i think that's a terrific target. i'm on board for it, let's make it happen! also, bug days are on for Friday the 2nd and Saturday the 3rd, both in the afternoon UTC. i'll try to be there from ~noon until evening on both days. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
In data mercoledì 23 novembre 2011 16:39:00, Aaron J. Seigo ha scritto: also, bug days are on for Friday the 2nd and Saturday the 3rd, both in the afternoon UTC. i'll try to be there from ~noon until evening on both days. If you're OK with it, I can publish an announcement on the forum or similar stuff. signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Wednesday, November 23, 2011 16:41:55 Luca Beltrame wrote: In data mercoled� 23 novembre 2011 16:39:00, Aaron J. Seigo ha scritto: also, bug days are on for Friday the 2nd and Saturday the 3rd, both in the afternoon UTC. i'll try to be there from ~noon until evening on both days. If you're OK with it, I can publish an announcement on the forum or similar stuff that would be awesome :) thanks .. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
Am Dienstag, 22. November 2011, 01:30:46 schrieb todd rme: On Sun, Nov 20, 2011 at 9:37 PM, Aaron J. Seigo ase...@kde.org wrote: if you have other ideas, let me know. Is there a feature for bugzilla that allows users to flag bugs as being fixed, duplicate, upstream, downstream, etc? I know people with administrator rights can close bugs in this way, but if non-admisitrator users could flag bugs so that people with administrator rights would get notified that the bug should be closed it might make triaging easier. I often encounter bugs that are duplicate, fixed, etc, and I post a comment on the bug report to that effect, but the comments seem to rarely be acted upon, probably because they appear the same as all the other random comments and thus get lost in all the noise coming from bko. So if there was some special way to notify devs about bugs that should be fixed, one that won't as easily get lost amongst ordinary comments, it might make things easier for everyone. But such a feature may not exist for bugzilla. -Todd ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel +1 that would be great! I have the same problem and *don't* know people with admin rights. -- The way some people find fault, you'd think there was some kind of reward. signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Tuesday 22 November 2011 01:30:46 todd rme wrote: Is there a feature for bugzilla that allows users to flag bugs as being fixed, duplicate, upstream, downstream, etc? You can use https://bugs.kde.org/enter_sysadmin_request.cgi and select component bugzilla to request the rights to edit bugs. If needed, you can mention me as an approver. Christoph Feck (kdepepo) KDE Quality Team ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Tue, Nov 22, 2011 at 9:29 AM, Christoph Feck christ...@maxiom.de wrote: On Tuesday 22 November 2011 01:30:46 todd rme wrote: Is there a feature for bugzilla that allows users to flag bugs as being fixed, duplicate, upstream, downstream, etc? You can use https://bugs.kde.org/enter_sysadmin_request.cgi and select component bugzilla to request the rights to edit bugs. If needed, you can mention me as an approver. Christoph Feck (kdepepo) KDE Quality Team Thanks! I will do so. But this isn't really about me specifically, it is a way for any user to make the bug triaging load easier. Even if users aren't specifically hunting for bugs that should be closed, they can still stumble upon them when using bko normally, and when they do it would be helpful if there was a way for them to notify developers about the issue so it can be fixed. Of course we can't just give every user admin rights, the final decision would still have to go through someone trusted, but the people who have the authority to make a decision can't if they don't know the issue exists. Hence a dedicated way to inform them would help, I think. -Todd ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Tuesday 22 November 2011 09:54:48 todd rme wrote: On Tue, Nov 22, 2011 at 9:29 AM, Christoph Feck christ...@maxiom.de wrote: On Tuesday 22 November 2011 01:30:46 todd rme wrote: Is there a feature for bugzilla that allows users to flag bugs as being fixed, duplicate, upstream, downstream, etc? You can use https://bugs.kde.org/enter_sysadmin_request.cgi and select component bugzilla to request the rights to edit bugs. If needed, you can mention me as an approver. Christoph Feck (kdepepo) KDE Quality Team Thanks! I will do so. Great, looking forward to your participation in bug squashing ;) But this isn't really about me specifically, it is a way for any user to make the bug triaging load easier. Even if users aren't specifically hunting for bugs that should be closed, they can still stumble upon them when using bko normally, and when they do it would be helpful if there was a way for them to notify developers about the issue so it can be fixed. Usually adding a comment to the bug should be sufficient, as the maintainer of the application receiving the message will close the bug later. Mentioning bug XY can be closed because it was fixed in KDE 4.x.y in #kde-bugs might work, too. Plasma bug list is a bit different. It does not have a maintainer looking at the messages regularily, so those messages are lost in noise, as you already mentioned. Of course we can't just give every user admin rights, the final decision would still have to go through someone trusted, Exactly. Sometimes I even have to reopen bugs from users that reported and closed their own bugs ;) but the people who have the authority to make a decision can't if they don't know the issue exists. Hence a dedicated way to inform them would help, I think. The sysadmin request does exactly that, or am I missing something? -Todd ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Tuesday, November 22, 2011 10:16:09 Christoph Feck wrote: Plasma bug list is a bit different. It does not have a maintainer looking at the messages regularily, so those messages are lost in noise, as you already mentioned. oh, i look at them on a regular basis. the rate of reports and comments is simply too high to keep up with given the time i have, however. some days there will be over 50 new messages; and if i'm away for a day or two (meetings, conference, etc) then it's easy to come back to 200+ reports. so it's a matter of having enough separate eyeballs looking at things and working on the triage together to make the load manageable. that's the key. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Tuesday, November 22, 2011 09:54:48 todd rme wrote: Thanks! I will do so. i can also grant these priveleges in b.k.o, so just ask and thou shalt receive :) But this isn't really about me specifically, it is a way for any user to make the bug triaging load easier. Even if users aren't this would be great if any user was capable of doing this work in a reliable manner. given the interactions we have with any user on b.k.o, this is really expecting too much and would likely do as much harm as good. identifying those who could and should get these priveleges is something we don't do an amazingly great job at, though, so on the flip side we do currently miss out on opportunities. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Tuesday, November 22, 2011 09:09:51 Gregor =?ISO-8859-1?Q?T=E4tzner?= wrote: +1 that would be great! I have the same problem and *don't* know people with admin rights. i have given the bugs.kde.org accounts for both you and Todd the ability to edit bugs ... handle with care, and welcome to the world of helping us tame the bug count... tip: when logged in to bugs.kde.org, go to Edit my Preferences under My Account in the left side bar. then click on Saved Searches you should see (in the massive list there) a few shared saved searches for plasma. you can add them to your sidebar (aka footer) or click on them to run them manually (and they can be bookmarked) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Monday, November 21, 2011 11:01:47 Aaron J. Seigo wrote: i'll arrange for a workshop + bug squash days near the end of the month. please take a moment to fill in this doodle: http://www.doodle.com/3rx2m4vz92qcrhm5 so far it looks like thursda the 1st afternoon and friday the 2nd in the evening will be the two best days. i'll give it another couple of days and then settle on final times, so be sure to fill out the doodle if you haven't already. btw.. we're down almost another 100 reports today. -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On 01/-10/-28163 11:59 AM, todd rme wrote: I often encounter bugs that are duplicate, fixed, etc, and I post a comment on the bug report to that effect, but the comments seem to rarely be acted upon Todd, I cannot imagine another person, currently WITHOUT admin bugzilla rights, who is as qualified and capable of using using those rights correctly as YOU. I was facing the same problem yesterday night -- looking at one of my favorite bugs, in which my final comments indicated exactly why and how it should be closed: With no action from the assignee. My solution? Jump on IRC, channel #kde-bugs, and point at that particular bug (the notorious https://bugs.kde.org/show_bug.cgi?id=34362) as the one I needed permissions to close. A 'big guy in KDE' happened to be online, even tough it was well after midnight EU time. He looked at my work, approved of what he saw, set me up, and the bug is now closed. (Thanks, Ben ;) I'm sure that nearly any Admin 'Voice' on #kde-bugs would do the same for you, or immediately pull in another person to do the review and confirm (if your original IRC contact hasn't already heard of you.) - - - - - A lengthy side-bar discussion - - - - - IMO, bugs being erroneously closed is _not_ one of our larger issues with KDE Bugzilla. And if a mistake is made, a bug which is closed in error can be re-opened quite easily. The lowest-hanging fruit consists of the bugs which don't even need 10-line fixes. I'll list 3 groups which have come to my little, feeble mind: 1. BugIDs which SHOULD be closed after re-triage and verification (the problem no longer exists). It sounds like you have found many of these, thanks! 2. Bugs which are so ill-defined that no one can really work on them. (Bugs with vast numbers of comments flung at the wall', asking for different things, with an assignee who has left them all still stuck. These need re-definition, restricting them to a unique problem and solution. (I have an example which I intend to take on myself, the almost-as-notorious https://bugs.kde.org/show_bug.cgi?id=48062. It asks for Mouse Buttons as modifier keys, which is ONE thing, but many of the comments- including a few of mine- talk abut high-numbered as shortcuts all be themselves (without another keystroke, without emulating a held-down modifier button). The difference between these two wishlist items is huge. 3. And the third group, which includes many cases of Group #1 or Group #2: The assignee is no longer listening. This appears to be the case with #48062, which (after 8 years or so) seems to have it's owner ignoring it completely. (He's still an open software guy, but not paying attention to activity on THIS bug.) In these cases, we need a person with Admin permission (me, or YOU) to re-assign it themselves after one final, polite 'Ping?' attempt. Then, after YOU taken ownership and responsibility, you take the action which you have explained in your comments. I suspect that we have many, many bug owners who have their bugs in limbo when they have chosen to move on- a real, REALLY Bad Thing To Do. One part of the solution for this probably needs to be an emphasis that we WILL accept a reverse assignment, from a specific person back to 'unassigned', if the assignee decides not to work on it. With no whining from us, either -- or these assignees will avoid the job by leaving them as they are, trapped in a non-productive assignment to an email which isn't listening, or isn't capable of resolving the problem. The lives of KDE people, past and present, are prone to change from time to time. A Bugzilla database full of false assignee values is MUCH worse than a database with these particular bugs sent back into 'unassigned' State. - - - - - end of side-bar, back to Todd So- please jump on IRC, get permission from an authoritative person, and take control of those bugs where YOU have already determined the Action(s) which needs to be done. Or -- someone reading this, and authoritative in offering BugZilla permissions - please set Todd up, and send him an email when he's got the ability to squash a few- we might find that he Resolves _way_ more than just a few. Thanks to all, I know that I was VERY wordy, but I feel that a thorough review of our 'stale assignee' problem could be beneficial. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Sunday, November 20, 2011 09:55:55 PM Luca Beltrame wrote: In data domenica 20 novembre 2011 21:37:16, Aaron J. Seigo ha scritto: * hold a seminar on irc to help teach others effective bugs.kde.org report sqashing, plasma style * host a bug-squash day on irc * help someone get started with pick 5 reports, send it to the plasma-devel list program that works, but which just isn't efficient if i am the one Would it be worthwhile to involve the forum for some of these, at least to promote/spread? I remember that bugweeks weere (IIRC) quite effective, back in the days. The more the merier! I'll be happy to help after the 28th (we have an AkademyFr next week-end) to anything that would be scheduled so count me in. Anne-Marie ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Sunday, November 20, 2011 21:37:16 Aaron J. Seigo wrote: so .. 1700+ bugs. fun, huh? :) awesome; we are now down by ~100 reports already, thanks to efforts of just the last 24 hours. i'll arrange for a workshop + bug squash days near the end of the month. please take a moment to fill in this doodle: http://www.doodle.com/3rx2m4vz92qcrhm5 so i can figure out when it is best to do this. i will then blog about it (and hopefully some of you will as well) and we'll get this rolling. in the meantime .. keep those bugs a squashing! :) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Re: bug killing
On Monday 21 November 2011 11:01:47 Aaron J. Seigo wrote: On Sunday, November 20, 2011 21:37:16 Aaron J. Seigo wrote: so .. 1700+ bugs. fun, huh? :) awesome; we are now down by ~100 reports already, thanks to efforts of just the last 24 hours. i'll arrange for a workshop + bug squash days near the end of the month. please take a moment to fill in this doodle: http://www.doodle.com/3rx2m4vz92qcrhm5 if we get enough people for two dates I am willing to hold also a workshop. Cheers Martin signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Sun, Nov 20, 2011 at 9:37 PM, Aaron J. Seigo ase...@kde.org wrote: if you have other ideas, let me know. Is there a feature for bugzilla that allows users to flag bugs as being fixed, duplicate, upstream, downstream, etc? I know people with administrator rights can close bugs in this way, but if non-admisitrator users could flag bugs so that people with administrator rights would get notified that the bug should be closed it might make triaging easier. I often encounter bugs that are duplicate, fixed, etc, and I post a comment on the bug report to that effect, but the comments seem to rarely be acted upon, probably because they appear the same as all the other random comments and thus get lost in all the noise coming from bko. So if there was some special way to notify devs about bugs that should be fixed, one that won't as easily get lost amongst ordinary comments, it might make things easier for everyone. But such a feature may not exist for bugzilla. -Todd ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
bug killing
hi everyone .. so .. 1700+ bugs. fun, huh? :) i spent a couple hours today scrolling to a random middle area of our bug list and opening reports. most fixes took less than half an hour, some less than 5 minutes. many were closed as already fixed, not enough info or down/upstream. i was able to kill ~30 reports today. we have very little bug triage happening (those who are doing triage, though, I LOVE YOU! :) and we need people willing and able to write some patches to get involved on a regular basis. 2-3 bug fixes a week by people on this list would make a huge difference. i asked previously for someone to collect ~5 reports at a time and send them to the list for the devs to tackle. didn't happen. so i tried it once and LO! the reports were fixed in short order. but you know what? it would have been faster for me to do it myself. and after that first set of bug reports, the people who actually contributed to the fixes didn't really do much more fixing after that. moreover there are TONS of reports that simply need to be closed. so .. we need to do something about this. i am willing to do any/all the following: * encourage people by setting goals like close 200 bug reports between now and 4.8.0 * hold a seminar on irc to help teach others effective bugs.kde.org report sqashing, plasma style * host a bug-squash day on irc * help someone get started with pick 5 reports, send it to the plasma-devel list program that works, but which just isn't efficient if i am the one doing it ;) but i need to know which of those options would be interesting to people. we can increase the quality and reliability of plasma, particularly on the desktop, dramatically here and make our users really happy. but we need to pull together to make this work. if you have other ideas, let me know. p.s. i am looking to some of the plasma old timers who are now quietly sitting around watching instead of doing as much as i am to the new comers who aren't sure how to proceed ;) -- Aaron J. Seigo humru othro a kohnu se GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43 KDE core developer sponsored by Qt Development Frameworks signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
In data domenica 20 novembre 2011 21:37:16, Aaron J. Seigo ha scritto: * hold a seminar on irc to help teach others effective bugs.kde.org report sqashing, plasma style * host a bug-squash day on irc * help someone get started with pick 5 reports, send it to the plasma-devel list program that works, but which just isn't efficient if i am the one Would it be worthwhile to involve the forum for some of these, at least to promote/spread? I remember that bugweeks weere (IIRC) quite effective, back in the days. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 signature.asc Description: This is a digitally signed message part. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Sun, Nov 20, 2011 at 3:37 PM, Aaron J. Seigo ase...@kde.org wrote: * host a bug-squash day on irc I'd like something along those lines. I have already closed a couple of bug reports in Plasma and PIM and each one of those took long enough due to the review process. If we had a chance to have all of the relevant reviewers around to give instant feedback, it would be far easier for us to work. And please do so in a schedule where us, developers in America, can participate with a fully functional brain :) David E. Narváez ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Mon, Nov 21, 2011 at 2:07 AM, Aaron J. Seigo ase...@kde.org wrote: ** * hold a seminar on irc to help teach others effective bugs.kde.orgreport sqashing, plasma style I'm *very* interested in this! Viranch ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: bug killing
On Sunday 20 November 2011, Luca Beltrame wrote: In data domenica 20 novembre 2011 21:37:16, Aaron J. Seigo ha scritto: * hold a seminar on irc to help teach others effective bugs.kde.org report sqashing, plasma style * host a bug-squash day on irc * help someone get started with pick 5 reports, send it to the plasma-devel list program that works, but which just isn't efficient if i am the one Would it be worthwhile to involve the forum for some of these, at least to promote/spread? I remember that bugweeks weere (IIRC) quite effective, back in the days. yeah, i think so, would at least make more participants to come to the irc session -- Marco Martin ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
