1] Component Name: VR

Guideline 1 (Clarity): VR is descriptive, and the enclosing Internals namespace indicates its scope.

Guideline 2 (Permanence): VR is a permanent feature/functionality.

Guideline 3 (Specific): The use is independent of any specific project, platform, milestone, or API.

Guideline 4 (Discoverable/ Predictable): "VR" is easily searchable.

The other VR-related components are Blink>WebVR and UI>Browser>VR. WebVR is clearly in the right place. We could consider moving "Browser" under this new "VR" component, but it is also fine where it is.

It would be nice of Monorail would also auto-complete "WebVR" when typing "VR".

In the future, we could add new sub-components, such as "Device", under this "VR" component.

2] Parent Component (e.g. Blink, UI>Browser, etc...): Internals

3] Description of Component: Internal VR-related functionality, such as infrastructure and VR device SDK usage.

4] Admin/ Owner: ddorwin, vollick

5] Please specify what triage practices will be followed for the component
The VR team will triage this component. Triage occurs as new issues are filed and periodically as we review priorities. This new component will improve our ability to triage and maintain the existing two components.



 

1] Component Name: VR

Guideline 1 (Clarity): VR is descriptive, and the enclosing Internals namespace indicates its scope.

Guideline 2 (Permanence): VR is a permanent feature/functionality.

Guideline 3 (Specific): The use is independent of any specific project, platform, milestone, or API.

Guideline 4 (Discoverable/ Predictable): "VR" is easily searchable.

The other VR-related components are Blink>WebVR and UI>Browser>VR. WebVR is clearly in the right place. We could consider moving "Browser" under this new "VR" component, but it is also fine where it is.

It would be nice of Monorail would also auto-complete "WebVR" when typing "VR".

In the future, we could add new sub-components, such as "Device", under this "VR" component.

2] Parent Component (e.g. Blink, UI>Browser, etc...): Internals

3] Description of Component: Internal Virtual Reality-related functionality, such as infrastructure and VR device SDK usage.

4] Admin/ Owner: ddorwin, vollick

5] Please specify what triage practices will be followed for the component
The VR team will triage this component. Triage occurs as new issues are filed and periodically as we review priorities. This new component will improve our ability to triage and maintain the existing two components.