Mapping of labels to owners and teamsGoalDeliver Blink bugs in crbug.com to engineers who are responsible for the bug area by adding Blink>Foo components.
Example InstructionsWe don't have a common instruction yet. The below is an example, and you don't need to follow it. Important points are:
Task 1: Handling Component=Blink issues (mandatory, daily)2) Read the issue description and comments and add Blink>Foo component and remove Blink component, if the area/ownership is clear. Otherwise:
Task 2: Reducing/Confirming Component=Blink bugs (mandatory, daily)1) Search for "Component=Blink Needs=Reduction", choose one, and investigate it to identify Blink areas by reading HTML/CSS/JS code and/or making a reduction. 2) Add Blink>Foo components, remove Blink component and Needs-Reduction when confirmed and updated the status accordingly, if needed. Task 3: Handling issues without Component: field (optional)Do the same things as task 1 and task 2 for issues without Component: field. If an issue isn't related to Blink, add appropriate non-Blink components such as Component: UI , Component:Internals .
Task 4: monitor stale P0/P1 security bugs (optional)
Contact |
Blink >