Add the cc-bugs@chromium.org mailing list to watchlist for the Chromium Compositor subdirectories.

Add the cc-bugs@chromium.org mailing list to watchlist for the Chromium Compositor subdirectories.


Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=156866

[John Grabowski, 2012-09-14 04:51:06]

Please use an @chromium.org mailing list instead?

[danakj, 2012-09-14 05:44:46]

On 2012/09/14 04:51:06, John Grabowski wrote:
> Please use an @chromium.org mailing list instead?

It's an already established mailing list from watching WebKIt. I can make a new
list if we need to but prefer to keep this one if it's okay?

[John Grabowski, 2012-09-14 05:51:27]

On 2012/09/14 05:44:46, danakj wrote:
> On 2012/09/14 04:51:06, John Grabowski wrote:
> > Please use an @chromium.org mailing list instead?
> 
> It's an already established mailing list from watching WebKIt. I can make a
new
> list if we need to but prefer to keep this one if it's okay?

Chromium tries extra-hard to make sure non-Googlers can be full participants. 
This includes access to mailing lists, bug databases, and chat rooms.

If you added a cc-bugs@chromium.org (with cc-bugs@google.com as a "member"),
this would allow external contributors to add themselves to the mailing list as
they see fit.

If you are confident there are alternative yet easy paths for external
contributors to be full-fledged project members within the context of Chromium
WebKit compositor bindings, I will approve this CL.

[danakj, 2012-09-14 06:10:18]

On 2012/09/14 05:51:27, John Grabowski wrote:
> On 2012/09/14 05:44:46, danakj wrote:
> > On 2012/09/14 04:51:06, John Grabowski wrote:
> > > Please use an @chromium.org mailing list instead?
> > 
> > It's an already established mailing list from watching WebKIt. I can make a
> new
> > list if we need to but prefer to keep this one if it's okay?
> 
> Chromium tries extra-hard to make sure non-Googlers can be full participants. 
> This includes access to mailing lists, bug databases, and chat rooms.
> 
> If you added a mailto:cc-bugs@chromium.org (with mailto:cc-bugs@google.com as
a "member"),
> this would allow external contributors to add themselves to the mailing list
as
> they see fit.
> 
> If you are confident there are alternative yet easy paths for external
> contributors to be full-fledged project members within the context of Chromium
> WebKit compositor bindings, I will approve this CL.

The list is used for watching bugs only, not for communication between people.
Since anyone can add their own email to this watchlist file already, I don't
feel like this is excluding or making things any more internal than adding my
own email to the watchlist is.

[Nirnimesh, 2012-09-14 06:30:33]

On 2012/09/14 06:10:18, danakj wrote:
> On 2012/09/14 05:51:27, John Grabowski wrote:
> > On 2012/09/14 05:44:46, danakj wrote:
> > > On 2012/09/14 04:51:06, John Grabowski wrote:
> > > > Please use an @chromium.org mailing list instead?
> > > 
> > > It's an already established mailing list from watching WebKIt. I can make
a
> > new
> > > list if we need to but prefer to keep this one if it's okay?
> > 
> > Chromium tries extra-hard to make sure non-Googlers can be full
participants. 
> > This includes access to mailing lists, bug databases, and chat rooms.
> > 
> > If you added a mailto:cc-bugs@chromium.org (with mailto:cc-bugs@google.com
as
> a "member"),
> > this would allow external contributors to add themselves to the mailing list
> as
> > they see fit.
> > 
> > If you are confident there are alternative yet easy paths for external
> > contributors to be full-fledged project members within the context of
Chromium
> > WebKit compositor bindings, I will approve this CL.
> 
> The list is used for watching bugs only, not for communication between people.
> Since anyone can add their own email to this watchlist file already, I don't
> feel like this is excluding or making things any more internal than adding my
> own email to the watchlist is.

We've gone by so far without having any @google.com addresses in this file. I
think it's better to keep it that way. If nothing else, @google.com would give
the wrong example. Is there any reason why it has to be @google.com? If it can
be @chromium.org, please make it so.

[danakj, 2012-09-14 17:22:51]

On 2012/09/14 06:30:33, Nirnimesh wrote:
> We've gone by so far without having any @google.com addresses in this file. I
> think it's better to keep it that way. If nothing else, @google.com would give
> the wrong example. Is there any reason why it has to be @google.com? If it can
> be @chromium.org, please make it so.

Ok, done!

[John Grabowski, 2012-09-14 17:25:14]

LGTM

[commit-bot: I haz the power, 2012-09-14 17:26:02]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/danakj@chromium.org/10919280/5001

[commit-bot: I haz the power, 2012-09-14 17:46:17]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/danakj@chromium.org/10919280/5001

[commit-bot: I haz the power, 2012-09-14 20:05:29]

Change committed as 156866