No, and that's sort of the issue at hand here. I've requested these mailing list changes because the dev@ traffic is typically github or JIRA chatter. We have no on list discussions. I'm basically trying to force you guys to actually talk to one another via email, since our other attempts have not worked out well.
I would expect that Slack discussions are summarized here by those participating in them. Not automatically. John On Tue, May 9, 2017 at 10:00 PM Arthur Berezin <art...@gigaspaces.com> wrote: > I missed the Slack chat, but sounds good +1. Is there an easy way to get a > digest of the slack chat over dev mailing list? > > On Tue, May 9, 2017, 21:43 John D. Ament <johndam...@apache.org> wrote: > > > All, > > > > Based on a brief chat on Slack, I'm going to go ahead and create two new > > mailing lists: > > > > - commits@ > > - issues@ > > > > The reason being, the dev list is designed for developer discussions, but > > most of the banter is on JIRA issues or GitHub PRs/commits. To > effectively > > measure the community openness we need to separate the types. > > > > All changes in a JIRA issue will be sent to issues@ and all commits will > > go > > to commits@. > > > > John > > >
