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.
The goal is for this query to be empty. Bugs can be removed from the triage queue by doing any of the following:
Internals>Network
component or subcomponent.Network-Triaged
(when there are multiple components).For each bug try to:
Internals>Network
component or subcomponent if it belongs
elsewhereWontFix
.Type-Bug-Security
.Privacy
.Task
or Feature
when it is not a bug.Needs-Feedback
and request more information if needed.Network-Triaged
label to the bug, and add a comment explaining which team
should triage further. Adding the Network-Triaged
serves to filter the
bug from our untriaged bug list.Available
with Priority 3.Needs-Feedback
labelchrome://net-export
and the
NetLog Viewer.Request a NetLog that captures the problem. You can paste this on the bug:
Please collect and attach a chrome://net-export log.
Instructions can be found here:
https://chromium.org/for-testers/providing-network-details
If a NetLog was provided, try to spend a bit of time reviewing it. See crash-course-in-net-internals.md for an introduction.
Move to a subcomponent of Internals>Network
if appropriate. See
bug-triage-labels.md for an overview of the components.
If the bug is a crash, see internal: Dealing with a crash ID and internal: Investigating crashers
Look through this list of Needs=Feedback bugs.
Needs-Feedback
label for over 30 days, and the
feedback needed to make progress was not yet provided, archive the bug.Look through the list of unowned high priority bugs. These bugs should either have an owner, or be downgraded to a lower priority.
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 net-dev@chromium.org detailing any interesting or concerning trends. Do not discuss any restricted bugs on the public mailing list.
Not all of the subcomponents of Interals>Network
are handled by this rotation.
The ones that are included are:
Internals>Network
Internals>Network>Auth
Internals>Network>Cache
Internals>Network>DNS
Internals>Network>Connectivity
Internals>Network>DomainSecurityPolicy
Internals>Network>FTP
Internals>Network>HTTP2
Internals>Network>Library
Internals>Network>Logging
Internals>Network>Proxy
Internals>Network>QUIC
Internals>Network>SSL
The rest of the Internals>Network
subcomponents are out of scope,
and covered by separate rotations:
Internals>Network>Certificate
Internals>Network>CertTrans
Internals>Network>Cookies
Internals>Network>DataProxy
Internals>Network>DataUse
Internals>Network>DoH
Internals>Network>EV
Internals>Network>NetInfo
Internals>Network>NetworkQuality
Internals>Network>ReportingAndNEL
Internals>Network>TrustTokens
Internals>Network>VPN
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 google.com_52n2p39ad82hah9v7j26vek830@group.calendar.google.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.