Bugs and sheriffs in London

Travelling Bugmaster update! I am in London with a bunch of the automation tools team for a work week. Ed, jeads, Chris, Ryan, dave, and mauro have been neck deep in making decisions about the structure of a new version of TBPL. By eavesdropping in their conference room I have learned a bit about how Ed and RyanVM and others watch the tree (sheriffing). Also, dkl and gerv and I met up to talk about bugzilla.mozilla.org and I got to bounce some ideas off them about possible ways to tweak the incoming bug triage workflow.

The London office is right between Trafalgar Square, Chinatown, and Covent Garden. It’s very accessible. If you come to Mozilla London offices and are a wheelchair user, you should know that the Tube stations near the office are not accessible. Give up and take the Heathrow Express to Paddington and then a taxi.

Lanterns sky

The BMO and IT teams (glob, dkl, and fox2mike, mostly) are planning to upgrade bugzilla.mozilla.org on March 8th. You can give it a test drive here: bugzilla-dev.allizom.org. This brings Mozilla’s implementation in line with the upstream version of Bugzilla 4.2. In theory, the new server hardware and architecture will also make BMO much faster.

I’m mostly excited about the user and product dashboards in this release. They look extremely cool — great for people who are doing bugmaster and triaging work. Someone who wants to drop in to triage Firefox bugs, or to get a mental image of what’s happening with bugs of interest to them, will be able to do so easily, without having set up a sort of pachinko palace labyrinth of bugmail and filters.

Bugzilla user dashboard 500

So if you would like a sneak preview of the user and product dashboards, take a look on bugzilla-dev.allizom.org and poke around! You can talk to us on #bmo or #bugmasters on irc.mozilla.org if you have feedback. And do please help us by filing bugs!

Besides the upgrade and move, and the archictecture of bzAPI current and possible future — gerv, dkl and I discussed the re-framing of early bug triage as “Bugmaster” or bug management work. We kicked around some ideas and it was very helpful to me to get their advice.

I am adding links to current wiki docs into the show_components.cgi descriptions and dkl has promised to expose those descriptions in show_bug.cgi views of individual bugs. My thought is that within the bug itself, the reporter and triagers, or an aspiring new developer, will have multiple ways to dive deeper into the bug.

We talked about adding common reply templates, which I am collecting in the Bugmaster Guide but which would work well, I think, built into Bugzilla. It turns out that dkl already has an extension started, canned comments, to do exactly this. Very intriguing!

Another thing I’d like to see is something that invites extra information when a bug is filed. This can be context sensitive, so that, if you file a bug in Firefox for Android in a particular component, there can be a link to relevant support forums, wiki pages, the irc channel, and the module owner information. This landing screen could also invite the bug reporter to add bits of information they have not included. If they haven’t attached a screenshot or included a url there could be an attempt to elicit them, or a few “next steps to help make this bug more reproducible” suggestions.

I am still thinking about the READY status flag and other ways to mark “early triaging is happening, or should be happening” vs. “in the hands of dev team”. That is a fuzzy boundary and different conditions would lead to it for different products/components. In this discussion we looked at Gerv’s and Jesse Ruderman‘s proposals for BMO workflow:
* Workflow Proposal 1 which simplifies the status chain.
* Workflow Proposal 2 which more radically changes the flow and statuses to a “next action” framing.

I can see benefits and drawbacks to both models.

It would be helpful from a triaging point of view to be able to declare, in an obvious-to-all way, that a bug is as triaged as we can get it for the moment and it either is ready for a developer to look at or is in some sort of Bug Limbo waiting for later re-assessment. We can do that with some assortment of existing tags and keywords but it may lack clarity and ease of use.

We brought up the idea that if I am doing some triage on a bug but don’t feel it is “ready” yet — for example perhaps I have identified its component, but not reproduced it, or vice versa — I can list myself as the QA contact. What would that indicate, though? Would it keep away other triagers? That is not what I’d want, of course. We could end up with some sort of “needstriage” checkbox, or make a tagging taxonomy that is well documented and evangelize it.

On Sunday I spent some time wandering around in a rented mobility scooter. It is possible now in London to hire a scooter for 70 pounds a week. Very much worth it not to have to push myself over thousands of cobblestones. I have only run over one person’s foot so far in the swarms of tourists, theater-goers, schoolchildren going to museums, and Londoners purposefully striding around in overcoats staring at their mobile phones. Though the scooter delivered is bigger than most cars in this country. It is like an enormous Mecha Gundam Wing suit on wheels so my adventures in the London streets are reminiscent of the Pacific Rim movie trailer.

