ubuntu-bugcontrol team mailing list archive

[Daniel Manrique <daniel.manrique@xxxxxxxxxxxxx>]

Hi Matt!

On 12-02-17 12:33 PM, Matt Fischer wrote:
> Hi bug-control:
> 
> 
> I've been a member of the bugsquad for a few months now. You've probably seen me
> in the
> IRC channel (mfisch) asking clarifying questions about the process (and updating
> the wiki some when I find the answer). I work on bugs for my day job at
> Canonical, but
> I want to join bug control to improve Ubuntu in general and help get bugs
> unstuck when they
> are in the wrong project, missing information, or are no longer applicable. When
> possible, I
> also intend on fixing some of the bugs via patches or merge proposals.
> 
> 
> * 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 will be polite to bug reporters. Since anyone filing a bug is dealing
> with frustration and is perhaps upset, this is critical. I have signed the code
> of conduct.
> 
> * Have you read the bug process wiki docs?
> 
> I have read the wiki pages. After working through the process over the past few
> months, I feel that I don't have any additional questions. The pages are still a
> valuable reference and I have subscribed to the pages so I can see any changes
> in the process that come up.
> 
> * What sensitive data should you look for in a private Apport crash report bug
> before making it public?
> 
> Private bugs should never be marked public if they contain a coredump file.
> Additionally, traces and other attachments should be checked for sensitive
> information (SSNs/passwords/etc). My day job at Canonical is focused primarily
> on private bugs, so I feel
> I have a good handle on this process and the concerns about public vs private bugs.
> 
> 
> * Is there a particular package or group of packages that you are interested in
> helping out with? 
> 
> I started looking at gnome-nettools, mainly because I ran into a bug on my
> system and wanted to learn GTK programming. I spent some time cleaning up the
> bug list since that project gets quite a few "my wifi doesn't work" type bugs. I
> also worked on patches/merge proposals for the 4 issues that were giving me
> issues with the package. Since that package does not require anywhere near my
> full attention, I also like to look any any untriaged bugs or bugs missing a
> project.
> 
> * Please list 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. 
> 
> 
> gnome-nettools:
> 
> In gnome-nettools, I took on the 5 bugs that I was seeing, confirmed them, took
> ownership, wrote a patch and a merge proposal in one instance, sent the patches
> upstream to the developer. I've also spent a lot of time marking duplicates in
> the project and fixing spellings/wording in bug headers. I discussed some of
> these bugs with Pedro Villavecencio (pvillavi) as this was when I was first
> ramping up on the process.

I notice a few of these have no importance set (e.g.
https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/891852). Did you
ask for someone to set the importance on #ubuntu-bugs? I'm just curious about
this, it's no big deal really.

> 
> Marked lots and lots of duplicates and then sent a patch upstream (see upstream
> link below):
> https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/806606
> 
> Patches for multiple bugs pushed upstream and accepted by the developer:
> https://bugzilla.gnome.org/show_bug.cgi?id=654117
> 
> Patched in precise with a merge proposal from me:
> https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/661753

You didn't triage this one per se, just fixed it :)

> 
> The bugs I worked in this package that have no status:
> This one should be low because it's an incorrect tool-tip and therefore fairly
> innocuous:
> https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/841007
> 
> This one should also be low because it is a layout issue, but the program is
> still usable. There are also some good notes in this one:
> https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/891852
> 
> I hope to pull the latest version of gnome-nettools and get it into precise when
> I have time.
> 
> Misc bugs:
> 
> - I found a very old bug with no home and it sounded serious. After confirming
> it, I worked to find an owner (skaet) We discussed the issue on IRC and she is
> now working the bug:
> https://bugs.launchpad.net/ubuntu/+bug/468778
> 
> - After extensive research, I found that the "no beep on ping" bug was a
> duplicate of a larger issue. My notes are at the bottom of this bug:
> https://bugs.launchpad.net/ubuntu/+source/gnome-nettool/+bug/188617
> 
> - In this bug, I investigated and confirmed the issue, then sent it upstream by
> filing a debian bug and discussed with the debian owner via email. I'd mark this
> bug a medium because gworldclock is a non-core application.
> https://bugs.launchpad.net/ubuntu/+source/gworldclock/+bug/800027
> 
> I have more examples if you need them, some of which are linked off my wiki page:
> https://wiki.ubuntu.com/MattFischer
> 
> 
> Thanks for your time,
> 
> Matthew Fischer

I've always been impressed by mfisch's thoroughness, but it's more evident
looking at these bug reports.

+1 from me.

Thanks for applying!


> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~ubuntu-bugcontrol
> Post to     : ubuntu-bugcontrol@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-bugcontrol
> More help   : https://help.launchpad.net/ListHelp