ubuntu-bugcontrol team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

On Wed, Dec 07, 2022 at 10:19:31PM +0800, Andy Chi wrote:
> Hi,

Hi! I'm sorry for the delay in reviewing your application. I lost track
of this with the end of year work and holidays.

> 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, I'll be polite even they are rude to me or Ubuntu. I've signed
> Ubuntu Code of Conduct.
> 
> 2. Have you readBugs/Triage
> <https://wiki.ubuntu.com/Bugs/Triage>,Bugs/Assignment
> <https://wiki.ubuntu.com/Bugs/Assignment>,Bugs/Status
> <https://wiki.ubuntu.com/Bugs/Status>andBugs/Importance
> <https://wiki.ubuntu.com/Bugs/Importance>? Do you have any questions about
> that documentation?
> 
>     Yes, I've read Bugs/Triage
> <https://wiki.ubuntu.com/Bugs/Triage>,Bugs/Assignment
> <https://wiki.ubuntu.com/Bugs/Assignment>,Bugs/Status
> <https://wiki.ubuntu.com/Bugs/Status>andBugs/Importance
> <https://wiki.ubuntu.com/Bugs/Importance>. I don't have any questions about
> it.
> 
> 3. What sensitive data should you look for in a private Apport crash report
> bug before making it public? SeeBugs/Triage
> <https://wiki.ubuntu.com/Bugs/Triage>for more information.
> 
>     Things that look likes bank account numbers, CSS keys, user names,
> server names, etc.
> 
> 4. Is there a particular package or group of packages that you are
> interested in helping out with?
> 
>     I'm interesting in libfprint.
> 
> 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/+source/libfprint/+bug/1990209:
> 
> //Set the bug status to triage since it's a back port from libfprint
> upstream. It's a medium bug because it only impact the user with certain
> fingerprint id.

I agree with the status and importance you'd give to this bug.

> https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1995349:
> 
>     Set the bug status to triage since it also link to a upstream bug and
> waiting the maintainer to fix it. The importance should be high because
> it'll impact all users who use Goodix fingerprint device.

I'm a little confused here because the previous bug you would have given
a Medium importance to but this one you think should be High. I'm okay
with either importance (given the proliferation of fingerprint devices
and expectations around them) but would just like to see some
consistency.

> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998882:
> 
>     It's waiting the reporter to submit patch. The importance is medium
> because it only impact the user who use that specific hardware.

Given that this is about LEDs not working I agree with the importance
here.

> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1998885:
>
>     Patch sent by reporter, but maintainer have not reviewed yet. The
> importance should be medium because it's a new chip from ODM/OEM enablement
> plan, the end user have not use it yet.

Even though users may not have access to the hardware yet I think we
should the importance to what it would be if they did have access to the
hardware. My thought behind this idea is that we aren't great about
updating Importance after initially setting it and that we wouldn't
necessarily know when the hardware is shipping.

> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965080:
> 
>     The importance should be medium because it only affect the user who use
> those laptop. The status is now fix-released since the package released
> already.

I agree with the importance here.

Based on what you've sent in I'm confident in your ability to set bug
status and importance correctly so I've added you to the team.

Cheers,
--
Brian Murray