Identify and track progress of open tasks in Wikimedia Phabricator with priority set to "Unbreak now" (and to some extend to "High") and identify issues to mark as deployment blockers
Triage new and existing reports by making sure that sufficient information is provided, setting priority if wanted by development teams, helping to find assignees, cleaning up and organizing older tickets.
Coordinate and (co)organize bugtriage, bugsquad community outreach and growth (via bugdays)
Keep an eye on other feedback channels where bugs might be reported, like Village Pumps, especially in the 24h after deployments of new software versions on the WMF servers
Phabricator maintenance (to some extend; taxonomy and configuration changes)
Monthly goals and tasks are now tracked for "Aklapper" (the bugwrangler) under the corresponding monthly ECT (Enginnering Community Team) project in Phabricator. See the ECT board and the corresponding monthly sprints and their boards.
Set up workflow for having a regular, easy "bug of the week" for new code contributors, with rotating support of Wikimedia development teams (based on Annoying little bugs) Status: planning page -- postponed to January (after Google Code-in)
Phabricator: Work on consensus on configuration settings, drive decisions and keep an overview Status: In progress
Have a bugday on UploadWizard Status: Not done, likely to happen on Sep 09th 17:00UTC
(With Quim) Set up workflow for having a regular, easy "bug of the week" for new code contributors, with rotating support of Wikimedia development teams (based on Annoying little bugs) Status: Postponed to October due to Phabricator being priority
Phabricator (driving tasks): Get Alpha instance up and running; work on consensus on configuration settings Status: In progress
(With Quim) Set up workflow for having a regular, easy "bug of the week" for new code contributors, with rotating support of Wikimedia development teams (based on Annoying little bugs) Status: Not done: planning page created on 2014-07-02 targetting end of July
Have a Pywikibot bugday with the Pywikibot hackers around the end of July Status: Done - summary email; wiki page
Mostly Phabricator business (driving tasks) Status: In progress
Prepare introducing "Bug of the week" by talking to development teams Status: In progress - Andre started preparing email draft to dev teams and workflow of planning on 2014-06-16
(With Guillaume) Close Phabricator RfC, and bring it to a decision if possible. Status: Done, see email
Phabricator: Identify "heavy topics" and blockers (vs. acceptable trade-offs) that must be fixed before starting a migration to Phabricator. Status: Done, see board
Phabricator: Act on top items in the "Doing" column for Phabricator migration Status: In progress
(With Guillaume) (Continued from March) Set up and facilitate the community RfC about Project management tools/Review, and bring it to a decision if possible. Status: Done - RfC started on 2014-04-14
(With Guillaume) Have another IRC office hour about Project management tools Status: Done on 2014-04-17 and 2014-04-22
Gather more feedback on rebooted Annoying little bugs after GSoC start Status: In progress - Andre sent an email to five GCI mentors on 2014-04-24 and received three answers
Prepare introducing "Bug of the week" by talking to development teams Status: Not done -- postponed to May
Have a bugday in the second half of April Status: Done: on 2014-04-29 about General MediaWiki, see Bug management/Triage/20140429
(With Guillaume) Have an IRC office hour about Project management tools Status: Done on 2014-03-28
(With Guillaume) Set up and facilitate the community RfC about Project management tools, and bring it to a decision. Status: Not done -- postponed to April
(With Quim) Reboot Annoying little bugs based on Google Code-In experience; Bugzilla's easy keyword; exposing an easy "bug of the week":
Kill curated list on the wikipage; provide specific Bugzilla queries and "getting started" instructions for each area: Status: Done on 2014-03-07 (diff)
Introduce "Bug of the week" after talking to teams? Status: Not done - postponed to Q2/2014
Provide a NEEDINFO flag in Bugzilla - bugzilla:36064. Status: In progress: (porting more complicated as bmo will skip 4.4) -- might get postponed to Q2/2014
Provide a way to mark an item as NEEDINFO in Bugzilla - bugzilla:36064. Status: In progress: Created list of pros and cons of two implementations on 2014-03-10; next step is start broader discussion on wikitech-l@ and agree on which way to do
Install component watching extension to be able to receive bugmail for specific product/component for devs and triagers, plus no more manual adding of people to auto-CC by admins - bugzilla:37105. Status: Not done -- database issues when testing; not yet tested on 4.4 and upstream code is still 4.2 only. Porting more complicated as bmo will skip 4.4 -- postponed to Q2/2014
Improve Bugzilla queries on Annoying little bugs to show a good subset: Status: Done on 2014-02-18
Add guidelines for triagers how to identify a bug report that is good for this audience: Status: Done by editing the "easy" keyword description on 2014-02-24
Retriage existing bugs with easy keyword: mostly Status: Done
Fix inline displaying of image files in Bugzilla - bugzilla:54181. Status: Done - andre successfully tested csteipp's patch on Labs on 2014-01-05; deployed on 2014-01-10
(With Quim) Finish running Google Code-In contest. Status: Done
Evaluate Project management / issue tracking requirements and potential tools. Status: In progress - kicked off on teampractices@ and wiki on 2013-12-13
Test Bugzilla 4.4 with our custom patches on Labs (or zirconium in eqiad if production is still on kaulen in Tampa). Status: In progress, will need help from ops. Steps discussed between dzahn and aklapper on 2013-12-06; dzahn has set up a copy of Bugzilla 4.2 on zirconium in eqiad (see RT #4783). Next steps are upgrading that machine to Bugzilla 4.4, applying our custom patches, testing, and finally switching over.
Google Code-In: Define generic information (template) for all task descriptions; clean up & import tasks from wiki into Google Melange. Status: Done (except for tasks missing a mentor)
Finish cleaning up and syncing custom CSS in Wikimedia Bugzilla. Status: Done - done (except for two CSS files) (bugzilla:54823)
Have a public bug day approximately once per month. Status: In progress, planning next on in phab:T78684
(With Quim) Expose a regular, easy "bug of the week" for new code contributors with rotating support of Wikimedia development teams (based on Annoying little bugs) Status: On hold -- after GCI, phab:T563
Successfully (co-)organize Wikimedia's participation in Google Code-In Status: In progress, phab:T76720
Progress on migrating to Phabricator: Set up Phabricator production instance, set up Legalpad instance, have test import of RT/Bugzilla data Status: In progress
(With Quim) Expose a regular, easy "bug of the week" for new code contributors with rotating support of Wikimedia development teams (based on Annoying little bugs) Status: postponed to October
(With Quim) Expose an easy "bug of the week" with dev team support (after Annoying little bugs is in shape) Status: In progress, Andre preparing
Have a public bug day approximately once per month. Status: Done on 20140428 and 20140624, planning for 201407 started
Some more Bugzilla taxonomy cleanup. - bugzilla:38990 Status: On hold -- not enough time for this plus low priority now that we favor Phabricator
Investigate closing components of extensions archived in the code repository. - bugzilla:47540 Status: On hold, postponing
Investigate splitting "enhancement" out of Bugzilla's "severity" dropdown and make it separate. - bugzilla:58096 Status: On hold, low priority & only if we stick with Bugzilla -- not enough time for this plus low priority now that we favor Phabricator
(With Guillaume) Meet Project management tools stakeholders, determine requirements, and document this research. Status: Done
(With Guillaume) Lead the community discussion about the shortlist of candidates for Project management tools, take the first implementation steps (possibly in Labs). Status: In progress
(With Guillaume) Set up and facilitate the community RfC about Project management tools, and bring it to a decision. Status: Not done - postponed to April 2014
(With Quim) Reboot Annoying little bugs; Bugzilla's easy keyword; exposing an easy "bug of the week": Based on Google Code-In experience, decrease manual curation work by providing links to common "getting started" questions. Status: Done on 2014-03-07
Upgrade Bugzilla to 4.4 Status: Done on 2014-02-13
Common queries on Bugzilla frontpage - bugzilla:22170. Status: Done on 2014-02-13
Provide a way to mark an item as NEEDINFO in Bugzilla - bugzilla:36064. Status: In progress: Created list of pros and cons of two implementations on 2014-03-10; next step is start broader discussion on wikitech-l@ and agree on which way to do
Install component watching extension to be able to receive bugmail for specific product/component for devs and triagers, plus no more manual adding of people to auto-CC by admins. Status: Not done -- postponed to Q2/2014
Evaluate Project management / issue tracking requirements and potential tools. Status: In progress - kicked off on teampractices@ and wiki on 2013-12-13
Andre to learn more about / understand better Wikimedia's Release Management from Greg. Status: Not done won't happen this quarter, too busy with additional projects added while in Q4 (BZ etiquette & PM Tools eval)
mw:Annoying_little_bugs - try announcing an exposed easy "bug of the week" for new contributors, with support from dev teams. Status: Not done -- Google Code-In has priority over this.
Bugzilla setup / code:
Show InlineHistory in Bugzilla - bugzilla:47256. Status: Done
Clean up custom Perl CPAN modules and replace by distribution packages; puppetize Bugzilla's package requirements - Status: Done - RT #4783
Copy current production Bugzilla 4.2 to zirconium in eqiad (from kaulen in Tampa) for testing. Status: Done on 20131225
Upgrade Bugzilla on zirconium from 4.2 to 4.4. Status: Not done
Apply custom changes to Bugzilla on zirconium. Status: Not done
Test Bugzilla on zirconium. Status: Not done
Switch from old server to new server. Status: Not done
Only after 4.4 upgrade: Provide a NEEDINFO flag in Bugzilla - bugzilla:36064. Status: In progress - moved to Q1/2014 as 4.4 upgrade takes longer
Only after 4.4 upgrade:Install component watching extension. Status: Not done -- database issues when testing; not yet tested on 4.4 and upstream code is still 4.2 only. - moved to Q1/2014 as 4.4 upgrade takes longer
Puppetize Bugzilla - bugzilla:51036 Status: In progress - dzahn of ops working on this since 12/2013
Due to Wikimedia's move from Bugzilla to Phabricatorany tasks in this list which are still valid and applicable should focus on Phabricator instead of Bugzilla!
General bug documentation updates (please see phab:T206 first!):
Document and explain the main things that people do in a bug report: Should I comment or not? Add myself to CC? (This was OPW feedback from Valerie.)
Extend triage guide to also cover enhancement requests. This is a bit more special (e.g. when it comes to WONTFIXing/declining tasks etc.).
Bug documentation updates that require discussing with other stakeholders first:
Make meanings of resolutions/statuses clearer (in Bug_report_life_cycle or How_to_triage?), e.g. when to set WONTFIX (and when not) in Bugzilla or DECLINED in Phabricator, and after how much time to close a report without enough information as WORKSFORME in Bugzilla or DECLINED in Phabricator? (This was OPW feedback from Valerie.)
design keyword (Bugzilla)/project (Phabricator) workflow: Improvements possible? Requires talking to the design team.
Talk to Mobile team: Are there instructions somewhere for users how to provide a stacktrace when the Wikipedia App crashes on iOS or Android that could be added to How to report a bug? (e.g. bugzilla:41027)
Policy: Define a policy when users are blocked or when insulting/useless comments will be hidden - might not be needed as the global Code of Conduct applies
Policy: Usually "community-consensus-needed" (keyword in Bugzilla, project in Phabricator) is used where there are concerns that the local community might not have discussed the change, or the change is not supported by them. Otherwise "shell" is used to show bugs which need a shell user to review, merge and deploy. "community-consensus-needed" is always turned into shell after clarification that community consensus exists, cf bugzilla:45539.
Consider collecting stock answers, cf. Maemo or MeeGo
Cleanup: Identify MediaWiki extensions in SVN which have not been converted from now read-only SVN to Gerrit and are hence dead. Close their bug reports as RESOLVED WONTFIX (Bugzilla) or DECLINED (Phabricator), explaining the situation, and add some "unmaintained" project (to be discussed and defined) so they could be identified later per component in case somebody wants to pick up development again? Also see Git/Conversion/Extensions_queue.
20131014: Enabled InlineHistory by default for all users - bugzilla:47256
20130930: Create good relation to upstream Bugzilla developers via attending upstream Bugzilla meetings and being active on IRC and the support-bugzilla mailing list
20130926: Do not limit Product column in buglist.cgi to 8 chars - bugzilla:40244
20130925: Show InlineHistory in Bugzilla - bugzilla:47256
201211: Creation of "immediate" priority in Bugzilla (discussion) due to varying use of "highest"
201211: consider introducing a status WAITINGFORUPSTREAM like in Mer Bugzilla - not wanted as per mailing list discussion, use lowest priority and "upstream" keyword instead
