emails notification updates for JIRA and GitHub

[Wilfred Spiegelenburg <wi...@apache.org>]

Hi all,

I noticed last week when moving all issues into the JIRA that there is no
email send for JIRAs at all. I checked the project settings and we have
currently not linked up the JIRA notifications to the correct list.
The original plan was to use issues@ as the mailing list. However we seem
to have missed that change.

If there are no reservations to using this I will ask INFRA to change the
notification list to issues@ for the following events:
* Created
* Updated
* Assigned
* Resolved
* Closed
* Commented
* Comment Edited
That will bring us in line with most of the other projects.

Second point for mailing lists: commits@ was originally slated for GitHub
emails. The mailing list does not exist at the moment. Currently all the
git emails come in on the dev@ mailing list which clutters that list.
Instead of creating commits@ I would like to propose to change the name to
reviews@ as it better covers what we do on GitHub with the PRs and the
review on the code.

Please respond to this mail if you are not OK with the changes. If there
are no objections I will start the changes on Monday 16 March 2020 (AEDT
+11).

Thank you,
Wilfred

Re: emails notification updates for JIRA and GitHub

[Weiwei Yang <ab...@gmail.com>]

Sounds good, thank you!

On Tue, Mar 17, 2020 at 8:57 PM Wilfred Spiegelenburg <wi...@apache.org>
wrote:

> Based on the fact that I have not had any further feedback on the changes
> have started the process to change the jira notifications.
> All notifications will go to: issues@ (new, changes, comments etc)
> Jira creation and closure will also be send to the dev@ list.
>
> I have asked the project mentors to create a reviews@ list for us and when
> that is done I'll ask the notification list for github to also be updated.
>
> I will send out and update when the changes have completed.
>
> Wilfred
>
> On Wed, 11 Mar 2020 at 14:23, Wilfred Spiegelenburg <wi...@apache.org>
> wrote:
>
> > Sunil,
> >
> > Yes we are going to use issues@ for JIRA. That is just around the
> corner,
> > really a no brainer.
> >
> > Reviews or GitHub mails is something different. Hadoop Ozone is one of
> the
> > reasons I am asking this.
> > The dev list got spammed by GitHub messages from ozone and they moved to
> a
> > separate list there.
> > I am trying to be ahead of the curve and move our GitHub messages too.
> >
> > There are a total of 12 projects that use a reviews@ mailing list for
> > apache projects.
> > Projects like Spark, impala, kudu & ambari to name a few. So I don't
> think
> > we are that out of sync.
> > Most of these projects also use a issues@ for their jira tracking.
> > I am also OK with mixing the GitHub and JIRA mails on one list (issues@)
> > if that is the preferred option, that is why I am asking.
> >
> > I looked at some other projects and if we mix the GitHub messages in with
> > the standard dev@ list.
> > It can cause the dev list to blow out from 1-2 messages per day to 20+
> > messages a day.
> > Off course you can always filter the messages and separate on receive but
> > keeping them separate to start with is easier.
> >
> > Cheers,
> > Wilfred
> >
> > On Wed, 11 Mar 2020 at 13:13, Sunil Govindan <su...@apache.org> wrote:
> >
> >> Hi Weiwei and Wilfred,
> >>
> >> I have not seen a reviews@ list so far. In other projects, I have seen
> >> issues@ list where all updates on jira will go.
> >> In any case, I agree in removing such notifications from dev@ list. And
> >> if possible, also having an issues@ list as well
> >>
> >> - Sunil
> >>
> >> On Tue, Mar 10, 2020 at 10:04 AM Wilfred Spiegelenburg <
> >> wilfreds@apache.org> wrote:
> >>
> >>> Hi Weiwei,
> >>>
> >>> Currently all notifications for github go to dev@, that is a setting
> on
> >>> the
> >>> github repos that can be changed.
> >>> I propose to move all of them to the reviews@ list and remove dev@
> from
> >>> the
> >>> github notifications
> >>> We should be using dev@ for mails that require discussions and votes
> >>> not as
> >>> a generic notification list I think.
> >>>
> >>> Wilfred
> >>>
> >>> On Tue, 10 Mar 2020 at 15:18, Weiwei Yang <ab...@gmail.com> wrote:
> >>>
> >>> > Hi Wilfred
> >>> >
> >>> > Thanks for taking care of this.
> >>> > For the second one, since we already have GitBox notification about
> >>> PRs,
> >>> > creating reviews@ mailing list would get us too many duplicated
> >>> messages?
> >>> >
> >>> > Weiwei
> >>> >
> >>> > On Mon, Mar 9, 2020 at 9:11 PM Wilfred Spiegelenburg <
> >>> wilfreds@apache.org>
> >>> > wrote:
> >>> >
> >>> >> Hi all,
> >>> >>
> >>> >> I noticed last week when moving all issues into the JIRA that there
> >>> is no
> >>> >> email send for JIRAs at all. I checked the project settings and we
> >>> have
> >>> >> currently not linked up the JIRA notifications to the correct list.
> >>> >> The original plan was to use issues@ as the mailing list. However
> we
> >>> seem
> >>> >> to have missed that change.
> >>> >>
> >>> >> If there are no reservations to using this I will ask INFRA to
> change
> >>> the
> >>> >> notification list to issues@ for the following events:
> >>> >> * Created
> >>> >> * Updated
> >>> >> * Assigned
> >>> >> * Resolved
> >>> >> * Closed
> >>> >> * Commented
> >>> >> * Comment Edited
> >>> >> That will bring us in line with most of the other projects.
> >>> >>
> >>> >> Second point for mailing lists: commits@ was originally slated for
> >>> GitHub
> >>> >> emails. The mailing list does not exist at the moment. Currently all
> >>> the
> >>> >> git emails come in on the dev@ mailing list which clutters that
> list.
> >>> >> Instead of creating commits@ I would like to propose to change the
> >>> name
> >>> >> to
> >>> >> reviews@ as it better covers what we do on GitHub with the PRs and
> >>> the
> >>> >> review on the code.
> >>> >>
> >>> >> Please respond to this mail if you are not OK with the changes. If
> >>> there
> >>> >> are no objections I will start the changes on Monday 16 March 2020
> >>> (AEDT
> >>> >> +11).
> >>> >>
> >>> >> Thank you,
> >>> >> Wilfred
> >>> >>
> >>> >
> >>> >
> >>> > --
> >>> > *Weiwei Yang*
> >>> > Software Engineer, Cloudera
> >>> >
> >>> > Create your own WiseStamp email signature
> >>> > <
> >>>
> https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112
> >>> >
> >>> >
> >>>
> >>
>