Lion unicorn palace

In London, when confronted with a giant wheeled exoskeleton, people generally give a tiny gasp and start (theatrically), mutter apologies, and make a show of getting out of the way while looking bewildered. They are relatively good at not acting shocked that I exist. That’s kind of pleasant really. Some buildings and restaurants are somewhat accessible. I get along here as long as I don’t think too hard about how I can’t use the Tube at all and I can afford the glorious taxis.

In Vienna, I used my manual chair. Almost nowhere is accessible even when it is declared to be. People there would loudly gasp, almost a little shriek, and leap forward to grab me, which reminded me of how people act in Beijing when they see an independent person using a wheelchair. They scream, and they leap, like kzinti. More details on hilarious wheelie adventures in the Hofburg, coming soon. Travel is lovely but I’ll be glad to be back in San Francisco at the end of the week.

Bug history and conversations

David Baron wrote an interesting post recently, Moving bug history out of the primary display of a bug report. I have noticed this problem in Bugzilla, that even if a bug is “ready to be fixed” or has patches submitted it is necessary to read through 5, 10, or 50 comments to understand what is supposed to happen next (if anything). dbaron proposes that the main page of a bug report should show its current state. What is true about it? And what is to be done next? This would be obviously awesome for some bugs, but not for others for which there isn’t a clear state of truth. My first instinct is to question dbaron’s idea, as there might be bugs for which the conversation is the most important aspect.

For example Bug 130835 – Make Bugzilla’s index.cgi (home page) useful for logged-in users has over 150 comments, stretching back 10 years. Here the problem may actually be that the bug (or enhancement request) was not well defined in scope, so had no clear end. It might be worth untangling the useful ends of these 150 comments to close this bug, and open several new and more specific ones for which “current state” *could* be summarized as dbaron suggests.

But what about a bug like Bug 83192184 – Make the plugin click-to-play UI look less like ‘plugin broken/crashed’ UI , where there is a useful active conversation? In that case trying to synthesize the conversation at every step of the way, each time someone comments, is probably not useful.

Day 32: Cats

So in some cases there is clear “current state” or content, as there is on a Wikipedia page, but in some, the conversation is the content. I don’t want to have (or read) conversations in a Bugzilla equivalent of Wikipedia talk pages and am not sure that would be an improvement on the current state of Bugzilla comments. For bugs with a long history, especially ones which have mutated significantly since their beginning, the “current state” field might be an easy way to untangle the mess.

My job, told with Up-Goer Five text editor

Today I had fun reading xkcd’s Up Goer Five cartoon and then playing with the Up Goer Five text editor.


I tried describing my new job:

Many people at my job work together to make free things that go on computers to make it so everyone can see the words and pictures on other computers in the world. Everyone can see the words that make these free things. The biggest thing we make is named after an an animal and fire. Fire Animal Computer thing can go on a a computer, or a phone. It can even start a phone and make it go. That is new!

There are other computer things too, like Rain Noise Flying Animal and Water Tree Animal. They have new parts all the time. When the Fire Animal Computer Thing or the other computer things have a problem, people tell us about the problem. That problem goes in a very big computer box place together with all the other problems. That very big computer box place is named Big Pretend Long Ago Problem Animal.

My new job is to watch all the almost hundred hundred hundred problems in Big Pretend Long Ago Problem Animal. I will remind everyone in the world to work together on a big big team to fix the problems. I have to know many things to help them do it. On this team we will all tell the people to talk to each other. I look at the words and put other words on the computer to tell about the problems. I work with many other people that help put more words on the problems to help fix them.

Some day I will know many more things and many more people who fix the problems, especially with Fire Animal Computer Thing. I will help make ways to make the work easier. There will be more computer things that work almost by themselves to do the work. Then, all the Big Pretend Problem Animal work people like me will tell the computer thing making people some more things to help them fix the problems. We do it in a way that everyone can see!

We will work together so all the people in the world can talk with each other and see pictures with no problems, free, on a computer and on a phone. They can make many more things. We think everyone can help the world this way. Some day, everyone can know all the things. That will be very good.

