Bugs, Bugs, Bugs!
summary
Counts and tools matter: Mozilla shows 450 new reports a day, Wikimedia/Wikipedia and GNOME have different scales, and concrete practices follow. Bugzilla tweaks (a needinfo flag, a ready state), a GreaseMonkey/extension for one‑click canned replies, saved‑search cleanup and dashboards, plus experiments with gentle mass closes and one‑file‑per‑issue repos all get described and tested. Watch if the talk’s concrete numbers, extensions built, and triage outcomes decide whether these methods work for large trackers.
AI-written summary · about
chapters (11)
- 0:00Start
- 3:45Should your project have a bugmaster?
- 4:50Platforms and tools
- 7:50Bugs can be healthy
- 10:19Who's all up in your bugs? Bug tracker user roles
- 15:47The Art of Bug Reporting
- 18:33Thorny problems
- 19:06List of complicated issues
- 22:16Changing the life cycle
- 28:03Developer reactions to changes in statuses
- 31:44Sample of very old open bugs
related talks
17mDiscussion - Protocols, Session 2
44mDefeating Firefox
29mEvent-based Fuzzing, Patch-based Research, and Comment Police: Finding Bugs Through a Bug
31mData Driven Bug Bounty
43mSyzbot and the Tale of Thousand Kernel Bugs
15m"You've Got Your Nice List of Bugs, Now What?" Vulnerability Discovery and Management
13mThe Bug Hunter’s Guide to High-Quality Reporting
38mBug Logging Tool Project
