[ubuntu-x] Minutes from today's meeting

[Bryce Harrington]

Summary from today's meeting on #ubuntu-x.

Divided out the tasks for triaging bug reports and sending them
upstream.  See https://wiki.ubuntu.com/X/Projects for details.

Also, here's a graph (updated hourly) for tracking X bug triaging
status for lucid:
http://bryceharrington.org/X/Reports/ubuntu-x-swat/totals-lucid.svg

Our goal is to drive the above graph down to zero.

Pitti is going to focus on -evdev bugs, RAOF will cover xorg-server,
-nouveau and -intel, tseliot will hammer on -nvidia and -synaptics, and
I'll cover -ati.  I will share some sample scripts with tseliot that
might help in doing some auto-triaging of the -nvidia bugs.  I'm going
to be the point person for the X side of the work for multitouch, and
other misc tasks not already covered.  We have some merges pending,
which tjaalton thinks will be a cinch for him to take care of.  Sarvatt
volunteered to look into how we can override video settings when KMS is
in use, and to skim through other distro X stacks for patches we ought
to look at.  Sarvatt's also currently helping with some of the -nvidia
triaging.  Jpetersen will primarily help offload some UNE work since
he's got experience in clutter that will be relevant, and beyond that
will assist with -intel triage work.  Geir has been investigating the
-intel X freezes and will continue helping there; we may have some false
positives and perhaps our tools could be better honed to reduce these
false positives.  He will be posting an email to this list when he's
gathered his next set of recommendations for tool improvements.

We didn't get a volunteer for doing -wacom triaging.  Most of the bug
reports are old though, and there's not really that many of them.  If I
have time I'll at least do a bug spam to get reporters to re-test with
latest bits.  Beyond that, if anyone would like to own -wacom triaging
let me know.

In terms of particular problem areas, Sarvatt shared a list of issues in
general at http://sarvatt.com/downloads/issues.txt - we discussed a few
of them but this list deserves further study.  RAOF has looked a bit
into getting ways in place to force failsafeX on when there's problems.
I think this is important; the move to KMS has rendered several of our
traditional debugging techniques no longer feasible, so the more hooks
we can add to enable users to get into debugging modes the better. I
will draft an email with further thoughts on this topic and send it here
and to the kernel list.  There are also some little polish things, like
making the apport hook not show glxinfo crashes when GLX is broken, and
doing something to quell some of the (innocuous?) error messages about
input devices that we're seeing in Xorg.0.log's lately.

To anyone else wishing to participate in X bug troubleshooting - great!
There is a tutorial at https://wiki.ubuntu.com/X/Triaging about how we
triage bugs for X.org, and tons more info at https://wiki.ubuntu.com/X/
and don't be shy about asking questions here.

Bryce