[platform-ui-dev] Triage / GreaseMonkey updates / upgrade

[Eric Moffatt <emoffatt@xxxxxxxxxx>]

While I've been doing triage this cycle
I've been hit with quite a few cases where it's not clear which 'bucket'
to use so Boris asked me to run a couple of brain cells together and see
if I could start a discussion on what (if anything) we could do to increase
the 'hit rate' (i.e. the number of times that I can simply use the script
to format a defect correctly). Perhaps we can talk this over at a future
team meeting.

Some of the issues I see are (feel free
to add your favorites):

General:

The JSON needs updating to remove Kim
as a component owner (if she can arrange to keep committing we can always
assign some back...;-). There are incoming defects that do requrie addressing
and simply putting them into the appropriate (but 'dead') bucket just raises
the probability that they'll slip through the cracks.

We have incoming defects (this round
it seemed to be FilteredTree issues) whose implementor isn't the person
that the most appropriate bucket is assigned to.(in this case Dani is doing
the work but it's in org.eclipse.ui.dialogs, CellEditor bugs are in my
bucket but Tom Schindl has done all the real work there for quite a while).

In general the current 'flat' bucket
list is OK by me. We could likely arrange to group the buckets (i.e. all
IDE buckets in one place) but the resulting advantage would only be incremental
over what we have. I'd thought of using a menu-like structure to show them
but then realized that this may actually make it harder for new folks to
use it since they'd have to memorize which sub-menus contain what 

Given unlimited resources we could likely
do a 'triage wizard' but that seems unlikely given the current resource
load.

The one GUI enhancement I'd love to
see is a tooltip for each button containing the rest of the JSON info.
This would allow the user to see the email address of the assignee and
would also allow for the display of the component area description. Given
that we could also provide a 'Triage Hints' field in the JSON that could
be used to capture the various edge conditions and present them to the
next eprson doing the triage.

Enhancements: 

In order to keep the metrics accurately
reflecting what we're doing we should be much more diligent about marking
defects as enhancements. Maybe an 'Enhancement' button? 

API: 

API changes can be requested against
almost any component but should be reviewed by some set of folks to ensure
consistency... Perhaps we could have an API button that would attach the
members of the API reviewers to the CC list of the bug?

Could any of the tools being worked
on externally (trace analyzers....) help ?

What do you all think?
Eric