+1 for using notification mailling list , it saves the time for us to
configure the mail filiter.

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Tue, Mar 10, 2020 at 4:30 PM Xiangdong Huang <[email protected]> wrote:
>
> Hi Chris,
>
> When I applied to change the notifications [1],  Chris Lambertus pointed
> out that we may need a new mailing list notifications@ to receives JIRA
> notification.
>
> I think it may help us to be out of stuck.
>
> If we have such a mailing list, then for those bug-fix issues, only
> developers need to focus on that.
> So, we recommend to let all current active developers subscribe to the
> mailing list.
>
> For new requirement discussions, new feature discussions and the roadmap
> discussions,
> even if they appear on the JIRA first, we can forward them manually to dev@
> mailing list, to attract more users that may be interested in.
>
> How about the proposal?
>
> [1] https://issues.apache.org/jira/browse/INFRA-19935
>
> -----------------------------------
> Xiangdong Huang
> School of Software, Tsinghua University
>
>  黄向东
> 清华大学 软件学院
>
>
> Christofer Dutz <[email protected]> 于2020年3月10日周二 下午3:41写道:
>
> > Hi Xiangdong,
> >
> > that's unfortunate, so I will probably continue to just skip jira emails.
> >
> > However if discussions keep being done in Jira, then I should probably
> > resign as a mentor as I am not willing to process these automated emails.
> >
> > If the project likes the status quo, that's absolutely fine. After all ...
> > all is happening on the list.
> >
> > It's just that I am signed up to about 50 lists at apache and have to
> > optimize how I process them if I don't want my contribution in the oss
> > world to be just being up to date with all that's happening and not having
> > any time left to contribute.
> >
> > So I just filter out all emails that require an increased time to read and
> > usually have a limited payload.
> > This usually relates totally escalating threads (posts coming in faster
> > than I can read them) and generally all Jira emails except the PLC4X ones.
> >
> >
> > Chris
> >
> >
> >
> >
> > Am 10.03.20, 03:23 schrieb "Xiangdong Huang" <[email protected]>:
> >
> >     Hi,
> >
> >     The wish to changing the Jira title template is rejected [1].
> >
> >     So, if we really want to change the template, we may have to:
> >      1. forward JIRA notifications to a single mailing list;
> >     2. A robot forwards the mails in the mailing list to dev@ and change
> > the
> >     email title.
> >
> >     [1] https://issues.apache.org/jira/browse/INFRA-19936
> >
> >     Best,
> >     -----------------------------------
> >     Xiangdong Huang
> >     School of Software, Tsinghua University
> >
> >      黄向东
> >     清华大学 软件学院
> >
> >
> >     Xin Wang <[email protected]> 于2020年3月7日周六 下午8:03写道:
> >
> >     > Nice, thanks Xiangdong for the great work.
> >     >
> >     > - Xin
> >     >
> >     > Xiangdong Huang <[email protected]> 于2020年3月7日周六 下午3:17写道:
> >     >
> >     > > Hi all,
> >     > >
> >     > > I created two tickets to INFRA to improve the experiences.
> >     > >
> >     > > [1] https://issues.apache.org/jira/browse/INFRA-19936
> >     > > [2] https://issues.apache.org/jira/browse/INFRA-19935
> >     > >
> >     > > Best,
> >     > > -----------------------------------
> >     > > Xiangdong Huang
> >     > > School of Software, Tsinghua University
> >     > >
> >     > >  黄向东
> >     > > 清华大学 软件学院
> >     > >
> >     > >
> >     > > Xiangdong Huang <[email protected]> 于2020年3月6日周五 下午9:35写道:
> >     > >
> >     > > > Hi all,
> >     > > >
> >     > > > I get two suggestions from this discussion thread:
> >     > > >
> >     > > > 1. To reduce the emails, only keep "created" and "commented"
> > event
> >     > > > notifications (According to [1], we have "closed" and "Generic
> > Event"
> >     > > event
> >     > > > notifications now).
> >     > > > 2. To make the title more readable, change the template of the
> > subject
> >     > of
> >     > > > the notification email, e.g., from "[JIRA][EVENT
> > TYPE](IOTDB-NUMBER)
> >     > > title"
> >     > > > to "title [JIRA][EVENT TYPE](IoTDB-NUMBER)". It is possible
> > according
> >     > to
> >     > > > [2].
> >     > > >
> >     > > > Both two changes require INFRA's help.
> >     > > > If there is no dissenting opinion, I can create an issue to
> > INFRA JIRA.
> >     > > >
> >     > > > If the INFRA can not change the title template, there is another
> >     > > solution:
> >     > > > a. JIRA sends notifications to a new mailing list; b. a robot
> >     > subscribes
> >     > > > the mailing list and once it receives a new mail, it sends it to
> > dev@
> >     > > > mailing list with a better title format.
> >     > > >
> >     > > > [1]
> >     > > >
> >     > >
> >     >
> > https://issues.apache.org/jira/plugins/servlet/project-config/IOTDB/notifications
> >     > > > [2]
> >     > > >
> >     > >
> >     >
> > https://community.atlassian.com/t5/Jira-questions/Configure-Email-Subject/qaq-p/617839
> >     > > >
> >     > > > Best,
> >     > > > -----------------------------------
> >     > > > Xiangdong Huang
> >     > > > School of Software, Tsinghua University
> >     > > >
> >     > > >  黄向东
> >     > > > 清华大学 软件学院
> >     > > >
> >     > > >
> >     > > > Christofer Dutz <[email protected]> 于2020年3月6日周五
> > 下午7:54写道:
> >     > > >
> >     > > >> Hi folks,
> >     > > >>
> >     > > >> here maybe an example how one of the Jira emails looks like for
> > me in
> >     > my
> >     > > >> inbox:
> >     > > >> https://ibb.co/WPJ5V9j
> >     > > >>
> >     > > >> As you can see, from the title there is almost no information I
> > can
> >     > get.
> >     > > >> So I can't see if I'm interested in reading the content or not.
> >     > > >>
> >     > > >> Usually my process is to simply delete all Jira emails as I am
> > not
> >     > > >> willing
> >     > > >> to klick on every email in order to find out what they are
> > about.
> >     > > >>
> >     > > >> It would be great if we could reduce the title of the jira
> > emails
> >     > > >> drastically ...
> >     > > >> perhaps even change the order of stuff so I could see more of
> > the
> >     > title
> >     > > >> text,
> >     > > >> then perhaps it would make working with these emails better.
> >     > > >>
> >     > > >> Chris
> >     > > >>
> >     > > >>
> >     > > >> Am 06.03.20, 08:42 schrieb "伍 雄" <[email protected]>:
> >     > > >>
> >     > > >>     +1
> >     > > >>
> >     > > >>     > 2020年3月6日 15:28,Julian Feinauer <
> > [email protected]>
> >     > > 写道:
> >     > > >>     >
> >     > > >>     > +1 from me also!
> >     > > >>     >
> >     > > >>     > Am 06.03.20, 04:32 schrieb "Dawei Liu" <[email protected]>:
> >     > > >>     >
> >     > > >>     >    Hi,
> >     > > >>     >
> >     > > >>     >    +1 for only forwarding Jira creation and comment
> >     > > >>     >
> >     > > >>     >    I think this is a good thing because chair noticed our
> > work.
> >     > > >>     >
> >     > > >>     >    Maybe we should put more discussion into email and
> > gradually
> >     > > >> reduce the distress caused by automatic generation
> >     > > >>     >
> >     > > >>     >
> >     > > >>     >    Thanks
> >     > > >>     >    ---
> >     > > >>     >    Dawei Liu
> >     > > >>     >
> >     > > >>     >
> >     > > >>     >
> >     > > >>     >> 2020年3月6日 上午10:53,Xin Wang <[email protected]> 写道:
> >     > > >>     >>
> >     > > >>     >> It's a real problem. +1 for only forwarding Jira
> > creation and
> >     > > >> comment.
> >     > > >>     >>
> >     > > >>     >> - Xin
> >     > > >>     >>
> >     > > >>     >> Jialin Qiao <[email protected]> 于2020年3月6日周五
> >     > 上午9:12写道:
> >     > > >>     >>
> >     > > >>     >>> Hi,
> >     > > >>     >>>
> >     > > >>     >>> +1 for only forwarding Jira creation and comment.
> >     > > >>     >>>
> >     > > >>     >>> Stopping forwarding operations like closing issue,
> > linking PR,
> >     > > >> assigning
> >     > > >>     >>> issue...
> >     > > >>     >>>
> >     > > >>     >>> Could we simplify the issue report format?
> >     > > >>     >>>
> >     > > >>     >>> Like this:
> >     > > >>     >>>
> >     > > >>     >>> @++++++++++<<<<<<<<<<<<
> >     > > >>     >>> [
> >     > > >>     >>>
> >     > > >>
> >     > >
> >     >
> > https://issues.apache.org/jira/browse/IOTDB-498?focusedWorklogId=397173&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-397173
> >     > > >>     >>> ]
> >     > > >>     >>>
> >     > > >>     >>> ASF GitHub Bot 在 IOTDB-498中添加了工作日志:
> >     > > >>     >>> ----------------------------------------
> >     > > >>     >>>
> >     > > >>     >>> 作者: ASF GitHub Bot
> >     > > >>     >>> 创建于: 04/三月/20 01:45
> >     > > >>     >>> 开始日期: 04/三月/20 01:45
> >     > > >>     >>> 耗费时间: 10分
> >     > > >>     >>> 工作说明: qiaojialin commented on pull request #878:
> > [IOTDB-498]
> >     > > >> Support date
> >     > > >>     >>> format "2020-02-10"
> >     > > >>     >>> URL: https://github.com/apache/incubator-iotdb/pull/878
> >     > > >>     >>>
> >     > > >>     >>>
> >     > ----------------------------------------------------------------
> >     > > >>     >>> This is an automated message from the Apache Git
> > Service.
> >     > > >>     >>> To respond to the message, please log on to GitHub and
> > use the
> >     > > >>     >>> URL above to go to the specific comment.
> >     > > >>     >>>
> >     > > >>     >>> For queries about this service, please contact
> > Infrastructure
> >     > > at:
> >     > > >>     >>> [email protected]
> >     > > >>     >>> @++++++++++<<<<<<<<<<<<
> >     > > >>     >>>
> >     > > >>     >>> The only useful information is only two lines:
> >     > > >>     >>>
> >     > > >>     >>> @++++++++++<<<<<<<<<<<<
> >     > > >>     >>> 工作说明: qiaojialin commented on pull request #878:
> > [IOTDB-498]
> >     > > >> Support date
> >     > > >>     >>> format "2020-02-10"
> >     > > >>     >>> URL: https://github.com/apache/incubator-iotdb/pull/878
> >     > > >>     >>> @++++++++++<<<<<<<<<<<<
> >     > > >>     >>>
> >     > > >>     >>>
> >     > > >>     >>> Thanks,
> >     > > >>     >>> --
> >     > > >>     >>> Jialin Qiao
> >     > > >>     >>> School of Software, Tsinghua University
> >     > > >>     >>>
> >     > > >>     >>> 乔嘉林
> >     > > >>     >>> 清华大学 软件学院
> >     > > >>     >>>
> >     > > >>     >>>> -----原始邮件-----
> >     > > >>     >>>> 发件人: "Xiangdong Huang" <[email protected]>
> >     > > >>     >>>> 发送时间: 2020-03-06 08:46:02 (星期五)
> >     > > >>     >>>> 收件人: [email protected]
> >     > > >>     >>>> 抄送:
> >     > > >>     >>>> 主题: Balance the mailing list and JIRA notification
> >     > > >>     >>>>
> >     > > >>     >>>> Hi all,
> >     > > >>     >>>>
> >     > > >>     >>>> In [1], Chirs pointed out that "most email traffic
> > generated
> >     > by
> >     > > >> jira
> >     > > >>     >>> (hard
> >     > > >>     >>>> to follow especially when trying to keep up to date
> > while
> >     > > >> commuting)".
> >     > > >>     >>>>
> >     > > >>     >>>> How do you think? IMO, I think discussions on JIRA can
> > be
> >     > > >> forwarded
> >     > > >>     >>>> directly to the mailing list, which is convenient. But
> > indeed
> >     > > >> sometimes
> >     > > >>     >>> we
> >     > > >>     >>>> have too many JIRA notifications.
> >     > > >>     >>>>
> >     > > >>     >>>> Should we stop some JIRA notifications like "closed
> > event" of
> >     > > >> ISSUE to
> >     > > >>     >>>> reduce the notifications?
> >     > > >>     >>>>
> >     > > >>     >>>> [1]
> >     > > >> https://cwiki.apache.org/confluence/display/INCUBATOR/March2020
> >     > > >>     >>>>
> >     > > >>     >>>> Best,
> >     > > >>     >>>> -----------------------------------
> >     > > >>     >>>> Xiangdong Huang
> >     > > >>     >>>> School of Software, Tsinghua University
> >     > > >>     >>>>
> >     > > >>     >>>> 黄向东
> >     > > >>     >>>> 清华大学 软件学院
> >     > > >>     >>>
> >     > > >>     >>
> >     > > >>     >>
> >     > > >>     >> --
> >     > > >>     >> Thanks,
> >     > > >>     >> Xin
> >     > > >>     >
> >     > > >>     >
> >     > > >>     >
> >     > > >>
> >     > > >>
> >     > > >>
> >     > > >>
> >     > >
> >     >
> >     >
> >     > --
> >     > Thanks,
> >     > Xin
> >     >
> >
> >
> >

Reply via email to