Re: emails notification updates for JIRA and GitHub

[Wilfred Spiegelenburg <wi...@apache.org>]

Based on the fact that I have not had any further feedback on the changes
have started the process to change the jira notifications.
All notifications will go to: issues@ (new, changes, comments etc)
Jira creation and closure will also be send to the dev@ list.

I have asked the project mentors to create a reviews@ list for us and when
that is done I'll ask the notification list for github to also be updated.

I will send out and update when the changes have completed.

Wilfred

On Wed, 11 Mar 2020 at 14:23, Wilfred Spiegelenburg <wi...@apache.org>
wrote:

> Sunil,
>
> Yes we are going to use issues@ for JIRA. That is just around the corner,
> really a no brainer.
>
> Reviews or GitHub mails is something different. Hadoop Ozone is one of the
> reasons I am asking this.
> The dev list got spammed by GitHub messages from ozone and they moved to a
> separate list there.
> I am trying to be ahead of the curve and move our GitHub messages too.
>
> There are a total of 12 projects that use a reviews@ mailing list for
> apache projects.
> Projects like Spark, impala, kudu & ambari to name a few. So I don't think
> we are that out of sync.
> Most of these projects also use a issues@ for their jira tracking.
> I am also OK with mixing the GitHub and JIRA mails on one list (issues@)
> if that is the preferred option, that is why I am asking.
>
> I looked at some other projects and if we mix the GitHub messages in with
> the standard dev@ list.
> It can cause the dev list to blow out from 1-2 messages per day to 20+
> messages a day.
> Off course you can always filter the messages and separate on receive but
> keeping them separate to start with is easier.
>
> Cheers,
> Wilfred
>
> On Wed, 11 Mar 2020 at 13:13, Sunil Govindan <su...@apache.org> wrote:
>
>> Hi Weiwei and Wilfred,
>>
>> I have not seen a reviews@ list so far. In other projects, I have seen
>> issues@ list where all updates on jira will go.
>> In any case, I agree in removing such notifications from dev@ list. And
>> if possible, also having an issues@ list as well
>>
>> - Sunil
>>
>> On Tue, Mar 10, 2020 at 10:04 AM Wilfred Spiegelenburg <
>> wilfreds@apache.org> wrote:
>>
>>> Hi Weiwei,
>>>
>>> Currently all notifications for github go to dev@, that is a setting on
>>> the
>>> github repos that can be changed.
>>> I propose to move all of them to the reviews@ list and remove dev@ from
>>> the
>>> github notifications
>>> We should be using dev@ for mails that require discussions and votes
>>> not as
>>> a generic notification list I think.
>>>
>>> Wilfred
>>>
>>> On Tue, 10 Mar 2020 at 15:18, Weiwei Yang <ab...@gmail.com> wrote:
>>>
>>> > Hi Wilfred
>>> >
>>> > Thanks for taking care of this.
>>> > For the second one, since we already have GitBox notification about
>>> PRs,
>>> > creating reviews@ mailing list would get us too many duplicated
>>> messages?
>>> >
>>> > Weiwei
>>> >
>>> > On Mon, Mar 9, 2020 at 9:11 PM Wilfred Spiegelenburg <
>>> wilfreds@apache.org>
>>> > wrote:
>>> >
>>> >> Hi all,
>>> >>
>>> >> I noticed last week when moving all issues into the JIRA that there
>>> is no
>>> >> email send for JIRAs at all. I checked the project settings and we
>>> have
>>> >> currently not linked up the JIRA notifications to the correct list.
>>> >> The original plan was to use issues@ as the mailing list. However we
>>> seem
>>> >> to have missed that change.
>>> >>
>>> >> If there are no reservations to using this I will ask INFRA to change
>>> the
>>> >> notification list to issues@ for the following events:
>>> >> * Created
>>> >> * Updated
>>> >> * Assigned
>>> >> * Resolved
>>> >> * Closed
>>> >> * Commented
>>> >> * Comment Edited
>>> >> That will bring us in line with most of the other projects.
>>> >>
>>> >> Second point for mailing lists: commits@ was originally slated for
>>> GitHub
>>> >> emails. The mailing list does not exist at the moment. Currently all
>>> the
>>> >> git emails come in on the dev@ mailing list which clutters that list.
>>> >> Instead of creating commits@ I would like to propose to change the
>>> name
>>> >> to
>>> >> reviews@ as it better covers what we do on GitHub with the PRs and
>>> the
>>> >> review on the code.
>>> >>
>>> >> Please respond to this mail if you are not OK with the changes. If
>>> there
>>> >> are no objections I will start the changes on Monday 16 March 2020
>>> (AEDT
>>> >> +11).
>>> >>
>>> >> Thank you,
>>> >> Wilfred
>>> >>
>>> >
>>> >
>>> > --
>>> > *Weiwei Yang*
>>> > Software Engineer, Cloudera
>>> >
>>> > Create your own WiseStamp email signature
>>> > <
>>> https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112
>>> >
>>> >
>>>
>>

