Yes lets have a separate firehouse/commit/whatever mailing list that if people
really want all of that data they can see it all. That way it is archived in
ASF infra. I do see value in having JIRA and GITHUB linked, I'm not sure if
there is a better way to link the two right now though. If someone does have
experience with this type of thing and can make a better solution I think we
can talk to INFRA about adopting/supporting those changes. - Bobby
On Thursday, August 11, 2016 8:41 AM, Aditya Desai <adity...@usc.edu> wrote:
Please reduce the number of emails. I am getting many many emails in recent
days and spam my inbox.
On Thu, Aug 11, 2016 at 2:41 AM, Erik Weathers <
eweath...@groupon.com.invalid> wrote:
> I will state again (as I've done on prior email threads) that I find no
> value in spamming the JIRA issues like this, and that I strongly believe
> that this behavior is in fact detrimental since it obscures the actual
> comments on the issue itself. The proposed solution of just moving the
> destination of the JIRA emails to a different list than
> dev@storm.apache.org
> doesn't solve that root problem.
>
> I want to be able to read a JIRA issue without having to skim over dozens
> and dozens of auto-appended code review messages. I truly cannot
> understand why this isn't an annoyance for others. I could be really
> snarky and reformat this email to have a bunch of random stuff in between
> every sentence to make my point, but I hope this sentence suffices to prove
> it?
>
> Though I must acknowledge your point Jungtaek that there is some Apache
> policy that all code review comments need to be archived into some apache
> system. Maybe we can use the attachment functionality of JIRA instead of
> making these separate comments on the JIRA issue? I'm not sure how the
> integration is set up right now, that seems feasible.
>
> - Erik
>
> On Thu, Aug 11, 2016 at 2:08 AM, Matthias J. Sax <mj...@apache.org> wrote:
>
> > I like the idea of have one more mailing list to reduce load on dev-list.
> >
> > -Matthias
> >
> > On 08/11/2016 11:07 AM, Jungtaek Lim wrote:
> > > I remember that Taylor stated that all github comments should be copied
> > to
> > > somewhere Apache infra, and it's Apache JIRA for us.
> > >
> > > It seems to make sense but I'm curious other projects respect this
> rule.
> > I
> > > also subscribed dev list of Kafka, Zeppelin, Flink, HBase, Spark
> > (although
> > > I barely see them) but no project is sending mail per each comment.
> Some
> > of
> > > them copy github comments to JIRA issue but no notification, and others
> > > doesn't even copy comments to JIRA issue.
> > > (You can check this with dev mailing list archive, too.)
> > >
> > > I'm in favor of reducing simple notification mails. Personally I saw
> most
> > > of Storm dev. mails so I'm fine to keep mailing as it is (with some
> > > annoying 'empty' notification), but it can also be done with watching
> > > Github project.
> > >
> > > This is not raised for the first time, and I would like to discuss
> > > seriously and see the changes.
> > >
> > > Thanks,
> > > Jungtaek Lim (HeartSaVioR)
> > >
> > > 2016년 8월 11일 (목) 오후 2:22, Kyle Nusbaum <knusb...@yahoo-inc.com.invali
> > d>님이
> > > 작성:
> > >
> > >> There seems to be a surplus of automatically-generated emails on the
> dev
> > >> mailing list.
> > >> Github and Apache's Jira constantly send mails to the dev list.
> > >>
> > >> I'm not sure that anyone finds these useful. Even if they do, I wonder
> > if
> > >> its better to move them to a separate list. It's possible that
> everyone
> > has
> > >> email filters employed to sort this out, but if every subscriber has
> the
> > >> same filters employed, it might indicate the need for a separate list.
> > --
> > >> Kyle
> > >
> >
> >
>
--
Aditya Ramachandra Desai
MS Computer Science Graduate Student
USC Viterbi School of Engineering
Los Angeles, CA 90007
M : +1-415-463-9864 | L : https://www.linkedin.com/in/adityardesai
