Issue metadata
Sign in to add a comment
|
[Component Request] UI>Internationalization>RTL |
||||||||||||||||||||||
Issue description1] Component Name: UI>Internationalization>RTL 2] Parent Component (e.g. Blink, UI>Browser, etc...): UI>Internationalization Note: We generally avoid creating new component namespaces, unless there is a new hierarchy that needs to be expressed. Please try and use existing components as parents. 3] Description of Component: Right-to-Left (RTL) UI issues 4] Admin/ Owner: ? No one is owner of UI>Internationalization 5] Please specify what triage practices will be followed for the component N/A There are currently 414 open UI>Internationalization bugs, 92 of which refer to "RTL". There are also 340 bugs containing "RTL". I have interacted with a bunch of these bugs, and a UI>Internationalization>RTL would always feel appropriate, whereas UI>Internationalization feels too broad.
,
Feb 11 2017
Created the component, although I'm a little concerned that we don't have any ownership for these issues. +Justin and Rachel to help figure out how to make this an owned component.
,
Feb 11 2017
Moving this out of the component request area, since that's done and it's now more of a business question of who looks after this set of issues.
,
Feb 13 2017
I really don't think we can make this an owned component. RTL in WebUI is nothing like RTL in Views is nothing like RTL in iOS. There's overlap, but not enough. RTL would be a fine *label* to apply to anything in the UI> family. (I actually think the same thing about UI>Internationalization) As far as I'm concerned, Components are functional areas of responsibility, labels are crosscutting concerns. (I.e. if there's no clear owner and it applies to multiple components, it should be a label)
,
Feb 13 2017
I agree with #4. This makes more sense as a label. +lgarron, thoughts?
,
Feb 13 2017
I think our label management (+discovery) is a mess, and we're not particularly diligent about components. That said, I can manage with either, since I will personally know the outcome of this discussion. 🤷
,
Feb 23 2017
Well, we certainly won't make it less of a mess by ignoring the conventions. (https://www.chromium.org/issue-tracking/requesting-a-component-or-label) Over to laforge - please remove this component and create a label instead. Sorry for the confusion.
,
Feb 23 2017
Holist-RTL work for everyone?
,
Apr 20 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by lgar...@chromium.org
, Feb 9 2017