ubuntu-bugcontrol team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxx>]

I'd like to give Geir my strong +1 for membership in Bug Control.
He has shown an impressive level of dedication and patience in dealing
with the influx of -intel bugs that we see.

Since we get so many bugs filed against X, a lot of the basic triage
work is automated.  Geir has been instrumental at the more advanced
level that really requires human intervention, patiently helping
frustrated bug reporters through tricky situations to gather the
necessary information, and in numerous cases helping guide the bug
towards a solution.  He has also taken an active role in establishing a
team-wide standardization of tags for X bugs to facilitate finding dupes
(http://wiki.ubuntu.com/X/Tagging).

Bryce

On Sat, May 09, 2009 at 05:19:27PM -0400, Geir Ove Myhr wrote:
> Hi!
> 
> I was encouraged by Bryce Harrington to apply for Bug Control
> membership, so I'm hereby doing that.
> 
> 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 to both.
> 
> 2. Have you read Bugs/HowToTriage, Bugs/Assignment, Bugs/Status and
> Bugs/Importance? Do you have any questions about that documentation?
> 
> Yes. Not really any questions at this point, but a comment:
> On Bugs/Status it says that for Confirmed bugs, "Another reporter has
> experienced the same bug, this can come in the form of a duplicate bug
> or a bug comment". This isn't really followed in the xorg packages,
> and with good reason. Many bugs are triggered by particular monitor
> models or laptop models, and it would be really counter-productive if
> we always had to find someone with the same hardware to confirm a bug.
> Instead, bugs are confirmed once the bug is sufficiently described and
> the necessary attachments are uploaded.
> 
> 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.
> 
> Private information in function calls, etc. I'll make sure to double
> check the first time I do this.
> 
> 4.  Is there a particular package or group of packages that you are
> interested in helping out with?
> 
> Yes, primarily xserver-xorg-video-intel.
> 
> 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.
> 
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/296020
> (already set to High)
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/299007
> (Medium)
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/321401
> (High)
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/336923
> (Medium)
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/353419
> (already set to Medium)
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/355629
> (Low)
> https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/370777
> (High)
> 
> Geir Ove