ubuntu-bugcontrol team mailing list archive

[Brian Murray <brian@xxxxxxxxxx>]

On Wed, Jun 10, 2009 at 07:44:42PM -0400, Scott Howard wrote:
> Hello,
> 
> Attached is my application for bug control. I've been mentored by Pedro
> Villavicencio, and have been working on bug days, random bugs, and
> gnome-power-manager bugs since the end of April. Thank you for
> consideration.
> LP: showard314
> IRC: showard
> 
> 
>    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?
> 
>    I promise to be polite to reporters. Politeness encourages participation
>    and gives people a good impression of the Ubuntu community and can only make
>    the distribution better, even if reporters have been rude. I have signed the
>    CoC.
> 
>    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, I have read them all. I don't have any questions now, I've been
>    discussing them with Pedro and #ubuntu-bugs.
> 
>    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.
> 
>    The traces from Apport can contain passwords, credit card info, serial
>    numbers, etc. Bug Control has to protect users by removing such information
>    from traces.
> 
>    4.
> 
>    Is there a particular package or group of packages that you are
>    interested in helping out with?
> 
>    I'm a laptop user, and have been working with gnome-power-manager, acpi,
>    and other power/laptop related packages. I'm also interested in "science"
>    packages (I have a PhD in electrical engineering and am a researcher in
>    applied physics).
> 
>    5.
> 
>    Please list of five or more bugs which you have triaged. These bugs
>    should demonstrate your understanding of the triage process and how to
>    properly handle bugs. If there is a bug in your list that does not have an
>    importance indicate what importance you would give it after becoming a
>    member of Ubuntu Bug Control. Please use urls in your list of bugs.
> 
> 
> Here's a collection of bugs that covers many aspects of bug control
> 
> 1) https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/375260
> Requested logs and debugged the problem, found a similar bug on mandriva:
> https://qa.mandriva.com/show_bug.cgi?id=50087
> through the logs found the bug through hal to acpi, found a duplicate report
> on:
> http://bugzilla.kernel.org/show_bug.cgi?id=12641
> and:
> https://bugs.launchpad.net/ubuntu/+source/hal/+bug/213128
> I posted information about the LP work on the linux bug report and linked
> the upstream linux report on launchpad.
> IMPORTANCE: LOW (already assigned)

This looks great to me.  Linking bug reports between bug trackers is
very valuable and benefits everyone.  Looking at the comments in bug
213128 it seems that someone may be having problems with their laptop
auto suspending due to this bug report.  If that is in fact the case I'd
recommend the bug have an importance of high.
 
> 2) Closed an old incomplete bug, when it was reopened I confirmed the bug
> (with the supporting info), found that the bug had already been reported
> with OOO and linked the upstream report.
> https://bugs.launchpad.net/ubuntu/+source/openoffice.org-hyphenation/+bug/105879
> IMPORTANCE: WISHLIST (already assigned)

This also looks great to me, thanks for finding the relevant upstream
bug report.  An importance of wishlist seems appropriate to me.
 
> 3) While I didn't post in the ubuntu report, detective work and
> communication with redhat and debian fixed the bug:
> https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/357556
> I found the fix in:
> https://bugzilla.redhat.com/show_bug.cgi?id=481146
> and reported the fix from redhat to the debian bug report at:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505379
> IMPORTANCE: MEDIUM (already assigned apport crash)

Again this is great work!  Thanks for finding the related bug reports.
Medium is the correct importance for this bug.
 
> 4) Helped reported file a complete report, then filed an upstream bugreport:
> https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/377576
> http://bugzilla.gnome.org/show_bug.cgi?id=582984
> IMPORTANCE: WISHLIST

Thanks for filing this upstream in the Gnome bug tracker this is quite
helpful.  I agree with the importance of wishlist.
 
> 5) https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/368681,
> helped reporter make an apport crash report which is posted here:
> https://bugs.launchpad.net/ubuntu/+source/openoffice.org/+bug/378601
> IMPORTANCE: LOW (although it is a crasher, it has not been able to be
> reproduced by anyone other than the reporter)

Getting the reporter to report the crash using apport was great.  An
importance of Low seems appropriate since they are the only one able to
recreate it.
 
> 6) https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/363326
> Assigned packages, removed incorrectly subscribed team,
> troubleshoot/triaged, found the bug was already reported as "will not fix"
> in linux (http://bugzilla.kernel.org/show_bug.cgi?id=12015), linked upstream
> report
> IMPORTANCE: MEDIUM (brightness control is a problem with a non-essential
> hardware component) but would list as "WILL NOT FIX" once I saw the linux
> upstream report.

This looks pretty good, however I might have included the workaround
that was reported upstream so the reporter and other Launchpad users
have everything they need in the bug report on Launchpad.  Won't Fix
does seem like the best status for this bug report.
 
> 6) Closed a bug that was caused by a misbehaving script, and encouraged
> someone posting with a different bug to file a new bug report
> https://bugs.edge.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/344989
> IMPORTANCE: LOW (already assigned)

This looks good to me.  Incidentally, as of Jaunty there is now an
apport package hook for gnome-power-manager which should make reporting,
via 'ubuntu-bug gnome-power-manager', high quality bugs much easier.  In
the event that this was a legitimate bug report an importance of High or
Medium would have been appropriate.
 
> 7)
> https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-180/+bug/371391,
> requested logs, found what was wrong from the log, and pointed to a
> potential fix.
> IMPORTANCE: LOW

This looks great to me also.  Thanks for including such detailed
information in your comments it makes thing easier for everyone.

Based on my review of your application and Pedro's positive endorsement
of your work I am happy to approve your membership in the bug control
team.  Thanks again for helping out and welcome to the team!

Sincerely,
-- 
Brian Murray                                                 @ubuntu.com

Attachment: signature.asc
Description: Digital signature