[headless] Create headless/ folder

[headless] Create headless/ folder

Create top-level headless/ folder and OWNERS for it.

BUG=546953
Committed: https://crrev.com/711497d0138297f221cd7283f313e6254b0409fe
Cr-Commit-Position: refs/heads/master@{#360095}

[altimin, 2015-11-13 13:41:25]

Description was changed from

==========
[headless] Create headless/ folder

BUG=546953
==========

to

==========
[headless] Create headless/ folder

Create top-level headless/ folder and OWNERS for it.

BUG=546953
==========

[altimin, 2015-11-13 13:41:25]

altimin@chromium.org changed reviewers:
+ alexclarke@chromium.org, jam@chromium.org, skyostil@google.com

[jam, 2015-11-13 17:16:12]

curious why we need a toplevel folder for this? what will go here?

[alex clarke (OOO till 29th), 2015-11-13 17:23:39]

On 2015/11/13 17:16:12, jam wrote:
> curious why we need a toplevel folder for this? what will go here?

I think the intention is the code we build for the headless API etc will live
there.  Specifically this sort of stuff:
https://codereview.chromium.org/1430673002/

I don't know where this should live in the tree and was hoping you'd be able to
advise us.

[altimin, 2015-11-13 23:59:16]

On 2015/11/13 17:23:39, alexclarke1 wrote:
> On 2015/11/13 17:16:12, jam wrote:
> > curious why we need a toplevel folder for this? what will go here?
> 
> I think the intention is the code we build for the headless API etc will live
> there.  Specifically this sort of stuff:
> https://codereview.chromium.org/1430673002/
> 
> I don't know where this should live in the tree and was hoping you'd be able
to
> advise us.

https://codereview.chromium.org/1410573004/ is relevant here too (it's first
version of headless_shell, there is some discussion about location in comments).

[Sami, 2015-11-16 09:59:30]

FWIW, we chose a toplevel folder instead of something inside content/ to make it
clear that headless/ only depends on the public api of content/. I guess another
option would be something like chrome/headless/ but that might only add to the
confusion since I don't think we'll need anything from chrome/.

[Sami, 2015-11-17 14:23:13]

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

[Sami, 2015-11-17 14:23:14]

Ping, any thoughts on this?

[jam, 2015-11-17 15:44:31]

On 2015/11/16 09:59:30, Sami wrote:
> FWIW, we chose a toplevel folder instead of something inside content/ to make
it
> clear that headless/ only depends on the public api of content/. I guess
another
> option would be something like chrome/headless/ but that might only add to the
> confusion since I don't think we'll need anything from chrome/.

thanks for the explanations, lgtm

[altimin, 2015-11-17 16:47:03]

The CQ bit was checked by altimin@chromium.org

[commit-bot: I haz the power, 2015-11-17 16:48:40]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1433933007/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1433933007/1

[commit-bot: I haz the power, 2015-11-17 17:05:43]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-17 17:06:37]

Patchset 1 (id:??) landed as
https://crrev.com/711497d0138297f221cd7283f313e6254b0409fe
Cr-Commit-Position: refs/heads/master@{#360095}