ubuntu-bugcontrol team mailing list archive

[C de-Avillez <hggdh2@xxxxxxxxxx>]

On Sun, 2 Jun 2013 17:29:44 -0400
Taowa Munene-Tardif <taowa4@xxxxxxxxx> wrote:

>    1. Do you promise to be polite to bug reporters even if they are
> rude to you or Ubuntu? Have you signed the Ubuntu Code of Conduct?
> Yes, yes 2.
> 
>    Have you read Bugs/HowToTriage
> <https://wiki.ubuntu.com/Bugs/HowToTriage>, Bugs/Assignment
> <https://wiki.ubuntu.com/Bugs/Assignment>,
> Bugs/Status<https://wiki.ubuntu.com/Bugs/Status>and Bugs/Importance
> <https://wiki.ubuntu.com/Bugs/Importance>? Do you have any questions
> about that documentation? Yes, no 3.
> 
>    What sensitive data should you look for in a private Apport crash
> report bug before making it public? See
> Bugs/HowToTriage<https://wiki.ubuntu.com/Bugs/HowToTriage>for more
> information.  Passwords, credit card numbers, anything you
>    wouldn't share with a stranger...

And the ubiquitous memory dump -- it can carry all of the above!

>    4. Is there a particular package or group of packages that you are
>    interested in helping out with? Not really
>    5.
> 
>    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.*
> 
> 
> https://bugs.launchpad.net/ubuntu/lucid/+source/linux/+bug/1185990
> It's a security issue & a proposed fix was given HIGH

This is a CVE report, and has a different workflow. We actually should
not touch it.

> 
> https://bugs.launchpad.net/ubuntu/+source/userconfig/+bug/583430
> someone could get locked out of their computer HIGH

So you changed the status for userconfig(Ubuntu) to Confirmed. Why? Did
you reproduce it? Did you follow the bug's comments and understand the
issue?

Whenever we change a bug status or priority we should state *what* are
our reasons to do it.

> 
> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/537970 It was
> confirmed by two others in a other version and was reproducible MEDIUM
> 

Why did you change the status for Cups? The bug is assigned to Tim
(and, as such, Tim should be aware of the current status and what is
this all about). Did you confirm it is still an issue on Saucy and
Lucid?

> 
> https://bugs.launchpad.net/ubuntu/+source/ubuntuone-control-panel/+bug/1082097Request
> not a
> bug. OPINION

You changed the status on a bug that is *not* for Ubuntu. We should
only work on Ubuntu bugs (as triagers), not on upstream packages.

> 
> https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/503779 It's a
> request not a bug. OPINION

Why?

Applicable to all above: whenever we change a bug status or priority,
we should -- no, let me rephrase, MUST -- explain *why*. 

Additionally, I do not see any real triage work from you in the bugs
you show. In *all* of them you *only* changed a task status.

Please have a look at:

 * https://wiki.ubuntu.com/Bugs/HowToTriage/
 * https://wiki.ubuntu.com/BugSquad/KnowledgeBase

Unfortunately, I cannot feel confidence that you do understand
triaging. as such,

-1.

Cheers,

..C..

Attachment: signature.asc
Description: PGP signature