Add COMPONENT and TEAM to sensors API OWNERS files

third_party/WebKit/Source/modules/device_orientation/OWNERS

Index: third_party/WebKit/Source/modules/device_orientation/OWNERS
diff --git a/third_party/WebKit/Source/modules/device_orientation/OWNERS b/third_party/WebKit/Source/modules/device_orientation/OWNERS
index f68d5d4216fbd594144cd3ce652f120d5c794403..3cbcc8589624571924b67641196dc15f7711b7de 100644
--- a/third_party/WebKit/Source/modules/device_orientation/OWNERS
+++ b/third_party/WebKit/Source/modules/device_orientation/OWNERS
@@ -1,3 +1,4 @@
 timvolodine@chromium.org
 
-# COMPONENT: IO>DeviceOrientation
+# COMPONENT: Blink>DeviceOrientation

[timvolodine, 2017/03/29 16:39:13]

The (IO|Blink)>DeviceOrientation seems somewhat confusing (or too verbose),
maybe just keep one? (i.e. IO>DeviceOrientation).

[Reilly Grant (use Gerrit), 2017/03/30 22:16:03]

The reason for the IO/Blink separation is that the IO>Foo component captures
bugs in the platform-specific code use for (in this case) accessing sensors
which might be used by multiple components of Chrome, while the Blink>Foo
component captures bugs in the implementation of the Foo web API. I established
this pattern when maintaining //device/usb, the WebUSB API and the chrome.usb
API because it was useful to have separate components for issues that effected
communication with USB devices in general (since this code is consumed in a
number of places) compared to issues in a particular developer-facing API.

Since Generic Sensors is adding a number of new sensor types would you support
renaming the existing IO>DeviceOrientation and Blink>DeviceOrientation
components to IO>Sensors and Blink>Sensors? If you don't think that the
separation described above makes sense for sensors then we can merge IO>Sensors
into Blink>Sensors, which would cover all web platform sensor APIs.

+# TEAM: sensors-dev@chromium.org