← Back to team overview

ubuntu-bugcontrol team mailing list archive

Re: Application for becoming a member of Bug-Control

 

On Wed, 2008-08-20 at 16:13 +0200, Andreas Moog wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Hi!
> 
> My Name is Andreas Moog, Nick Ampelbein on freenode. I'm 29 yrs old and
> would like to apply as a member of Ubuntu Bug-Control. I read all the
> available documentation on triaging bugs and already signed the Code of
> Conduct. Now for the Application as listed on the Wiki:
> 
> > 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 and Yes. Since my day-job is in IT-Support, I'm familiar with
> rudeness and impoliteness from others and I manage to stay calm and polite.
> 
> > 2. Have you read Bugs/HowToTriage, Bugs/Assignment, Bugs/Status and
> > Bugs/Importance? Do you have any questions about that documentation?
> 
> Yes, I Read that and currently I have no Questions about them.
> 
> > 3. What sensitive data should you look for in a private Apport crash
> > report bug before making it public? See Bugs/HowToTriage for more
> > information.
> 
> I should check for things like passwords, account-numbers/-names. Simply
> anything that is not designed to be public knowledge.

Also, please do not forget coredumps.

> 
> > 4. Is there a particular package or group of packages that you are
> > interested in helping out with?
> 
> I mostly go the list of bugs down and don't have a preferred package.
> But I would be very interested in helping with xorg and mozilla-packages.
> 
> > 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.
> 
> Ok, here we go:
> 
> 1. https://bugs.launchpad.net/ubuntu/+source/libxslt/+bug/85439
> 	I would rate this bug with Low importance since it has only a 		
> 	moderate impact on a non-core package
> 
Nice work.

> 2. https://bugs.launchpad.net/xserver-xorg-video-intel/+bug/256820
> 	This bug would get High importance since it has a severe Impact
> 	on users with the same graphics-card.
> 
> 3.https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-savage/+bug/255826
> 	This one has already a priority set. I gathered the Information
> 	and forwarded it Upstream.

Nice work. The fact that priority was already set does not mean it
cannot be adjusted, if needed.
> 
> 4. https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/256679
> 	In this bug, all information was ready, so I filed it Upstream
> 	and linked to it.

Nice work.

> 
> 5.https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/154643
> 	This one I would rate with Medium-Priority. Though it seems that 	for
> now it only a cosmetic issue, the user can't tell the
> 	difference when his RAM is actually flawed.

Not sure I follow the reasoning, but at least there might be a chance
for someone with more knowledge of how ECC is worked to look at it.

> 
> 6.https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/155840
> 	This would be rated Low. It's a cosmetic issue that can easily
> 	be worked around.
Valid. Although the interface has been changed, a decision by a
maintainer is needed (although I personally would mark it WONTFIX).

> 
> 7. https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/227819
> 	This one would also be rated Low because the issue does not seem
> 	to harm the function.
> 
Agree.

> There are some more bugs which I either confirmed, invalidated or
> reported upstream. If you need to know anything more, I'll be happy to
> give you what you want. Thanks for reviewing my application.

I have interacted with Andreas on #ubuntu-bugs, and have observed his
behaviour there. It is my opinion that his work is good, and I approve
his application.

..hggdh..

Attachment: signature.asc
Description: This is a digitally signed message part


References