Re: [DISCUSS] New List for Commit and CI Emails

[Mark Bretl]

+0

I think sending notifications another list are likely to be ignored, or
at-least hard to make sure people sign up for the new list. I would be for
anything to 'optimize' the amount of emails from the automated systems.

--Mark

On Thu, Mar 22, 2018 at 12:55 PM, Ernest Burghardt 
wrote:

> +1 for less noise and spam
>
> On Wed, Mar 21, 2018 at 11:56 AM, Galen O'Sullivan 
> wrote:
>
> > Yeah, I think I'm sending myself convinced by Swapnil's argument.
> >
> > How about muting the "nightly build succeeded" email?
> >
> > On Wed, Mar 21, 2018 at 9:58 AM, Sean Goller  wrote:
> >
> > > Concourse sends mail whenever a job fails.
> > >
> > > On Wed, Mar 21, 2018 at 9:49 AM, Swapnil Bawaskar <
> sbawas...@pivotal.io>
> > > wrote:
> > >
> > > > I know travis is already configured to send emails only when the
> build
> > > > breaks and then when it is fixed. Is concourse configured the same?
> > > >
> > > > On Wed, Mar 21, 2018 at 9:38 AM Patrick Rhomberg <
> prhomb...@pivotal.io
> > >
> > > > wrote:
> > > >
> > > > > I'm with Swapnil on this one.  I think the way we make it less
> noisy
> > is
> > > > to
> > > > > take the time to fix the failing tests.
> > > > >
> > > > > I suppose we could split the difference and give the CI emails a,
> > say,
> > > > > daily cadence.  No news is good news, or else it gives you all the
> > > > failures
> > > > > in the last 24 hours.  Don't know how easy that would be to cache
> and
> > > > > report under the existing framework, though.
> > > > >
> > > > > On Wed, Mar 21, 2018 at 12:05 AM, Jacob Barrett <
> jbarr...@pivotal.io
> > >
> > > > > wrote:
> > > > >
> > > > > > It’s sad that the most frequent spammer... e... I mean mailer
> > is
> > > > the
> > > > > > new CI process. If we aren’t going to send it elsewhere how can
> we
> > > make
> > > > > it
> > > > > > less noisy?
> > > > > >
> > > > > > -Jake
> > > > > >
> > > > > >
> > > > > > > On Mar 20, 2018, at 8:37 PM, Dan Smith 
> > wrote:
> > > > > > >
> > > > > > > I was curious about the stats for bot vs. humans on the dev
> list.
> > > Out
> > > > > of
> > > > > > > 915 messages, looks like we're about 50% robot.
> > > > > > >
> > > > > > > I'm still be in favor of not sending these messages to
> dev@geode.
> > > > Long
> > > > > > time
> > > > > > > members have probably already created a mail filter by now (I
> > know
> > > I
> > > > > > have)
> > > > > > > so we're only hurting newbies by sending a bunch of messages.
> > > > > > >
> > > > > > > 1) apac...@gmail.com 241
> > > > > > > 2) Spring CI 109
> > > > > > > 3) Kirk Lund 63
> > > > > > > 4) Apache Jenkins Server 51
> > > > > > > 5) Anthony Baker 41
> > > > > > > 6) Dan Smith 40
> > > > > > > 7) Travis CI 38
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] New List for Commit and CI Emails

[Ernest Burghardt]

+1 for less noise and spam

On Wed, Mar 21, 2018 at 11:56 AM, Galen O'Sullivan 
wrote:

> Yeah, I think I'm sending myself convinced by Swapnil's argument.
>
> How about muting the "nightly build succeeded" email?
>
> On Wed, Mar 21, 2018 at 9:58 AM, Sean Goller  wrote:
>
> > Concourse sends mail whenever a job fails.
> >
> > On Wed, Mar 21, 2018 at 9:49 AM, Swapnil Bawaskar 
> > wrote:
> >
> > > I know travis is already configured to send emails only when the build
> > > breaks and then when it is fixed. Is concourse configured the same?
> > >
> > > On Wed, Mar 21, 2018 at 9:38 AM Patrick Rhomberg  >
> > > wrote:
> > >
> > > > I'm with Swapnil on this one.  I think the way we make it less noisy
> is
> > > to
> > > > take the time to fix the failing tests.
> > > >
> > > > I suppose we could split the difference and give the CI emails a,
> say,
> > > > daily cadence.  No news is good news, or else it gives you all the
> > > failures
> > > > in the last 24 hours.  Don't know how easy that would be to cache and
> > > > report under the existing framework, though.
> > > >
> > > > On Wed, Mar 21, 2018 at 12:05 AM, Jacob Barrett  >
> > > > wrote:
> > > >
> > > > > It’s sad that the most frequent spammer... e... I mean mailer
> is
> > > the
> > > > > new CI process. If we aren’t going to send it elsewhere how can we
> > make
> > > > it
> > > > > less noisy?
> > > > >
> > > > > -Jake
> > > > >
> > > > >
> > > > > > On Mar 20, 2018, at 8:37 PM, Dan Smith 
> wrote:
> > > > > >
> > > > > > I was curious about the stats for bot vs. humans on the dev list.
> > Out
> > > > of
> > > > > > 915 messages, looks like we're about 50% robot.
> > > > > >
> > > > > > I'm still be in favor of not sending these messages to dev@geode.
> > > Long
> > > > > time
> > > > > > members have probably already created a mail filter by now (I
> know
> > I
> > > > > have)
> > > > > > so we're only hurting newbies by sending a bunch of messages.
> > > > > >
> > > > > > 1) apac...@gmail.com 241
> > > > > > 2) Spring CI 109
> > > > > > 3) Kirk Lund 63
> > > > > > 4) Apache Jenkins Server 51
> > > > > > 5) Anthony Baker 41
> > > > > > 6) Dan Smith 40
> > > > > > 7) Travis CI 38
> > > > >
> > > >
> > >
> >
>

Re: [DISCUSS] New List for Commit and CI Emails

[Galen O'Sullivan]

Yeah, I think I'm sending myself convinced by Swapnil's argument.

How about muting the "nightly build succeeded" email?

On Wed, Mar 21, 2018 at 9:58 AM, Sean Goller  wrote:

> Concourse sends mail whenever a job fails.
>
> On Wed, Mar 21, 2018 at 9:49 AM, Swapnil Bawaskar 
> wrote:
>
> > I know travis is already configured to send emails only when the build
> > breaks and then when it is fixed. Is concourse configured the same?
> >
> > On Wed, Mar 21, 2018 at 9:38 AM Patrick Rhomberg 
> > wrote:
> >
> > > I'm with Swapnil on this one.  I think the way we make it less noisy is
> > to
> > > take the time to fix the failing tests.
> > >
> > > I suppose we could split the difference and give the CI emails a, say,
> > > daily cadence.  No news is good news, or else it gives you all the
> > failures
> > > in the last 24 hours.  Don't know how easy that would be to cache and
> > > report under the existing framework, though.
> > >
> > > On Wed, Mar 21, 2018 at 12:05 AM, Jacob Barrett 
> > > wrote:
> > >
> > > > It’s sad that the most frequent spammer... e... I mean mailer is
> > the
> > > > new CI process. If we aren’t going to send it elsewhere how can we
> make
> > > it
> > > > less noisy?
> > > >
> > > > -Jake
> > > >
> > > >
> > > > > On Mar 20, 2018, at 8:37 PM, Dan Smith  wrote:
> > > > >
> > > > > I was curious about the stats for bot vs. humans on the dev list.
> Out
> > > of
> > > > > 915 messages, looks like we're about 50% robot.
> > > > >
> > > > > I'm still be in favor of not sending these messages to dev@geode.
> > Long
> > > > time
> > > > > members have probably already created a mail filter by now (I know
> I
> > > > have)
> > > > > so we're only hurting newbies by sending a bunch of messages.
> > > > >
> > > > > 1) apac...@gmail.com 241
> > > > > 2) Spring CI 109
> > > > > 3) Kirk Lund 63
> > > > > 4) Apache Jenkins Server 51
> > > > > 5) Anthony Baker 41
> > > > > 6) Dan Smith 40
> > > > > 7) Travis CI 38
> > > >
> > >
> >
>