Bugzilla quicksearch, or else!

Here is a fabulous tip if you are messing around in bugzilla.mozilla.org and are searching for bugs. As, by now, as a reader of my blog, you should be.

You can search Bugzilla right from the location bar. I cannot quite bring myself to say “Awesome bar” as people do at Mozilla because I’ve said “location bar” for many years, and it feels silly.

First you will need to be logged in to a Bugzilla account!

Right(command)-click in the Search box. Choose “Add a keyword for this Search”.

Pick something short that you will remember, like “b” or “bug”. I added both since they both seem intuitive enough to me that I’ll probably forget choosing one or the other.

Command-L is the keystroke on a Mac to move to the location bar.

So, type Command-L, type bug 831552 and you will be whooshed directly to that bug.

Command-L, bug retina will result in a fairly quick list of around 18 bugs (as of right now.)

Here are a bunch of quicksearch tips for bugzilla.mozilla.org!

Take a look at the tips and see what quicksearch looks at by default. There is lots of useful info there and it is worth going through and trying some of the options and noting which field names might be specially useful.

The Advanced Shortcuts are the best thing about quicksearch for me so far. For example, Command-L, bug UNCO retina returns all the unconfirmed bugs with the keyword “retina”. (About 4, currently). Though keywords aren’t case-sensitive, the Advanced shortcut “Status” search terms are. So you have to type bug UNCO retina, not bug unco retina.

At the moment, quicksearch look in comments and various other bug metadata. After January 24th that will change — comments will be excluded by default from quicksearch. That should make it actually quicksearch instead of kinda_slow_search. Or at least quickersearch. Until then, you can type bug --comments retina and your search about retina-related bugs will be a bit faster.

Here is the “or else” part from the title of this post: If you have been calling yourself “The Bugmaster for Mozilla” for several weeks, and you slowly mouse over to a search box to type something, and you do this in front of some kick ass developer, instead of using quicksearch in the location bar, you will be embarrassed. So take it from me and don’t do that.

cats in hats

Thrills, chills, filters, and bugmail

Any bugmail at all is probably way too much bugmail. That means you will need to set up some structures to filter it!

This explanation may be useful for anyone interested in contributing to Mozilla — especially bugmasters, triagers, and developers. Even if you don’t use the same email setup, there’s some good tips.

Byron (aka glob) explained how I could set up my Bugzilla email, or bugmail. Within Bugzilla, in the Email preferences tab, there are a complicated set of checkboxes to control what conditions in Bugzilla trigger your bugmail. Right now, my email notifications are set to fire off email to me whenever anything happens to a bug I may be interested in.

Bugzilla email prefs

I then set up some users to watch, at the bottom of the Email preferences screen. Whenever Matti, Tyler, or Benjamin do anything with a bug, Bugzilla emails me about it. I can also see that Josh is watching my Bugzilla activity. People often refer to this as “stalking” in Bugzilla, without any creepy connotation intended. It is basically TMI about someone else’s bugs (or what bugs they poke at.)

Bugzilla user watching

“If you watch a user, it is as if you are standing in their shoes for the purposes of getting email. Email is sent or not according to your preferences for their relationship to the bug (e.g. Assignee).” The meaning of that takes a while to work out, much like Bilbo Baggins’ famous statement at his eleventy-first birthday party… “I don’t know half of you half as well as I should like; and I like less than half of you half as well as you deserve.”

I have picked two components to watch. Bugs in BMO (bugzilla.mozilla.org) are organized first by Product, such as Firefox, Firefox for Android, Thunderbird, and so on; then by Component, which seems to be a division by who is working on a particular area or project. You can’t pick a Component, or even see it, till you figure out what Product your bug belongs to. Here is a helpful guide from the Mozilla Developer Network with a list of Mozilla Products and their Components, handily all on one page, so it is easily searchable. I have also been using the list of Modules and their owners from the Mozilla.org wiki.

Bugzilla component watching

We don’t even have any bugmail yet, and see how much we have learned about the structure of a giant complicated FLOSS ecosystem! Hurray!!!! *waves pom poms*

Cheerleader cat

At this point, I made some folders in Zimbra inside a general Bugmail folder. While I’m still not sure how I’ll settle on bugmail organization, right now I have separate folders for my watched components and people. Then, in Zimbra preferences,there is a sidebar option for “Filters”.

