ubuntu-bugcontrol team mailing list archive

[∅ <wxl@xxxxxxxxxx>]

> Do you promise to be polite to bug reporters even if they are rude to you or Ubuntu?

Yes, as that's the only way anything's going to get done! Focusing on
common goals (fixing Ubuntu) is always a good approach.

> Have you signed the Ubuntu Code of Conduct?

Indeed:
https://launchpad.net/~wxl/+codesofconduct

> Have you read Bugs/Triage, Bugs/Assignment, Bugs/Status and Bugs/Importance?

Yes.

> Do you have any questions about that documentation?

My only question about improving bug reports is understanding what
apport-collect does. In the even of a failure in debian-installer, for
example, the apport tools are not available and being that it is not
necessarily a crash, it makes it hard to report. What files should we
request?

> What sensitive data should you look for in a private Apport crash report bug before making it public? See Bugs/Triage for more information.

Passwords, keys, codes, server information, etc.

> Is there a particular package or group of packages that you are interested in helping out with?

As one of the Release Managers and Head of Testing for Lubuntu, it is
mainly the packages that make it unique, i.e. mostly those that relate
to LXDE. Currently Lubuntu QA doesn't emphasize bug triage very much
and I'm working to change that. I'd like to be a good citizen of the
Bug Control Team to encourage others to join.

> Please list five or more bug reports which you have triaged and include an explanation of your decisions. Please note that these bugs should be representative of your very best work and they should demonstrate your understanding of the triage process and how to properly handle bugs. For all the bugs in the list, please indicate what importance you would give it and explain the reasoning. Please use urls in your list of bugs.

As I understand it, one can't mark bugs as triaged or set importance
of bugs without first being a member of the Bug Control team. That
being said, it's hard to answer this one.

What I have spent most of my time doing is trying to confirm bugs and
trying to ask for more information and/or remove possible variables. I
will try to give some examples that relate to that:

1. This bug appears to affect debian-installer in daily testing, so I
have confirmed it against other images (including coordinating with
others to confirm other architectures) that use debian-installer over
more than one day. I have also changed the title to reflect its
generality. I also corrected the spelling and grammar in the original
description to make it more clear, especially to non-native English
speakers.
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1380774

2. Guided others to confirm a fix here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1363180

3. Linked an upstream tracker (which didn't work through the normal
means; filed a bug on that) here, as well as updating the description.
This one is interesting in that it is a symptom of a larger problem:
https://bugs.launchpad.net/ubuntu/+source/lxsession/+bug/1376380

4. Clarified what was going on with this bug in the title and
description. Confirmed:
https://bugs.launchpad.net/ubuntu/+source/obconf/+bug/1272834

5. This bug was against an EOL release (I called it Invalid because I
couldn't Won't FIx) but then was explained it is valid in Ubuntu+1. I
called it incomplete and asked a bunch of questions to discover what
the real problem is:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1216788

Thanks for the consideration. Please let me know if you need any
further information. Thank you!

wxl