ubuntu-bugcontrol team mailing list archive

["Null Ack" <nullack@xxxxxxxxx>]

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 am an Ubentero and have signed the Ubuntu Code of Conduct. I
currently have 1126 karma points. I have studied the bug squad
knowledge base, read the triage, importance, status and assignment
details as well as discussing potential process improvement topics in
the context of the QA Team. I have asked questions on IRC in the past
to clarify items I was unsure about. I treat personal privacy of our
users as a serious issue and am familiar with how to look through the
apport dumps such as stacktrace.txt for any personal information.

I'm generally interested in just about all aspects of Ubuntu. I have
particular personal interests in digital multimedia but I have a
sincere desire to see all of Ubuntu reach the highest levels of
quality. Since it is the weekend I am not able to ask Sebastien Bacher
if he would vouch for me, but I certainly have gotten positive
feedback from him about my bug and testing work on Ubuntu.

I have provided five examples below that shows some examples of my work.

Example One:

https://bugs.launchpad.net/network-manager/+bug/258743

http://bugzilla.gnome.org/show_bug.cgi?id=548114

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. 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.

Example Two:

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 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. 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.

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. I was also able
to confirm that the error occured under multiple video driver
configurations. When it became evident that the problem could not be
replicated on all Intrepid builds I worked with the developer
Alexander Sack on IRC to understand the root cause. The root cause was
identified by him, helped by my details on what was happening and then
me doing unit tests with the developer to confirm the fix. The fix is
to reinstall the package due to the way Intrepid packages were
installed in the past, which is why new installs could not replicate
the problem. I posted the workaround, noting that the dev would
trigger the fix later but the work around could be implemented now by
users who wanted it. The importance was correctly set to high as a
small number of people using Intrepid for sometime had the problem
which broke the web flash experience, and the majority of users on new
Intrepid builds did not.

Example Four:

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

There was some negative feedback coming from users testing Intrepid
about the synaptic quick search being disabled by default. I
identified the bug in question by searching launchpad, read the
comments and verified the situation on my test machine. I contacted
the developer responsible on IRC about this initially reported his
intentions in the bug comments to inform the users that this was being
worked on and what the situation was. Some days later when the
developer had fixed it, I watched the build farm build the change and
on success moved the status to fix released. I also added that my own
tests demonstrated the issue to be fixed on a daily ISO build I tested
it with. I was careful to only move the Ubuntu portion of the bug as I
was not involved with the Xubuntu side of the issue.

Example Five:

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

I encountered a serious bug with Intrepid's Alpha 1 where it would
failt to install grub correctly on my system. I reported the bug
including details for how to workaround the problem in the interim
before a developer could fix the code. I included logs, but due to
what was then an unknown problem with alpha 1's file roller the
compressed archive became corrupted. I attempted to fix the archive
problem to get the report ready for triaging when I became aware of it
but unfortunately my backup of the logs was lost amongst machines.
I've included this an example as I think it shows an element of my
character where I fessed up about the mistake and I apologized for it
- were all human and I think this is important to recognise mistakes.
To properly follow through on the bug I appealed to other testers to
provide the needed logs (as my testing hardware that has this bug was
no longer available to me), which was in fact done by another tester
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.

Please consider, thanks

Nullack