Bugzilla filters

Create a new filter, then for users you’re watching, filter on header, and set the header name to X-Bugzilla-Watch-Reason. (For other filters, check the full headers and see what X-Bugzilla header info will work best.)

Bugzilla x headers

Since the X-Bugzilla-Watch-Reason filter contains the person’s email, if they change their own bugzilla email address, my filter will break.

Bugzilla user watching

Onward to Thunderbird, which I have set up with IMAP to check my Zimbra account.

Right-click (or command-click for a mac) on your account name in the Thunderbird sidebar, and choose “Subscribe”. This shows you the folders on your IMAP-connected account. Expand the folders and check the tickybox next to the new folders you just created in Zimbra (or whatever else you use). This will create a copy of that folder in Thunderbird.

Bugzilla thunderbird subscribe

One more step. In the Thunderbird sidebar, right-click one of the new folders that was just copied over from your IMAP account. Choose “Properties”. Then check the tickybox labelled “When getting new messages for this account, always check this folder.”

Now your bugmail will nicely filter itself — in both email clients.

That was non-obvious enough that I really wanted to document all the steps. Maybe some other new hire at Mozilla will be helped!

If anyone has bugmail tips for me, I would appreciate that!

Bonus points to anyone reading this who notices my PretendOffice filter and has a good laugh.

Twiddling my email, calendar, irc, and phone notification settings

Calendar and email notifications may sound very boring but they has engrossed me for at least an hour.

For the first time in life I have a work laptop and a personal laptop. For the last 10+ years I’ve come into a job with an existing laptop which I use seamlessly for work and personal stuff. So far, I like having less “personal” things on my work laptop. It is especially nice not to have the distraction of personal email and non-work related mailing lists. It also feels amazingly luxurious to set aside the work laptop at the end of the day.

I have Zimbra for work email, but prefer to read my email in Thunderbird on my work laptop. Zimbra calendar has my work meetings and Google Calendar has the general schedule for my life. This morning I realized Zimbra was nagging me about missing a meeting. I need to know beforehand in some way that isn’t inside a browser tab!

Instead, I’d like my phone to make a special alert noise for meetings 10 minutes beforehand so I know to open up Skype or Vidyo (what Mozilla generally uses for meetings).

BEEP cover

The last bit of information in this scenario: I didn’t want to install some special Zimbra app on my phone.

Here’s what I did:

1. Set up Zimbra to SMS me at (my 10-digit phone number@tmomail.net) before meetings.

In Zimbra, go to Settings, calendar, set up phone number for notifications.
In each meeting there is a checkbox for email notification. This works for recurring meetings as well.

2. Set up my phone so that gmail notifications only make a noise for priority inbox mail. (I realized that my phone makes a noise every time it syncs email. I normally ignore that noise. )

Open Gmail on the phone, Menu>More>Settings>click the email account>Labels to Notify>Inbox ***>Ringtones (set to silent)

*** Tweak the settings for the Priority Inbox too.

4. Go to gmail.com and set up whatever should go into “priority inbox” i.e. filtered to “important”

google calendar already has its own notifications on android phone if you have its app installed. If not you can set up a forwarding address and make the calendar email to SMS you.

5. make sure incoming SMS messages have a different noise than priority emails
Go to messages, menu, then settings, Select ringtone.

It took a little thought to figure out what to use to get the simple result I wanted. And while most of it happens in web services and phone settings, some of it was in my training myself in a different behavior (paying attention to a particular noise on my phone.)

A final note: Long ago I set up voicemail from my phone to Google Voice. I hate listening to voicemail. It takes a long time. Text is so much nicer, and it helps that I read very quickly. All voicemail interfaces suck. The last time I used one, it had a default menu message that took about 15 years to go through that played after every single voicemail. This resulted in my *never* listening to my messages. (Fortunately I have not had a work phone for years; just email.)

People sometimes leave long messages, but the gist of them is just “call me back”. Google Voice is lovely for this as it sends me an email transcript of the voicemail. The transcripts are often hilarious garbled but it’s enough to get the idea of who’s calling, what their number is, and what they want. If I want to hear them, I can press “play”. Their messages are also nicely archived for me in Gmail. Hurrah!

In which I explain Yggdrazilla, the World-Tree, and see some fireboats

