device/bluetooth/OWNERS: Add set noparent.

device/bluetooth/OWNERS: Add set noparent.

BUG=none
R=keybuk@chromium.org

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=265784

[keybuk, 2014-04-24 00:03:25]

lgtm

[armansito, 2014-04-24 00:11:59]

Committed patchset #1 manually as r265784 (presubmit successful).

[Nico, 2015-07-26 03:19:22]

thakis@chromium.org changed reviewers:
+ thakis@chromium.org

[Nico, 2015-07-26 03:19:22]

owner files should generally not have noparent. why is this needed?

[AzoozAlmalki84, 2015-07-26 07:48:31]

On 2015/07/26 03:19:22, Nico (vacation Mon Jul 27) wrote:
> owner files should generally not have noparent. why is this needed?

[Nico, 2015-07-28 19:59:26]

On 2015/07/26 03:19:22, Nico wrote:
> owner files should generally not have noparent. why is this needed?

ping

[armansito, 2015-07-29 16:19:24]

On 2015/07/28 19:59:26, Nico wrote:
> On 2015/07/26 03:19:22, Nico wrote:
> > owner files should generally not have noparent. why is this needed?
> 
> ping

I believe the reason was that we felt the device/OWNERS was too high-level and
people were generally sneaking in features/bugs without explicit approval from
us which made life difficult. At this point though I'm fine with reverting this.

[Nico, 2015-07-29 16:21:44]

On 2015/07/29 16:19:24, armansito wrote:
> On 2015/07/28 19:59:26, Nico wrote:
> > On 2015/07/26 03:19:22, Nico wrote:
> > > owner files should generally not have noparent. why is this needed?
> > 
> > ping
> 
> I believe the reason was that we felt the device/OWNERS was too high-level and
> people were generally sneaking in features/bugs without explicit approval from
> us which made life difficult. At this point though I'm fine with reverting
this.

Cool thanks, will revert then.

If you feel you need to add `set noparent`, that's usually a sign that
communication with higher-level owners isn't quite dialed in yet. Most of the
time this can be fixed by telling the higher-level owners that your code is
tricky and that any interesting change should go to more specialized owners (as
always). Sounds like this is dialed in for device/ now, great :-)

[Nico, 2015-07-29 16:22:53]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1267513002/ by thakis@chromium.org.

The reason for reverting is: `set noparent` is generally an anti-pattern; if
it's necessary there are usually bigger issues that need to be fixed. Sounds
like that has happened for device/ and people are fine without noparent here, so
reverting this..