The Chrome network team uses a two day bug triage rotation. The goal is to review outstanding issues and keep things moving forward. The rotation is time based rather than objective based. Sheriffs are expected to spend the majority of their two days working on bug triage/investigation.
Look through this list of untriaged bugs.
For each bug try to:
Internals>Networkcomponent if it belongs elsewhere
Needs-Feedbackand request more information if needed.
Please collect and attach a chrome://net-export log. Instructions can be found here: https://chromium.org/for-testers/providing-network-details
Internals>Networkif appropriate. See bug-triage-labels.md for an overview of the components.
Look through this list of Needs=Feedback bugs.
Needs-Feedbacklabel for over a week and the feedback needed to make progress was not yet provided, archive the bug.
Top crashes will already be entered into the bug system by a different process, so will be handled by the triage steps above.
However if you have time to look through lower threshold crashes, see internal: Looking for new crashers
On the final day of your rotation, send a brief summary to firstname.lastname@example.org detailing any interesting or concerning trends. Do not discuss any restricted bugs on the public mailing list.
Your rotation will appear in Google Calendar as two days. You are expected to work on it full-time (as best you can) during those calendar days, during your ordinary working hours.
Google Calendar email@example.com
Owners for the network bug triage rotation can find instructions on generating and modifying shifts here (internal-only).
An overview of bug trends can be seen on Chromium Dashboard
There is also an internal dashboard with bug trends for Web Platform that includes network issues.
The issue tracker doesn't track any official mappings between components and OWNERS. This internal document enumerates the known owners for subcomponents.