Yesterday I headed into the Mozilla San Francisco office with my son Milo in tow. It was sunny and beautiful! We had lunch at the High Dive, a little diner right on the waterfront. He tried out my TV-B-Gone delux and we laughed very hard at the feeling of being super-spies with our spy gadget. Or, he might have just been laughing at me. It’s hard to tell!

On the walk back from the diner I pointed out the old SFFD building and that there was a fireboat on the other side of it. We went round to watch the boat pull out of its berth, apparently giving some non-firemen a tour in the sparkly winter sunshine. On its side it was labeled Guardian, boat #2. There was a sign in front of the building explaining the history of San Francisco fireboats. We both avidly read this sort of thing. The more famous of SF’s fireboats is the Phoenix from 1955, which saved the Marina district after the 1989 Loma Prieta quake. “I guess it’s still useful, even though it’s old-fashioned” he commented. The fireboat is also extremely cute; stubby and with a little striped tower, like a tugboat.

guardian fireboat

At the office I picked up a B2G test drivers phone so I can help test FirefoxOS. Sights of the office for my son were: my cube (unexciting), the shelves of free snack food (from which, abstemiously, he snagged a banana and two starburst candies), and the roof with its view of the Bay Bridge. The night before, I had read him the first few chapters of Flatland. He had picked it up to read on the bus and while I worked, since it’s lighter to carry than the Draconomicon. He kept interrupting my concentration on email and Bugzilla to read me bits from Flatland.

I figured I would return the favor. “So, would you like to know what I am actually working on?” Yes he would. Whatever I do for my job On The Computer is something of a mystery. Even to me . . .

We read the principles in the Mozilla Manifesto. (“Nice, Mom. That sounds like you. But, no offense, but, well, I’m already reading a book where people explain boring things about politics.”) Okay, moving on. I explained that there is a non-profit Mozilla Foundation as well as Mozilla Corporation, then that there is a greater Mozilla community (Mozillians!), who all work on making various tools better: Firefox in various flavors, which he is familiar with, but also Thunderbird, Bugzilla, and other stuff.

He got that Bugzilla is a product anyone can download, install, and use to track problems, but that Mozilla has its own implementation of Bugzilla, which we call BMO (for bugzilla.mozilla.org). Someone puts a bug into BMO; then a lot of people might look at it and do something with or to it.

My job as the newly-fledged Bugmaster is to help manage the huge volume of bugs in BMO. I pointed out that in a search for bugs filed in the last 24 hours the ID numbers for the bugs are up to 82600. So 800,000 bugs have been reported since Mozilla has been around, over 10 years ago.

(ETA: You need to have a bugzilla.mozilla.org login in order to use the above link. Hmmm.)

I’m taking a look at triaging new bugs, or in this case, adding information to bugs with UNCONFIRMED status and moving them to some new status. Generally, a bug that is UNCONFIRMED has not been triaged. My big question right now is, though there is no natural “end” to triaging a bug, how can we demarcate untriaged and partly triaged, bugs from ones that are… let’s say… good enough for now for a developer to look at? I could encourage people who do something with a bug to move it out of UNCONFIRMED. I could invent a system of whiteboard tags or flags to mark up bugs for the bugmastering throngs who live in #bugmasters.

Anyway, I didn’t go into that for Milo. I gave a very quick, hand-wavy explanation of how FOSS projects tend to have a “trunk” which is basically the code that’s been tested and released, trying to give an impression for him that a lot of people touch that code as it gets committed to branches, tested, and merged in to the trunk, watched over by Sheriffs. I showed him the tinderbox push log page which displays commits and a battery of automated tests that they pass or fail. Milo (who is not into programming at all) commented that there is Mozilla, and Bugzilla, and everythingzilla, so there should be Yggdrazilla, like the world-tree from Norse myth, to describe this cool giant tree of code.

I love the name Yggdrazilla! Though I’m not sure what exactly it would describe!

This morning as I fired up to work from home, Milo came in to show me an amazing coincidence! One of his giant phone book sized DC comics compilations from Christmas has a comic book about Center City and its new fireboat, the Phoenix!


