Bug management/Triage/20130402



Starting on April 1st, 2013 and all week long with a dedicated session on April 02, we're cleaning up bug reports related to skin/theme and page rendering issues.

Skin and page rendering bug reports
What: Bug Triage of Skin and page rendering reports - see the full list of reports. We will be focusing on cleaning up, improving the quality of the reports, and retesting some on mediawiki.org or test2.wikipedia.org.

When: Week of April 01, 2013, with a dedicated Bug Day on April 02 from 16:30 UTC until 20:30 UTC. This is an ongoing activity: you can arrive / leave at any time.

Where: IRC channel. After joining on IRC, say Hello Bug Squad!. Look for users  and. We will welcome you with instructions and help. Our progress is documented in the Bug Day Etherpad.

Who: Anyone who is interested, including you!

Why: The idea came up in the Bugsquad discussion space.

See also How to triage.

This is a weekly QA activity organized by the Bug Squad team. Join us!

Attendees

 * - Trying to tame some bug reports and having fun hanging out with others on IRC!
 * feel free to add yourself here
 * feel free to add yourself here
 * feel free to add yourself here
 * feel free to add yourself here
 * feel free to add yourself here
 * feel free to add yourself here
 * feel free to add yourself here
 * feel free to add yourself here
 * feel free to add yourself here
 * feel free to add yourself here

Reports
87 reports were changed in this week, 60+ of them being identifiable as part of the bugday:

Highlights

 * https://bugzilla.wikimedia.org/show_bug.cgi?id=27312
 * Encouraging the reporter to list this interesting feature under http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects#Raw_projects
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=40622
 * Good point, no replies. Commented.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=46486
 * added accessibility keyword and priority
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=24481
 * Still relevant, added Design keyword. Updated version.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=27047
 * Added patch keyword and commented. They seemed to be close to applying it.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=24667
 * Enhancement -> Normal. Added Easy keyword.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=28131
 * Asked whether it is a candidate for http://www.mediawiki.org/wiki/Mentorship_programs/Possible_projects
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=42193
 * Cannot reproduce, asked for more information
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=33586
 * Cannot reproduce, asked for more information
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=26544
 * still valid
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=24544
 * Retested and updated summary

WORKSFORME

 * https://bugzilla.wikimedia.org/show_bug.cgi?id=25447
 * WORKSFORME
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=19757
 * WORKSFORME.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=22463
 * WORKSFORME
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=25234
 * WORKSFORME
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=16928
 * WORKSFORME
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=20842
 * WORKSFORME, cannot reproduce
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=11687
 * Close as worksforme, no answer by reporter
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=24779
 * WORKSFORME nowadays
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=36626
 * Still cannot reproduce plus no answer, closing as WORKSFORME

INVALID

 * https://bugzilla.wikimedia.org/show_bug.cgi?id=42081
 * INVALID as legacy skins have been removed
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=20533
 * INVALID as legacy skins have been removed
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=23638
 * INVALID as per comment 2

WONTFIX

 * https://bugzilla.wikimedia.org/show_bug.cgi?id=16235#c3
 * WONTFIXed as it was removed

DUPLICATE

 * https://bugzilla.wikimedia.org/show_bug.cgi?id=41887
 * Dup of LQT bug https://bugzilla.wikimedia.org/show_bug.cgi?id=41974

Moved
to gather the attention of maintainers sensitive with multilingual content.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=28920
 * Narrowing the request to the case explained above and moving to i18n in order
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=38334
 * moved to LQT per comment #16
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=45535
 * Moved to the Internationalization component, it's nothing related to skins and page rendering
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=46225
 * Moved to VisualEditor after checking with JamesF.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=15489
 * moved to Wikimedia > Site requests, as it asks for a server configuration change (user rights)
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=20807
 * Moved to Internationalizaton.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=8171
 * Changed component: Skin and page rendering -> History/Diffs
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=12664
 * Left a comment asking reporter how the current layout is. The report was filed in 2008, but I don't want to just close it.
 * Updated URL field with a non-deleted image link
 * Moved to File Management.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=24591
 * retested: way better now but still smaller issues left. Moved to Search
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=16038
 * moved to Page editing as it's not skin related

