RE: [Fwd: Accessibility bugs status]

[Calum Benson <calum benson sun com>]

On Wed, 2003-04-23 at 23:47, Alex Duggan wrote:
> Hi Calum,
> 
> What keywords would specify bugs that should be displayed in the a11y
> column?

Well, it's all a bit complicated :)  The simple answer to your question
is "anything with the accessibility or keynav keyword", but as I
mentioned before, it's the priorities that get a bit sticky.

Up to now, we've been using the semi-manually produced table at
http://developer.gnome.org/projects/gap/tech-docs/access-bugs.html , so
ideally we'd like something that breaks down the report into similar
categories. 

Basically we use two priority schemes, depending on the module:

* bugzilla priority : for modules we have direct control over, we just
set the priority in bugzilla.

* whiteboard priority : for modules that someone else maintains, we add
AP0 (immediate), AP1 (critical), AP2 (high), AP3 (normal) or AP4 (low)
to the status_whiteboard field.

I've mocked up a possible 'ideal' report page (HTML blatantly copied and
pasted from  the existing ones) at
http://www.gnome.org/~calum/gnome-a11y-report.html ... here's what's in
each of the tables.

Totals: 
This one is easy enough, it's everything added up from the three tables
below. (The count of 'untriaged' bugs at the bottom of the page isn't
included in these totals).

Accessible Technologies:
All the open bugs against GOK, Gnopernicus, and the Keyboard
Accessibility capplet, broken down by category.  Bugzilla Priorities are
used for GOK and Gnopernicus.  Whiteboard priorities are used for the
Keyboard Accessibility Capplet... that is, bugs in the KAC's Urgent
column are those that have AP1 in their whiteboard field, regardless of
their actual bugzilla priority, and so on for the other priorities.

Accessibility Infrastructure:
All open bugs against atk, at-spi, gnome-speech and gnome-mag, broken
down by category.  Bugzilla priorities are used for all these.

Theming, Keynav, and Other - Triaged:
All open bugs against any other module that have either the keynav or
accessibility keyword set, AND have a whiteboard priority.  That is,
bugs in the Urgent column are those that have AP1 in their whiteboard
field, regardless of their actual bugzilla priority, and so on for the
other priorities. Only broken down to the product level this time, I
don't think we need anything more granular than that for these ones.

Theming, Keynav, and Other - Untriaged:
All open bugs against any other module that have either the keynav or
accessibility keyword set, and have NO whiteboard priority.  Therefore
bugs are shown in this table by their actual bugzilla priorities.  Only
broken down to the product level again.  (This table might not actually
be necessary at all, it's just handy for getting at lists of bugs that
we might have overlooked in the a11y triage process.)

Preferably, in each table, rows are only shown if the bug count in that
row is non-zero.

So there you have it... anyone got nothing better to do this weekend
with a desperate urge to help us out? :o) 

Cheeri,
Calum.

-- 
CALUM BENSON, Usability Engineer       Sun Microsystems Ireland
mailto:calum benson sun com            GNOME Desktop Group
http://ie.sun.com                      +353 1 819 9771

Any opinions are personal and not necessarily those of Sun Microsystems