Re: [DISCUSS] New List for Commit and CI Emails

[Sean Goller]

Concourse sends mail whenever a job fails.

On Wed, Mar 21, 2018 at 9:49 AM, Swapnil Bawaskar 
wrote:

> I know travis is already configured to send emails only when the build
> breaks and then when it is fixed. Is concourse configured the same?
>
> On Wed, Mar 21, 2018 at 9:38 AM Patrick Rhomberg 
> wrote:
>
> > I'm with Swapnil on this one.  I think the way we make it less noisy is
> to
> > take the time to fix the failing tests.
> >
> > I suppose we could split the difference and give the CI emails a, say,
> > daily cadence.  No news is good news, or else it gives you all the
> failures
> > in the last 24 hours.  Don't know how easy that would be to cache and
> > report under the existing framework, though.
> >
> > On Wed, Mar 21, 2018 at 12:05 AM, Jacob Barrett 
> > wrote:
> >
> > > It’s sad that the most frequent spammer... e... I mean mailer is
> the
> > > new CI process. If we aren’t going to send it elsewhere how can we make
> > it
> > > less noisy?
> > >
> > > -Jake
> > >
> > >
> > > > On Mar 20, 2018, at 8:37 PM, Dan Smith  wrote:
> > > >
> > > > I was curious about the stats for bot vs. humans on the dev list. Out
> > of
> > > > 915 messages, looks like we're about 50% robot.
> > > >
> > > > I'm still be in favor of not sending these messages to dev@geode.
> Long
> > > time
> > > > members have probably already created a mail filter by now (I know I
> > > have)
> > > > so we're only hurting newbies by sending a bunch of messages.
> > > >
> > > > 1) apac...@gmail.com 241
> > > > 2) Spring CI 109
> > > > 3) Kirk Lund 63
> > > > 4) Apache Jenkins Server 51
> > > > 5) Anthony Baker 41
> > > > 6) Dan Smith 40
> > > > 7) Travis CI 38
> > >
> >
>

Re: [DISCUSS] New List for Commit and CI Emails

[Swapnil Bawaskar]

I know travis is already configured to send emails only when the build
breaks and then when it is fixed. Is concourse configured the same?

On Wed, Mar 21, 2018 at 9:38 AM Patrick Rhomberg 
wrote:

> I'm with Swapnil on this one.  I think the way we make it less noisy is to
> take the time to fix the failing tests.
>
> I suppose we could split the difference and give the CI emails a, say,
> daily cadence.  No news is good news, or else it gives you all the failures
> in the last 24 hours.  Don't know how easy that would be to cache and
> report under the existing framework, though.
>
> On Wed, Mar 21, 2018 at 12:05 AM, Jacob Barrett 
> wrote:
>
> > It’s sad that the most frequent spammer... e... I mean mailer is the
> > new CI process. If we aren’t going to send it elsewhere how can we make
> it
> > less noisy?
> >
> > -Jake
> >
> >
> > > On Mar 20, 2018, at 8:37 PM, Dan Smith  wrote:
> > >
> > > I was curious about the stats for bot vs. humans on the dev list. Out
> of
> > > 915 messages, looks like we're about 50% robot.
> > >
> > > I'm still be in favor of not sending these messages to dev@geode. Long
> > time
> > > members have probably already created a mail filter by now (I know I
> > have)
> > > so we're only hurting newbies by sending a bunch of messages.
> > >
> > > 1) apac...@gmail.com 241
> > > 2) Spring CI 109
> > > 3) Kirk Lund 63
> > > 4) Apache Jenkins Server 51
> > > 5) Anthony Baker 41
> > > 6) Dan Smith 40
> > > 7) Travis CI 38
> >
>