Demoted

 * https://bugzilla.wikimedia.org/show_bug.cgi?id=11415
 * Moved to Parser and priority changed from High to Low.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=14396
 * It had 15 votes and a discussion that died. Poking. Normal -> Low.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=23626
 * Normal -> Low
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=24739
 * Commented: I'm against. Normal -> Low. Design keyword.
 * Commented: there is code for gadget available.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=26292
 * Enhancement -> Trivial. Normal -> Low. Can be still reproduced. Updated version.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=40062
 * Normal -> Lowest. In my previous projects this would smell to WONTFIX, but here...
 * Link to current code on mediawiki.org
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=30525
 * Marked as low and trivial.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=28253
 * Normal -> Lowest
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=36160
 * Normal -> Low
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=41363
 * Linked to extension providing that functionality. Normal -> Low.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=32684
 * Asked for retest and dropped priority from Normal -> Low
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=24515
 * Improved bug summary, set prio to low (Level B browser)
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=23141
 * Nomal -> Lowest
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=25001
 * Normal -> Low. De-assigned from Trevor.

Other

 * https://bugzilla.wikimedia.org/show_bug.cgi?id=32281
 * Agreement to reassign all dependent bugs to Echo. CCing Andre so he can decide / execute.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=10013
 * Added See also https://bugzilla.wikimedia.org/show_bug.cgi?id=40763
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=28770
 * Functionality today provided by Universal Language Selector. Proposing WORKSFORME.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=29199
 * De-assigned from Trevor.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=13627
 * Recently updated, hence only setting Version field.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=38109
 * added upstream keyword, and linked to upstream bug report in the See Also field.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=38213
 * Added a comment regarding the context and topic of the bug
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=23475
 * Report doesn't link to a page to test and doesn't have a screenshot. Asked to retest.
 * Wondering if I should change to UNCONFIRMED
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=26032
 * Easy keyword. De-assigned from Trevor.
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=12693
 * Still valid, improved the bug summary
 * https://bugzilla.wikimedia.org/show_bug.cgi?id=34557
 * Added patch-in-gerrit keyword

Promotion

 * Announcement sent to social media channels.
 * Invitation sent to 199 contributors with open bug reports related to this goal (14 had email delivery failures).
 * Announced on English Wikipedia Village Pump.
 * Reminder sent to wikitech-l.

Evaluation

 * For an example, see QA/Browser testing/Search features.

★★★★★


 * Summary: Best results so far in terms of dedicated people and reports addressed. We also fine tuned the announcement to be sent in future bug days including a URL a personal list of reports.
 * Results: 87 reports were changed in this week, 60+ of them being identifiable as part of the Bug Day. 11 highlighted, 9 WORKSFORME, 3 INVALID, 1 WONTFIX, 1 DUPLICATE, 10 moved to other components (see Accurate bug triage metrics)
 * Participation: 10 contributors declared, from which 4 were WMF employees (see Accurate bug triage metrics).
 * New: FIXME
 * Repeating: FIXME
 * Mood: good collaboration during the Bug Day scheduled hours. Going for #wikimedia-office helped a lot isolating this activity.
 * Documentation: No complaints received. Seems to be stable.
 * Promotion: Email to bug reporters considered useful but we got 2 peoples replying that the URL was vague. Now we have a better URL showing only your personal results.
 * Developer team: Yes, especially and  were involved and supporting. The Bug Day's scope was MatmaRex's idea.
 * Organizers: We had to invest less time organizing and we obtained better results. Maybe we are onto something. :)
 * Lessons learned:
 * This was the first bugday in #wikimedia-office instead of #wikimedia-dev which was less noisy and allowed to explicitly welcome people entering the channel.
 * Using #wikimedia-office requires checking first that there are no other office hours planned at the same time.
 * Outreach to cardinal developers was successful; documentation was updated accordingly
 * Having a prepared short list of reports to start with would be helpful, to be able to point new triagers to good tickets to start with.