Bug management/Development teams usage
This page is obsolete. It is being retained for archival purposes. It may document extensions or features that are obsolete and/or no longer supported. Do not rely on the information here being up-to-date. |
Results of mw:User:AKlapper (WMF) contacting development teams by email on team information and the usage of Bugzilla. Also see mw:Wikimedia Features engineering, mw:Wikimedia Platform Engineering, mw:Wikimedia Language engineering, mw:Wikimedia Mobile engineering.
| Eng. area/team | Active projects | Legacy projects | PM Contact | Lead Eng contact | Other devs / members | Main tools | Meetings | Finding info in BZ | BZ complaints, or works well? | BZ Wishes | Misc. by Andre |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Core Features (E2) | FeedbackDashboard, AFT4/5, Page Curation, Echo | Fabrice Florin | Ryan Kaldari | Setting bug priorites: "As a rule of thumb, we view priority setting as the responsibility of the product manager, not anyone who feels like changing it. [...] We welcome people flagging unprioritized items that appear to be really important [...]" | |||||||
| Growth (E3) | Campaigns, E3 Experiments, LastModified, EventLogging, GuidedTours, GettingStarted, User login and signup | ClickTracking, PostEdit | Steven Walling | S Page | Ori Livneh, Matt Flaschen, Munaf Assaf, Maryana Pinchuk, Ryan Falkner, (Dario Taraborelli) | Primarily Trello ( https://trello.com/b/FdtPTV2y ), plus a bit of Bugzilla, Meta, mw.org | Searching bugmail to find issues | "Since Bugzilla attributes are editable by anyone, I can't rely on Bugzilla to tell the team's actual priorities." | weekly report to product-list about all bugs tagged with interface, design, or shell on en.wp | E3 uses Trello to prioritize extensions (except for "MW/User login and signup"), syncing priorities is done manually. Trello tickets that could be interesting for community are copied to Bugzilla and "higher" priorities are set in Bugzilla though. Default priority of Bugzilla tickets could be set to Normal/Low. | |
| Language Eng. | Narayam, Translate, ULS, WebFonts, CLDR, Translation notifications, Milkshake | also keeping an eye on keyword "i18n" and MW/I18n | Siebrand Mazeland | Niklas Laxström, Santhosh Thottingal, Amir Aharoni, Pau Giner, Runa Bhattacharjee | Primarily Mingle. Some tasks have a corresponding bug report | Daily hangout Mon-Fri at 08:00 UTC. Join with wikimedia.org account at http://hexm.de/i18n if you really need to... | Via shared queries in products and i18n keyword | Runa and Siebrand have bug triages. No target milestones used, might change with extension bundle releases | "Get list of bugs affecting i18n deployments, mostly config changes / enabling ULS extension. Bug 39480 should get more attention. Back porting notification is a mess." | ||
| Eng. area/team | Active projects | Legacy proj. (e.g. 20%) | PM Contact | Lead Eng contact | Other devs / members | Main tools | Meetings | Finding info in BZ | BZ complaints, or works well? | BZ Wishes | Misc. by Andre |
| Mobile | MobileFrontend; apps in Mobile product; Zero | Howie Fung | Tomasz Finc / Arthur Richards | Mobile Apps: Yuvaraj Pandian, Brion Vibber. ZeroRated: Dan Foy, Yuri Astrakhan, Adam Baso | Trello for Mobile Apps. Bingle for Mobile Frontend. | Bugs must be actionable, "non-essential" (clear how to fix), have become non-contentious. "Proud how we manage bugs as it's manageable. Our list is much smaller than most other MW projects." | Not really using the "Priority" field. Enhancement requests for Mobile Frontend/Beta can by default be set to low priority. Mingle and Bugzilla are kept in sync via the Bingle script. | ||||
| Editor Tools | VisualEditor | Vector (Trevor and Roan) ResourceLoader (Timo and Roan) Micro Design Improvements (Rob) Continuous integration (Timo) |
James Forrester | Trevor Parscal | Roan Kattouw, Rob Moen, Ed Sanders, Timo Tijhof, Inez Korczyński (Wikia), Christian Williams (Wikia) | Google Docs spreadsheet for feature planning; Bugzilla for tracking | Weekly prioritisation and bug review meetings | Shared queries | Severity vs priority: allows sort on one at a time, want sort by one and then the other | Uses BZ TMs: "VE-deploy-2012-12-10"; high prio = within 4 weeks. James sets priority when bugs come in to show they're actively working on it, or have decided not to do so and want to communicate this. | |
| Editor Tools | Parsoid | James Forrester | Gabriel Wicke | Mark Holmquist and Subbu | MediaWiki for planning, Bugzilla for tracking | No formal meetings; #mediawiki-parsoid | Using severity and priority and some blocker bugs | Gabriel sets priority: 'new' vs. something like a 'triaged' state- we are using the priority as a workaround for now. Unknown priority marks really new bugs. | |||
| Eng. area/team | Active projects | Legacy proj. (e.g. 20%) | PM Contact | Lead Eng contact | Other devs / members | Main tools | Meetings | Finding info in BZ | BZ complaints, or works well? | BZ Wishes | Misc. by Andre |
| Multimedia | UploadWizard | Ryan Kaldari | Mark Holmquist, Nischay, Jeroen De Dauw | ||||||||
| Multimedia | TimedMediaHandler | Jan Gerber | Michael Dale | Priority field | "Generally I can find things in bugzilla" | Want automatic linking of patches in gerrit/bugzilla. Now patches are linked to the bug in gerrit but not visible from bugzilla | Setting an initial priority on bug reports is welcome (according to Michael). | ||||
| Analytics | Kraken, Limn, Reportcard, Wikistats | Diederik van Liere | Dave Schoonover | Dan Andreescu, Andrew Otto, Erik Zachte | Limn: Github, Wikistats: asana.com, Kraken: not decided yet, Misc: Bugzilla; "we don't really use Bugzilla ATM" | Diederik bookmarks queries, "some Analytics engineers hate Bugzilla" | Prioritizing and scheduling is done in Mingle | ||||
| Fundraising | FundraiserLandingPage, FundraiserPortal, Fundraising: Misc., Fundraising: Requirements | (use of CiviCRM) | Katie Horn | Mingle, not really using Bugzilla | No long answer yet as busiest season in the year | ||||||
| Eng. area/team | Active projects | Legacy proj. (e.g. 20%) | PM Contact | Lead Eng contact | Other devs / members | Main tools | Meetings | Finding info in BZ | BZ complaints, or works well? | BZ Wishes | Misc. by Andre |
| Wikidata | WikidataClient, WikidataRepo, Wikidata | - | Denny Vrandečić (WMDE) | Bugzilla | Denny tries to set bug priorities, "but feel free to initialize them [...] if there are still many left" a while after filing. | ||||||
| OTRS | OTRS | - | Philippe Beaudette | Bugzilla | Setting priorities and help triaging is welcome. | ||||||
| Ops/Engineering/Product | Shell/deployment, Wikimedia Labs, Git/Gerrit repositories, Mailman, Ops RT, Bugzilla, Etherpad, (Nimsoft, Thawte, ...) | CT Woo | n/a | n/a | n/a | n/a | n/a | n/a | n/a | n/a | |
| Eng. area/team | Active projects | Legacy proj. (e.g. 20%) | PM Contact | Lead Eng contact | Other devs / members | Main tools | Meetings | Finding info in BZ | BZ complaints, or works well? | BZ Wishes | Misc. by Andre |
| Labs | Ryan Lane (General, Infrastructure, Other) | Coren (Tools) | Not using bugzilla for prioritization; engineers set their own priorities. Generally everything is low priority by default. |