Re: emails notification updates for JIRA and GitHub

[Wilfred Spiegelenburg <wi...@apache.org>]

Sunil,

Yes we are going to use issues@ for JIRA. That is just around the corner,
really a no brainer.

Reviews or GitHub mails is something different. Hadoop Ozone is one of the
reasons I am asking this.
The dev list got spammed by GitHub messages from ozone and they moved to a
separate list there.
I am trying to be ahead of the curve and move our GitHub messages too.

There are a total of 12 projects that use a reviews@ mailing list for
apache projects.
Projects like Spark, impala, kudu & ambari to name a few. So I don't think
we are that out of sync.
Most of these projects also use a issues@ for their jira tracking.
I am also OK with mixing the GitHub and JIRA mails on one list (issues@) if
that is the preferred option, that is why I am asking.

I looked at some other projects and if we mix the GitHub messages in with
the standard dev@ list.
It can cause the dev list to blow out from 1-2 messages per day to 20+
messages a day.
Off course you can always filter the messages and separate on receive but
keeping them separate to start with is easier.

Cheers,
Wilfred

On Wed, 11 Mar 2020 at 13:13, Sunil Govindan <su...@apache.org> wrote:

> Hi Weiwei and Wilfred,
>
> I have not seen a reviews@ list so far. In other projects, I have seen
> issues@ list where all updates on jira will go.
> In any case, I agree in removing such notifications from dev@ list. And
> if possible, also having an issues@ list as well
>
> - Sunil
>
> On Tue, Mar 10, 2020 at 10:04 AM Wilfred Spiegelenburg <
> wilfreds@apache.org> wrote:
>
>> Hi Weiwei,
>>
>> Currently all notifications for github go to dev@, that is a setting on
>> the
>> github repos that can be changed.
>> I propose to move all of them to the reviews@ list and remove dev@ from
>> the
>> github notifications
>> We should be using dev@ for mails that require discussions and votes not
>> as
>> a generic notification list I think.
>>
>> Wilfred
>>
>> On Tue, 10 Mar 2020 at 15:18, Weiwei Yang <ab...@gmail.com> wrote:
>>
>> > Hi Wilfred
>> >
>> > Thanks for taking care of this.
>> > For the second one, since we already have GitBox notification about PRs,
>> > creating reviews@ mailing list would get us too many duplicated
>> messages?
>> >
>> > Weiwei
>> >
>> > On Mon, Mar 9, 2020 at 9:11 PM Wilfred Spiegelenburg <
>> wilfreds@apache.org>
>> > wrote:
>> >
>> >> Hi all,
>> >>
>> >> I noticed last week when moving all issues into the JIRA that there is
>> no
>> >> email send for JIRAs at all. I checked the project settings and we have
>> >> currently not linked up the JIRA notifications to the correct list.
>> >> The original plan was to use issues@ as the mailing list. However we
>> seem
>> >> to have missed that change.
>> >>
>> >> If there are no reservations to using this I will ask INFRA to change
>> the
>> >> notification list to issues@ for the following events:
>> >> * Created
>> >> * Updated
>> >> * Assigned
>> >> * Resolved
>> >> * Closed
>> >> * Commented
>> >> * Comment Edited
>> >> That will bring us in line with most of the other projects.
>> >>
>> >> Second point for mailing lists: commits@ was originally slated for
>> GitHub
>> >> emails. The mailing list does not exist at the moment. Currently all
>> the
>> >> git emails come in on the dev@ mailing list which clutters that list.
>> >> Instead of creating commits@ I would like to propose to change the
>> name
>> >> to
>> >> reviews@ as it better covers what we do on GitHub with the PRs and the
>> >> review on the code.
>> >>
>> >> Please respond to this mail if you are not OK with the changes. If
>> there
>> >> are no objections I will start the changes on Monday 16 March 2020
>> (AEDT
>> >> +11).
>> >>
>> >> Thank you,
>> >> Wilfred
>> >>
>> >
>> >
>> > --
>> > *Weiwei Yang*
>> > Software Engineer, Cloudera
>> >
>> > Create your own WiseStamp email signature
>> > <
>> https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112
>> >
>> >
>>
>

