Make more apport hooks

[Nigel Babu]

Hello fellow triagers:

Over the past cycles, we've seen that bugs with an apport hook are
easier to triage since most of the required information is collected and
we can easily identify the source of the bug.  Not many people know how
to write a hook though.  Last cycle, I wrote 2 hooks, one for rhythmbox
and one for cheese, and I can say I have a good idea on how to go about
it.  I'd like to share this knowledge with anyone interested.

Most of the time, upstream doesn't know how to write a hook and are
confused as to whom to ask for help.  The idea is to train a bunch of
people to be able to write hooks.  Now, I'd like to open a discussion on
how we go about it.

Option A
We create a wiki page where there would be a table with package name,
bug number, and upstream contact name/irc nick.  Upstream contacts or
Ubuntu developers can open a bug with the information that a hook should
collect and list the bug there with their nickname so we can get in
touch with them if we run into any issues.  Anyone interested can
subscribe to the wiki page and assign the bug to themselves if they're
working on writing the hook.  Once upstream is happy with the
information, package it, and request sponsorship for the bug fix.

Option B
We create a tag like 'apport-hook-request' (or whatever) and we keep
track of all the bugs with that tag.  Anyone who wants can assign the
bug to themselves and work on it. Disadvantage here would be that its
difficult to get a nudge when a new 'apport-hook-request' tag is added,
which might mean more infrastructure to be set up like a team being
subscribed, etc.

Or we could mix both.

Anyone would like to offer comments or suggestions?