Re: [DISCUSS] New List for Commit and CI Emails

[Patrick Rhomberg]

I'm with Swapnil on this one.  I think the way we make it less noisy is to
take the time to fix the failing tests.

I suppose we could split the difference and give the CI emails a, say,
daily cadence.  No news is good news, or else it gives you all the failures
in the last 24 hours.  Don't know how easy that would be to cache and
report under the existing framework, though.

On Wed, Mar 21, 2018 at 12:05 AM, Jacob Barrett  wrote:

> It’s sad that the most frequent spammer... e... I mean mailer is the
> new CI process. If we aren’t going to send it elsewhere how can we make it
> less noisy?
>
> -Jake
>
>
> > On Mar 20, 2018, at 8:37 PM, Dan Smith  wrote:
> >
> > I was curious about the stats for bot vs. humans on the dev list. Out of
> > 915 messages, looks like we're about 50% robot.
> >
> > I'm still be in favor of not sending these messages to dev@geode. Long
> time
> > members have probably already created a mail filter by now (I know I
> have)
> > so we're only hurting newbies by sending a bunch of messages.
> >
> > 1) apac...@gmail.com 241
> > 2) Spring CI 109
> > 3) Kirk Lund 63
> > 4) Apache Jenkins Server 51
> > 5) Anthony Baker 41
> > 6) Dan Smith 40
> > 7) Travis CI 38
>

Re: [DISCUSS] New List for Commit and CI Emails

[Jacob Barrett]

It’s sad that the most frequent spammer... e... I mean mailer is the new CI 
process. If we aren’t going to send it elsewhere how can we make it less noisy?

-Jake


> On Mar 20, 2018, at 8:37 PM, Dan Smith  wrote:
> 
> I was curious about the stats for bot vs. humans on the dev list. Out of
> 915 messages, looks like we're about 50% robot.
> 
> I'm still be in favor of not sending these messages to dev@geode. Long time
> members have probably already created a mail filter by now (I know I have)
> so we're only hurting newbies by sending a bunch of messages.
> 
> 1) apac...@gmail.com 241
> 2) Spring CI 109
> 3) Kirk Lund 63
> 4) Apache Jenkins Server 51
> 5) Anthony Baker 41
> 6) Dan Smith 40
> 7) Travis CI 38

Re: [DISCUSS] New List for Commit and CI Emails

[Dan Smith]

I was curious about the stats for bot vs. humans on the dev list. Out of
915 messages, looks like we're about 50% robot.

I'm still be in favor of not sending these messages to dev@geode. Long time
members have probably already created a mail filter by now (I know I have)
so we're only hurting newbies by sending a bunch of messages.

1) apac...@gmail.com 241
2) Spring CI 109
3) Kirk Lund 63
4) Apache Jenkins Server 51
5) Anthony Baker 41
6) Dan Smith 40
7) Travis CI 38

Re: [DISCUSS] New List for Commit and CI Emails

[Anthony Baker]

Looking at other ASF projects it’s pretty rare to see much beyond 
user/dev/issues/commits.  Cassandra has a ‘pr’ list.


> On Mar 20, 2018, at 2:50 PM, Nick Reich  wrote:
> 
> +1
> I use an email filter (from:apachegeod...@gmail.com) to move all the
> automated CI messages to a different section of my inbox, but having a
> fully distinct email list, if possible, would be even nicer.
> 
> On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan 
> wrote:
> 
>> Hi all,
>> 
>> I'm wondering if it would be possible to have a separate list for commit
>> announcements, CI emails and similar automated messages, and keep this
>> mailing list for discussion. It would make it easier to filter email, and I
>> think it might help improve the discussion. I know I've missed messages
>> sent to this list in the flood of email. What do you think? Who's in charge
>> of lists and gets to make those decisions?
>> 
>> Thanks,
>> Galen
>> 

