Bug 206013

Summary:	EWS could be more helpful when a queue is far behind
Product:	WebKit	Reporter:	Alexey Proskuryakov <ap>
Component:	Tools / Tests	Assignee:	Nobody <webkit-unassigned>
Status:	NEW ---
Severity:	Normal	CC:	aakash_jain, darin
Priority:	P2
Version:	Other
Hardware:	Unspecified
OS:	Unspecified

Description Alexey Proskuryakov 2020-01-09 09:55:39 PST

Sometimes we have EWS queues remain waiting for a long time. It helps that we show the position in queue. It's still difficult for a contributor to figure out what to do.

Some ideas:
- show contact info or a button to report an issue;
- link to a bug tracking the issue;
- show how many patches were processed in the last 8 hours (exact time period subject to tweaking), so that it's known whether the issue is already fixed;
- calculate and show an ETA;
- agree on a policy and show it in the bubble (e.g. "we consider it acceptable to ignore an EWS queue if it's not done in 48 hours, see <...> for details").

Comment 1 Darin Adler 2020-01-09 10:33:45 PST

Some thoughts spurred by the ideas above:

I really like the idea of being able to see "queue speed" as well as "queue size" so you can tell apart slow and stuck. Could considering indicating the number of patches processed in 8 hours as a speed (in patches per hour) rather than a count. ETA is also a neat idea along the same lines.

I think it’s valuable that someone who makes a decision for the project (this queue is down and we'll do without it for a while), can make that decision visible to everyone else. I think that could be more valuable than quoting a policy. Generally we could hide any EWS bubbles that don’t currently have valuable data, but be able to show them with a click.