You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by Julian Hyde <jh...@apache.org> on 2016/03/11 21:56:54 UTC
[DISCUSS] Email notifications for JIRA cases
I’d like to discuss the channels we use for notifying changes to JIRA cases. Currently[1], you will receive a notification for just about every change to a JIRA if you subscribe to issues@ (but only 18 people do)[2]. You will also receive a notification if you are the reporter or assignee.
I propose that when a JIRA is created, we send an email to both dev@ and issues@. This will be an extra 40 emails per month on the dev list. I am really cautious about increasing the number of messages on the dev list, because I think high-volume lists discourage part-time contributors, but I think this change is worthwhile. It will make people aware of conversations that are happening and if it helps to channel conversations onto JIRA cases it could possibly even REDUCE the volume on the dev list.
Julian
[1] https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications <https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications>
[2] Email stats:
* issues: 18 subscribers, 300 emails per month
* commits: 18 subscribers, 140 emails per month
* dev: 173 subscribers, 150 emails per month
Re: [DISCUSS] Email notifications for JIRA cases
Posted by Julian Hyde <jh...@apache.org>.
Since we’re in agreement, I’ve changed the policy, and you should start seeing an email each time an issue is created. If a particular issue is of interest, add yourself to its ‘watchers’ list, otherwise you won’t hear any more about it.
I hope we never become a “popular project” if the measure of such a project is a crushing volume of emails. Let’s do what we can do keep the traffic on the dev list reasonable. If anyone has any further ideas how to achieve that, let’s discuss.
Julian
Re: [DISCUSS] Email notifications for JIRA cases
Posted by Rajat Venkatesh <rv...@qubole.com>.
Support Jesse Yates view. I find the JIRA volume too high on popular
projects. I like to focus on discussions and forcing me to add a filter is
an irritation. Though I'll do it if I have to. For JIRAs I care about, I'll
watch them. Also I am happy to search for JIRAs before starting a
discussion.
On Sat, 12 Mar 2016 at 10:02, Jesse Yates <je...@gmail.com> wrote:
> +0 in Phoenix and HBase land I setup filters so any issue gets archived if
> it's not directed at me. Tends to clutter my inbox with things I don't care
> about, esp as a part-time contributor. If this (or another project) isn't
> your full time job, then it's hard to care when you have 10s-100s of other
> emails to triage.
>
> This only gets worse as the project gets more active. If people setup
> filters, which is likely as the project gets more active, then you are back
> in the same boat.
>
> We already have a place to go if people want to see all the issues. And
> then you can see jira of you want to look at velocity and changes.
>
> To me dev list is for general discussion, with jira being the action items
> from that discussion (of any). If there is a big concern in a jira and its
> not getting attention, then @dev is a good place to raise that concern.
>
> There will always be ppl who want to look at all the changes in jira, so as
> long as they have a reasonable way to do that, it seems OK.
>
> Either way, it won't bother me too much - there is a work around.
>
> Just my $0.02
>
> On Fri, Mar 11, 2016, 6:59 PM James Taylor <ja...@apache.org> wrote:
>
> > +1. We do the same for Phoenix and it seems to work fine.
> >
> > On Friday, March 11, 2016, Michael Mior <mm...@uwaterloo.ca> wrote:
> >
> > > +1 from me FWIW as a new very minor contributor.
> > >
> > > --
> > > Michael Mior
> > > mmior@uwaterloo.ca <javascript:;>
> > >
> > > 2016-03-11 15:56 GMT-05:00 Julian Hyde <jhyde@apache.org
> > <javascript:;>>:
> > >
> > > > I’d like to discuss the channels we use for notifying changes to JIRA
> > > > cases. Currently[1], you will receive a notification for just about
> > every
> > > > change to a JIRA if you subscribe to issues@ (but only 18 people
> > do)[2].
> > > > You will also receive a notification if you are the reporter or
> > assignee.
> > > >
> > > > I propose that when a JIRA is created, we send an email to both dev@
> > and
> > > > issues@. This will be an extra 40 emails per month on the dev list.
> I
> > am
> > > > really cautious about increasing the number of messages on the dev
> > list,
> > > > because I think high-volume lists discourage part-time contributors,
> > but
> > > I
> > > > think this change is worthwhile. It will make people aware of
> > > conversations
> > > > that are happening and if it helps to channel conversations onto JIRA
> > > cases
> > > > it could possibly even REDUCE the volume on the dev list.
> > > >
> > > > Julian
> > > >
> > > > [1]
> > > >
> > >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> > > > <
> > > >
> > >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> > > > >
> > > >
> > > > [2] Email stats:
> > > > * issues: 18 subscribers, 300 emails per month
> > > > * commits: 18 subscribers, 140 emails per month
> > > > * dev: 173 subscribers, 150 emails per month
> > > >
> > > >
> > > >
> > >
> >
>
Re: [DISCUSS] Email notifications for JIRA cases
Posted by Jesse Yates <je...@gmail.com>.
+0 in Phoenix and HBase land I setup filters so any issue gets archived if
it's not directed at me. Tends to clutter my inbox with things I don't care
about, esp as a part-time contributor. If this (or another project) isn't
your full time job, then it's hard to care when you have 10s-100s of other
emails to triage.
This only gets worse as the project gets more active. If people setup
filters, which is likely as the project gets more active, then you are back
in the same boat.
We already have a place to go if people want to see all the issues. And
then you can see jira of you want to look at velocity and changes.
To me dev list is for general discussion, with jira being the action items
from that discussion (of any). If there is a big concern in a jira and its
not getting attention, then @dev is a good place to raise that concern.
There will always be ppl who want to look at all the changes in jira, so as
long as they have a reasonable way to do that, it seems OK.
Either way, it won't bother me too much - there is a work around.
Just my $0.02
On Fri, Mar 11, 2016, 6:59 PM James Taylor <ja...@apache.org> wrote:
> +1. We do the same for Phoenix and it seems to work fine.
>
> On Friday, March 11, 2016, Michael Mior <mm...@uwaterloo.ca> wrote:
>
> > +1 from me FWIW as a new very minor contributor.
> >
> > --
> > Michael Mior
> > mmior@uwaterloo.ca <javascript:;>
> >
> > 2016-03-11 15:56 GMT-05:00 Julian Hyde <jhyde@apache.org
> <javascript:;>>:
> >
> > > I’d like to discuss the channels we use for notifying changes to JIRA
> > > cases. Currently[1], you will receive a notification for just about
> every
> > > change to a JIRA if you subscribe to issues@ (but only 18 people
> do)[2].
> > > You will also receive a notification if you are the reporter or
> assignee.
> > >
> > > I propose that when a JIRA is created, we send an email to both dev@
> and
> > > issues@. This will be an extra 40 emails per month on the dev list. I
> am
> > > really cautious about increasing the number of messages on the dev
> list,
> > > because I think high-volume lists discourage part-time contributors,
> but
> > I
> > > think this change is worthwhile. It will make people aware of
> > conversations
> > > that are happening and if it helps to channel conversations onto JIRA
> > cases
> > > it could possibly even REDUCE the volume on the dev list.
> > >
> > > Julian
> > >
> > > [1]
> > >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> > > <
> > >
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> > > >
> > >
> > > [2] Email stats:
> > > * issues: 18 subscribers, 300 emails per month
> > > * commits: 18 subscribers, 140 emails per month
> > > * dev: 173 subscribers, 150 emails per month
> > >
> > >
> > >
> >
>
Re: [DISCUSS] Email notifications for JIRA cases
Posted by James Taylor <ja...@apache.org>.
+1. We do the same for Phoenix and it seems to work fine.
On Friday, March 11, 2016, Michael Mior <mm...@uwaterloo.ca> wrote:
> +1 from me FWIW as a new very minor contributor.
>
> --
> Michael Mior
> mmior@uwaterloo.ca <javascript:;>
>
> 2016-03-11 15:56 GMT-05:00 Julian Hyde <jhyde@apache.org <javascript:;>>:
>
> > I’d like to discuss the channels we use for notifying changes to JIRA
> > cases. Currently[1], you will receive a notification for just about every
> > change to a JIRA if you subscribe to issues@ (but only 18 people do)[2].
> > You will also receive a notification if you are the reporter or assignee.
> >
> > I propose that when a JIRA is created, we send an email to both dev@ and
> > issues@. This will be an extra 40 emails per month on the dev list. I am
> > really cautious about increasing the number of messages on the dev list,
> > because I think high-volume lists discourage part-time contributors, but
> I
> > think this change is worthwhile. It will make people aware of
> conversations
> > that are happening and if it helps to channel conversations onto JIRA
> cases
> > it could possibly even REDUCE the volume on the dev list.
> >
> > Julian
> >
> > [1]
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> > <
> >
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> > >
> >
> > [2] Email stats:
> > * issues: 18 subscribers, 300 emails per month
> > * commits: 18 subscribers, 140 emails per month
> > * dev: 173 subscribers, 150 emails per month
> >
> >
> >
>
Re: [DISCUSS] Email notifications for JIRA cases
Posted by Michael Mior <mm...@uwaterloo.ca>.
+1 from me FWIW as a new very minor contributor.
--
Michael Mior
mmior@uwaterloo.ca
2016-03-11 15:56 GMT-05:00 Julian Hyde <jh...@apache.org>:
> I’d like to discuss the channels we use for notifying changes to JIRA
> cases. Currently[1], you will receive a notification for just about every
> change to a JIRA if you subscribe to issues@ (but only 18 people do)[2].
> You will also receive a notification if you are the reporter or assignee.
>
> I propose that when a JIRA is created, we send an email to both dev@ and
> issues@. This will be an extra 40 emails per month on the dev list. I am
> really cautious about increasing the number of messages on the dev list,
> because I think high-volume lists discourage part-time contributors, but I
> think this change is worthwhile. It will make people aware of conversations
> that are happening and if it helps to channel conversations onto JIRA cases
> it could possibly even REDUCE the volume on the dev list.
>
> Julian
>
> [1]
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> <
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> >
>
> [2] Email stats:
> * issues: 18 subscribers, 300 emails per month
> * commits: 18 subscribers, 140 emails per month
> * dev: 173 subscribers, 150 emails per month
>
>
>
Re: [DISCUSS] Email notifications for JIRA cases
Posted by Josh Elser <jo...@gmail.com>.
+1 I'm a fan of the issue creation hitting dev@. Makes me not feel so
bad if I ignore issues@ for a while.
Julian Hyde wrote:
> I’d like to discuss the channels we use for notifying changes to JIRA cases. Currently[1], you will receive a notification for just about every change to a JIRA if you subscribe to issues@ (but only 18 people do)[2]. You will also receive a notification if you are the reporter or assignee.
>
> I propose that when a JIRA is created, we send an email to both dev@ and issues@. This will be an extra 40 emails per month on the dev list. I am really cautious about increasing the number of messages on the dev list, because I think high-volume lists discourage part-time contributors, but I think this change is worthwhile. It will make people aware of conversations that are happening and if it helps to channel conversations onto JIRA cases it could possibly even REDUCE the volume on the dev list.
>
> Julian
>
> [1] https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications<https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications>
>
> [2] Email stats:
> * issues: 18 subscribers, 300 emails per month
> * commits: 18 subscribers, 140 emails per month
> * dev: 173 subscribers, 150 emails per month
>
>
>
Re: [DISCUSS] Email notifications for JIRA cases
Posted by Dan <da...@dankeeley.co.uk>.
+1
In my experience reading jira and tracking it is the single most effective
way to keep up to speed on a project.
It also highlights the ways people use the product.. often in ways
developers didn't envisage and that's where the fun comes in.
Dan
Sent from my phone
On 11 Mar 2016 20:56, "Julian Hyde" <jh...@apache.org> wrote:
> I’d like to discuss the channels we use for notifying changes to JIRA
> cases. Currently[1], you will receive a notification for just about every
> change to a JIRA if you subscribe to issues@ (but only 18 people do)[2].
> You will also receive a notification if you are the reporter or assignee.
>
> I propose that when a JIRA is created, we send an email to both dev@ and
> issues@. This will be an extra 40 emails per month on the dev list. I am
> really cautious about increasing the number of messages on the dev list,
> because I think high-volume lists discourage part-time contributors, but I
> think this change is worthwhile. It will make people aware of conversations
> that are happening and if it helps to channel conversations onto JIRA cases
> it could possibly even REDUCE the volume on the dev list.
>
> Julian
>
> [1]
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> <
> https://issues.apache.org/jira/plugins/servlet/project-config/CALCITE/notifications
> >
>
> [2] Email stats:
> * issues: 18 subscribers, 300 emails per month
> * commits: 18 subscribers, 140 emails per month
> * dev: 173 subscribers, 150 emails per month
>
>
>