Add SQLite contacts to sheriffing docs
Change-Id: I8ad871b406588f428d88a8cc288aff707f6ee7da Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2600245 Reviewed-by: Adrian Taylor <adetaylor@chromium.org> Reviewed-by: Carlos IL <carlosil@chromium.org> Commit-Queue: Mustafa Emre Acer <meacer@chromium.org> Cr-Commit-Position: refs/heads/master@{#838773}
This commit is contained in:

committed by
Chromium LUCI CQ

parent
3024d7c93d
commit
d16b6fc4bf
@ -192,24 +192,25 @@ assigning it to someone else.
|
||||
A few components have their own triage processes or points of contact who can
|
||||
help.
|
||||
|
||||
* V8 ClusterFuzz bugs can be assigned to the [V8 ClusterFuzz
|
||||
* **V8 ClusterFuzz bugs** can be assigned to the [V8 ClusterFuzz
|
||||
Sheriff](https://rotation.googleplex.com/status?id=5714662985302016) for
|
||||
triage. Note that V8 CHECK failure crashes can have security implications, so
|
||||
don't triage it yourself and instead assign it to V8 ClusterFuzz Sheriff. They
|
||||
can make an informed decision on whether it is a security vulnerability or not
|
||||
and whether it is safe to strip the security tags (**Type=Bug-Security**,
|
||||
**Restrict-View-SecurityTeam**).
|
||||
* V8 non-ClusterFuzz bugs shouldn't be assigned to the V8 ClusterFuzz sheriff.
|
||||
* **V8 non-ClusterFuzz bugs** shouldn't be assigned to the V8 ClusterFuzz sheriff.
|
||||
Instead, Googlers should refer to [the V8 security bug triage instructions](http://go/v8-security-issue-triage-how-to)
|
||||
for lists of component owners.
|
||||
* Skia bugs can be assigned to hcm@chromium.org. Be careful while triaging
|
||||
* **Skia bugs** can be assigned to hcm@chromium.org. Be careful while triaging
|
||||
these! The place where we're crashing isn't necessarily the place where the
|
||||
bug was introduced, so blame may be misleading. Skia fuzzing bugs can be
|
||||
assigned to kjlubick@chromium.org, as Skia is heavily fuzzed on OSS-Fuzz and
|
||||
some issues reported in Chromium are already known or even fixed upstream.
|
||||
* URL spoofing issues, especially related to RTL or IDNs? See
|
||||
* **URL spoofing issues**, especially related to RTL or IDNs? See
|
||||
[go/url-spoofs](http://go/url-spoofs) for a guide to triaging these.
|
||||
|
||||
* **SQLite bugs** can be assigned to huangdarwin@. CC drhsqlite@ for upstream
|
||||
issues.
|
||||
|
||||
Tips for reproducing bugs:
|
||||
|
||||
|
Reference in New Issue
Block a user