Thanks for everyone who has spoken out. I have filed https://issues.apache.org/jira/browse/INFRA-14336
to Apache INFRA. Guozhang On Fri, Jun 9, 2017 at 3:07 PM, Matthias J. Sax <matth...@confluent.io> wrote: > +1 > > On 6/9/17 3:01 PM, Bill Bejeck wrote: > > +1 > > > > Thanks, > > Bill > > > > On Fri, Jun 9, 2017 at 4:56 PM, Gwen Shapira <g...@confluent.io> wrote: > > > >> +1, thank you > >> > >> On Fri, Jun 9, 2017 at 1:37 PM Jeff Widman <j...@netskope.com> wrote: > >> > >>> +1 > >>> > >>> Thanks for driving this > >>> > >>> On Jun 9, 2017 1:22 PM, "Guozhang Wang" <wangg...@gmail.com> wrote: > >>> > >>>> I have just confirmed with Jun that de cannot change the notification > >>> edits > >>>> himself as well. So I'll talk to Apache Infra anyways in order to make > >>> that > >>>> change. > >>>> > >>>> So I'd update my proposal to: > >>>> > >>>> 1. create an "iss...@kafka.apache.org" which will receive all the > JIRA > >>>> events. > >>>> 2. remove "dev@kafka.apache.org" from all the JIRA event > notifications > >>>> except "Issue Created", "Issue Resolved" and "Issue Reopened". > >>>> > >>>> > >>>> Everyone's feedback are more than welcome! I will wait for a few days > >> and > >>>> if there is an agreement create a ticket to Apache JIRA. > >>>> > >>>> Guozhang > >>>> > >>>> > >>>> On Wed, Jun 7, 2017 at 2:43 PM, Guozhang Wang <wangg...@gmail.com> > >>> wrote: > >>>> > >>>>> Yeah I have thought about that but that would involve Apache Infra. > >> The > >>>>> current proposal is based on the assumption that removing the > >>>> notification > >>>>> can be done by ourselves. > >>>>> > >>>>> > >>>>> Guozhang > >>>>> > >>>>> On Wed, Jun 7, 2017 at 1:24 PM, Matthias J. Sax < > >> matth...@confluent.io > >>>> > >>>>> wrote: > >>>>> > >>>>>> Have you considered starting a new mailing list "issues@" that gets > >>> the > >>>>>> full load of all emails? > >>>>>> > >>>>>> -Matthias > >>>>>> > >>>>>> On 6/6/17 7:26 PM, Jeff Widman wrote: > >>>>>>> What about also adding "Issue Resolved" to the events that hit > >> dev? > >>>>>>> > >>>>>>> While I don't generally care about updates on issue progress, I do > >>>> want > >>>>>> to > >>>>>>> know when issues are resolved in case undocumented behavior that I > >>> may > >>>>>> have > >>>>>>> accidentally been relying on may have changed. > >>>>>>> > >>>>>>> With or without this suggested tweak, I am +1 (non-binding) on > >> this. > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> > >>>>>>> On Tue, Jun 6, 2017 at 3:49 PM, Guozhang Wang <wangg...@gmail.com > >>> > >>>>>> wrote: > >>>>>>> > >>>>>>>> (Changing the subject title to reflect on the proposal) > >>>>>>>> > >>>>>>>> Hey guys, > >>>>>>>> > >>>>>>>> In order to not drop the ball on the floor I'd like to kick off > >>> some > >>>>>>>> proposals according to people's feedbacks on this issue. Feel > >> free > >>> to > >>>>>>>> brainstorm on different ideas: > >>>>>>>> > >>>>>>>> We change JIRA notifications to remove `Single Email Address ( > >>>>>>>> dev@kafka.apache.org)` for all events EXCEPT "Issue Created" (5 > >> - > >>> 8 > >>>>>>>> events per day). Currently `dev@kafka.apache.org` is notified on > >>> all > >>>>>>>> events (~180 events per day). > >>>>>>>> > >>>>>>>> > >>>>>>>> Though as a PMC member I can view these notification schemes on > >> the > >>>>>> JIRA > >>>>>>>> admin page, I cannot edit on them. Maybe Jun can check if he has > >>> the > >>>>>>>> privilege to do so after we have agreed on some proposal; > >> otherwise > >>>> we > >>>>>> need > >>>>>>>> to talk to Apache INFRA for it. > >>>>>>>> > >>>>>>>> > >>>>>>>> Guozhang > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> On Tue, May 30, 2017 at 11:57 PM, Michal Borowiecki < > >>>>>>>> michal.borowie...@openbet.com> wrote: > >>>>>>>> > >>>>>>>>> +1 agree with Jeff, > >>>>>>>>> > >>>>>>>>> Michał > >>>>>>>>> > >>>>>>>>> On 31/05/17 06:25, Jeff Widman wrote: > >>>>>>>>> > >>>>>>>>> I'm hugely in favor of this change as well... > >>>>>>>>> > >>>>>>>>> Although I actually find the Github pull request emails less > >>> useful > >>>>>> than > >>>>>>>>> the jirabot ones since Jira typically has more info when I'm > >>> trying > >>>> to > >>>>>>>>> figure out if the issue is relevant to me or not... > >>>>>>>>> > >>>>>>>>> On Tue, May 30, 2017 at 2:28 PM, Guozhang Wang < > >>> wangg...@gmail.com> > >>>> < > >>>>>> wangg...@gmail.com> wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> I actually do not know.. Maybe Jun knows better than me? > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Guozhang > >>>>>>>>> > >>>>>>>>> On Mon, May 29, 2017 at 12:58 PM, Gwen Shapira < > >> g...@confluent.io > >>>> > >>>> < > >>>>>> g...@confluent.io> wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> I agree. > >>>>>>>>> > >>>>>>>>> Guozhang, do you know how to implement the suggestion? JIRA to > >>>> Apache > >>>>>>>>> Infra? Or is this something we can do ourselves somehow? > >>>>>>>>> > >>>>>>>>> On Mon, May 29, 2017 at 9:33 PM Guozhang Wang < > >> wangg...@gmail.com > >>>> > >>>> < > >>>>>> wangg...@gmail.com> > >>>>>>>>> > >>>>>>>>> wrote: > >>>>>>>>> > >>>>>>>>> I share your pains. Right now I use filters on my email accounts > >>> and > >>>>>> it > >>>>>>>>> > >>>>>>>>> has > >>>>>>>>> > >>>>>>>>> been down to about 25 per day. > >>>>>>>>> > >>>>>>>>> I think setup a separate mailing list for jirabot and jenkins > >> auto > >>>>>>>>> generated emails is a good idea. > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Guozhang > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> On Mon, May 29, 2017 at 12:58 AM, <marc.schle...@sdv-it.de> < > >>>>>> marc.schle...@sdv-it.de> wrote: > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> Hello everyone > >>>>>>>>> > >>>>>>>>> I find it hard to follow this mailinglist due to all the mails > >>>>>>>>> > >>>>>>>>> generated > >>>>>>>>> > >>>>>>>>> by Jira. Just over this weekend there are 240 new mails. > >>>>>>>>> Would it be possible to setup something like > >>> j...@kafka.apache.org > >>>>>>>>> > >>>>>>>>> where > >>>>>>>>> > >>>>>>>>> everyone can subscribe interested in those Jira mails? > >>>>>>>>> > >>>>>>>>> Right now I am going to setup a filter which just deletes the > >>>>>>>>> > >>>>>>>>> jira-tagged > >>>>>>>>> > >>>>>>>>> mails, but I think the current setup also makes it hard to read > >>>>>>>>> > >>>>>>>>> through > >>>>>>>>> > >>>>>>>>> the archives. > >>>>>>>>> > >>>>>>>>> regards > >>>>>>>>> Marc > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> -- Guozhang > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> -- Guozhang > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> -- > >>>>>>>>> <http://www.openbet.com/> Michal Borowiecki > >>>>>>>>> Senior Software Engineer L4 > >>>>>>>>> T: +44 208 742 1600 <+44%2020%208742%201600> > >>> <+44%2020%208742%201600> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> +44 203 249 8448 <+44%2020%203249%208448> > >>> <+44%2020%203249%208448> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> > >>>>>>>>> E: michal.borowie...@openbet.com > >>>>>>>>> W: www.openbet.com > >>>>>>>>> OpenBet Ltd > >>>>>>>>> > >>>>>>>>> Chiswick Park Building 9 > >>>>>>>>> > >>>>>>>>> 566 Chiswick High Rd > >>>>>>>>> > >>>>>>>>> London > >>>>>>>>> > >>>>>>>>> W4 5XT > >>>>>>>>> > >>>>>>>>> UK > >>>>>>>>> <https://www.openbet.com/email_promo> > >>>>>>>>> This message is confidential and intended only for the > >> addressee. > >>> If > >>>>>> you > >>>>>>>>> have received this message in error, please immediately notify > >> the > >>>>>>>>> postmas...@openbet.com and delete it from your system as well > >> as > >>>> any > >>>>>>>>> copies. The content of e-mails as well as traffic data may be > >>>>>> monitored by > >>>>>>>>> OpenBet for employment and security purposes. To protect the > >>>>>> environment > >>>>>>>>> please do not print this e-mail unless necessary. OpenBet Ltd. > >>>>>> Registered > >>>>>>>>> Office: Chiswick Park Building 9, 566 Chiswick High Road, > >> London, > >>> W4 > >>>>>> 5XT, > >>>>>>>>> United Kingdom. A company registered in England and Wales. > >>>> Registered > >>>>>> no. > >>>>>>>>> 3134634. VAT no. GB927523612 > >>>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> > >>>>>>>> -- > >>>>>>>> -- Guozhang > >>>>>>>> > >>>>>>> > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> -- Guozhang > >>>>> > >>>> > >>>> > >>>> > >>>> -- > >>>> -- Guozhang > >>>> > >>> > >> > > > > -- -- Guozhang