Re: emails notification updates for JIRA and GitHub

[Sunil Govindan <su...@apache.org>]

Hi Weiwei and Wilfred,

I have not seen a reviews@ list so far. In other projects, I have seen
issues@ list where all updates on jira will go.
In any case, I agree in removing such notifications from dev@ list. And if
possible, also having an issues@ list as well

- Sunil

On Tue, Mar 10, 2020 at 10:04 AM Wilfred Spiegelenburg <wi...@apache.org>
wrote:

> Hi Weiwei,
>
> Currently all notifications for github go to dev@, that is a setting on
> the
> github repos that can be changed.
> I propose to move all of them to the reviews@ list and remove dev@ from
> the
> github notifications
> We should be using dev@ for mails that require discussions and votes not
> as
> a generic notification list I think.
>
> Wilfred
>
> On Tue, 10 Mar 2020 at 15:18, Weiwei Yang <ab...@gmail.com> wrote:
>
> > Hi Wilfred
> >
> > Thanks for taking care of this.
> > For the second one, since we already have GitBox notification about PRs,
> > creating reviews@ mailing list would get us too many duplicated
> messages?
> >
> > Weiwei
> >
> > On Mon, Mar 9, 2020 at 9:11 PM Wilfred Spiegelenburg <
> wilfreds@apache.org>
> > wrote:
> >
> >> Hi all,
> >>
> >> I noticed last week when moving all issues into the JIRA that there is
> no
> >> email send for JIRAs at all. I checked the project settings and we have
> >> currently not linked up the JIRA notifications to the correct list.
> >> The original plan was to use issues@ as the mailing list. However we
> seem
> >> to have missed that change.
> >>
> >> If there are no reservations to using this I will ask INFRA to change
> the
> >> notification list to issues@ for the following events:
> >> * Created
> >> * Updated
> >> * Assigned
> >> * Resolved
> >> * Closed
> >> * Commented
> >> * Comment Edited
> >> That will bring us in line with most of the other projects.
> >>
> >> Second point for mailing lists: commits@ was originally slated for
> GitHub
> >> emails. The mailing list does not exist at the moment. Currently all the
> >> git emails come in on the dev@ mailing list which clutters that list.
> >> Instead of creating commits@ I would like to propose to change the name
> >> to
> >> reviews@ as it better covers what we do on GitHub with the PRs and the
> >> review on the code.
> >>
> >> Please respond to this mail if you are not OK with the changes. If there
> >> are no objections I will start the changes on Monday 16 March 2020 (AEDT
> >> +11).
> >>
> >> Thank you,
> >> Wilfred
> >>
> >
> >
> > --
> > *Weiwei Yang*
> > Software Engineer, Cloudera
> >
> > Create your own WiseStamp email signature
> > <
> https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112
> >
> >
>

