code review 9391043: odbc: remove golang-dev from defaultcc

odbc: remove golang-dev from defaultcc

[adg, 2013-05-13 17:52:36]

Hello alex.brainman@gmail.com (cc: golang-dev@googlegroups.com),

I'd like you to review this change to
https://code.google.com/p/odbc

[adg, 2013-05-13 17:54:11]

Hi Alex,

I'd like to cut down the mail volume of golang-dev. Would you mind moving
odbc reviews to a separate mailing list?

Thanks,
Andrew

[alexb_frankandoak.com, 2013-05-13 18:30:02]

That's some solid proof real work is being done guys!
I love your comment Andrew, and good work Alex, keep it up (:

On 2013-05-13, at 1:53 PM, Andrew Gerrand <adg@golang.org> wrote:

> Hi Alex,
> 
> I'd like to cut down the mail volume of golang-dev. Would you mind moving odbc
reviews to a separate mailing list?
> 
> Thanks,
> Andrew
> 
> -- 
>  
> --- 
> You received this message because you are subscribed to the Google Groups
"golang-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
email to golang-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>  
>  

[alexb_frankandoak.com, 2013-05-13 18:34:20]

I'm just throwing this idea,
but why don't we have golang-dev for development/coordination/design decisions,
and golang-review for code review?

It seems to me like both should be two different process.
If you need both, just subscribe to both, right?

[bradfitz, 2013-05-13 18:35:28]

Yes, we're changing the process.  Expect announcements soon.



On Mon, May 13, 2013 at 11:34 AM, Alex Belanger <alexb@frankandoak.com>wrote:

> I'm just throwing this idea,
> but why don't we have *golang-dev* for development/coordination/design
> decisions,
> and *golang-review* for code review?
>
> It seems to me like both should be two different process.
> If you need both, just subscribe to both, right?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "golang-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to golang-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

[minux1, 2013-05-13 18:38:08]

On Tue, May 14, 2013 at 2:34 AM, Alex Belanger <alexb@frankandoak.com>wrote:

> I'm just throwing this idea,
> but why don't we have *golang-dev* for development/coordination/design
> decisions,
>
the contribution guideline says that design proposal and its discussion
should be made on
golang-nuts, and code review is placed on golang-dev.

> and *golang-review* for code review?
>
> It seems to me like both should be two different process.
> If you need both, just subscribe to both, right?
>
i think most of subscriber of golang-dev will indeed need both, so there is
little benefit
splitting golang-dev into two.

[nitrix, 2013-05-13 18:51:38]

I though golang-nuts was mostly for help? That's where we redirect everyone
when its not development related.

Because something to consider is the fact in the near future, we will want
a  list to get help with the language (not everyone has IRC), another list
less noisy for development decisions and serious stuff when (that helps
identifying flamewars) and a last one for code review, which is only
increasing in volume.

You call them how you want, but to start with these three would be a good
begining.

golang-nuts
golang-dev
golang-review

Cheers.

[brainman, 2013-05-14 05:41:33]

LGTM

Sorry for the noise.

Alex

[brainman, 2013-05-14 05:42:17]

*** Submitted as https://code.google.com/p/odbc/source/detail?r=93ba376e9242 ***

odbc: remove golang-dev from defaultcc

R=alex.brainman, alexb, bradfitz, minux.ma, i.caught.air
CC=golang-dev
https://codereview.appspot.com/9391043

Committer: Alex Brainman <alex.brainman@gmail.com>

[bradfitz, 2013-05-14 05:48:35]

On Mon, May 13, 2013 at 10:41 PM, <alex.brainman@gmail.com> wrote:

> LGTM
>
> Sorry for the noise.
>

No worries.

It was just the final straw on the camel's back.

The camel was due to collapse imminently anyway.