Make more apport hooks

[Sense Hofstede]

On 19 May 2010 18:44, markus korn <thekorn at gmx.de> wrote:
> On Wed, May 19, 2010 at 5:39 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?
>>
>
> Hey,
> I think the best idea would be to create a project called
> "ubuntu-bugpatterns", and make the bugsquad its contact.
> This way we can use the full power of launchpad to organize our
> efforts, like we get this nice bug views to show us the state of
> pending hooks, we can discuss hooks in bugreports. We can even move
> the branch to the project and use code review features etc.
>
> And if we are happy with a hook, we just open a task for the ubuntu
> package to track the progress of adding this hook the the related
> package.
>
> Markus
>
I'm against the use of yet another Launchpad project; not only would
it provide _another_ place where bugs can get lost, it would also
require more work to maintain; more work than I think is necessary.
Why can't we use the 'ubuntu' project? The bugs would only be used for
discussing Apport hooks, so there is no need to take that discussion
to a separate project, or maintain its status elsewhere.

Adding a tag is very easy and it allows you to maintain an overview
and get bug views, just as a project would.

-- 
Sense Hofstede
[ˈsɛn.sə ˈɦɔf.steː.də]