You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@apex.apache.org by Pramod Immaneni <pr...@datatorrent.com> on 2016/07/12 21:35:47 UTC
auto-generated emails
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
Re: auto-generated emails
Posted by Sanjay Pujare <sa...@datatorrent.com>.
Strong +1 from me as well (both points 1&2).
On Tue, Jul 12, 2016 at 2:38 PM, David Yan <da...@datatorrent.com> wrote:
> I'm strong +1 for Pramod's suggestion.
>
> David
>
> On Tue, Jul 12, 2016 at 2:35 PM, Pramod Immaneni <pr...@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
> >
>
Re: auto-generated emails
Posted by David Yan <da...@datatorrent.com>.
I'm strong +1 for Pramod's suggestion.
David
On Tue, Jul 12, 2016 at 2:35 PM, Pramod Immaneni <pr...@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
>
Re: auto-generated emails
Posted by Thomas Weise <th...@datatorrent.com>.
https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-12419
On Fri, Aug 12, 2016 at 10:07 AM, Sanjay Pujare <sa...@datatorrent.com>
wrote:
> I recommend leaving JIRA untouched and only turn off PR comments to the
> dev@ mailing list.
>
> On 8/11/16, 6:16 PM, "Thomas Weise" <th...@datatorrent.com> wrote:
>
> 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
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
>
>
>
Re: auto-generated emails
Posted by Sanjay Pujare <sa...@datatorrent.com>.
I recommend leaving JIRA untouched and only turn off PR comments to the dev@ mailing list.
On 8/11/16, 6:16 PM, "Thomas Weise" <th...@datatorrent.com> wrote:
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 <ch...@datatorrent.com>
wrote:
> Sure Pramod. I'll take a look at it.
>
> On Tue, Jul 26, 2016 at 1:17 PM, Pramod Immaneni <pr...@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
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: auto-generated emails
Posted by Thomas Weise <th...@datatorrent.com>.
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 <ch...@datatorrent.com>
wrote:
> Sure Pramod. I'll take a look at it.
>
> On Tue, Jul 26, 2016 at 1:17 PM, Pramod Immaneni <pr...@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
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: auto-generated emails
Posted by Chinmay Kolhatkar <ch...@datatorrent.com>.
Sure Pramod. I'll take a look at it.
On Tue, Jul 26, 2016 at 1:17 PM, Pramod Immaneni <pr...@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
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: auto-generated emails
Posted by Pramod Immaneni <pr...@datatorrent.com>.
Chinmay,
Do you want to investigate setting these up.
Thanks
On Mon, Jul 18, 2016 at 9:15 PM, Chinmay Kolhatkar <ch...@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 <pr...@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 <ch...@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
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: auto-generated emails
Posted by Chinmay Kolhatkar <ch...@datatorrent.com>.
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 <pr...@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 <ch...@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
> > > > >
> > > >
> > >
> >
>
Re: auto-generated emails
Posted by Pramod Immaneni <pr...@datatorrent.com>.
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 <ch...@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 <ra...@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
> > > >
> > >
> >
>
Re: auto-generated emails
Posted by Yogi Devendra <de...@gmail.com>.
+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 <ch...@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 <ra...@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
> > >
> >
>
Re: auto-generated emails
Posted by Chinmay Kolhatkar <ch...@datatorrent.com>.
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 <ra...@datatorrent.com>
wrote:
> +1
>
> Ram
>
> On Tue, Jul 12, 2016 at 2:35 PM, Pramod Immaneni <pr...@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
> >
>
Re: auto-generated emails
Posted by Munagala Ramanath <ra...@datatorrent.com>.
+1
Ram
On Tue, Jul 12, 2016 at 2:35 PM, Pramod Immaneni <pr...@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
>