Add OWNERS file for build/android/buildbot

Add OWNERS file for build/android/buildbot

- Owners based on number of commits and numbers of reviews of
  code in this directory.

R=yaron,cmp
BUG=

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

[Yaron, 2012-09-25 22:47:03]

lgtm

[cmp, 2012-09-25 23:02:28]

lgtm

+dpranke for review since he added the OWNERS file in src/build/

[Dirk Pranke, 2012-09-25 23:35:00]

why the 'set noparent'? I thought we wanted to move away from using that.

[Isaac (away), 2012-09-25 23:51:04]

because build/ directory is * but this directory manages our buildbots, incl
ones on the main waterfall

[Dirk Pranke, 2012-09-25 23:58:48]

There is no "*" in build/OWNERS that I see ... are you worried that
there are too many people in there you don't want to be able to lgtm
the changes on these bots?


On Tue, Sep 25, 2012 at 4:51 PM,  <ilevy@chromium.org> wrote:
> because build/ directory is * but this directory manages our buildbots, incl
> ones on the main waterfall
>
> https://codereview.chromium.org/10979024/

[cmp, 2012-09-26 00:04:23]

On 2012/09/25 23:58:48, Dirk Pranke wrote:
> There is no "*" in build/OWNERS that I see

Can you confirm that?  Before I lgtm'd I checked src/build/OWNERS and saw that
it had * as its only content:
http://src.chromium.org/viewvc/chrome/trunk/src/build/OWNERS?revision=126218&...


> ... are you worried that
> there are too many people in there you don't want to be able to lgtm
> the changes on these bots?

Right, the purpose of this OWNERS is equivalent to why we have OWNERS in
chrome/trunk/tools/build and depot_tools/OWNERS.  Changes to files in this
directory can effect lots of bots, so only those familiar with how they work
should be approving changes here.

Not sure what I think about the set noparent rule.  I understand why we want to
move away from it.  If we replaced the * in build/ with a set of 3-4 people that
would respect the OWNERS in build/android/buildbot, that might be a solution for
not having set noparent in this OWNERS file.  But perhaps we want to keep * in
build/?  I think it would make sense to identify some strong owners in build/
and guide that directory forward.  WDYT?

[Dirk Pranke, 2012-09-26 00:10:30]

On Tue, Sep 25, 2012 at 5:04 PM,  <cmp@chromium.org> wrote:
> On 2012/09/25 23:58:48, Dirk Pranke wrote:
>>
>> There is no "*" in build/OWNERS that I see
>
>
> Can you confirm that?  Before I lgtm'd I checked src/build/OWNERS and saw
> that
> it had * as its only content:
>
http://src.chromium.org/viewvc/chrome/trunk/src/build/OWNERS?revision=126218&...
>

I'm sorry, my mistake. I was looking in tools/build, not src/build.
Your use of the "*" is fine, then :).

lgtm.