Make more apport hooks

[Rohan Garg]

Hey Nigel
I think option A is better as it gives us a wider scope covering more
people,also more people can contribute to the wiki and improve the
quality.Whereas option B  just concerns people who actually know how to
write a apport hook.
But thats just my 2 cents.

Regards
Rohan Garg
www.launchpad.net/~rohangarg


On Wed, May 19, 2010 at 9:09 PM, Nigel Babu <nigelbabu at ubuntu.com> wrote:

> 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?
>
>
> --
> Ubuntu-bugsquad mailing list
> Ubuntu-bugsquad at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-bugsquad/attachments/20100519/2f0c9e7c/attachment.html>