ubuntu-bugcontrol team mailing list archive

[Andreas Moog <andreas.moog@xxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Null Ack wrote:
> Hi, I'm Nullack and would like please to apply for membership into the
> Bug Control Team. Briefly, I have thirteen years professional
> experience in ICT and have a lifetime interest in computing. I am a
> bug squadder, along with being a hopeful for QA Team and Ubuntu
> membership. I can provide more value in my work on Ubuntu by becoming
> a Bug Control Team member.

I've seen some good triaging work by nullack lately. He is an active
triager and a regular of #ubuntu-bugs where he checks back often to get
opinions of others.

> Example One:
> 
> https://bugs.launchpad.net/network-manager/+bug/258743
> 
> http://bugzilla.gnome.org/show_bug.cgi?id=548114

Please don't confirm you own bugs. It could be a problem specific to
your system and you should therefore see if others experience it too.

> I discovered this bug as part of my work with testing Intrepid. I
> reported the bug, upon later discussing it on IRC with the developer
> Sebastien Bacher, I reported the bug upstream on the gnome bugzilla
> and setup a bug watch on launchpad for it. 

Nice work! Reporting bugs upstream is one of the most important things
to do.

> I am not able to set the
> importance currently due to not being a member of the bug control team
> but I consider the importance to be high because it has a severe
> impact on a small portion of Ubuntu users. The default MTU of 1500
> will work for most network setups but those that require specific MTU
> values have this regression and be non functional.

I agree with the importance here.

> https://bugs.launchpad.net/ubuntu/intrepid/+source/network-manager/+bug/256054
> 
> As part of my involvement in Intrepid as well as upstream on network
> manager I was looking at this bug. I correctly added the source
> package for this problem being network manager 

That's great!

> and setup the bug watch
> to the upstream gnome bugzilla for it. When upstream decided their bug
> was a duplicate of another (which I personally consider to be
> debatable) I swapped the bug watch tracker to the other upstream bug
> so that our launchpad watch status' would correctly show this problem
> to be valid. 

Again, nice work. Not only reporting issues but also see if there is any
change in the upstream bugtrackers is a necessary part of triaging.

> The importance is correctly set at high due to the
> estimated small number of users who would edit the conf file manually
> to set network configuration items.

Agreed.

> Example Three:
> 
> https://bugs.launchpad.net/ubuntu/+source/flashplugin-nonfree/+bug/262693
> 
> Following feedback on Intrepid Firefox problems on the Ubuntu Forums I
> looked at this bug. I was able to identify a testing process to
> consistently replicate the problem on my test machine. 

Nice work!

> Example Four:
> 
> https://bugs.launchpad.net/ubuntu/+source/synaptic/+bug/250524

Again, nice work, although little triaging work was done.

> Example Five:
> 
> https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/243803

There is little triaging work done in this one, too.

> and then confirmed. The importance of this bug is high as it is a
> serious show stopper for a small portion of users involving a non
> intuitive fix for newer users.

Agreed.

> Please consider, thanks

Do you have any more bugs where you've done basic triaging work like
requesting information from submitter, file upstream reports and so on?
- From the bugs you brought as an example here, you reported 3 of them
yourself and did little actual triaging. Nonetheless, your work on the
bugs was great, but personally I would like to see some more triaged bugs.

If you can provide some, it's a +1 by me for your application. Thanks
for all your work.

Regards, Andreas Moog
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkjOmbcACgkQ06FgkPZwicTjrACfd2rE3pwE+RucszdY6iH6lZvS
BLAAoIT7V6Kg76FMRLQPWI1MOJRJtwKj
=WKSB
-----END PGP SIGNATURE-----