Re: [DISCUSS] New List for Commit and CI Emails

[Swapnil Bawaskar]

I don't think we should send ci to a different email list for it to be
ignored. We ideally should be in a place where emails from ci are not the
norm but an exception which prompts immediate action.

On Tue, Mar 20, 2018 at 3:05 PM Dan Smith  wrote:

> +1 to removing all automated messages from dev@geode
>
> I think we've already shunted commit messages to commits@geode and jira
> issue updates to issues@geode. What I see now is mostly messages related
> to
> ci. Should we create a new ci@geode mailing list, or send those messages
> to
> some other mailing list?
>
> If we want to create a new list, I think the next step is to file a ticket
> with infra after we come to a consensus. Unless our illustrious leader Mark
> has access to do that :)
>
> To move the CI emails to the the new list, we'll have to update concourse,
> jenkins, travis, and spring CI it looks like.
>
> -Dan
>
> On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan 
> wrote:
>
> > Hi all,
> >
> > I'm wondering if it would be possible to have a separate list for commit
> > announcements, CI emails and similar automated messages, and keep this
> > mailing list for discussion. It would make it easier to filter email,
> and I
> > think it might help improve the discussion. I know I've missed messages
> > sent to this list in the flood of email. What do you think? Who's in
> charge
> > of lists and gets to make those decisions?
> >
> > Thanks,
> > Galen
> >
>

Re: [DISCUSS] New List for Commit and CI Emails

[Dan Smith]

+1 to removing all automated messages from dev@geode

I think we've already shunted commit messages to commits@geode and jira
issue updates to issues@geode. What I see now is mostly messages related to
ci. Should we create a new ci@geode mailing list, or send those messages to
some other mailing list?

If we want to create a new list, I think the next step is to file a ticket
with infra after we come to a consensus. Unless our illustrious leader Mark
has access to do that :)

To move the CI emails to the the new list, we'll have to update concourse,
jenkins, travis, and spring CI it looks like.

-Dan

On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan 
wrote:

> Hi all,
>
> I'm wondering if it would be possible to have a separate list for commit
> announcements, CI emails and similar automated messages, and keep this
> mailing list for discussion. It would make it easier to filter email, and I
> think it might help improve the discussion. I know I've missed messages
> sent to this list in the flood of email. What do you think? Who's in charge
> of lists and gets to make those decisions?
>
> Thanks,
> Galen
>

Re: [DISCUSS] New List for Commit and CI Emails

[Nick Reich]

+1
I use an email filter (from:apachegeod...@gmail.com) to move all the
automated CI messages to a different section of my inbox, but having a
fully distinct email list, if possible, would be even nicer.

On Tue, Mar 20, 2018 at 2:27 PM, Galen O'Sullivan 
wrote:

> Hi all,
>
> I'm wondering if it would be possible to have a separate list for commit
> announcements, CI emails and similar automated messages, and keep this
> mailing list for discussion. It would make it easier to filter email, and I
> think it might help improve the discussion. I know I've missed messages
> sent to this list in the flood of email. What do you think? Who's in charge
> of lists and gets to make those decisions?
>
> Thanks,
> Galen
>

[DISCUSS] New List for Commit and CI Emails

[Galen O'Sullivan]

Hi all,

I'm wondering if it would be possible to have a separate list for commit
announcements, CI emails and similar automated messages, and keep this
mailing list for discussion. It would make it easier to filter email, and I
think it might help improve the discussion. I know I've missed messages
sent to this list in the flood of email. What do you think? Who's in charge
of lists and gets to make those decisions?

Thanks,
Galen