RE: [Fwd: Accessibility bugs status]

[Murray Cumming Comneon com]

> From: Calum Benson [mailto:calum benson sun com] 
> > The accessibility team might also consider adding an 
> (accessibility) column
> > here, or generating a similar report:
> > http://bugzilla.gnome.org/gnome-22-report.html
> 
> Would be happy to try and generate one if I knew how, but don't have
> read access on the perl scripts on widget that presumably 
> generate it...
> can somebody point me at them?[1]  Or could one of the bugmeisters add
> the necessary reports to this page for us?

Aldug (Alex Duggan, CCed) put the latest iteration of this together, but I
think it's quite simple. I _think_ this is the script, in the bugzilla
module in gnome's cvs:
http://cvs.gnome.org/lxr/source/bugzilla/gnome-report.cgi#184
(I've linked directly to a relevant part)

I'm CCing bugsquad, because it's generally more responsive than bugmaster.

>  (Note: the 
> prioritisation of
> the a11y bugs isn't quite as simple as it is for the other
> currently-listed modules though, it involves querying the
> status_whiteboard for some modules and not for others, and other
> exciting stuff like that).

Yes, but I think it _might_ still be useful. Hopefully the priorities don't
differ that much. If there's one or two that need special mention then they
can be mentioned in emails. I can't think of a perfect solution for this but
I do think we need some kind of system that keeps working without too much
manual intervention.

> In the meantime, I'm happy to mail out weekly reminders with a link to
> the manually-produced page.

Cheers. I think it's worth a try.

Murray Cumming
murrayc usa net
www.murrayc.com