Help with filing issues for browser engines for a given spec change

[zcorpan]

From https://docs.google.com/document/d/1YiFR8tYoE1PZYlZJaCqcFW000UroxfAjmzCkyqGS7Ko/edit?usp=sharing

Help with filing issues for browser engines and other projects for a given spec change/wpt PR.

• Typically copy/paste between bug trackers with links to the spec change and wpt PR.
• Could be different levels of automated:
  • no automation (now)
  • having a web UI to file a bug once
  • having a bot figure out which browsers/projects are affected (new failing tests), and file the bugs
• Benefits:
  • Tedious and error prone when done manually.
  • Helps consistently file bugs to all vendors.

Example: whatwg/html#4830 ("Implementation bugs are filed:")

[zcorpan]

The next idea in that doc is related, or would build on top:

Help maintaining a comment that tracks the status of bugs.

• Example: Track PR #364 whatwg/webidl#376
• Next to each link, show a badge with the status (NEW, FIXED...)
• Benefits:
  • Easier to keep an eye on status of issues.
  • Helps vendors see how others are handling the issue.
  • Helps show progress and impact.

[zcorpan]

Mockup for how the UI could be: https://jsfiddle.net/khq7mezy/

[marcoscaceres]

Don't have anything useful to add... but this would be amazing.

[plehegar]

not sure where this is intended for. Is it for a GH issue template available for all spec repos? An online service somewhere on w3.org? A script to be added for all documents in /TR?

[zcorpan]

Is it for a GH issue template available for all spec repos?

No.

An online service somewhere on w3.org?

For "having a web UI to file a bug once", yes, but doesn't need to be on w3.org.

A script to be added for all documents in /TR?

No.