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 <[email protected]> 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 <[email protected]> wrote: > > > +1. We do the same for Phoenix and it seems to work fine. > > > > On Friday, March 11, 2016, Michael Mior <[email protected]> wrote: > > > > > +1 from me FWIW as a new very minor contributor. > > > > > > -- > > > Michael Mior > > > [email protected] <javascript:;> > > > > > > 2016-03-11 15:56 GMT-05:00 Julian Hyde <[email protected] > > <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 > > > > > > > > > > > > > > > > > >
