authors update- add herb and reorganize

authors update- add herb and reorganize

BUG=skia:

TBR=reed@google.com

NOTRY=true

Committed: https://skia.googlesource.com/skia/+/45453c2acfa39755081616fd9c02e567b3369d40

[hcm, 2015-01-28 14:27:25]

hcm@google.com changed reviewers:
+ rmistry@google.com

[rmistry, 2015-01-28 14:30:31]

On 2015/01/28 14:27:25, hcm wrote:
> mailto:hcm@google.com changed reviewers:
> + mailto:rmistry@google.com

As mentioned in https://codereview.chromium.org/877363002/:
We should find out if our gmail accounts need to sign the CLA for us to submit
code using them. Google knows that google.com and chromium.org accounts are ours
but there is AFAIK no way to connect personal accounts with them.

[hcm, 2015-01-28 22:16:05]

The CQ bit was checked by hcm@google.com

[commit-bot: I haz the power, 2015-01-28 22:16:38]

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

[commit-bot: I haz the power, 2015-01-28 22:16:49]

Committed patchset #1 (id:1) as
https://skia.googlesource.com/skia/+/45453c2acfa39755081616fd9c02e567b3369d40

[hcm, 2015-01-28 22:21:53]

On 2015/01/28 14:30:31, rmistry wrote:
> On 2015/01/28 14:27:25, hcm wrote:
> > mailto:hcm@google.com changed reviewers:
> > + mailto:rmistry@google.com
> 
> As mentioned in https://codereview.chromium.org/877363002/:
> We should find out if our gmail accounts need to sign the CLA for us to submit
> code using them. Google knows that http://google.com and http://chromium.org
accounts are ours
> but there is AFAIK no way to connect personal accounts with them.

Pushed this in as agreed for now, we are abiding by the rules of making sure all
authors are listed/authorized/covered by a CLA.. I don't think we want
individuals signing CLAs who are already covered by Google or another
corporation's CLA, it seems we just need a way to keep track of additional
aliases for approved authors.  Will work on this and fold it into our plans
around automated checks as well.