Re: emails notification updates for JIRA and GitHub

[Wilfred Spiegelenburg <wi...@apache.org>]

Hi Weiwei,

Currently all notifications for github go to dev@, that is a setting on the
github repos that can be changed.
I propose to move all of them to the reviews@ list and remove dev@ from the
github notifications
We should be using dev@ for mails that require discussions and votes not as
a generic notification list I think.

Wilfred

On Tue, 10 Mar 2020 at 15:18, Weiwei Yang <ab...@gmail.com> wrote:

> Hi Wilfred
>
> Thanks for taking care of this.
> For the second one, since we already have GitBox notification about PRs,
> creating reviews@ mailing list would get us too many duplicated messages?
>
> Weiwei
>
> On Mon, Mar 9, 2020 at 9:11 PM Wilfred Spiegelenburg <wi...@apache.org>
> wrote:
>
>> Hi all,
>>
>> I noticed last week when moving all issues into the JIRA that there is no
>> email send for JIRAs at all. I checked the project settings and we have
>> currently not linked up the JIRA notifications to the correct list.
>> The original plan was to use issues@ as the mailing list. However we seem
>> to have missed that change.
>>
>> If there are no reservations to using this I will ask INFRA to change the
>> notification list to issues@ for the following events:
>> * Created
>> * Updated
>> * Assigned
>> * Resolved
>> * Closed
>> * Commented
>> * Comment Edited
>> That will bring us in line with most of the other projects.
>>
>> Second point for mailing lists: commits@ was originally slated for GitHub
>> emails. The mailing list does not exist at the moment. Currently all the
>> git emails come in on the dev@ mailing list which clutters that list.
>> Instead of creating commits@ I would like to propose to change the name
>> to
>> reviews@ as it better covers what we do on GitHub with the PRs and the
>> review on the code.
>>
>> Please respond to this mail if you are not OK with the changes. If there
>> are no objections I will start the changes on Monday 16 March 2020 (AEDT
>> +11).
>>
>> Thank you,
>> Wilfred
>>
>
>
> --
> *Weiwei Yang*
> Software Engineer, Cloudera
>
> Create your own WiseStamp email signature
> <https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112>
>

Re: emails notification updates for JIRA and GitHub

[Weiwei Yang <ab...@gmail.com>]

Hi Wilfred

Thanks for taking care of this.
For the second one, since we already have GitBox notification about PRs,
creating reviews@ mailing list would get us too many duplicated messages?

Weiwei

On Mon, Mar 9, 2020 at 9:11 PM Wilfred Spiegelenburg <wi...@apache.org>
wrote:

> Hi all,
>
> I noticed last week when moving all issues into the JIRA that there is no
> email send for JIRAs at all. I checked the project settings and we have
> currently not linked up the JIRA notifications to the correct list.
> The original plan was to use issues@ as the mailing list. However we seem
> to have missed that change.
>
> If there are no reservations to using this I will ask INFRA to change the
> notification list to issues@ for the following events:
> * Created
> * Updated
> * Assigned
> * Resolved
> * Closed
> * Commented
> * Comment Edited
> That will bring us in line with most of the other projects.
>
> Second point for mailing lists: commits@ was originally slated for GitHub
> emails. The mailing list does not exist at the moment. Currently all the
> git emails come in on the dev@ mailing list which clutters that list.
> Instead of creating commits@ I would like to propose to change the name to
> reviews@ as it better covers what we do on GitHub with the PRs and the
> review on the code.
>
> Please respond to this mail if you are not OK with the changes. If there
> are no objections I will start the changes on Monday 16 March 2020 (AEDT
> +11).
>
> Thank you,
> Wilfred
>


-- 
*Weiwei Yang*
Software Engineer, Cloudera

Create your own WiseStamp email signature
<https://www.wisestamp.com/signature-in-email/?utm_source=promotion&utm_medium=signature&utm_campaign=create_your_own&srcid=6536956273754112>