After the great bugday on Skin and page rendering issues yesterday, any preferences for the next bugday which will be about old and rotten bug reports? The list of ancient UsabilityInitiative issues feels a bit short (stuff would nowadays be WikiEditor, or Vector, or probably invalid for PrefSwitch and NavigableTOC) and that won't really help anybody. :) Also wondering about the vague stuff under "Wiktionary Tools" but I don't know the story behind either, plus will require something where a better place would be for these requests.
Topic on Project talk:WikiProject Bug Squad/Flow
We could have a default for Old Bug weeks: list in a whiteboard the 50 oldest bugs that haven't got a single comment and are not Lowest, and go after them.
Not bad. More ideas. The [Drafts extension] contains some the oldest unanswered bug reports we have, although perhaps we could simply assign Lowest to all of them and be done with it.
Also fwiw, I got pretty interesting lists of bugs searching for "WhatLinksHere", scattered in different places.
Thanks, that's a really good idea (as usual), though I'd extend the amount of tickets (50 feels low, we triaged 86 this week, see mw:Bug management/Triage/20130402). Currently thinking of setting up Monday 20130418 for the next bugday (as start of the bug week) and keeping #wikimedia-office instead #wikimedia-dev (it went pretty well last week).
Drafts extension: I think valerie investigated the situation but I cannot remember the outcome whether "Drafts" is still under development at all. :( Valerie?
WhatLinksHere: Interesting. I'd put it under SpecialPages by default but if backend issues are only *shown* or triggered by that special page they might be correctly filed under e.g. File management.
Choose your preferred number. 100?
Drafts, it was developed by Trevor. Not working on it anymore.
Yeah, most of the Drafts bug reports were assigned to Trevor, and after confirming that Trevor was not working on the reports, I assigned them to Nobody.
I would add Lowest for all of them, if they don't have them already.
On a global priority level that's likely correct. Refering to bug reports under "Drafts" only, this would remove any kind of prioritization, so I wouldn't do it. See bug 40482 being the main blocker for bug 37992).
Fair enough.
Re "list in a whiteboard": Either that (by a whiteboard entry, if we want specific "bugday-YYYYMMDD" style), or reuse the existing "bugsmash" keyword (generic without a date) what once upon a time was meant for this and dormant (I just cleaned up all remaining reports with that keyword). Whiteboard might be less noisy than keyword, as we wouldn't have to remove the entry every time after the bugday to keep the list clean. On the other hand, if the "rotten bugs" query more or less stays the same (and hence the tickets for the next bugday), we could also use the keyword. Hmm, hmm. Too many options, as usual with Bugzilla. :)
I like the idea with "one comment only" a lot, and it's a good workaround for the "no comments except for the reporter" query that is broken in Bugzilla upstream code. I think I'd prefer to exclude enhancement requests (there's very often not much to comment on) and set it to 18 months, which would currently result in 138 tickets.
Proposing next Monday for the bugday - could be a nice start for the week. If we agree I (or anybody who is faster) will create mw:Bug management/Triage/20130415 soon and do all the rest listed on our Meeting preparations wikipage.
Ok, but let's offer a default list sorted by bug number, which reflects the real age of te reports.
Yeah, doing some queries it is evident that enhancement requests accumulate a lot of dust alone: 78 enhancements vs 23 bugs unanswered after 2 years or more. If you count 18 months or more the numbers are 331 requests vs 136 bugs... I think these links would be very useful for Product_development.
I don't know if it is the best place to post an Annoying Little Bug opened 6 years ago about the image gallery not being to show a specific djvu page. As billinghurst suggested 3 years ago it would be a matter of supporting the "File:Book.djvu/5" syntax. Any volunteer to kill this bug?
In case you're looking for somebody to fix the bug report, Bugsquad does not write software patches, that's work for developers. :) You might want to list that ticket on https://www.mediawiki.org/wiki/Annoying_little_bugs ?
Thanks for letting me know! :) I added it to the list, hopefully someone will notice it!
I triaged the bug a bit. :) Next time you can simply put Andre and/or me in CC in the bug report.