+1 for less Spam 🎵 spam 🎵 spam 🎵 spam Seriously - considering the comments started by Kirk's email, given the amount of spam, it's not surprising that folks would use a different means of getting a speedier response (Slack) rather than using email. Point being that the lower the noise/signal ratio in our inboxes, the more likely we may be to have conversations there.
On Fri, Aug 24, 2018 at 8:12 AM Ernest Burghardt <eburgha...@pivotal.io> wrote: > +1 for lowering SPAM > > On Thu, Aug 23, 2018 at 9:19 PM, Jacob Barrett <jbarr...@pivotal.io> > wrote: > > > Must we get spammed with every thing that happens? It seems to me a log > in > > GitHub, JIRA and email is obscene. > > > > All this email we get now just gets bulk deleted and I often miss > > important conversations. If we move it all to another email group and > > nobody registers for it then what’s the point. I say let the GitHub and > > JIRA logs stay where they are and leave email for real conversations. > > > > -Jake > > > > > > > On Aug 23, 2018, at 8:15 PM, Anthony Baker <aba...@pivotal.io> wrote: > > > > > > AFAICT, PR comments are added to the JIRA worklog but only JIRA > comments > > are sent to issues@g.a.o <mailto:issues@g.a.o>. > > > > > >> On Aug 23, 2018, at 8:10 PM, Jacob Barrett <jbarr...@pivotal.io> > wrote: > > >> > > >> I am pretty sure all PRs are logged to JIRA and then emailed from > JIRA. > > >> > > >>> On Aug 23, 2018, at 8:06 PM, Anthony Baker <aba...@pivotal.io> > wrote: > > >>> > > >>> Hi all, > > >>> > > >>> I read a lot of PR emails from Geode, but I was noticing that those > > are not being archived on a public Geode mailing list. Is that correct? > > >>> > > >>> I suggest we create a notifications@g.a.o mailing list to make sure > > all discussion on PR’s is archived on an ASF mailing list. This pattern > > has been adopted by several other ASF projects, see [1][2] for example. > > >>> > > >>> Thoughts? I’m happy to followup with INFRA if y’all agree. > > >>> > > >>> Anthony > > >>> > > >>> [1] https://issues.apache.org/jira/browse/INFRA-16330 > > >>> [2] https://issues.apache.org/jira/browse/INFRA-14730 > > >>> > > > > > >