We stopped on the way home at a TMobile store to get a SIM card for the B2G test phone, and then excitedly fought over it to play Little Alchemy on the bus and after dinner. I’m going to set aside time to poke at FirefoxOS (aka B2G or Boot2Gecko) every day but am not sure I’m going to use it for my primary phone. I informally reported one UI issue with it, and today would like to double check on that and will probably put it into Bugzilla. It immediately wanted to import all my contacts from Facebook, and all the contact info for my Facebook friends. Wow. Scary but interesting. FirefoxOS is going to released soon and will make smart phones a lot cheaper and therefore more accessible for people. As soon as I can buy one for Milo, I will — it will be his first smart phone. It’s really tempting to try to write an app for it.


First day at Mozilla!

I spent yesterday in the San Francisco Mozilla office, meeting people, setting up my laptop, and getting a general orientation. It’s in the Hills Brothers Coffee building across the plaza from Google, so I went past a hilarious statue (too late from the bus to study it in any detail) into a marble-floored entry hall and into one of those dark woodpaneled elevators with a mirror that are successfully posh, but need cheering up or art on the wall or something to look at other than the reflection of elevator-awkwardness. In elevators I have the choice of lining up my wheelchair or scooter foolishly backwards to back in, then emerge with dignity; barrelling in over-fast to jump the gap and scaring anyone already in the elevator, then waiting facing the “wrong” way; or, jumping the gap forwards and then executing a clumsy or neat 7 or 5 or 3 point turn which definitely scares everyone else’s feet. Sometimes I forget to slow the scooter speed and crash into the elevator wall.

Enough about that! The 7th floor is more cheerful, light, full of colored couches and enormous refrigerators and baskets of candy and snacks enough to feed armies of squirrels. An extremely nice person named Peter gave me a laptop and pointed me at a videoconference set up on a tablet in a sort of tablet holster with headphones so that I could be in the HR orientation, which was fairly painless and lasted about an hour. I am one of the first batch of new hires to go through their new “onboarding” system, which has been bombarding me for a week with exhortations to Join the Glorious Mozillian Cause, Comrade, join every mailing list/newsgroup/irc channel in the world, and fill out my forms. It seems a good system. “Firehose” is too weak of a term.

mozilla lizard logo

I kept notes on all the tiny errors in the process, throughout last week, to report them in batches. I felt that I was already working there, without being paid, which, well, why not when they are so awesome and it is free/open source and a huge worldwide volunteer community! Onwards!! I spent some time last week, and then, much more fiercely yesterday, coming up with ways to organize these huge tributaries of information and systems for myself to skim off the bits necessary to move something forward, respond or act. I feel like a little space station way out somewhere, beginning to turn on its ansible and light up, coming online in a giant network of ships and stars.

Right, where was I. I was introduced as a new hire at an amazingly competent video conferenced short Mozilla weekly meeting. I had already looked at past meetings while studying up on what was going on at the company, to interview. Then was on irc, on the #qa and #ateam channel, then meeting the Bugzilla team who are in town for the week and who were very amiable. I wonder if they would like to come to Noisebridge? It is amusing to work at a grownup job where people are introduced to you with names like “glob” and “potch” and it is normal for me to be named “lizzard” since it has been my irc name for forever. I listened to the Bugzilla folks for a while. They super nicely offered to take me with them tomorrow on a datacenter tour, where I will arrive as a sort of wheely cyborg surprise to whoever is squiring us around. Then had lunch (free, catered, very nice lunch on Mondays) with Lukas Blakk, ran into Tantek, met Boris and Dave and the guy with the purple mohawk, and Heather who showed me around the building. My cube is in a somewhat depressing cube farm on the 3rd floor, but everyone was super nice and I decided to work in the community room on the 7th floor where there is a beautiful view of the Bay Bridge and the water. There are couches on the roof, and tables to work at. Lukas and I hung out (we know each other from geekfeminism.org already) and I got to see a lot of great and promising stuff built on top of Bugzilla’s API, just the sort of thing I was hoping to (someday) build to visualize Mozilla’s bug data.

This is more about first impressions and my enjoyment of them than an organization of facts and information and my systems to keep them neat. Those systems, right now, live in my private TiddlyWiki instance, a new lizzardZilla wiki separate for work where I brain dump, then organize everything. I will try to convey actual information later today! But, in short, I am the Bugmaster, and on “The Ateam” and cannot wait to order business cards that say “Bugmaster” on them. Maybe with this picture on the back, shopped with some extra -zillatude to it:

All shall triage bugs with me and despair make awesomeness possible!