Mailing-List: contact dev-help@apex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@apex.apache.org
MIME-Version: 1.0
In-Reply-To: <CABAipVY9e=RcY1soQ6S5J6ZD-KgHbK7onwvgKri7pmR8B+q4uw@mail.gmail.com>
References: <CAA7LveH=CVjV2PVxAq1tQRA-QjUm0bkg914wtH1+-i4u8MVgog@mail.gmail.com>
 <CAJ484Biqd8ara=ytXKW-09d4Z2X+hWNUvQS4QohpYsE5zv=cWg@mail.gmail.com>
 <CABAipVa57sMkzdhzL=D4QXupC7C4mXn0oia_F2NTAh=kkvvaEw@mail.gmail.com>
 <CAHekGF_gbHa4peYka-1+WFuCg6febck2yb=sqp+wdz3JLuTkUA@mail.gmail.com>
 <CAA7LveFXVac2vMGPqJC1bJiOns-rMB4VOSv5nTsDFmQqC_ZmjQ@mail.gmail.com>
 <CABAipVYc2_J1EaDxjDMqtfHj9=gFv34G7f0FhJDEb9iDJPVQFw@mail.gmail.com>
 <CAA7LveELs-JffQGYeNpoS_DpVPWkt5Kau4PYVf07JD0tRgfUqg@mail.gmail.com> <CABAipVY9e=RcY1soQ6S5J6ZD-KgHbK7onwvgKri7pmR8B+q4uw@mail.gmail.com>
From: Thomas Weise <thomas@datatorrent.com>
Date: Thu, 11 Aug 2016 18:16:37 -0700
Message-ID: <CAKJfLDN-8nnQ0Xe9cozAqtK_s7JaCWEw2EYHRPW8o-U-sEJMdA@mail.gmail.com>
Subject: Re: auto-generated emails
To: dev@apex.apache.org
Content-Type: multipart/alternative; boundary=94eb2c0484b05875cf0539d5a237
archived-at: Fri, 12 Aug 2016 01:16:44 -0000

--94eb2c0484b05875cf0539d5a237
Content-Type: text/plain; charset=UTF-8

I'm going to create a ticket to turn off pull request comments to the dev@
mailing list.

In addition to that, we have also PR comments attached to JIRA:

https://reference.apache.org/pmc/github

The JIRA comments are also sent to the mailing list. So we could either
turn off attaching PR comments to JIRA or turn off all JIRA comments to the
mailing list. It may be useful though to have JIRA comments other then PR
comments on the mailing list?


On Tue, Jul 26, 2016 at 1:05 AM, Chinmay Kolhatkar <chinmay@datatorrent.com>
wrote:

> Sure Pramod. I'll take a look at it.
>
> On Tue, Jul 26, 2016 at 1:17 PM, Pramod Immaneni <pramod@datatorrent.com>
> wrote:
>
> > Chinmay,
> >
> > Do you want to investigate setting these up.
> >
> > Thanks
> >
> > On Mon, Jul 18, 2016 at 9:15 PM, Chinmay Kolhatkar <
> > chinmay@datatorrent.com>
> > wrote:
> >
> > > Pramod,
> > >
> > > My Suggestion is on the same lines as what Yogi suggested, except
> instead
> > > of creating a seperate mailing list, send further mails to folks in the
> > > comments.
> > >
> > > -Chinmay.
> > >
> > >
> > > On Tue, Jul 19, 2016 at 3:07 AM, Pramod Immaneni <
> pramod@datatorrent.com
> > >
> > > wrote:
> > >
> > > > Chinmay are you suggesting the first mail only sent to folks
> mentioned
> > > and
> > > > not everyone in the list? I like Yogi's suggestion on having a
> separate
> > > > commits list where all commit emails go but initial emails are still
> > sent
> > > > to dev and dev can mostly focus on discussions.
> > > >
> > > > Anyone, wants to volunteer to investigate these options?
> > > >
> > > > Thanks
> > > >
> > > > On Fri, Jul 15, 2016 at 2:34 AM, Yogi Devendra <
> > > > devendra.vyavahare@gmail.com
> > > > > wrote:
> > > >
> > > > > +1 on reducing automated emails for comments on dev list.
> > > > >
> > > > > How about having separate mailing list such as commits@apex which
> > > would
> > > > > have full archive of comments?
> > > > >
> > > > > New JIRA, PR can be sent to both dev, commits.
> > > > >
> > > > > ~ Yogi
> > > > >
> > > > > On 13 July 2016 at 10:22, Chinmay Kolhatkar <
> chinmay@datatorrent.com
> > >
> > > > > wrote:
> > > > >
> > > > > > Strongly +1 for this.
> > > > > >
> > > > > > For 1, can the mail be sent to someone who is mentioned in the
> PR?
> > So
> > > > for
> > > > > > e.g., if I mention @PramodSSImmaneni , then Pramod will be part
> of
> > PR
> > > > > email
> > > > > > notification all further back and forth communication for that
> PR.
> > > > > >
> > > > > > @Pramod, just using your name as an example.. :)
> > > > > >
> > > > > > - Chinmay.
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 13, 2016 at 3:18 AM, Munagala Ramanath <
> > > > ram@datatorrent.com>
> > > > > > wrote:
> > > > > >
> > > > > > > +1
> > > > > > >
> > > > > > > Ram
> > > > > > >
> > > > > > > On Tue, Jul 12, 2016 at 2:35 PM, Pramod Immaneni <
> > > > > pramod@datatorrent.com
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I was wondering how everyone felt about the volume of
> > > > auto-generated
> > > > > > > emails
> > > > > > > > on this list. Looks like multiple emails are generated and
> sent
> > > to
> > > > > > > everyone
> > > > > > > > on the list even for relatively smaller actions such as
> > > commenting
> > > > > on a
> > > > > > > > pull request, one from git, another from JIRA etc.
> > > > > > > >
> > > > > > > > Understanding that there is a need for openness, how about
> > > finding
> > > > a
> > > > > > > > balance. Here are some ideas. I do not know if all of these
> are
> > > > > > > technically
> > > > > > > > feasible.
> > > > > > > >
> > > > > > > > 1. An email is sent to all in the list when a new pull
> request
> > is
> > > > > > created
> > > > > > > > or merged but email notifications for back and forth comments
> > > > during
> > > > > > the
> > > > > > > > review are only sent to participants in that particular pull
> > > > request.
> > > > > > > > 2. Similar process as above with JIRA. If someone is
> interested
> > > in
> > > > > all
> > > > > > > the
> > > > > > > > updates to JIRA, including those that come from the pull
> > request,
> > > > > they
> > > > > > > can
> > > > > > > > add themselves to the watch list for that particular JIRA.
> > > > > > > >
> > > > > > > > Thanks
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>

--94eb2c0484b05875cf0539d5a237--